From: Andre Russ <russ@laba9.de>
To: linux-kernel@vger.kernel.org
Subject: Promise TX4 { DriveReady SeekComplete Error }
Date: Fri, 20 May 2005 11:43:39 +0200 [thread overview]
Message-ID: <d6kbem$vs2$1@ulysses.news.tiscali.de> (raw)
Hi,
I get the following error an my hardware:
May 20 11:28:30 ss1 kernel: ata6: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:28:30 ss1 kernel: ata6: called with no error (51)!
May 20 11:28:32 ss1 kernel: ata6: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:28:32 ss1 kernel: ata6: called with no error (51)!
May 20 11:28:32 ss1 kernel: ata7: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:28:32 ss1 kernel: ata7: called with no error (51)!
May 20 11:28:35 ss1 kernel: ata8: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:28:35 ss1 kernel: ata8: called with no error (51)!
May 20 11:28:43 ss1 kernel: ata5: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:28:43 ss1 kernel: ata5: called with no error (51)!
May 20 11:29:14 ss1 kernel: ata8: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:29:14 ss1 kernel: ata8: called with no error (51)!
May 20 11:29:35 ss1 kernel: ata8: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:29:35 ss1 kernel: ata8: called with no error (51)!
May 20 11:29:35 ss1 kernel: ata8: status=0x51 { DriveReady SeekComplete
Error }
May 20 11:29:35 ss1 kernel: ata8: called with no error (51)!
I am using a Promise TX4 SATAII150 controller. I have the same issue on
multiple hardwares (different boards, different processors). I am very
sure it is not a problem with the cableing or any other part in the box,
because I exchanged every part behind the controller with other parts.
HDD's and cables work excellent on a ICH6.
I tried with the latest stable kerenel (2.6.11.x) and even with the
newer 2.6.12rc4 where ordered flushing was introduced, but it does not
solve the problem.
Any ideas ?
Regards
Andre Russ
reply other threads:[~2005-05-20 9:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='d6kbem$vs2$1@ulysses.news.tiscali.de' \
--to=russ@laba9.de \
--cc=linux-kernel@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®