From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Promise ATA/133 Errors With 2.6.10+
Date: Fri, 24 Jun 2005 16:55:57 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0506241653580.31140@p34> (raw)
I have two different machines with the 7200.8 Seagate 8MB 400GB drives.
Both have ATA/133 controllers, the error is the same on both:
Jun 24 15:24:18 localhost kernel: hde: no DRQ after issuing MULTWRITE_EXT
I put the drive on an (older) Promise ATA/100 controller = works great!
I put the drive on the second box on the motherboard IDE interface = works
great!
What happened > 2.6.10 to the promise driver?
??
Jun 24 15:24:18 localhost kernel: PDC202XX: Primary channel reset.
Jun 24 15:24:18 localhost kernel: hde: timeout waiting for DMA
Jun 24 15:24:18 localhost kernel: hde: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Jun 24 15:24:18 localhost kernel:
Jun 24 15:24:18 localhost kernel: ide: failed opcode was: unknown
Jun 24 15:24:18 localhost kernel: hde: drive not ready for command
Jun 24 15:24:18 localhost kernel: hde: status timeout: status=0xd0 { Busy
}
Jun 24 15:24:18 localhost kernel:
Jun 24 15:24:18 localhost kernel: ide: failed opcode was: unknown
Jun 24 15:24:18 localhost kernel: PDC202XX: Primary channel reset.
Jun 24 15:24:18 localhost kernel: hde: no DRQ after issuing MULTWRITE_EXT
Jun 24 15:24:18 localhost kernel: ide2: reset: success
next reply other threads:[~2005-06-24 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 20:55 Justin Piszcz [this message]
2005-06-25 8:29 ` Promise ATA/133 Errors With 2.6.10+ Erik Slagter
2005-06-25 8:35 ` Justin Piszcz
2005-06-26 17:59 ` Alan Cox
2005-06-27 10:11 ` Erik Slagter
2005-06-27 11:33 ` Vojtech Pavlik
2005-06-27 11:46 ` Erik Slagter
[not found] ` <20050728223221.7f18a5a4.akpm@osdl.org>
2005-08-27 0:02 ` Justin Piszcz
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=Pine.LNX.4.63.0506241653580.31140@p34 \
--to=jpiszcz@lucidpixels.com \
--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