Date: Sat, 28 Dec 1996 17:33:10 -0500 From: Mike Tancsa <mike@sentex.net> To: freebsd-scsi@freebsd.org Subject: SCSI BUS Resets... What are the causes / solutions ? Message-ID: <3.0.32.19961228173309.00973970@sentex.net>
next in thread | raw e-mail | index | archive | help
After I installed a new SCSI drive into our news server, we have been getting a lot of the following errors. I searched through the list to see if there were any other mention of it, but failed to see anything other than perhaps a power issue. However, I have a machine here at home (same power supply and motherboard Dec 28 07:43:05 flint /kernel: sd4(ahc0:1:0): timed out in dataout phase, SCSISIGI == 0x4 Dec 28 07:43:05 flint /kernel: sd4(ahc0:1:0): BUS DEVICE RESET message queued. Dec 28 07:43:07 flint /kernel: sd4(ahc0:1:0): timed out in dataout phase, SCSISIGI == 0x4 Dec 28 07:43:07 flint /kernel: ahc0: Issued Channel A Bus Reset #1. 8 SCBs aborted Dec 28 07:43:07 flint /kernel: sd2(ahc0:6:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): Power on, reset, or bus device reset occurred Dec 28 07:43:08 flint /kernel: , retries:3 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:08 flint /kernel: , retries:3 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:08 flint /kernel: , retries:2 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:09 flint /kernel: , retries:2 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:09 flint /kernel: , retries:1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:09 flint /kernel: , retries:1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:10 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:10 flint /kernel: , FAILURE Dec 28 07:43:10 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:10 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:11 flint /kernel: , FAILURE Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:11 flint /kernel: , retries:4 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:11 flint /kernel: , retries:4 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:12 flint /kernel: , retries:3 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:12 flint /kernel: , retries:3 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:12 flint /kernel: , retries:2 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:13 flint /kernel: , retries:2 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:13 flint /kernel: , retries:1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:14 flint /kernel: , retries:1 Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:14 flint /kernel: , FAILURE Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:14 flint /kernel: , FAILURE Dec 28 07:43:14 flint /kernel: sd3(ahc0:4:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:14 flint /kernel: sd3(ahc0:4:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Dec 28 07:43:15 flint /kernel: , retries:3 Dec 28 07:43:15 flint /kernel: sd4(ahc0:1:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:15 flint /kernel: sd4(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Dec 28 07:43:15 flint /kernel: , retries:3 Dec 28 07:43:15 flint /kernel: sd1(ahc0:5:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:15 flint /kernel: sd1(ahc0:5:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Dec 28 07:43:15 flint /kernel: , retries:3 And then, on the new drive, that I added when I modified the disklabel, I got Dec 28 17:22:04 flint /kernel: sd5(ahc0:3:0): UNIT ATTENTION asc:29,2 Dec 28 17:22:05 flint /kernel: , retries:2 This is on a Pentium 133 with 128Meg of RAM, Adaptec 2940 version 1.16 (or might be .18) Dec 28 01:50:09 flint /kernel: FreeBSD 2.1.5-RELEASE #0: Fri Dec 27 11:32:42 EST 1996 Dec 28 01:50:09 flint /kernel: mdtancsa@flint.sentex.net:/usr/src/sys/compile/FLINT Dec 28 01:50:10 flint /kernel: CPU: 133-MHz Pentium 735\90 or 815\100 (Pentium-class CPU) Dec 28 01:50:10 flint /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Dec 28 01:50:10 flint /kernel: Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8> Dec 28 01:50:11 flint /kernel: real memory = 134217728 (131072K bytes) Dec 28 01:50:11 flint /kernel: avail memory = 130138112 (127088K bytes) Dec 28 01:50:11 flint /kernel: Probing for devices on PCI bus 0: Dec 28 01:50:12 flint /kernel: chip0 <Intel 82439> rev 1 on pci0:0 Dec 28 01:50:12 flint /kernel: chip1 <Intel 82371 PCI-ISA bridge> rev 0 on pci0:7:0 Dec 28 01:50:12 flint /kernel: chip2 <Intel 82371 Bus-Master IDE controller> rev 0 on pci0:7:1 Dec 28 01:50:13 flint /kernel: vga0 <VGA-compatible display device> rev 211 int a irq 11 on pci0:9 Dec 28 01:50:13 flint /kernel: ahc0 <Adaptec 2940 SCSI host adapter> rev 3 int a irq 10 on pci0:11 Dec 28 01:50:13 flint /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs Dec 28 01:50:14 flint /kernel: ahc0 waiting for scsi devices to settle Dec 28 01:50:14 flint /kernel: (ahc0:0:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 Dec 28 01:50:15 flint /kernel: sd0(ahc0:0:0): Direct-Access 1003MB (2055035 512 byte sectors) Dec 28 01:50:15 flint /kernel: (ahc0:1:0): "SEAGATE ST31200N 8630" type 0 fixed SCSI 2 Dec 28 01:50:16 flint /kernel: sd4(ahc0:1:0): Direct-Access 1006MB (2061108 512 byte sectors) Dec 28 01:50:16 flint /kernel: (ahc0:3:0): "FUJITSU M2954S-512 0124" type 0 fixed SCSI 2 Dec 28 01:50:16 flint /kernel: sd5(ahc0:3:0): Direct-Access 4149MB (8498506 512 byte sectors) Dec 28 01:50:16 flint /kernel: (ahc0:4:0): "SEAGATE ST31200N 8648" type 0 fixed SCSI 2 Dec 28 01:50:16 flint /kernel: sd3(ahc0:4:0): Direct-Access 1006MB (2061108 512 byte sectors) Dec 28 01:50:17 flint /kernel: (ahc0:5:0): "SEAGATE ST15150N 0023" type 0 fixed SCSI 2 Dec 28 01:50:17 flint /kernel: sd1(ahc0:5:0): Direct-Access 4095MB (8388315 512 byte sectors) Dec 28 01:50:17 flint /kernel: (ahc0:6:0): "IBM DORS-32160 WA0A" type 0 fixed SCSI 2 Dec 28 01:50:17 flint /kernel: sd2(ahc0:6:0): Direct-Access 2063MB (4226725 512 byte sectors) SD0 and SD1 are both external drives and do not draw off the power supply... Are there any bugs in 2.1.5 that might be the cause of this? Our other machine is running 2.1.6 and has not seen these errors ever. ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.32.19961228173309.00973970>