Skip to contentSkip to conversation

Dmesg is not showing whole boot list

DISCUSSION CIJOML 6 participants 8 messages Mar 14, 2006 – Mar 15, 2006

lore
Share & tools
lore

CIJOML

author
#0 lore raw

Hello,

maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines at the beginning are missing.

Is there any option I can increase to get full dmesg?

ine.. 4801.43 BogoMIPS (lpj=2400718)
Security Framework v1.0.0 initialized

SELinux:  Initializing.
SELinux:  Starting in permissive mode
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 

00004400 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 128K
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
CPU: Intel(R) Celeron(R) CPU 2.40GHz stepping 09
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 0c88)
.
.
.

Linux Debian testing, kernel 2.6.16-rc5

Thanks for reply a regards

Michal

#1 lore raw
Quoted 6 lines · CIJOML

Hello,

maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines at the beginning are missing.

Is there any option I can increase to get full dmesg?

Try increasing CONFIG_LOG_BUF_SHIFT and recompile. That's likely the source of your problem.

Peter Hagervall

#2 lore raw

Or look in your /var/log/kern.log file instead of asking dmesg. dmesg just dumps the kernel ring buffer which is of finite size. The entire contents should be logged to /var/log/kern.log.

Quoted 14 lines · Peter Hagervall
Quoted 5 lines · CIJOML

Hello,

maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines at the beginning are missing.

Is there any option I can increase to get full dmesg?

Try increasing CONFIG_LOG_BUF_SHIFT and recompile. That's likely the source of your problem.

Peter Hagervall

#3 lore raw
Quoted 3 lines · Phillip Susi

Or look in your /var/log/kern.log file instead of asking dmesg. dmesg just dumps the kernel ring buffer which is of finite size. The entire contents should be logged to /var/log/kern.log.

You've got to have /var checked and mounted to be able to do that log write, if the buffer overflows before that, then the head end of the dmesg dump to the /var/log/dmesg file is lost forever.

There is a line that can be changed, in xconfig or by hand, to control the memory allocated for this ring buffer.

Finally found it in the xconfig display, left panel line=kernel hacking, right panel its under kernel debugging and shows only if thats checked, double click on the line that says : kernel log buffer size and enter a one digit increment from whats there now, maybe 2, I have mine set for
16. Your default may be as low as 14, why I have NDI because 16k sure as heck isn't enough if something gets chatty.

Quoted 21 lines
Quoted 6 lines · Peter Hagervall
Quoted 5 lines · CIJOML

Hello,

maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines at the beginning are missing.

Quoted 8 lines
Quoted 1 line

Is there any option I can increase to get full dmesg?

Try increasing CONFIG_LOG_BUF_SHIFT and recompile. That's likely the source of your problem.

Peter Hagervall

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 7 lines
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
#4 lore raw
Quoted 8 lines · Gene Heskett
Quoted 1 line · Phillip Susi

Or look in your /var/log/kern.log file instead of asking dmesg. dmesg just dumps the kernel ring buffer which is of finite size. The entire contents should be logged to /var/log/kern.log.

You've got to have /var checked and mounted to be able to do that log write, if the buffer overflows before that, then the head end of the dmesg dump to the /var/log/dmesg file is lost forever.

There is a line that can be changed, in xconfig or by hand, to control the memory allocated for this ring buffer.

Finally found it in the xconfig display, left panel line=kernel hacking, right panel its under kernel debugging and shows only if thats checked, double click on the line that says : kernel log buffer size and enter a one digit increment from whats there now, maybe 2, I have mine set for 16. Your default may be as low as 14, why I have NDI because 16k sure as heck isn't enough if something gets chatty.

To continue this point; on my desktop I have root/var/tmp/vicepa-on-LVM-on-RAID5, boot-on-RAID1, and swap-on-RAID1, so I would easily overflow the default SMP dmesg buffer size in messages well before syslogd/bootlogd got started. I finally ended up having to increment the default by 3 in order to have the boot messages still available after booting. It would be nice if we could quiet down some of the more excessively verbose kernel messages, there's a lot of mostly-irrelevant spew that chews up log buffer space.

Cheers,
Kyle Moffett

#5 lore raw
Quoted 21 lines · Kyle Moffett
Quoted 12 lines · Gene Heskett
Quoted 3 lines · Phillip Susi

Or look in your /var/log/kern.log file instead of asking dmesg. dmesg just dumps the kernel ring buffer which is of finite size. The entire contents should be logged to /var/log/kern.log.

You've got to have /var checked and mounted to be able to do that log write, if the buffer overflows before that, then the head end of the dmesg dump to the /var/log/dmesg file is lost forever.

There is a line that can be changed, in xconfig or by hand, to control the memory allocated for this ring buffer.

Quoted 7 lines

Finally found it in the xconfig display, left panel line=kernel hacking, right panel its under kernel debugging and shows only if thats checked, double click on the line that says : kernel log buffer size and enter a one digit increment from whats there now, maybe 2, I have mine set for 16. Your default may be as low as 14, why I have NDI because 16k sure as heck isn't enough if something gets chatty.

Quoted 8 lines

To continue this point; on my desktop I have root/var/tmp/vicepa-on- LVM-on-RAID5, boot-on-RAID1, and swap-on-RAID1, so I would easily overflow the default SMP dmesg buffer size in messages well before syslogd/bootlogd got started. I finally ended up having to increment the default by 3 in order to have the boot messages still available after booting. It would be nice if we could quiet down some of the more excessively verbose kernel messages, there's a lot of mostly- irrelevant spew that chews up log buffer space.

I think thats somewhat true but then when you need that info for figureing out what didn't work, its priceless. The only thing I'd stick a hot potato in is ACPI, its turned off in the config and still supplies about 5k of its mewling on boot. But my /proc/interrupts says its not working, which is what counts so I can keep good time with ntpd.

Quoted 2 lines

Cheers,
Kyle Moffett

Signature · 7 lines
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
author
#6 lore raw
In reply to Peter Hagervall

This helped.

Thanks

Michal

Dne út 14. března 2006 09:38 jste napsal(a):

Quoted 14 lines · CIJOML
Quoted 6 lines

Hello,

maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines at the beginning are missing.

Is there any option I can increase to get full dmesg?

Try increasing CONFIG_LOG_BUF_SHIFT and recompile. That's likely the source of your problem.

Peter Hagervall

#7 lore raw
Quoted 5 lines · On Wed, 15 Mar 2006 05:34:42 +0100 CIJOML wrote:

This helped.

Thanks

Michal

BTW, you don't have to recompile to get this. You can also add this to the kernel boot/command line:

log_buf_len=n Sets the size of the printk ring buffer, in bytes.
Format: { n | nk | nM }
n must be a power of two. The default size is set in the kernel config file.

Quoted 11 lines

Dne út 14. března 2006 09:38 jste napsal(a):

Quoted 10 lines · CIJOML
Quoted 6 lines

Hello,

maybe this si a wrong list to ask, bug after boot, dmesg shows that few lines at the beginning are missing.

Is there any option I can increase to get full dmesg?

Try increasing CONFIG_LOG_BUF_SHIFT and recompile. That's likely the source of your problem.

---
~Randy