Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57076 - [linux-zen] trace_printk() being used. Allocating extra memory.

Attached to Project: Arch Linux
Opened by Zdenek Janak (astrograzl) - Friday, 12 January 2018, 20:31 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 12 January 2018, 22:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Found this warning notice in dmesg output during boot.

Additional info:
* package version(s)

linux-zen 4.14.13-1

* config and/or log files etc.

**********************************************************
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
** **
** trace_printk() being used. Allocating extra memory. **
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
** **
** If you see this message and you are not debugging **
** the kernel, report this immediately to your vendor! **
** **
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
**********************************************************

Steps to reproduce:

Update linux-zen kernel to latest version.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Friday, 12 January 2018, 22:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.14.13-2
Comment by Doug Newgard (Scimmia) - Friday, 12 January 2018, 20:42 GMT
With what out-of-tree modules?
Comment by Zdenek Janak (astrograzl) - Friday, 12 January 2018, 20:45 GMT
bbswitch-dkms
nvidia-dkms
virtualbox-host-dkms
Comment by Doug Newgard (Scimmia) - Friday, 12 January 2018, 20:50 GMT
Hmm, I wouldn't suspect any of those, but can you see if you still get the message without them?
Comment by Zdenek Janak (astrograzl) - Friday, 12 January 2018, 21:08 GMT
Yes, the message is stil present after uninstall of all dkms modules. Full dmesg.log after fresh boot is in attachment.
May it be the result of latest patch for CPU's bugs?
   dmesg.log (61.4 KiB)
   cpuinfo.txt (4.7 KiB)

Loading...