From: Ryan Anderson <ryan@autoweb.net>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-scsi@vger.kernel.org
Subject: RE: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraidPERC 3/Di Container goes offline
Date: Tue, 23 Nov 2004 17:15:53 -0500 [thread overview]
Message-ID: <1101248153.26294.84.camel@ryan2.internal.autoweb.net> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458B694F1B@otce2k01.adaptec.com>
[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]
On Tue, 2004-11-23 at 17:07 -0500, Salyzyn, Mark wrote:
> Do you have the latest Firmware from Dell? Do you have the Read and
> Write Cache disabled as Dell has recommended (for pre 6091(?) Firmware)?
The latest Dell firmware that I have seen is 6092, which would seem to
make your second question irrelevant. Is that correct?
dmesg says this about the controller:
AAC0: kernel 2.8.4 build 6092
AAC0: monitor 2.8.4 build 6092
AAC0: bios 2.8.0 build 6092
AAC0: serial 83ac41d3fafaf001
scsi0 : percraid
Vendor: DELL Model: PERCRAID RAID5 Rev: V1.0
Type: Direct-Access ANSI SCSI revision: 02
Vendor: DELL Model: PERCRAID RAID5 Rev: V1.0
Type: Direct-Access ANSI SCSI revision: 02
> The `container going offline' is a result of the Firmware in the card
> not responding to a SCSI command within 60 seconds (the Linux SCSI layer
> timeout). In the older firmware this would occur at the combination of
> high load, drive or scsi bus problems and the card flushing the cache.
> If the problem persists, preventing the card building up a large amount
> of cache data may be the only way to mitigate this.
Ok, I can experiment with this. Where should I start? (I'm not afraid
of source-level hacking, just don't know where to start.)
> I have had others experiment with overriding the SCSI timeout (the
> Adaptec driver branch has an AAC_EXTENDED_TIMEOUT) to limited success.
> Turning off the SCSI timeout (add a scsi_del_timer as command is issued
> to the controller, and a scsi_add_timer in the interrupt service routine
> before completion) worked extremely well, but this makes me
> understandably nervous.
That completely disables *any* timeout, correct?
That would make me a .. bit nervous, too.
I'm going to try to build a load today that can trigger the problem.
(It's rather hard to debug when the problem is very hard to trigger -
sigh)
--
Ryan Anderson
AutoWeb Communications, Inc.
email: ryan@autoweb.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-23 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 22:07 Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraidPERC 3/Di Container goes offline Salyzyn, Mark
2004-11-23 22:15 ` Ryan Anderson [this message]
2004-11-23 22:35 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 12:59 Salyzyn, Mark
2004-11-24 13:09 ` Christoph Hellwig
2004-11-24 14:58 ` Brian King
2004-11-24 20:29 ` Mike Christie
2004-11-24 20:28 ` Brian King
2004-11-24 20:31 ` Mike Christie
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=1101248153.26294.84.camel@ryan2.internal.autoweb.net \
--to=ryan@autoweb.net \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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