From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5 Description of problem: I've been using K3B without problems on Fedora 7 x86_64. With Fedora 9, the CD are rarely automatically detected and automounted. If I launch K3b, I'm always stuck to the splash screen, and the process can't be killed (un-interruptible state seen in the system monitor) Version-Release number of selected component (if applicable): k3b-1.0.4-6.fc9.x86_64 How reproducible: Always Steps to Reproduce: 1. Just open the K3B from the gnome desktop 2. 3. Actual Results: Expected Results: Additional info:
I can do any testing you want including debug on source code.
afaik, on launch, k3b probes the kernel asking for information wrt cdr's, cdrw's, dvd-rw's, etc... it is very likely this is where the hang occurs. Try launching k3b from a command line, and what, if any, information is displayed in the launching-terminal.
[omar@localhost ~]$ (K3bDevice::HalConnection) initializing HAL >= 0.5 Mapping udi /org/freedesktop/Hal/devices/storage_model_CD/DVDW_TS_H652M to device /dev/sr0 /dev/sr0 resolved to /dev/sr0 /dev/sr0 is block device (0) /dev/sr0 seems to be cdrom bus: 3, id: 0, lun: 0 (K3bDevice::Device) /dev/sr0: init() (K3bDevice::Device) /dev/sr0 feature: CD Mastering (K3bDevice::Device) /dev/sr0 feature: CD Track At Once (K3bDevice::Device) /dev/sr0 feature: DVD Read (MMC5) (K3bDevice::Device) /dev/sr0 feature: DVD+R (K3bDevice::Device) /dev/sr0 feature: DVD+RW (K3bDevice::Device) /dev/sr0 feature: DVD+R Double Layer (K3bDevice::Device) /dev/sr0 feature: DVD-R/-RW Write (K3bDevice::Device) /dev/sr0 feature: Rigid Restricted Overwrite (K3bDevice::Device) /dev/sr0 feature: Layer Jump Recording (K3bDevice::ScsiCommand) failed: command: GET CONFIGURATION (46) errorcode: 72 sense key: NO SENSE (2) asc: 0 ascq: 3 (K3bDevice::ScsiCommand) failed: command: MODE SENSE (5a) errorcode: 72 sense key: NO SENSE (2)
I think what you said is true. Now the problem is that sometimes there is no hang up. I have seen that generally, if I use another programe like PackegeKit before starting K3B the hang happens. Also, the automount of CD/DVD doesn't succeed all the time. So, I am running after a kernel x64 bug ?
A definite maybe. :) Roman, what do you think? Should we punt this over to the kernel folks?
I'm not sure. What about some ugly output of:# strace -f k3b 2>strace.log
Created attachment 306968 [details] strace -f k3b 2>strace.log
And what does: $ cdrecord -scanbus say?
Same thing : It hangs up without displaying anything.
OK, definitely not k3b then, something deeper.
So, could you guys suggest how I can progress on this issue ? For example, should I forward to the kernels bugs ? How can I do this (I'm not accustomed with bugzilla) ?
No problems, we're still trying to figure out how/where to assign this appropriately.
# dmesg .... ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata4.00: status: { DRDY } ata4: soft resetting link ata4.00: configured for UDMA/33 ata4: EH complete ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata4.00: status: { DRDY } ata4: soft resetting link ata4.00: configured for UDMA/33 ata4: EH complete ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ... ata4.00: status: { DRDY } ata4: soft resetting link ata4.00: configured for UDMA/33 ata4: EH complete ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Reassigning to the kernel folks
Created attachment 310753 [details] part of dmesg output
Comment on attachment 310753 [details] part of dmesg output I have the same problem when in Fedora 8 when I updated my kernel from 2.6.24.7-92.fc8 to 2.6.25.6-27.fc8. The splash screen shows and hangs at /dev/sr1 resolved to /dev/sr1 in command line.
I have always update my Fedora version and now it seems that the problem is fixed. uname -r 2.6.25.11-97.fc9.x86_64
Omar, as it seems to be resolved with the latest kernels, I'm closing this ticket. Feel free to re-open it if you encounter any other problem related to it.