The problem can be shown by this: tfoerste@n22 ~ $ ls -l dmesg-2.6.1*; head -n 3 dmesg-2.6.1* -rw-r--r-- 1 tfoerste users 14711 Jan 2 10:55 dmesg-2.6.18-gentoo-r6 -rw-r--r-- 1 tfoerste users 15433 Feb 12 14:44 dmesg-2.6.19-gentoo-r5 ==> dmesg-2.6.18-gentoo-r6 <== Linux version 2.6.18-gentoo-r6 (root@n22) (gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #1 Wed Dec 27 15:14:07 CET 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) ==> dmesg-2.6.19-gentoo-r5 <== S-e820: 000000003ff67000 - 000000003ff79000 (ACPI NVS) BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved) BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved) ANd using the argument "-s" for dmesg doesn't help :-( Reproducible: Always
dmesg is a simple userspace utility that asks the kernel for its log
however, that still doesnt make this a valid bug ... your newer kernel fills up the buffer faster so the kernel starts to overwrite old messages
Ok, is there any chance for an enhancement request to increase the buffer size ?
no because it's already an option; increase it in your kernel config