FS#9689 - initcall messages not included in kernel logs

Attached to Project: Arch Linux
Opened by Dawid Wróbel (cromo) - Tuesday, 26 February 2008, 13:31 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 March 2008, 10:28 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I've been asked by a kernel developer to do some debugging in order to find the reason for my system failing to resume with recent 2.6.24 kernel. I am supposed to add the initcall_debug kernel option to the kernel command line and provide the initcall output. So I added it and during booting several initcall messages appear on the screen as they should, but these messages are not saved to everything.log or kernel.log files. Not even dmesg shows them, it looks like the dmesg output buffer size is not enough or sth.

Steps to reproduce:
Add the initcall_debug option to the kernel command line. Observe the initcall messages flood during booting and then check the dmesg and log files for these messages' absence.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 04 March 2008, 10:28 GMT
Reason for closing:  Fixed
Comment by Dawid Wróbel (cromo) - Wednesday, 27 February 2008, 23:44 GMT
The solution is to increase the CONFIG_LOG_BUF_SHIFT to 18 or 19 (tried 19 and it's fine).

Loading...