From: Gregory Boyce <gboyce@badbelly.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Burning CDs with a CD-ROM is a bad idea
Date: Sat, 15 May 2004 10:17:21 -0400 [thread overview]
Message-ID: <1084630641.1540.8.camel@qube.badbelly.com> (raw)
In-Reply-To: <20040515104752.GC24600@suse.de>
On Sat, 2004-05-15 at 06:47, Jens Axboe wrote:
> On Fri, May 14 2004, gboyce@badbelly.com wrote:
> > Hello folks,
> >
> > Yesterday I made a slight thinko while attempting to burn a CD. Rather
> > than specifying dev=/dev/hdd, I add dev=/dev/hdc, which is my CD-ROM
> > drive rather than my cd burner. Whoops!
> >
> > Now, I believe I've done this before, and recieved an error message.
> > However, in this particular case with 2.6.6, the system behaved a bit
> > different.
> >
> > bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
> > cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
> > ide-cd: cmd 0x1e timed out
> > hdc: lost interrupt
>
> Looks like one of the burning commands confused the drive so much, that
> it now refuses to do anything (the above command is a simple medium
> removal prevention command, doesn't even need a data transfer).
>
> So I don't think this is a kernel problem. Well maybe we could reset the
> device and see if it recovers (do you see any resets in the log?)
There was a reset early on, but it was before the majority of errors.
Here is the begining of problem:
May 13 16:38:14 cthulhu hdc: DMA interrupt recovery
May 13 16:38:14 cthulhu hdc: lost interrupt
May 13 16:38:14 cthulhu hdc: status timeout: status=0xd0 { Busy }
May 13 16:38:14 cthulhu hdc: status timeout: error=0x00
May 13 16:38:14 cthulhu hdc: DMA disabled
May 13 16:38:14 cthulhu hdc: drive not ready for command
May 13 16:38:15 cthulhu hdc: ATAPI reset complete
May 13 16:38:15 cthulhu cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC
May 13 16:38:15 cthulhu sector 0, nr/cnr 0/0
May 13 16:38:15 cthulhu bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
May 13 16:38:15 cthulhu cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 13 16:38:15 cthulhu hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
May 13 16:39:15 cthulhu ide-cd: cmd 0x1e timed out
May 13 16:39:15 cthulhu hdc: lost interrupt
May 13 16:39:15 cthulhu cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
May 13 16:39:15 cthulhu sector 0, nr/cnr 0/0
May 13 16:39:15 cthulhu bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
May 13 16:39:15 cthulhu cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 13 16:39:15 cthulhu hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
There are an additional 700K of errors like this before I finally
rebooted the machine the next day. The machine also refused to let me
burn CDs on the actual CD burner during this time.
--
Greg
prev parent reply other threads:[~2004-05-15 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 17:58 gboyce
2004-05-15 10:47 ` Jens Axboe
2004-05-15 14:17 ` Gregory Boyce [this message]
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=1084630641.1540.8.camel@qube.badbelly.com \
--to=gboyce@badbelly.com \
--cc=axboe@suse.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
all inboxes | Powered by JetHome®