From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Geert Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>
Cc: linux-scsi@vger.kernel.org,
"Linux Kernel Development" <linux-kernel@vger.kernel.org>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Maarten Bressers" <mbres@gentoo.org>,
"Daniel Drake" <dsd@gentoo.org>,
"Cell Broadband Engine OSS Development" <cbe-oss-dev@ozlabs.org>
Subject: Re: [Cbe-oss-dev] [regression/bisected] corrupt CD data after media change and delay
Date: Sun, 22 Jun 2008 15:14:33 +0200 [thread overview]
Message-ID: <5a4c581d0806220614seab6598ufa798d8642295495@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806221018220.9736@vixen.sonytel.be>
On Sun, Jun 22, 2008 at 10:18 AM, Geert Uytterhoeven
<Geert.Uytterhoeven@sonycom.com> wrote:
> On Sat, 21 Jun 2008, Alessandro Suardi wrote:
>> On Wed, Jun 18, 2008 at 2:15 PM, Alessandro Suardi
>> <alessandro.suardi@gmail.com> wrote:
>> > On Wed, Jun 18, 2008 at 1:13 PM, Geert Uytterhoeven
>> > <Geert.Uytterhoeven@sonycom.com> wrote:
>> >> On Wed, 18 Jun 2008, Alessandro Suardi wrote:
>> >>> On Fri, Jun 13, 2008 at 7:33 PM, Geert Uytterhoeven
>> >>> <Geert.Uytterhoeven@sonycom.com> wrote:
>> >>> > On Fri, 6 Jun 2008, Geert Uytterhoeven wrote:
>> >>> >> When mounting a CD/DVD more than 30 seconds after inserting it, and reading
>> >>> >> from it, we get:
>> >>> >
>> >>> > Apparently the fix didn't make it to all the CCed lists...
>> >>> >
>> >>> > http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fjejb%2Fscsi-rc-fixes-2.6.git;a=commitdiff_plain;h=d1daeabf0da5bfa1943272ce508e2ba785730bf0
>> >>>
>> >>> Oh, that's in mainline ? I still have the problem of having to
>> >>
>> >> Not yet, it's in the scsi-rc-fixes-2.6 tree.
>> >>
>> >>> insert DVD / try accessing it and get errors / eject / re-insert
>> >>> and then it magically works... the messages have changed
>> >>> from what they were as reported here
>> >>>
>> >>> http://bugzilla.kernel.org/show_bug.cgi?id=10116
>> >>>
>> >>> (see comments #8 and #9) to these ones, in 2.6.26-rc6-git4:
>> >>>
>> >>> Jun 17 22:38:43 sandman kernel: sr 1:0:0:0: [sr0] Result:
>> >>> hostbyte=0x00 driverbyte=0x08
>> >>> Jun 17 22:38:43 sandman kernel: sr 1:0:0:0: [sr0] Sense Key : 0x3 [current]
>> >>> Jun 17 22:38:43 sandman kernel: sr 1:0:0:0: [sr0] ASC=0x11 ASCQ=0x0
>> >>> Jun 17 22:38:43 sandman kernel: end_request: I/O error, dev sr0, sector 232
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 29
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 30
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 31
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 32
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 33
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 34
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 35
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 36
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 37
>> >>> Jun 17 22:38:43 sandman kernel: Buffer I/O error on device sr0, logical block 38
>> >>>
>> >>> here I eject and reinsert the disc, and:
>> >>>
>> >>> Jun 17 22:39:10 sandman kernel: UDF-fs: No VRS found
>> >>>
>> >>> lo and behold, no problem.
>> >>>
>> >>> This does not, alas, happen every time. It might be at the first
>> >>> DVD access after booting the laptop, but I haven't investigated
>> >>> in this detail yet.
>> >>
>> >> Does /sys/block/sr0/size reflect the correct size of the DVD?
>> >>
>> >> Did you try applying the patch?
>> >
>> > ATM I'm away from home (as usual), I'll post back when
>> > I have the info you asked for and tried applying the
>> > above patch. Thanks !
>>
>> Sigh. I haven't been able to reproduce the problem once since
>> I posted this. Will keep trying...
>
> Perhaps because the fix is now in mainline?
Eh, that may be a reason :)
I'm indeed tracking mainline and haven't reproduced with
at least six different discs in -rc7.
--alessandro
"Give me love / Or give me hate
Give me anything that's not just ok"
(Sophia, 'Weightless')
next prev parent reply other threads:[~2008-06-22 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 14:06 [regression/bisected] corrupt CD data after media change and delay Geert Uytterhoeven
2008-06-06 15:13 ` James Bottomley
2008-06-06 17:27 ` Geert Uytterhoeven
2008-06-09 12:54 ` Geert Uytterhoeven
2008-06-09 13:54 ` [Cbe-oss-dev] " Geert Uytterhoeven
2008-06-09 15:05 ` James Bottomley
2008-06-09 15:27 ` Geert Uytterhoeven
2008-06-13 17:33 ` Geert Uytterhoeven
2008-06-18 8:47 ` Alessandro Suardi
2008-06-18 11:13 ` Geert Uytterhoeven
2008-06-18 12:15 ` Alessandro Suardi
2008-06-21 14:18 ` Alessandro Suardi
2008-06-22 8:18 ` Geert Uytterhoeven
2008-06-22 13:14 ` Alessandro Suardi [this message]
2008-07-11 21:25 ` Alessandro Suardi
2008-07-12 12:08 ` Alessandro Suardi
2008-07-13 13:33 ` James Bottomley
2008-07-23 20:25 ` Alessandro Suardi
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=5a4c581d0806220614seab6598ufa798d8642295495@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mbres@gentoo.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