From: Alan <alan@lxorguk.ukuu.org.uk>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Parag Warudkar <kernel-stuff@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: CD/DVD drive errors and lost ticks
Date: Sat, 9 Dec 2006 13:25:42 +0000 [thread overview]
Message-ID: <20061209132542.6bcfc864@localhost.localdomain> (raw)
In-Reply-To: <457A28FF.4030508@scientia.net>
> I've also hat some errors like this:
> hdb: irq timeout: status=0xd0 { Busy }
> ide: failed opcode was: unknown
> hdb: DMA disabled
The drive went away and stopped talking
> hdb: ATAPI reset complete
> hdb: irq timeout: status=0x80 { Busy }
> ide: failed opcode was: unknown
> hdb: ATAPI reset complete
> hdb: irq timeout: status=0x80 { Busy }
> ide: failed opcode was: unknown
> hdb: cdrom_read_intr: data underrun (4 blocks)
> end_request: I/O error, dev hdb, sector 7831400
> Buffer I/O error on device hdb, logical block 1957850
And eventually got back to sanity
> That happened on a DVD (successfully read in and played by the drive),..
> but when I pushed the eject button (while xine sill was playing) I got
> those errors,..
> I assume that xine continued to read data but the DVD was already
> ejected and thus the request errors....
> But I think there shouldn't be a request error but more something like
> "no medium found" or the eject button should have been disabled at
> all,... so I think something goes really wrong with that drive ;)
The requests were outstanding so the behaviour is expected. As to the
eject button - Xine chooses not to lock the drive. I don't know why it
prefers to work that way but it's an application choice on the whole.
next prev parent reply other threads:[~2006-12-09 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 15:52 Parag Warudkar
2006-12-09 3:09 ` Christoph Anton Mitterer
2006-12-09 13:25 ` Alan [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-03 4:08 Christoph Anton Mitterer
2006-12-03 4:30 ` Parag Warudkar
2006-12-03 15:01 ` Christoph Anton Mitterer
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=20061209132542.6bcfc864@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=calestyo@scientia.net \
--cc=kernel-stuff@comcast.net \
--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
Powered by JetHome