On 2006/09/24 09:45, Alf Schlichting wrote: > You may be a victim of the "feature" that ( for hardware related reasons) > the dmesg buffer doesn't get cleared after reboot so you actually have 2 > dmesgs, (or maybe even more ?) one after the other, in dmesg buffer. > This can easily be overlooked by scrolling back to fast.
It sounds like you don't like it - but it can actually be very useful; ddb(4) normally logs commands and responses to the message buffer, so if you have a machine that doesn't clear memory at reboot, after a kernel panic you can often still retrieve the error, and the commands you entered (hopefully to display a backtrace and process list) - if you don't have a null nodem cable or pencil handy this is pretty good.
