From: Moritz Muehlenhoff <jmm@informatik.uni-bremen.de>
To: linux-kernel@vger.kernel.org
Cc: "Barry K. Nathan" <barryn@pobox.com>
Subject: Re: [BUG] 100% reproducible oops on ATAPI CD-ROM I/O error, 2.5.75
Date: Mon, 14 Jul 2003 00:10:08 +0200 [thread overview]
Message-ID: <E19bp2m-0006gf-00@regenbogen.informatik.uni-bremen.de> (raw)
In-Reply-To: <20030711093335.GC2860@ip68-4-255-84.oc.oc.cox.net>
In stuga.ml.linux.kernel, you wrote:
> I added this as a comment to bugme.osdl.org bug 878, but here's a
> cleaned-up version of the reproduction instructions:
>
> 5. readcd dev=/dev/hdc f=/dev/null
> (readcd chokes near the end of the CD, tries reading again, and oopses
> the kernel)
With kernel 2.5.75-bk3 it doesn't oops neither on my CD-RW, nor on
my CD-ROM. I guess that's related to ChangeSet@1.486 from Jens Axboe
[PATCH] Fix IDE-CD command failure re-play
Does anyone have an explanation why cdrecord fails to write the last
sector properly? Is this a kernel issue or a bug in cdrecord?
I'm using cdrtools 2.01a15.
next prev parent reply other threads:[~2003-07-13 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 9:33 [BUG] 100% reproducible oops on ATAPI CD-ROM I/O error, 2.5.75 Barry K. Nathan
2003-07-13 22:10 ` Moritz Muehlenhoff [this message]
2003-07-14 2:18 ` Barry K. Nathan
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=E19bp2m-0006gf-00@regenbogen.informatik.uni-bremen.de \
--to=jmm@informatik.uni-bremen.de \
--cc=barryn@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).