/me ponders some more..
Well, the bind message is about three times more data then you gave me
initially.. :-)
You're also all up to date on your patches, I just checked. The only
one not applied is gpm-root update, but I'm sure that'll get fixed as soojn
as you read this.. :-)
Like I said earlier, I'd be willing to bet on Derek's answer of bad
hardware. I noticed that the last time it occured, it was up for nearly 9
days. I think that the bind messages are simply what was last thrown in the
log, and not what happened 'just before the crash'. Any idea how long it
was hung before you rebooted?
May 27 13:11:15 rigor named[391]: bad referral (199.198.151.in-addr.arpa !<
2.19
9.198.151.IN-ADDR.ARPA)
May 27 13:34:33 rigor syslogd 1.3-3: restart.
According to this, it was like 23 minutes before the reboot. I also
noted this, which is pretty trivial, but should be noted:
May 27 13:34:54 rigor kernel: keyboard: Too many NACKs -- noisy kbd cable?
May 27 13:34:54 rigor kernel: keyboard: Too many NACKs -- noisy kbd cable?
Also, what did you end up doing about the CDROM drive and floppy drive?
I noticed untill yesterday that they are still listed using supermount,
which leads to the millions of daily device errors. *BAPBAPBAP* Try making
them normal mount points for now, not using supermount.
----- Original Message -----
From: Brian Chabot <[EMAIL PROTECTED]>
To: Greater NH Linux Users Group <[EMAIL PROTECTED]>
Cc: Data Squire System Administration <[EMAIL PROTECTED]>
Sent: Saturday, May 27, 2000 2:51 PM
Subject: Kernel Panic!
> OK. This has happenned before, but I thought by removing references to
> non-existent hardware, it was solved... (like USB...)
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
