From: David Haring <david.haring@billboard.cz>
To: linux-scsi@vger.kernel.org
Cc: Ari <ari@goron.de>, abba@cs.sunysb.edu
Subject: Re: [2.4.25], [aic79xx-2.0.8] problems with aic79xx on 2.4 (fwd)
Date: Tue, 06 Apr 2004 23:24:35 +0200 [thread overview]
Message-ID: <40732013.2080904@billboard.cz> (raw)
In-Reply-To: <20040406212126.A30706@www.goron.de>
Hello,
I would recommend reducing TCQ depth too - I have also had
troubles with recent Maxtor Atlas disks / Adaptec / aic79xx
and reducing TCQ depth solved the problem.
Interesting note though - the troubles only showed with Adaptec
controller. When I have replaced the Adaptec aic79xx SCSI card
with Tekram Ultra320 one the system worked without problem.
Ari wrote:
>
> Hi,
> I've ran into similar problems with the same controller and same disks
> (Maxtor Atlas 10K4 73G WLS, mine are revision DFV0 however).
> After a lot of frustration including changing all related hardware,
> especially the cabling, resultless googling, etc, I found the solution:
> Speeding down the disks does not really help. It works better, but under
> stress load (3 bonnie++ at the same time) they quickly produce lost
> SCB commands, even at 80Mhz.
> What fixed it for me was limiting the Tagged Queuing depth to 16 (in
> kernel config). After my raid5 array worked flawlessly under a 24h
> 3 simultaneous bonnie++ test.
> I've found some hints googling that there might be a firmware problem
> related to this (which should be fixed with the DFV0 version on my
> drives, but obviously is not).
> Anyhow, try to reduce tagged queuing to 16, if that fixes it, it will
> also confirm my findings.
David Haring
next prev parent reply other threads:[~2004-04-06 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 19:21 [2.4.25], [aic79xx-2.0.8] problems with aic79xx on 2.4 (fwd) Ari
2004-04-06 21:24 ` David Haring [this message]
2004-04-15 16:42 ` Abhishek Rai
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 23:41 Abhishek Rai
2004-04-02 14:13 ` Matthew Wilcox
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=40732013.2080904@billboard.cz \
--to=david.haring@billboard.cz \
--cc=abba@cs.sunysb.edu \
--cc=ari@goron.de \
--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