| 2020-09-02 07:29:27 |
Juerg Haefliger |
bug |
|
|
added bug |
| 2020-09-02 07:29:36 |
Juerg Haefliger |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-09-02 07:29:36 |
Juerg Haefliger |
bug task added |
|
linux (Ubuntu Groovy) |
|
| 2020-09-02 07:29:36 |
Juerg Haefliger |
nominated for series |
|
Ubuntu Focal |
|
| 2020-09-02 07:29:36 |
Juerg Haefliger |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2020-09-02 07:30:08 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2020-09-02 07:30:10 |
Ubuntu Kernel Bot |
linux (Ubuntu Focal): status |
New |
Incomplete |
|
| 2020-09-02 07:33:45 |
Juerg Haefliger |
description |
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). |
|
| 2020-09-02 07:34:30 |
Juerg Haefliger |
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 and will also drop the plymouth bootsplash sceen back to the text console (so that users can see the error). |
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. |
|
| 2020-09-02 07:34:59 |
Juerg Haefliger |
bug task added |
|
linux-raspi (Ubuntu) |
|
| 2020-09-02 07:35:05 |
Juerg Haefliger |
bug task deleted |
linux (Ubuntu) |
|
|
| 2020-09-02 07:35:13 |
Juerg Haefliger |
bug task deleted |
linux (Ubuntu Focal) |
|
|
| 2020-09-02 07:35:17 |
Juerg Haefliger |
bug task deleted |
linux (Ubuntu Groovy) |
|
|
| 2020-09-02 07:35:25 |
Juerg Haefliger |
linux-raspi (Ubuntu Focal): status |
New |
Triaged |
|
| 2020-09-02 07:35:29 |
Juerg Haefliger |
linux-raspi (Ubuntu Groovy): status |
New |
Triaged |
|
| 2020-09-02 07:38:59 |
Juerg Haefliger |
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. |
[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 |
|
| 2020-09-09 12:51:28 |
Juerg Haefliger |
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 |
[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. |
|
| 2020-09-16 04:27:12 |
Khaled El Mously |
linux-raspi (Ubuntu Focal): status |
Triaged |
Fix Committed |
|
| 2020-09-17 11:53:39 |
Juerg Haefliger |
linux-raspi (Ubuntu Groovy): status |
Triaged |
Fix Committed |
|
| 2020-10-08 10:59:44 |
Launchpad Janitor |
linux-raspi (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2020-10-08 10:59:44 |
Launchpad Janitor |
cve linked |
|
2020-14386 |
|
| 2020-10-13 22:41:57 |
Launchpad Janitor |
linux-raspi (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-10-13 22:41:57 |
Launchpad Janitor |
cve linked |
|
2020-16119 |
|
| 2020-10-13 22:41:57 |
Launchpad Janitor |
cve linked |
|
2020-16120 |
|
