[SRU][raspi2-eoan][PATCH 0/1] fbdev: dmesg prints calltrace when continuous memory allocation fails

Hui Wang hui.wang at canonical.com
Wed Dec 11 07:15:00 UTC 2019

BugLink: https://bugs.launchpad.net/bugs/1855990

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.

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.

Hui Wang (1):
  bcm2708_fb: Disable warning when calling dma_alloc_coherent

 drivers/video/fbdev/bcm2708_fb.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


More information about the kernel-team mailing list