[Bug 26572] Re: k3b locks up on searching for devices after running app 1st time on 2.6.12-10-686-smp

[exxcomm]

I'm experiencing this too since updating to Feisty (and new kernel
image) and beryl.

With the new 2.6.20 k3b refuses to recognize the Plextor DVDR PX-716A
altogether, although the device is recognized in dmesg  and asigned sr0,
as well as Gnome device manager.

In 2.6.17-11 I can launch and burn once. If the application is set to
eject the disk after burning, that's where it starts locking. After a
burn GUI and CLI CD access tools cannot access the SATA burner, the LED
reporting drive activity glows solidly after this, though the  button
ejection of the device still works.

dmesg says this during these episodes:
[75578.553656] sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
[75578.553663] sr: Current [descriptor]: sense key: Aborted Command
[75578.553666]     Additional sense: Scsi parity error
[75580.664892] ata1 is slow to respond, please be patient
[75591.059913] ata1 failed to respond (30 secs)
[75591.064241] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x0
[75591.064245] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[75591.056432] sr 0:0:0:0: ioctl_internal_command return code = 8000002
[75591.056438]    : Current [descriptor]: sense key: Aborted Command
[75591.056443]     Additional sense: Scsi parity error
[75596.176401] ata1 is slow to respond, please be patient
[75606.573079] ata1 failed to respond (30 secs)
[75606.577421] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x0
[75606.577428] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[75608.689056] ata1 is slow to respond, please be patient
[75619.085733] ata1 failed to respond (30 secs)
[75619.090122] ata1: command 0xa0 timeout, stat 0xd0 host_stat 0x0
[75619.090129] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00

Every burn that has caused this is has been good data-wise, so far. It
almost looks like it's hardware related except it happened the 1st burn
after upgrading to Feisty, which was 15 minutes after install end, and
never before.

When I look at processes k3b and supporting kde-libs are the only
programs associated still running. I don't see cdrecord or cdparanoia
hanging out. k3b is difficult to kill needing a few "sudo kill -9 'PID'"
to remove.

System: Asus A8V AMD Athalon X2 4800 4Gb RAM NVidia Geforce 6800
Kernel:   Linux 64-bit 2.6.17-11-generic #2 SMP Tue Mar 13 22:06:20 UTC 2007 x86_64 GNU/Linux
Xconfig: gdm and beryl

-- 
k3b locks up on searching for devices after running app 1st time on 2.6.12-10-686-smp
https://bugs.launchpad.net/bugs/26572
You received this bug notification because you are a member of Kernel
Bugs, which is a bug contact for linux-source-2.6.12 in ubuntu.