From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Erik Slagter <erik@slagter.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Promise ATA/133 Errors With 2.6.10+
Date: Sat, 25 Jun 2005 04:35:22 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0506250435110.32759@p34> (raw)
In-Reply-To: <1119688191.4293.5.camel@localhost.localdomain>
On Sat, 25 Jun 2005, Erik Slagter wrote:
> On Fri, 2005-06-24 at 16:55 -0400, Justin Piszcz wrote:
>
>> 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
>
> I have exactly this (these messages) but then with a amd/via ata driver
> on tyan/amd motherboard with an IBM/Hitachi harddisk.
>
> It looks like the drive cpu locks up every now and then, notably when
> the environmental temperature and/or the drive's temperature are high
> and there is much activity on the drive.
>
> A reset (either from the driver or manually using hdparm) helps
> (temporarily).
>
> I was going to buy new drives for this fact (from another brand) but it
> looks that won't necessarily mean my problem will be solved :-(
>
> BTW I have another, exactly identical harddisk in the same computer
> (well, ok, 1 year younger) and that one doesn't show the problem.
>
> BTW2 could it be that somewhere a timeout has been lowered in recent
> kernels? That must have been pre-2.6.11 then.
>
^^
I think so!
The box has worked for the past 6 months and started to have hiccups when
I upgraded it to 2.6.11.x or 2.6.12.x.
next prev parent reply other threads:[~2005-06-25 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 20:55 Promise ATA/133 Errors With 2.6.10+ Justin Piszcz
2005-06-25 8:29 ` Erik Slagter
2005-06-25 8:35 ` Justin Piszcz [this message]
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.0506250435110.32759@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=erik@slagter.name \
--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