On Sat, 13 Jul 2002, Michael G. Schabert wrote:

> >>  fill up what is displayed when you type dmesg.
> >
> >Look at /var/run/dmesg.boot. (And see /etc/rc.d/dmesg.)
>
> alpha# more /var/run/dmesg.boot
> s Applied
>       FRU CODE:  0xd0
>           SKSV:  Actual Retry Count: 2
>
> sd0(siop0:0:0:0):  Check Condition on CDB: 0x28 00 00 cd 2a 72 00 00 02 00
>      SENSE KEY:  Recovered Error
>     INFO FIELD:  13445746
>       ASC/ASCQ:  Recovered Data With Retries
>       FRU CODE:  0xd0
>           SKSV:  Actual Retry Count: 5
> <SNIP>
>
> As I said. The dmesg command doesn't always help. And if uptime is

Running "dmesg" and looking at /var/run/dmesg.boot can be different. So I
understand that dmesg doesn't always help -- due to the message buffer
being filled up.

Thanks for your example of it filling up at the initial boot up time.

   Jeremy C. Reed
   http://bsd.reedmedia.net/