Bug 7441 - Failed to play VCD
Summary: Failed to play VCD
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-31 20:38 UTC by Arief M Utama
Modified: 2007-02-10 00:21 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.18.1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Arief M Utama 2006-10-31 20:38:18 UTC
Most recent kernel where this bug did not occur:
Distribution: Debian Unstable
Hardware Environment: Thinkpad T43
Software Environment: Debian Unstable with GNOME 2.14
Problem Description:

VCD play is always failed. 
This is the output I get (from dmesg):

---- start output ---- 
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x0)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x0)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x0)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: limiting speed to UDMA/25
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x0)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: soft resetting port
ata2.00: configured for UDMA/25
sr 1:0:0:0: SCSI error: return code = 0x08000002
sr0: Current [descriptor]: sense key: Medium Error
    Additional sense: Address mark not found for data field
Descriptor sense data with sense descriptors (in hex):
        72 03 13 00 00 00 00 0e 09 0e 00 51 00 03 00 00
        00 00 00 18 a0 51
end_request: I/O error, dev sr0, sector 76
Buffer I/O error on device sr0, logical block 19
Buffer I/O error on device sr0, logical block 20
Buffer I/O error on device sr0, logical block 21
Buffer I/O error on device sr0, logical block 22
Buffer I/O error on device sr0, logical block 23
Buffer I/O error on device sr0, logical block 24
Buffer I/O error on device sr0, logical block 25
ata2: EH complete
---- end output ----

The VCD is verified as a good medium, played just fine on Windows and VCD players. 

GNOME autodetection (uses HAL?) failed and nothing appears.

Tried to access directly using Totem Movie Player and Xine is not succeeded
also, possibly because the drive still blocked by HAL. 

Ejecting the drive will take sometime.

AFAIK this might not be related only to SATA, I had same problem on T30.
Happened since 2.6.something that I cannot remember when exactly.

Reading data CD or audio CD worked just fine.


Steps to reproduce:

Insert a VCD in the drive and just wait.
Comment 1 Arief M Utama 2006-11-01 18:29:51 UTC
I tried again to test the VCD, 
this time, I disabled udev and hal and didn't login with GNOME, just a plain
failsafe terminal.

I run gxine (a gtk based xine) and it plays the VCD, but not in good way. A
little slow, I'm not sure why. 

I remember that one time in Linux, I used to be able to just insert the VCD, and
click "Play VCD/CD/DVD" on totem/xine/mplayer (or have it autoplay on insert)
just fine. At that time I can even go to the folder of the mounted VCD and copy
one of the movie file inside it to my hard drive.




Comment 2 Vasilis Vasaitis 2006-11-18 07:20:34 UTC
  Can you test again with 2.6.19-rc6? I had similar problems with previous
versions, but now they seem to be gone, with only one issue remaining (see bug#7547).
Comment 3 Adrian Bunk 2007-02-10 00:21:03 UTC
Please reopen this bug if it's still present with kernel 2.6.20.

Note You need to log in before you can comment on or make changes to this bug.