Messages in this thread |  | | Subject | Re: PROBLEM: aic7xxx SCSI system hangs | Date | Thu, 11 Oct 2001 13:59:26 -0600 | From | "Justin T. Gibbs" <> |
| |
>I am rather sure that the cabling is Ok. Besides I am not a SCSI newbie >(although I don't have any ideas how it works internally) - everything >else works without problems. High data rate reading of a CD-ROM, >ripping, reading the TOC of data CD-ROM and reading the TOC of a CDDA >with cdda2wav. On my system 3 things have to come together. > >1) I use cdrecord -toc to read the TOC >2) A CDDA disc is inserted in the drive >3) I use my Plextor PX 32TS drive > >The problem is 100% reproducable here.
That's great and all, but it doesn't change the fact that the problem, from the Adaptec chip's perspective, is a protocol violation *on the bus*. I'm willing to believe that there is a chip bug in the aic7896/97 if you can provice a SCSI bus trace indicating that everything is normal on the SCSI bus.
>A co-developer of my project has similar problems with reading the TOC.
On the same or different controller?
>> As for why you cannot talk to the device after a while, the device >> has been set offline. The controller was unable to talk to it >> successfully, so the SCSI layer decided to ignore it. > >If the device is only set offline it would be a minor problem. Probably >I could do rmmod/insmod or scsi-remove-single-device and re-add it. As I >mailed in my first posts even a cdrecord -scanbus or accesses to other >drives on the same controller hang and will be in uninterruptible state >after this call. The processes cannot be killed, the module cannot be >unloaded and I have to reboot to do any SCSI accesses again.
To diagnose why things are hung will require you to grovel around in the SCSI data structures to determine why I/O is hung. Perhaps use kdb to change the SCSI loging level after the hangs start, then try access to another device and see where the traces lead you? I cannot reproduce the problem here, so it is difficult for me to debug it.
-- Justin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |