[Bug 516520] New: Blu-Ray drive not accessible if no medium in drive during system boot
http://bugzilla.novell.com/show_bug.cgi?id=516520 Summary: Blu-Ray drive not accessible if no medium in drive during system boot Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: teheo@novell.com ReportedBy: swehnert@novell.com QAContact: qa@suse.de Found By: Customer Created an attachment (id=300442) --> (http://bugzilla.novell.com/attachment.cgi?id=300442) archive with requested info Hardware: Drive type: MATSHITABD-CMB UJ-120 Laptop: Medion P8610 BIOS Rev: M1.08 (no newer version available, in fact the one on the download site is older) OS: openSUSE 11.1 x86-64 Situation: if the system is booted with an empty DVD and a medium is inserted after the user logs in there is no automount or possibility to mount the device. In /var/log/messages we see instead: Jun 6 17:46:02 XXL kernel: ata2.00: qc timeout (cmd 0xa0) Jun 6 17:46:02 XXL kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 6 17:46:02 XXL kernel: ata2.00: irq_stat 0x40000001 Jun 6 17:46:02 XXL kernel: ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Jun 6 17:46:02 XXL kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Jun 6 17:46:02 XXL kernel: res 51/60:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout) Jun 6 17:46:02 XXL kernel: ata2.00: status: { DRDY ERR } Jun 6 17:46:02 XXL kernel: ata2: hard resetting link Jun 6 17:46:03 XXL kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 6 17:46:03 XXL kernel: ata2.00: configured for PIO0 Jun 6 17:46:03 XXL kernel: ata2: EH complete Jun 6 17:46:10 XXL kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Jun 6 17:46:15 XXL kernel: ata2.00: qc timeout (cmd 0xa0) Jun 6 17:46:15 XXL kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 6 17:46:15 XXL kernel: ata2.00: irq_stat 0x40000001 Jun 6 17:46:15 XXL kernel: ata2.00: cmd a0/00:00:00:fe:00/00:00:00:00:00/a0 tag 0 pio 16640 in Jun 6 17:46:15 XXL kernel: cdb 12 01 00 00 fe 00 00 00 00 00 00 00 00 00 00 00 Jun 6 17:46:15 XXL kernel: res 51/50:03:00:fe:00/00:00:00:00:00/a0 Emask 0x5 (timeout) Jun 6 17:46:15 XXL kernel: ata2.00: status: { DRDY ERR } Jun 6 17:46:15 XXL kernel: ata2: hard resetting link Jun 6 17:46:15 XXL kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 6 17:46:15 XXL kernel: ata2.00: configured for PIO0 Jun 6 17:46:15 XXL kernel: ata2: EH complete If he runs hwinfo --cdrom the medium can be mounted afterwards. If the media is in the drive while the system starts it is possible to access it too. Will attach supportconfig and archive with requested info. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=516520
User swehnert@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=516520#c1
--- Comment #1 from Sascha Wehnert
http://bugzilla.novell.com/show_bug.cgi?id=516520
User teheo@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=516520#c2
Tejun Heo
http://bugzilla.novell.com/show_bug.cgi?id=516520
User swehnert@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=516520#c3
Sascha Wehnert
At the first glance, it looks like a highly quirky firmware which likes to throw up if subjected to any different command sequence than what windows uses. The media in/out or hwinfo reviving access don't seem to mean all that much. They just end up hitting the right series of errors which lead to somewhat working state. I'm not entirely sure how to proceed at this point. Matshita drives has had quite a few firmware issues but this seems, ummm, a bit too drastic to work around with a few quirks. It's probably because BD drives are fairly new and so is the firmware.
Another possibility is the mcp ahci messing up something but I don't think it's too likely. Is it possible to test the drive on a different machine?
Thanks.
Pulling out the drive of the laptop would void warranty so we are not able to provide a solution on this. Please feel free to close the bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=516520
User teheo@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=516520#c4
Tejun Heo
participants (1)
-
bugzilla_noreply@novell.com