From: Jens Axboe <axboe@suse.de>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.46: ide-cd cdrecord (almost) success report
Date: Thu, 7 Nov 2002 15:33:14 +0100 [thread overview]
Message-ID: <20021107143314.GC32005@suse.de> (raw)
In-Reply-To: <20021106232529.GC27210@www.kroptech.com>
On Wed, Nov 06 2002, Adam Kropelin wrote:
> On Wed, Nov 06, 2002 at 08:44:57AM +0100, Jens Axboe wrote:
> > On Wed, Nov 06 2002, Jens Axboe wrote:
> > > > when the cdrecord buffer underran was surprising, though: oops below.
> > > > Very repeatable. Can supply copious hw details if it helps.
> > >
> > > I'll try and reproduce that here, there's been a similar report (same
> > > oops) before. If you can just send me the dmesg output after a boot that
> > > should be fine.
> >
> > Could you reproduce with this patch? I'd like to see the request state
> > when this happens.
>
> Here you go... This was with max tags locked at 4. I've included some of
> the surrounding lines from cdrecord.
ok
> --Adam
>
> Track 01: 85 of 437 MB written (fifo 0%) [buf 31%] 3.3x./opt/schily/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error
> CDB: 2A 00 00 00 AA BE 00 00 1F 00
> status: 0x1 (GOOD STATUS)
> resid: 63488
> cmd finished after 0.011s timeout 40s
>
> write track data: error after 89518080 bytes
> cdrom_newpc_intr: dev hdc: flags = REQ_RW REQ_NOMERGE REQ_STARTED REQ_BLOCK_PC REQ_FAILED REQ_QUIET
> sector 0, nr/cnr 124/8
> bio 00000000, biotail c1cd0860, buffer c968d000, data 00000000, len 63488
> cdb: 2a 00 00 00 aa be 00 00 1f 00 00 00 00 00 00 00
> hdc: padding 63488 bytes
> Sense Bytes: 70 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00
>From the ide-cd POV, the best we can do here is just try to continue
safely in case of error. So a slight modification to last patch should
be fine, I think.
At least that is the atapi part of.
===== drivers/ide/ide-cd.c 1.32 vs edited =====
--- 1.32/drivers/ide/ide-cd.c Sun Nov 3 19:57:35 2002
+++ edited/drivers/ide/ide-cd.c Thu Nov 7 15:25:05 2002
@@ -1722,6 +1722,11 @@
blen = bio_iovec(rq->bio)->bv_len;
}
+ if (!ptr) {
+ printk("%s: confused, missing data\n", drive->name);
+ break;
+ }
+
if (blen > thislen)
blen = thislen;
@@ -1741,8 +1746,6 @@
* pad, if necessary
*/
if (len) {
- printk("%s: padding %u bytes\n", drive->name, len);
-
while (len) {
int pad = 0;
--
Jens Axboe
next prev parent reply other threads:[~2002-11-07 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 4:13 2.5.46: ide-cd cdrecord (almost) success report Adam Kropelin
2002-11-06 7:22 ` Jens Axboe
2002-11-06 7:44 ` Jens Axboe
2002-11-06 23:25 ` Adam Kropelin
2002-11-07 14:33 ` Jens Axboe [this message]
2002-11-06 15:56 ` Adam Kropelin
2002-11-06 18:11 ` Patrick Mansfield
2002-11-06 23:33 ` Adam Kropelin
2002-11-06 23:52 ` Patrick Mansfield
2002-11-07 0:05 ` Adam Kropelin
2002-11-06 18:45 ` Jens Axboe
2002-11-06 23:23 ` Adam Kropelin
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=20021107143314.GC32005@suse.de \
--to=axboe@suse.de \
--cc=akropel1@rochester.rr.com \
--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.