public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Feigl <Alexander.Feigl@gmx.de>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: aic7xxx SCSI system hangs
Date: 11 Oct 2001 21:44:41 +0200	[thread overview]
Message-ID: <1002829481.12402.16.camel@PowerBox.MysticWorld.de> (raw)
In-Reply-To: <200110111915.f9BJFLY97700@aslan.scsiguy.com>
In-Reply-To: <200110111915.f9BJFLY97700@aslan.scsiguy.com>

Am Don, 2001-10-11 um 21.15 schrieb 1002827721:
>
> To sum up, from time to time, the controller sees the first REQ for
> the data-in phase that follows the command phase, prior to seeing the
> phase lines change to data-in.  This is either caused by the plextor
> not allowing the proper bus-settle time for the phase change to be
> seen prior to asserting REQ *OR* your cabling is poor (too long,
> marginal/bent pin, incorrect termination, etc.) giving a similar
> result.
>

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. 

A co-developer of my project has similar problems with reading the TOC.
But he owns a Plextor PX40 drive and has problems with cdda2wav. I
cannot remember if it hangs when reading CDDA or CD-ROM TOCs on his
machine. cdda2wav is working fine on my machine and I am unable to hang
the SCSI subsystem with it - he gets reproducible hangs on his machine.
cdrecord works fine on his machine and makes problems on mine.
 
> 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.

Alexander Feigl


  reply	other threads:[~2001-10-11 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 14:03 PROBLEM: aic7xxx SCSI system hangs Alexander Feigl
2001-10-10 16:22 ` Justin T. Gibbs
2001-10-10 19:36   ` Alexander Feigl
2001-10-10 20:27     ` Justin T. Gibbs
2001-10-11 12:58       ` Alexander Feigl
2001-10-11 19:15         ` Justin T. Gibbs
2001-10-11 19:44           ` Alexander Feigl [this message]
2001-10-11 19:59             ` Justin T. Gibbs
2001-10-10 17:47 ` Cliff Albert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1002829481.12402.16.camel@PowerBox.MysticWorld.de \
    --to=alexander.feigl@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox