public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan Gibb <duncangibb@uk.dmgworldmedia.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: "Cress, Andrew R" <andrew.r.cress@intel.com>,
	Rohit Gupta <rohit@davsys.com>,
	linux-scsi@vger.kernel.org
Subject: RE: aic79xx U320 + e1000 Intel hangs on Idual Xeon 7505
Date: 09 Apr 2003 23:01:05 +0100	[thread overview]
Message-ID: <1049925671.16881.104.camel@astrognat> (raw)
In-Reply-To: <239330000.1049920048@aslan.btc.adaptec.com>

On Wed, 2003-04-09 at 21:27, Justin T. Gibbs wrote:

JG> The latest driver is 1.3.6:

I superimposed your 2.4-20030328 driver over my kernel tree and
rebuilt.  It still locked up :-(

JG> Depending on the drives you are using, you may also need to run
JG> with a fairly low tag depth {..} to get the drivers stable.

I tried lowering global tag depth to 4 (which I presume is a low number,
but I don't really know what I'm doing).  And it still locks up.
Moreover, according to /proc/scsi/aic79xx/[01], the driver has
negotiated "Max Tagged Openings 0" with all the devices on this bus.

I noticed /proc/scsi/aic79xx/1 correctly refers to the controller as
Channel B, but all the device info says Channel A.  Hope this doesn't
mean it's getting scsi0 and scsi1 mixed up at a lower level.

My other theory is that all the devices on this bus are removable in one
form or another, and hence are being polled for media changes.  The
actions which cause the bus/driver to lock up are things which need a
long period (several seconds) of data transfer - scanning in colour,
writing a CD.  Could the disconnect logic be getting screwed up
somewhere?  How could I test that?


Duncan



  reply	other threads:[~2003-04-09 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 19:26 aic79xx U320 + e1000 Intel hangs on Idual Xeon 7505 Cress, Andrew R
2003-04-09 20:23 ` Duncan Gibb
2003-04-09 20:27   ` Justin T. Gibbs
2003-04-09 22:01     ` Duncan Gibb [this message]
2003-04-10 16:55       ` Justin T. Gibbs
2003-04-10 21:00         ` Duncan Gibb
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09 15:47 Duncan Gibb

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=1049925671.16881.104.camel@astrognat \
    --to=duncangibb@uk.dmgworldmedia.com \
    --cc=andrew.r.cress@intel.com \
    --cc=gibbs@scsiguy.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rohit@davsys.com \
    /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