From: Mark Haverkamp <markh@osdl.org>
To: Christoffer Hall-Frederiksen <hall@jiffies.dk>
Cc: linux-scsi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux aacraid devel <linux-aacraid-devel@dell.com>
Subject: Re: Problem with aacraid driver in 2.5.63-bk-latest
Date: 12 Mar 2003 15:06:21 -0800 [thread overview]
Message-ID: <1047510381.12193.28.camel@markh1.pdx.osdl.net> (raw)
In-Reply-To: <20030228133037.GB7473@jiffies.dk>
On Fri, 2003-02-28 at 05:30, Christoffer Hall-Frederiksen wrote:
> I have a dell poweredge 1650 with a perc3/DI controller. When the
> AACRAID driver loads it stops with the following lines:
>
> AAC0: kernel 2.7.4 build 3170
> AAC0: monitor 2.7.4 build 3170
> AAC0: bios 2.7.0 build 3170
> AAC0: serial 0b9c810d3
> scsi0 : percraid
>
We just ran into this too at osdl. I have something that gets the
driver to load, but I'm not sure what the right thing is to do.
The cmd_per_lun element of the driver_template is set to
AAC_NUM_IO_FIB. This is 512.
During probe, scsi_alloc_sdev is called. It calls
scsi_adjust_queue_depth with the cmd_per_lun value.
scsi_adjust_queue_depth returns without doing anything if the tags value
is greater than 256. This leaves the Scsi_Device queue_depth at zero.
Later when an I/O is queued, scsi_request_fn checks for device_busy >=
queue_depth. If so, the function does a break and exits. This is where
it hangs.
To get things to load I set cmd_per_lun to 256. I don't know if the is
the correct way to deal with the problem. Maybe someone else can say
something about that.
===== drivers/scsi/aacraid/linit.c 1.12 vs edited =====
--- 1.12/drivers/scsi/aacraid/linit.c Mon Feb 24 13:03:30 2003
+++ edited/drivers/scsi/aacraid/linit.c Wed Mar 12 14:32:18 2003
@@ -693,7 +693,7 @@
this_id: 16,
sg_tablesize: 16,
max_sectors: 128,
- cmd_per_lun: AAC_NUM_IO_FIB,
+ cmd_per_lun: 256,
eh_abort_handler: aac_eh_abort,
eh_device_reset_handler:aac_eh_device_reset,
eh_bus_reset_handler: aac_eh_bus_reset,
--
Mark Haverkamp <markh@osdl.org>
next parent reply other threads:[~2003-03-12 22:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030228133037.GB7473@jiffies.dk>
2003-03-12 23:06 ` Mark Haverkamp [this message]
2003-03-13 0:18 ` Alan Cox
2003-03-12 23:55 ` Douglas Gilbert
2003-03-13 1:06 ` Alan Cox
2003-03-13 0:50 ` Mike Anderson
2003-03-13 23:13 ` Mark Haverkamp
2003-03-14 7:05 ` Denis Vlasenko
2003-03-14 10:18 ` Mike Anderson
2003-03-13 1:31 ` Douglas Gilbert
2003-03-13 23:27 ` Doug Ledford
2003-03-13 15:42 ` Mark Haverkamp
2003-03-13 23:17 ` Doug Ledford
2003-03-13 23:22 ` Mark Haverkamp
2003-03-13 23:25 ` Doug Ledford
2003-03-14 14:57 ` Alan Cox
2003-03-14 15:34 ` Mark Haverkamp
2003-03-14 16:48 ` Alan Cox
2003-03-03 10:05 Christoffer Hall-Frederiksen
2003-03-03 13:40 ` Alan Cox
2003-03-03 14:46 ` Christoffer Hall-Frederiksen
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=1047510381.12193.28.camel@markh1.pdx.osdl.net \
--to=markh@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hall@jiffies.dk \
--cc=linux-aacraid-devel@dell.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
all inboxes | Powered by JetHome®