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-2019-14615
- drm/i915/gen9: Clear residual context state on context switch
* PAN is broken for execute-only user mappings on ARMv8 (LP: #1858815)
- arm64: Revert support for execute-only user mappings
* Miscellaneous Ubuntu changes
- update dkms package versions
linux-raspi2 (5.3.0-1016.18) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1016.18 -proposed tracker (LP: #1858941)
* linux-raspi2: dmesg prints calltrace when continuous memory allocation fails
(LP: #1855990)
- bcm2708_fb: Disable warning when calling dma_alloc_coherent
[ Ubuntu: 5.3.0-27.29 ]
* eoan/linux: 5.3.0-27.29 -proposed tracker (LP: #1858943)
* [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
(LP: #1856608)
- SAUCE: Revert "usb: handle warm-reset port requests on hub resume"
[ Ubuntu: 5.3.0-26.28 ]
* eoan/linux: 5.3.0-26.28 -proposed tracker (LP: #1856807)
* nvidia-435 is in eoan, linux-restricted-modules only builds against 430,
ubiquity gives me the self-signed modules experience instead of using the
Canonical-signed modules (LP: #1856407)
- Add nvidia-435 dkms build
-- Manoj Iyer <manoj.i...@canonical.com> Wed, 15 Jan 2020 15:09:58
-0600
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1855990
Title:
linux-raspi2: dmesg prints calltrace when continuous memory allocation
fails
Status in linux-raspi2 package in Ubuntu:
Fix Released
Status in linux-raspi2 source package in Eoan:
Fix Released
Bug description:
[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 allocation.
[Fix]
Disable the warning, then the calltrace will not be printed out.
[Test Case]
Booting the kernel with high resolution moinitor, the fb drver print the
log about failure of allocation, but there is no calltrace anymore.
[Regression Risk]
Low, just disable a warning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1855990/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
