Disable CONFIG_BRCM_TRACING
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
CONFIG_BRCM_TRACING is currently enabled which results in regular information being printed as errors. Using pr_err for things which are not errors is a bad idea and might confuse users. It will also drop the plymouth bootsplash screen back to the text console so that users can see the (bogus) error.
[Test Case]
Boot a Pi and run 'dmesg'. The following info is printed as errors (in red):
[ 15.478168] brcmfmac: brcmf_fw_
[ 15.786996] brcmfmac: brcmf_fw_
[ 15.821301] brcmfmac: brcmf_c_
[Regression Potential]
Some messages are now being printed with log level INFO rather than ERR.
CVE References
description: | updated |
description: | updated |
no longer affects: | linux (Ubuntu) |
no longer affects: | linux (Ubuntu Focal) |
no longer affects: | linux (Ubuntu Groovy) |
Changed in linux-raspi (Ubuntu Focal): | |
status: | New → Triaged |
Changed in linux-raspi (Ubuntu Groovy): | |
status: | New → Triaged |
description: | updated |
description: | updated |
Changed in linux-raspi (Ubuntu Focal): | |
status: | Triaged → Fix Committed |
Changed in linux-raspi (Ubuntu Groovy): | |
status: | Triaged → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1893905
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.