From: Jens Axboe <axboe@suse.de>
To: PROFETA Mickael <profeta@crans.ens-cachan.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide retry on 2.4.5-ac7
Date: Mon, 4 Jun 2001 23:09:33 +0200 [thread overview]
Message-ID: <20010604230932.A23128@suse.de> (raw)
In-Reply-To: <20010604140207.A529@alezan.dyndns.org> <20010604221404.A19333@suse.de> <20010604230215.A6188@alezan.dyndns.org>
In-Reply-To: <20010604230215.A6188@alezan.dyndns.org>; from profeta@crans.ens-cachan.fr on Mon, Jun 04, 2001 at 11:02:15PM +0200
On Mon, Jun 04 2001, PROFETA Mickael wrote:
> On Mon, Jun 04, 2001 at 10:14:04PM +0200, Jens Axboe wrote:
> >
> > It worked sucessfully for you in 2.4.5-ac4 but not in -ac7? I can't see
> > any changes to the patch, so more details on the nature of the problem
> > would be helpful.
>
> Ok, this is the results of a hdparm -tT on my second hard disk:
>
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
> ide1: reset: success
> 64 MB in 7.03 seconds = 9.10 MB/sec
>
> and then the kernel has shifted to udma3 and I have no more error in this
> session with that hard disk
>
> I tried the same thing on -ac7 and I always have the errors, the kernel does
> not reset ide... Looking at the different change on ac patches, I can not see
> why...
This is not the case that is attempted solve. The above could be a cable
error (it looks like it). These are usually genuine and indicate a real
hw problem.
--
Jens Axboe
next prev parent reply other threads:[~2001-06-04 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 12:02 ide retry on 2.4.5-ac7 PROFETA Mickael
2001-06-04 20:14 ` Jens Axboe
2001-06-04 21:02 ` PROFETA Mickael
2001-06-04 21:09 ` Jens Axboe [this message]
2001-06-04 21:25 ` PROFETA Mickael
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=20010604230932.A23128@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=profeta@crans.ens-cachan.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.