From: Con Kolivas <kernel@kolivas.org>
To: Jens Axboe <axboe@suse.de>
Cc: Pascal Schmidt <der.eremit@email.de>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Who has record no. of DriveReady SeekComplete DataRequest errors?
Date: Mon, 7 Jun 2004 09:06:46 +1000 [thread overview]
Message-ID: <200406070906.46392.kernel@kolivas.org> (raw)
In-Reply-To: <20040606203942.GA20267@suse.de>
On Mon, 7 Jun 2004 06:39, Jens Axboe wrote:
> I could easily imagine some vendors not setting the field, but setting
> it to some "buggy" value is far less likely. But might as well add the
> check.
>
> Con later confirmed that it was 2.6.2 that introduced the breakage, so
> the patch isn't the culprit after all. There are a few seperate things
> to look at there - Con, what are you doing when these messages trigger?
> Is the drive permanently mounted, or does it happen on open?
It only happens on boot and never again. During this part:
ICH4: IDE controller at PCI slot 0000:00:1f.1
ICH4: chipset revision 2
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: ST340014A, ATA DISK drive
hdb: ST340014A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: JLMS XJ-HD165H, ATAPI CD/DVD-ROM drive
hdd: RICOH CD-R/RW MP7163A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
hda: hda1 hda2 < hda5 hda6 hda7 >
hdb: max request size: 1024KiB
hdb: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
hdb: hdb2 < hdb5 hdb6 hdb7 >
hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x20LastFailedSense 0x02
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
..etc
I'll try that other patch when I get a chance later today.
Con
next prev parent reply other threads:[~2004-06-06 23:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 14:07 [OT] Who has record no. of DriveReady SeekComplete DataRequest errors? Con Kolivas
2004-06-05 14:24 ` Jan Dittmer
2004-06-06 9:28 ` Jens Axboe
2004-06-06 10:38 ` Con Kolivas
2004-06-06 10:58 ` Jens Axboe
2004-06-06 11:05 ` Con Kolivas
2004-06-06 11:10 ` Jens Axboe
2004-06-06 11:37 ` Con Kolivas
2004-06-06 11:51 ` Con Kolivas
2004-06-06 12:11 ` Pascal Schmidt
2004-06-06 20:39 ` Jens Axboe
2004-06-06 23:06 ` Con Kolivas [this message]
2004-06-07 0:21 ` Grant Byers
2004-06-07 7:24 ` Jens Axboe
2004-06-07 9:18 ` Con Kolivas
2004-06-07 9:36 ` Jens Axboe
2004-06-07 9:50 ` Con Kolivas
2004-06-07 9:54 ` Jens Axboe
2004-06-07 10:08 ` Con Kolivas
2004-06-07 10:17 ` Jens Axboe
2004-06-07 10:29 ` Con Kolivas
2004-06-07 10:33 ` Jens Axboe
2004-06-07 16:29 ` Jens Axboe
2004-06-07 17:59 ` Jan Dittmer
2004-06-07 18:06 ` Jens Axboe
2004-06-08 13:50 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2004-06-05 18:01 Steve Lee
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=200406070906.46392.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=axboe@suse.de \
--cc=der.eremit@email.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 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.