Public bug reported:
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.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: Triaged
** Affects: linux-raspi (Ubuntu Groovy)
Importance: Undecided
Status: Triaged
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
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:
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.
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
