** Description changed:
- TBD
+ 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 and will also drop the
+ plymouth bootsplash sceen back to the text console (so that users can
+ see the error).
** Description changed:
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 and will also drop the
- plymouth bootsplash sceen back to the text console (so that users can
- see the error).
+ 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.
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** 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 changed:
+ [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_alloc_request: using
brcm/brcmfmac43455-sdio for chip BCM4345/6
+ [ 15.786996] brcmfmac: brcmf_fw_alloc_request: using
brcm/brcmfmac43455-sdio for chip BCM4345/6
+ [ 15.821301] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893905
Title:
Disable CONFIG_BRCM_TRACING
Status in linux-raspi package in Ubuntu:
Triaged
Status in linux-raspi source package in Focal:
Triaged
Status in linux-raspi source package in Groovy:
Triaged
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_alloc_request: using
brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 15.786996] brcmfmac: brcmf_fw_alloc_request: using
brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 15.821301] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1893905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
