** 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
+ 
+ [Regression Potential]
+ 
+ Some messages are now being printed with log level INFO rather than ERR.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893905

Title:
  Disable CONFIG_BRCM_TRACING

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1893905/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to