mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Emmanuel FUSTE" <e.fuste@wanadoo.fr>
To: <phil@fifi.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: aic7xxx problem.  (PCI related ?)
Date: Wed, 06 Nov 2002 10:57:41 +0100 (MET)	[thread overview]
Message-ID: <3DA24C0A01244F0A@mel-rta10.wanadoo.fr> (raw)
In-Reply-To: <87bs53qyli.fsf@ceramic.fifi.org>

> Which hardware is connected to your SCSI adapter? (hint: cat /proc/scsi/scsi)
> 
> I've found out that some IBM hard disks give the above error when too
> many tagged commands are queued (firmware bug probably). I definitely
> have a DDRS-39130D drive which shows this behavior. The old SCSI
> driver (5.x) was not as bold as the 6.x driver which is in 2.4 with
> regards to queueing: the 6.x driver use 253 tagged command openings by
> default.
> 
> For me, passing `aic7xxx=tag_info:{{,,,8}}' to the kernel solved the
> problems. The above tells the aic7xxx driver to limit tagged queuing
> depth to 8 for the drive at ID 3 on the first aic7xxx adapter, but
> YMMV.
> 
> Phil.

Thanks Phil, unfortunately, this doesnt solve my problem.
The 5.x driver never worked for me on the 2940u2w, it lock the computer.

I could even trigger the kernel message with no devices attached to the scsi bus.
With the two adapters in the computer, when I issue a scsiadd -s 1, I've got the
errors but whithout  the hard lock.

For reference:
http://marc.theaimsgroup.com/?l=linux-kernel&m=99295558926036&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=100852862320948&w=2

Is someone knew something about my pblm with the pci latency timer set to 0 ?

Emmanuel.


      reply	other threads:[~2002-11-06  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 22:34 aic7xxx problem Emmanuel Fuste
2002-11-06  1:24 ` Philippe Troin
2002-11-06  9:57   ` Emmanuel FUSTE [this message]

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=3DA24C0A01244F0A@mel-rta10.wanadoo.fr \
    --to=e.fuste@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@fifi.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

all inboxes | Powered by JetHome®