From: Robert Hancock <hancockr@shaw.ca>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27.3, ata_piix: cannot play audio CD, "disk change detected"
Date: Mon, 27 Oct 2008 19:30:53 -0600 [thread overview]
Message-ID: <49066B4D.8050109@shaw.ca> (raw)
In-Reply-To: <fa.tiFnp4ilM9dVHkjmbJfon9+fKdc@ifi.uio.no>
Harald Dunkel wrote:
> Hi folks,
>
> If I insert an audio CD in my sata drive to play it via grip, then
> it fails. Grip does not even show the list of audio tracks, nor does
> it play the CD. Instead there is a kernel message saying
>
> [ 6730.836999] sr0: CDROM not ready yet.
> [ 6732.838572] sr0: disc change detected.
> [ 6783.659021] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> [ 6783.659034] ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [ 6783.659035] cdb 1b 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00
> [ 6783.659036] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> [ 6783.659038] ata4.00: status: { DRDY }
> [ 6783.659046] ata4: hard resetting link
> [ 6784.115039] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [ 6785.622185] ata4.00: configured for UDMA/100
> [ 6785.622193] ata4: EH complete
>
>
> The same CDs work fine with an USB CD drive attached to the same
> PC, so this might be a sata driver issue. (BTW, stopping hal doesn't
> make a difference. Data CDs work fine.)
>
> Any idea what goes wrong here? Does grip violate the SCSI protocol
> here? Is there something I could try to help to track this down?
Well, it looks like it was a START STOP UNIT command with the eject bit
set that timed out. Was something trying to eject the disc?
next parent reply other threads:[~2008-10-28 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.tiFnp4ilM9dVHkjmbJfon9+fKdc@ifi.uio.no>
2008-10-28 1:30 ` Robert Hancock [this message]
2008-10-27 19:26 2.6.27.3, ata_piix: cannot play audio CD, "disk change detected" Harald Dunkel
2008-10-27 19:35 ` Jeff Garzik
2008-10-30 5:32 ` Harald Dunkel
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=49066B4D.8050109@shaw.ca \
--to=hancockr@shaw.ca \
--cc=harald.dunkel@t-online.de \
--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).