linux-raspi2: dmesg prints calltrace when continuous memory allocation fails
Bug #1855990 reported by
Hui Wang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi2 (Ubuntu) |
Fix Released
|
High
|
Hui Wang | ||
Eoan |
Fix Released
|
Medium
|
Unassigned |
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.
CVE References
Changed in linux-raspi2 (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
Changed in linux-raspi2 (Ubuntu Eoan): | |
importance: | Undecided → Medium |
Changed in linux-raspi2 (Ubuntu Eoan): | |
status: | New → Fix Committed |
Changed in linux-raspi2 (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
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) d-modules only builds against 430, signed modules (LP: #1856407)
* nvidia-435 is in eoan, linux-restricte
ubiquity gives me the self-signed modules experience instead of using the
Canonical-
- Add nvidia-435 dkms build
-- Manoj Iyer <email address hidden> Wed, 15 Jan 2020 15:09:58 -0600