atom feed17 messages in org.freebsd.freebsd-scsiRe: Invalidating pack messages
FromSent OnAttachments
Nick SlagerJun 20, 2000 12:27 am 
Don LewisJun 20, 2000 12:53 am 
Scott DonovanJun 20, 2000 1:51 am 
Nick SlagerJun 20, 2000 1:59 am 
Nick SlagerJun 20, 2000 2:02 am 
Ian WestJun 20, 2000 7:48 am 
Nick SlagerJun 20, 2000 9:35 pm 
Don LewisJun 22, 2000 12:29 am 
Steve PasseJun 22, 2000 2:27 am 
Don LewisJun 22, 2000 2:33 am 
Steve PasseJun 22, 2000 2:40 am 
Nick SlagerJun 23, 2000 12:38 am 
Wilko BulteJun 23, 2000 10:12 am 
Thomas ZenkerJun 26, 2000 2:08 am 
Nick SlagerJun 26, 2000 10:45 pm 
Thomas ZenkerJun 28, 2000 1:03 am 
Nick SlagerJun 28, 2000 5:43 am 
Subject:Re: Invalidating pack messages
From:Don Lewis (Don.@tsc.tdk.com)
Date:Jun 22, 2000 2:33:13 am
List:org.freebsd.freebsd-scsi

On Jun 22, 3:27am, Steve Passe wrote: } Subject: Re: Invalidating pack messages } Hi, } > On Jun 21, 2:36pm, Nick Slager wrote: } > } Subject: Re: Invalidating pack messages } > } > [ snip ] } > } > } If this is the case (and I'm not doubting what you say), what else could
cause } > } this problem? } > } > If your seeing funny blinking lights on the drive, and you are not the only } > person having problems with this particular drive model, I would be very } > suspicious that a drive firmware bug is being tickled. The best solution } > ... } } I've been running old and new cheetahs on sym and 29160 controllers } without a hint of trouble:

I think I saw two reports of this problem, both involving 18 GB drives. Yours look like 4 GB and 8 GB drives.

} ahc0: <Adaptec 29160 Ultra160 SCSI adapter> port 0x3000-0x30ff mem } 0xfe004000-0xfe004fff irq 19 at device 1.0 on pci1 } ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs } sym1: <896> port 0x3400-0x34ff mem 0xfe000000-0xfe001fff,0xfe005000-0xfe0053ff } irq 10 at device 3.0 on pci1 } sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking } sym2: <896> port 0x3800-0x38ff mem 0xfe002000-0xfe003fff,0xfe005400-0xfe0057ff } irq 2 at device 3.1 on pci1 } sym2: No NVRAM, ID 7, Fast-40, LVD, parity checking } } da0 at sym1 bus 0 target 0 lun 0 } da0: <SEAGATE ST34502LW 0004> Fixed Direct Access SCSI-2 device } da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing } Enabled } da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) } da1 at sym1 bus 0 target 1 lun 0 } da1: <SEAGATE ST34502LW 0004> Fixed Direct Access SCSI-2 device } da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing } Enabled } da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) } da3 at ahc0 bus 0 target 8 lun 0 } da3: <SEAGATE ST39204LW 0002> Fixed Direct Access SCSI-3 device } da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing } Enabled } da3: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) } da4 at ahc0 bus 0 target 9 lun 0 } da4: <SEAGATE ST39204LW 0002> Fixed Direct Access SCSI-3 device } da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing } Enabled } da4: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) } da5 at ahc0 bus 0 target 10 lun 0 } da5: <SEAGATE ST39204LW 0002> Fixed Direct Access SCSI-3 device } da5: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing } Enabled } da5: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) } } -- } Steve Passe | powered by } sm@csn.net | Symmetric MultiProcessor FreeBSD } } }-- End of excerpt from Steve Passe

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message