dmesg showing garbage
Hello, I have noticed for some time now that the top of dmesg after a reboot often contains garbage. The more strange thing is that it some times also contains console output from the previous shutdown sequence. Example of somewhat garbled data: %dmesg |head module /bo\^?t/kErnel/snd_via82c686.ko\^B ap 0xc06560a8. Xre|oaded elf module /boot/kerned/snd_pcm.ko at \M-0xc065615c. Preloaded elf module /boot/kernel/uplcom.ko at 0xc0656208. Preloaded elf m/dule /boot/kernel/\M-ucom\M-.ko at 0xc06562b4. Preloaded elf module /boot/kerngl/firewire.ko at 0xc065636 . Preloaded elf module!/boot/iernel/acpi.ko at 0xc0656410. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequencY 11936924410Hz CPU: Pentium III'Pentium III Xeon/Celeron (1193.69-MHz 686-class CPU) Origin = GenuineIntel Id 5 0x6b1 Stepping = 1 % Whenever I reboot to singleusermode to run installworld + mergemaster, after a reboot I get some of the console output from before the reboot in the dmesg log. Example: %dmesg |head *** Temp ./etc/mtree/BSD.usr.dist and installed have the same CVS Id, deleting Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 13 13 13 done Uptime: 43s Terminate ACPI Rebooting... % Is this a feature, or a bug? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dmesg showing garbage
On Sun, 2002-10-13 at 01:11, Juli Mallett wrote: If you reboot and the memory is not cleared, the buffer (stored at a fixed address) may still be intact, and the kernel buffering code will be smart enough to span to the end of the buffer, and append (circularly) there. This does not explain the garbled data in the normal dmesg output though. And it also happens after a power-down (shutdown -p). But, this is a laptop, with battery (and power cord plugged in). And it may keep memory alive for some obscure reason. Anyway, it could show that FreeBSD could do a better job initializing memory on bootup? -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dmesg showing garbage
* De: Frode Nordahl [EMAIL PROTECTED] [ Data: 2002-10-12 ] [ Subjecte: Re: dmesg showing garbage ] Anyway, it could show that FreeBSD could do a better job initializing memory on bootup? This is a job of the BIOS, and I wasn't trying to explain the garbage, merely why there's stuff from the previous boot. I didn't quote the bits asking why there was corruption. -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dmesg showing garbage
* De: Frode Nordahl [EMAIL PROTECTED] [ Data: 2002-10-12 ] [ Subjecte: dmesg showing garbage ] Hello, The more strange thing is that it some times also contains console output from the previous shutdown sequence. If you reboot and the memory is not cleared, the buffer (stored at a fixed address) may still be intact, and the kernel buffering code will be smart enough to span to the end of the buffer, and append (circularly) there. -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
