Date: Thu, 18 Sep 2003 19:48:29 +1000 From: Andrew Snow <als@kanji.com.au> To: freebsd-scsi@freebsd.org Subject: Re: adaptec 2120S report Message-ID: <3F697F6D.4050108@kanji.com.au> In-Reply-To: <3F696CD4.20602@freebsd.org> References: <3F690CB5.6000001@kanji.com.au> <3F696CD4.20602@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> The only downside was I cannot get it working at Ultra-320 >> with this IBM x345 hotswap backplane, but it is working great at >> Ultra-160. Scott Long wrote: > What tool are you using to report the speed? I haven't tried the IBM > backplanes much, but it wouldn't surprise me if it didn't support > packetized mode and therefore not support Ultra320. I use aaccli to report the speed - combined with the fact that if I try to set the speed in the BIOS to 320, I get SCSI parity errors and failure messages all over the place, where 160 works fine (with "Packetized" enabled, too) The backplane is supposed to support Ultra-320. It works with the motherboard LSI Ultra-320 controller. However, the docs for the board say "Data integrity cannot be guaranteed when using third party controller" or something to that effect. It doesn't help that the backplane has the weirdest connector I have ever seen, so I was forced to use another SCSI cable with no terminator and a female-to-female adaptor (the supplied SCSI cable is very short!). >> FreeBSD won't boot during rebuild > This should not happen, and I cannot reproduce this locally. What > circumstances surrounded the build? Was it initiated by the BIOS? > Would it be possible to enable 'bootverbose' and send me a transcript > of the boot log? Scenario: pull a drive out (I pulled out SCSI ID#5), wait, push it back in, and a rebuild begins automatically. The freebsd driver happily logs the messages explaining what is going on. Then, reboot freebsd. When it boots again you get this: ----- pcib6: <ServerWorks host to PCI bridge(unknown chipset)> at pcibus 6 on motherboard pci6: <PCI bus> on pcib6 aac0: <Adaptec SCSI RAID 2120S> mem 0xf4000000-0xf7ffffff irq 9 at device 1.0 on pci6 aac0: i960RX 100MHz, 48MB cache memory, optional battery present aac0: Kernel 4.0-0, Build 6008, S/N b88205 aac0: Supported Options=1f7e<CLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,NORECOND,SGMAP64,ALARM,NONDASD> aacp0: <SCSI Passthrough Bus> on aac0 .............. ata0-master: piomode=12 dmamode=34 udmamode=66 dmaflag=1 ata0-master: success setting PIO4 on ServerWorks CSB5 chip acd0: <LG CD-ROM CRN-8245B/1.16> CDROM drive at ata0 as master acd0: read 4125KB/s (32015KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc aacd0: <RAID 0/5> on aac0 aacd0: 138850MB (284364800 sectors) GEOM: new disk aacd0 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:284350437 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure aacd0s1, start 32256 length 145587423744 end 145587455999 GEOM: Configure aacd0s1a, start 0 length 536870912 end 536870911 GEOM: Configure aacd0s1b, start 143344533504 length 1073741824 end 144418275327 GEOM: Configure aacd0s1c, start 0 length 145587423744 end 145587423743 GEOM: Configure aacd0s1d, start 536870912 length 10737418240 end 11274289151 GEOM: Configure aacd0s1e, start 11274289152 length 132070244352 end 143344533503 GEOM: Configure aacd0s1f, start 144418275328 length 1169148416 end 145587423743 (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): error 5 (probe3:aacp0:0:3:0): Retries Exausted (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): error 5 (probe5:aacp0:0:5:0): Retries Exausted (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): error 5 (probe4:aacp0:0:4:0): Retries Exausted (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): error 5 (probe0:aacp0:0:0:0): Retries Exausted (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): error 5 (probe1:aacp0:0:1:0): Retries Exausted (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): error 5 (probe2:aacp0:0:2:0): Retries Exausted stray irq 7 got 5 stray irq 7's: not logging anymore ses0 at aacp0 bus 0 target 8 lun 0 ses0: <IBM 32P0032a S320 1 1> Fixed unknown SCSI-2 device ses0: Serial Number 1 ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device pass0 at aacp0 bus 0 target 0 lun 0 pass0: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass1 at aacp0 bus 0 target 1 lun 0 pass1: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass2 at aacp0 bus 0 target 2 lun 0 pass2: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass2: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass3 at aacp0 bus 0 target 3 lun 0 pass3: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass4 at aacp0 bus 0 target 4 lun 0 pass4: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass5 at aacp0 bus 0 target 5 lun 0 pass5: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass6 at aacp0 bus 0 target 8 lun 0 pass6: <IBM 32P0032a S320 1 1> Fixed unknown SCSI-2 device pass6: Serial Number 1 pass6: 3.300MB/s transfers pass0 at aacp0 bus 0 target 0 lun 0 pass0: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass1 at aacp0 bus 0 target 1 lun 0 pass1: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass2 at aacp0 bus 0 target 2 lun 0 pass2: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass2: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass3 at aacp0 bus 0 target 3 lun 0 pass3: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass4 at aacp0 bus 0 target 4 lun 0 pass4: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass5 at aacp0 bus 0 target 5 lun 0 pass5: <IBM-ESXS DTN036C3UCDY10FN S25J> Fixed unknown SCSI-3 device pass5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) Mounting root from ufs:/dev/aacd0s1a ----- Above shows one time it got through OK, wasn't able to reproduce this. It normally locks up after "got 5 stray irq 7's: not logging anymore" When I say it locks up, the keyboard still works (scroll lock, page up, page down) and the RAID continues to rebuild (the drive access LEDs show activity). But even waiting 5-10 minutes doesn't show any more console messages... I can either pull the drive out and then boot-up continues OK. Or, hard reset the machine, pull the drive out, and FreeBSD boots. With verbose logging disabled, I see: ----- aacd0: <RAID 0/5> on aac0 aacd0: 138850MB (284364800 sectors) stray irq 7 stray irq 7 stray irq 7 stray irq 7 stray irq 7 got 5 stray irq 7's: not logging anymore ----- followed by the locking up. >> 2. I could not get SMP kernel to work > Would you be > able to test a very recent 5-current snapshot? Sadly this machine is going into production shortly and I don't think I can afford to mess around with anything newer than RELENG_5_1.... is it worth playing around patches to the aac driver while leaving the rest of the system at 5.1 state? >> Other than that, it seems to be working very nicely. I look forward >> to seeing the Serveraid / ips driver issues resolved in 5.2... > It's on my TODO list. I apologize for not being responsive, I've been > quite buried under other projects. No problem at all - the fact that these SCSI cards and servers work as well as they do in a FREE operating system that the vendor refuses to acknowledge amazes me. Thanks for all your excellent work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F697F6D.4050108>