From: Tejun Heo <htejun@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: kekcsibe@gmail.com, Borislav Petkov <petkovbb@googlemail.com>,
linux-ide <linux-ide@vger.kernel.org>
Subject: Re: [kekcsibe@gmail.com: PROBLEM: Pioneer DVD-RW DVR-112D does not work since linux 2.6.29]
Date: Sat, 06 Feb 2010 09:33:28 +0900 [thread overview]
Message-ID: <4B6CB8D8.8090304@gmail.com> (raw)
In-Reply-To: <4B633A49.8000700@gmail.com>
Hello,
On 01/30/2010 04:43 AM, Robert Hancock wrote:
> kazimir:~# mount /cdrom
> sr 1:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08
> sr 1:0:0:0: [sr0] Sense Key : 0x5 [current]
> sr 1:0:0:0: [sr0] <<vendor>> ASC=0xa8 ASCQ=0x1ASC=0xa8 ASCQ=0x1
> sr 1:0:0:0: [sr0] CDB: cdb[0]=0x28: 28 00 00 00 00 10 00 00 02 00
> end_request: I/O error, dev sr0, sector 64
> Buffer I/O error on device sr0, logical block 8
>
> The kernel tried to read some sectors off the disk (command 0x28) and
> the drive returned an error. ASC of 0xa8 is a vendor-specific error
> code, so only Pioneer can likely say what that error means.
>
> You're sure that 2.6.22 is still able to successfully access this drive?
> Any unusual dmesg output there?
One thing which could affect this is the change in the isofs code.
Locating the anchor blocks for isofs involves some guesswork and that
part has changed somewhat during past several releases. Different
kernel versions would request different sequence of blocks. It could
be that access to certain sectors is confusing the drive.
Thanks.
--
tejun
prev parent reply other threads:[~2010-02-06 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 4:48 [kekcsibe@gmail.com: PROBLEM: Pioneer DVD-RW DVR-112D does not work since linux 2.6.29] Borislav Petkov
2010-01-29 19:43 ` Robert Hancock
2010-02-06 0:33 ` Tejun Heo [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=4B6CB8D8.8090304@gmail.com \
--to=htejun@gmail.com \
--cc=hancockrwd@gmail.com \
--cc=kekcsibe@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=petkovbb@googlemail.com \
/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).