This bug was fixed in the package linux-raspi2 - 5.3.0-1017.19
---
linux-raspi2 (5.3.0-1017.19) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker (LP: #1859692)
[ Ubuntu: 5.3.0-28.30 ]
* eoan/linux: 5.3.0-28.30 -proposed tracker (LP: #1859694)
* CVE-2
This bug was fixed in the package linux-raspi2 - 5.3.0-1017.19
---
linux-raspi2 (5.3.0-1017.19) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker (LP: #1859692)
[ Ubuntu: 5.3.0-28.30 ]
* eoan/linux: 5.3.0-28.30 -proposed tracker (LP: #1859694)
* CVE-2
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855990
Title:
linux-raspi2: dmesg prints calltrace when continuous memory
** Changed in: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855990
Title:
linux-raspi2: dmesg prints calltrace when continuous memory
** Also affects: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855990
Title:
linux-raspi2: dmesg prints calltrace when continu
** Description changed:
- This bug is for tracking purpose
+ [Impact]
+ When booting our raspi2 eoan kernel on rpi2/3/4, the dmesg sometimes
+ prints calltrace, that is because the fb driver fails to allocate memory
+ from cma, this is not critical since the fb driver could handle the
+ failure of
