Wolfgang Weisselberg wrote:
Hi!
Trying to kill the keyboard, brauki@cityweb.de produced:
today my linux system crashed and hung. (2.0.33-suse, i486dx4, vlb, adaptec 2970scsi)
famous last words in messages: .... (scsi0:0:5:-1) Unexpected busfree, LASTPHASE = 0x80, SEQADDR = 0x14a
anything serious?
When Linux crashes, that is very serious ... unlike some other 'operating' 'systems', Linux should never crash. Either you stumbled on a bug in the kernel or your hardware is ... suboptimal.
any ideas?
Yes, try to give us the complete error message. There should have been some info on the console 1 ... and maybe there's a _bit_ more info in /var/log/messages ... without that it's hard to mindread.
look now a bit ugly ;-(, but there was not much more: Jun 6 19:45:05 slartibartfast isdnlog: Jun 06 19:45:05 tei 64 calling ? with ? PROGRESS: Inband Information available Jun 6 19:45:06 slartibartfast isdnlog: Jun 06 19:45:06 tei 64 calling ? with ? HANGUP User busy Jun 6 19:45:25 slartibartfast isdnlog: Jun 06 19:45:25 * tei 127 calling Juergen Braukmann with ? RING () Jun 6 19:53:00 slartibartfast /USR/SBIN/CRON[865]: (root) CMD ($HOME/bin/cron.daily) Jun 6 19:55:52 slartibartfast su: (to nobody) root on none # I start a script that might shut down ISDN if telecom sponsoring was done... Jun 6 19:59:00 slartibartfast /USR/SBIN/CRON[1031]: (root) CMD (test -e /sbin/e-break && /sbin/e-break) # good bye:-( Jun 6 20:04:52 slartibartfast kernel: (scsi0:0:5:-1) Unexpected busfree, LASTPHASE = 0x80, SEQADDR = 0x14a # coming back to live Jun 6 20:33:46 slartibartfast syslogd 1.3-0: restart. Jun 6 20:33:47 slartibartfast named[179]: starting Jun 6 20:33:47 slartibartfast named[179]: cache zone "" loaded (serial 0) Jun 6 20:33:47 slartibartfast named[180]: Ready to answer queries. Jun 6 20:33:48 slartibartfast kernel: klogd 1.3-0, log source = /proc/kmsg started. after all, there was a little bit of thunder&lightning outside, but realy not so much to call it so.
Anyway, your SCSI system got a SCSI interrupt, and something was a bit strange, so it said: Hmmm ... let's wait for the commands to time out, and tell (as an info) that that happened. (see /usr/src/linux/drivers/scsi/aic7xxx.c)
well, I do not speak C, just ancient FORTRAN and a bit Pascal...
So that in itself was not critical at all, it seems.
that's what I guess too. First realy "serious" crash for a long time.
-Wolfgang
Jürgen -- ========================================== __ _ Jürgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / ========================================== /____/_/_//_/\_,_/ /_/\_\ -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e