*BSD News Article 62752


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!newsfeed.internetmci.com!swrinde!howland.reston.ans.net!surfnet.nl!news.nic.surfnet.nl!tuegate.tue.nl!asterix.urc.tue.nl!rcjvdb
From: rcjvdb@urc.tue.nl (Jan van den Bosch)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: panics: aha0 timeout
Date: 4 Mar 1996 10:38:39 GMT
Organization: Eindhoven University of Technology, The Netherlands
Lines: 41
Message-ID: <4heh7f$ccc@tuegate.tue.nl>
NNTP-Posting-Host: asterix.urc.tue.nl

Till now I was working with a very stable NetBSD 1.0 and 1.1 system,
However, since I added a 1GB IBM SCSI-disk (sd1), it often panics.
There are 2 other SCSI devices, sd0 and cd0.
I don't have any problems if I do not mount sd1 (the IBM disk),
or if I do nut use it together with the CD-ROM.
But copying a whole CD from cd0 to sd1 is always good for a panic.
It looks as if there is to much speed difference between the CD and
the IBM disk.
Btw: swap is on wd0 and sd0.

Some diagnostic info:

From /var/log/messages 
----------------------
/netbsd: scsibus0 at aha0
/netbsd: aha0 targ 0 lun 0: <TOSHIBA, CD-ROM XM-4101TA, 2483> SCSI2 
                            5/cdrom removable
/netbsd: cd0 at scsibus0: drive empty
/netbsd: aha0 targ 1 lun 0: <FUJITSU, M2684S-512, 2035> SCSI2 0/direct fixed
/netbsd: sd0 at scsibus0: 507MB, 2380 cyl, 6 head, 72 sec, 512 bytes/sec
/netbsd: aha0 targ 2 lun 0: <IBM, DPES-31080, S31Q> SCSI2 0/direct fixed
/netbsd: sd1 at scsibus0: 1034MB, 4903 cyl, 4 head, 108 sec, 512 bytes/sec
/netbsd: wdc0 at isa0 port 0x1f0-0x1f7 irq 14
...
/netbsd: sd1(aha0:2:0): timed out
/netbsd: sd0(aha0:1:0): timed out

The console message:
panic: timeout aha0: not taking commands

After reboot: in /var/log/messages :
-----------------------------------
savecore: reboot after panic: should call debugger here (aha1542.c)
savecore: writing core to /var/crash/netbsd.4.core
savecore: writing kernel to /var/crash/netbsd.4

Anyone has some ideas or suggestions what the reason for the 
time-outs could be??

Jan van den Bosch
rcjvdb@urc.tue.nl