linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Oliver <lists@foxhill.co.uk>
To: linux-ide@vger.kernel.org
Subject: Lockup when using three or more TX2plus/PDC20375 cards
Date: Tue, 02 Aug 2005 16:35:13 +0100	[thread overview]
Message-ID: <VA.00001960.01b93e16@foxhill.co.uk> (raw)

Hi,

I am using Ubuntu Hoary with the standard 2.6.10 kernel.
I have 4x Maxtor SATA cards using the PDC20375 (rebranded Promise 
TX2plus) in PCI slots. Each drive is cabled to 2 SATA HDs and these are 
used as two groups of four for software raid using mdadm. Boot drive is 
a non-raid PATA drive.

When I really hammer the sw raid that's on two of the cards it will 
generate lots of these in the log -
Jul 25 17:33:42 localhost kernel: ata7: status=0x51 { DriveReady 
SeekComplete Error }
Jul 25 17:33:42 localhost kernel: ata7: error=0x0c { DriveStatusError }

then I get the following on the console -
ata7: command timeout
and then the whole machine locks solid.

I can do whatever I like to the raid on the 1st four cards and it seems 
rock solid.

I hear talk of 3rd and subsequent cards not being initialised by the 
BIOS, and my "lspci -v" results back this up. (Please see 
http://bugzilla.ubuntu.com/show_bug.cgi?id=13046 rather than cluttering 
this list.)

How can I address this problem? I have just built a 2.6.10 kernel and 
modules (very much a first for me) so I think I can apply patches and 
try things out.

Note that I think Ubuntu has some patches from later kernels applied to 
their libata to add pass through, but I don't know the status of the 
sata_promise.

Regards

Ian




             reply	other threads:[~2005-08-02 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 15:35 Ian Oliver [this message]
2005-08-03 14:16 ` Lockup when using three or more TX2plus/PDC20375 cards Jarrod Johnson

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=VA.00001960.01b93e16@foxhill.co.uk \
    --to=lists@foxhill.co.uk \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).