public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	der.eremit@email.de
Subject: Re: [OT] Who has record no. of  DriveReady SeekComplete DataRequest errors?
Date: Sun, 6 Jun 2004 21:51:41 +1000	[thread overview]
Message-ID: <200406062151.41224.kernel@kolivas.org> (raw)
In-Reply-To: <200406062137.27323.kernel@kolivas.org>

On Sun, 6 Jun 2004 21:37, Con Kolivas wrote:
> On Sun, 6 Jun 2004 21:10, Jens Axboe wrote:
> > On Sun, Jun 06 2004, Con Kolivas wrote:
> > > On Sun, 6 Jun 2004 20:58, Jens Axboe wrote:
> > > > On Sun, Jun 06 2004, Con Kolivas wrote:
> > > > > On Sun, 6 Jun 2004 19:28, Jens Axboe wrote:
> > > > > > On Sun, Jun 06 2004, Con Kolivas wrote:
> > > > > > > hdd: status error: status=0x58 { DriveReady SeekComplete
> > > > > > > DataRequest } hdd: status error: error=0x00
> > > > > > > hdd: drive not ready for command
> > > > > > > hdd: ATAPI reset complete
> > > >
> > > > I'll take a better look then. Can you check if backing out the entire
> > > > change makes 2.6.7-rcX work? I've attached it for you.
> > >
> > > drivers/ide/ide-cd.c: In function `cdrom_start_read_continuation':
> > > drivers/ide/ide-cd.c:1279: warning: implicit declaration of function
> > > `MIN'
> > >
> > > followed by
> > > drivers/built-in.o(.text+0x687cf): In function
> > > `cdrom_start_read_continuation':
> > > drivers/ide/ide-cd.c:1279: undefined reference to `MIN'
> > > make: *** [.tmp_vmlinux1] Error 1
> >
> > Ah fudge, can you make the obvious corrections and test that?
>
> I sorted out the compile error but I still get my 88 errors.

Ok I've gone and rebooted into all kernels from 2.6.0 to now and discovered I 
was off by one sorry. The errors occur from 2.6.2 onwards. Hopefully that 
helps?

Con

  reply	other threads:[~2004-06-06 11:52 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 [this message]
2004-06-06 12:11   ` Pascal Schmidt
2004-06-06 20:39     ` Jens Axboe
2004-06-06 23:06       ` Con Kolivas
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=200406062151.41224.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox