FS#76681 - [linux] trace_printk() being used warning from Linux
Attached to Project:
Arch Linux
Opened by Yassine Oudjana (Tooniis) - Sunday, 27 November 2022, 08:53 GMT
Last edited by Toolybird (Toolybird) - Monday, 28 August 2023, 21:02 GMT
Opened by Yassine Oudjana (Tooniis) - Sunday, 27 November 2022, 08:53 GMT
Last edited by Toolybird (Toolybird) - Monday, 28 August 2023, 21:02 GMT
|
Details
Description:
This has been appearing in dmesg since at least linux 6.0.9: [ 7.661903] ********************************************************** [ 7.661905] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** [ 7.661907] ** ** [ 7.661909] ** trace_printk() being used. Allocating extra memory. ** [ 7.661911] ** ** [ 7.661913] ** This means that this is a DEBUG kernel and it is ** [ 7.661915] ** unsafe for production use. ** [ 7.661916] ** ** [ 7.661918] ** If you see this message and you are not debugging ** [ 7.661920] ** the kernel, report this immediately to your vendor! ** [ 7.661922] ** ** [ 7.661924] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** [ 7.661925] ********************************************************** Additional info: * package version(s): 6.0.9.arch1-1, 6.0.10.arch2-1 Steps to reproduce: - Check dmesg |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 28 August 2023, 21:02 GMT
Reason for closing: Upstream
Additional comments about closing: If still happening with latest kernels, please follow up with upstream kernel folks.
Monday, 28 August 2023, 21:02 GMT
Reason for closing: Upstream
Additional comments about closing: If still happening with latest kernels, please follow up with upstream kernel folks.
FS#56363FS#57076.I should say that I noticed this while trying to figure out some issue with the backlight control, which stopped working after upgrading to 6.0.10. Downgrading the kernel back to 6.0.5 where it was working didn't fix it. This is the only lead to the issue I could find in dmesg:
```
[ 3.062041] i915 0000:00:02.0: [drm] *ERROR* Failed to get the SoC PWM chip
```
Could this random breakage be related in anyway or is it likely just a coincidence?
[1] https://wiki.archlinux.org/title/Kernel_module#Using_kernel_command_line_2
[2] https://lore.kernel.org/all/20211028124217.394cc49b%40sal.lan/
[1] https://bbs.archlinux.org/viewtopic.php?pid=2070789#p2070789
[2] https://lore.kernel.org/all/20211028124217.394cc49b%40sal.lan/