| 2019-12-11 06:54:52 |
Hui Wang |
bug |
|
|
added bug |
| 2019-12-11 06:55:02 |
Hui Wang |
linux-raspi2 (Ubuntu): importance |
Undecided |
High |
|
| 2019-12-11 07:33:24 |
Hui Wang |
description |
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. |
|
| 2020-01-07 12:53:17 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-01-07 12:53:17 |
Kleber Sacilotto de Souza |
bug task added |
|
linux-raspi2 (Ubuntu Eoan) |
|
| 2020-01-07 12:59:42 |
Stefan Bader |
linux-raspi2 (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-01-07 12:59:59 |
Kleber Sacilotto de Souza |
linux-raspi2 (Ubuntu Eoan): status |
New |
Fix Committed |
|
| 2020-01-27 18:42:46 |
Launchpad Janitor |
linux-raspi2 (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-01-27 18:42:46 |
Launchpad Janitor |
cve linked |
|
2019-14615 |
|
| 2020-01-27 23:27:07 |
Launchpad Janitor |
linux-raspi2 (Ubuntu): status |
New |
Fix Released |
|
