** 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 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.
-- 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 allocation fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1855990/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
