From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-scsi@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [regression] CD-DA delay needed after insertion
Date: Sun, 15 Jun 2008 09:39:41 -0500 [thread overview]
Message-ID: <1213540781.3517.18.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0806131352360.2141@vixen.sonytel.be>
On Fri, 2008-06-13 at 13:57 +0200, Geert Uytterhoeven wrote:
> We've found another regression in 2.6.25 w.r.t. CD media change on PS3.
>
> It can easily be reproduced by:
>
> 1. Inserting an audio CD
> 2. Running the following command as soon as the blue CD/DVD/BD drive LED
> stops blinking and is lit continuously:
>
> cdparanoia -Z -q 1-1[:1] /dev/null || echo failed
>
> On 2.6.25 (and current mainline), you have to wait ca. 10 seconds after
> insertion, or it will fail.
> On 2.6.24 and older, it just works immediately.
>
> It does not matter whether
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fjejb%2Fscsi-rc-fixes-2.6.git;a=commitdiff_plain;h=d1daeabf0da5bfa1943272ce508e2ba785730bf0
> is applied or not.
>
> We haven't bisected it yet.
There aren't that many commits affecting sr between 2.6.24 and 2.6.25,
so I'd bet on the previous culprits.
This time, the taxonomy looks like NOT_READY isn't being waited for
properly. I'd still tend to blame
210ba1d1724f5c4ed87a2ab1a21ca861a915f734 it's just that this time I
suspect this to be the problem line:
if (sshdr.sense_key == NOT_READY && sshdr.asc == 0x04)
return CDS_DISC_OK;
Previously the code would have returned CDS_NO_DISC for the not ready
case. The CD would have tried to close the door but (and this is the
key) it would have waited for the door to close before trying again.
James
next prev parent reply other threads:[~2008-06-15 14:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 11:57 [regression] CD-DA delay needed after insertion Geert Uytterhoeven
2008-06-15 12:46 ` Boaz Harrosh
2008-06-15 14:33 ` James Bottomley
2008-06-15 14:39 ` James Bottomley [this message]
2008-06-16 15:05 ` Geert Uytterhoeven
2008-06-16 20:30 ` James Bottomley
2008-06-17 13:31 ` Geert Uytterhoeven
2008-06-18 20:40 ` James Bottomley
2008-06-19 9:34 ` Geert Uytterhoeven
2008-06-27 22:27 ` James Bottomley
2008-06-30 9:25 ` [regression] CD-DA delay needed after insertion (http://bugzilla.kernel.org/show_bug.cgi?id=10974) Geert Uytterhoeven
2008-06-30 15:51 ` James Bottomley
2008-07-01 15:18 ` James Bottomley
2008-09-17 15:05 ` Geert Uytterhoeven
2008-09-30 8:17 ` Monty Montgomery
2008-09-30 12:33 ` Geert Uytterhoeven
2008-09-30 12:48 ` Monty Montgomery
2008-09-30 12:51 ` Monty Montgomery
2008-09-30 14:51 ` Geert Uytterhoeven
2008-09-30 15:07 ` Monty Montgomery
2008-09-30 15:21 ` Geert Uytterhoeven
2008-09-30 17:32 ` Monty Montgomery
2008-09-30 17:41 ` Matthew Wilcox
2008-09-30 17:45 ` Matthew Wilcox
2008-09-30 18:10 ` Monty Montgomery
2008-10-01 7:51 ` Geert Uytterhoeven
2008-09-30 13:37 ` Geert Uytterhoeven
2008-07-30 13:06 ` Geert Uytterhoeven
2008-06-17 22:56 ` [regression] CD-DA delay needed after insertion Chuck Ebbert
2008-06-17 22:59 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2008-06-18 5:18 Pat Read
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=1213540781.3517.18.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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