public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Con Kolivas <kernel@kolivas.org>
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 11:28:25 +0200	[thread overview]
Message-ID: <20040606092825.GD2733@suse.de> (raw)
In-Reply-To: <200406060007.10150.kernel@kolivas.org>

On Sun, Jun 06 2004, Con Kolivas wrote:
> Well since 2.6.3 I think I've been getting the record number of 
> 
> hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hdd: status error: error=0x00
> hdd: drive not ready for command
> hdd: ATAPI reset complete
> 
> errors from my cdrw on hdd; and it's only one drive's worth.
> 
> 
> dmesg -s 32768 | grep DataRequest | wc -l
> 88
> 
> Note the -s 32768 is because my dmesg is so long due to the massive
> number of seekcomplete errors :-)
> 
> Since the cdrw works fine after re-enabling dma I never really
> bothered to do anything about it, but I'm just curious if anyone has a
> higher record ;-)

Interesting, and 2.6.2 works flawlessly? The only change in 2.6.3 wrt
ide-cd is the addition of the != 2kB sector size support from Pascal
Schmidt. A quick guess would be that blocklen isn't set, does this
change anything for you?

===== drivers/ide/ide-cd.c 1.83 vs edited =====
--- 1.83/drivers/ide/ide-cd.c	2004-05-29 19:04:42 +02:00
+++ edited/drivers/ide/ide-cd.c	2004-06-06 11:27:51 +02:00
@@ -2205,6 +2205,8 @@
 		*capacity = 1 + be32_to_cpu(capbuf.lba);
 		*sectors_per_frame =
 			be32_to_cpu(capbuf.blocklen) >> SECTOR_BITS;
+		if (*sectors_per_frame == 0)
+			*sectors_per_frame = SECTORS_PER_FRAME;
 	}
 
 	return stat;

-- 
Jens Axboe


  parent reply	other threads:[~2004-06-06  9:28 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 [this message]
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
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=20040606092825.GD2733@suse.de \
    --to=axboe@suse.de \
    --cc=der.eremit@email.de \
    --cc=kernel@kolivas.org \
    --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