From: Hannes Reinecke <hare@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFT][PATCH] aic79xx: remove busyq
Date: Mon, 13 Jun 2005 15:56:25 +0200 [thread overview]
Message-ID: <42AD9089.5080006@suse.de> (raw)
In-Reply-To: <20050529074620.GA26151@havoc.gtf.org>
Jeff Garzik wrote:
> Can anyone with aic79xx hardware give me a simple "it works"
> or "this breaks things" answer, for the patch below?
>
> This changes the aic79xx driver to use the standard Linux SCSI queueing
> code, rather than its own. After applying this patch, NO behavior
> changes should be seen.
>
> The patch is against 2.6.12-rc5, but probably applies OK to recent 2.6.x
> kernels.
>
Hmm. Does not quite work here:
scsi0: Starting DV
scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.11
<Adaptec 29320 Ultra320 SCSI adapter>
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz,
512 SCBs
In DV Thread
scsi0: Beginning Domain Validation
scsi0:A:0:0: Performing DV
scsi0:2223: Going from state 0 to state 1
scsi0:A:0:0: Sending INQ
scsi0: Timeout while doing DV command 12.
And from there all hell breaks loose.
It looks as if it simply refuses to send any commands ...
Investigating.
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
prev parent reply other threads:[~2005-06-13 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 7:46 [RFT][PATCH] aic79xx: remove busyq Jeff Garzik
2005-05-29 9:21 ` Alexey Dobriyan
2005-05-30 21:28 ` J.A. Magallon
2005-05-30 22:26 ` Jeff Garzik
2005-05-30 22:42 ` J.A. Magallon
2005-05-30 22:48 ` Jeff Garzik
2005-06-13 23:14 ` J.A. Magallon
2005-06-14 21:27 ` J.A. Magallon
2005-06-13 13:56 ` Hannes Reinecke [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=42AD9089.5080006@suse.de \
--to=hare@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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