Bug 151087

Summary: k3b halts system recording
Product: [Applications] k3b Reporter: David Losada <david.losadag>
Component: generalAssignee: Sebastian Trueg <trueg>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: echidnaman
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: k3b recording DVD data log

Description David Losada 2007-10-20 12:36:40 UTC
Version:           1.0.3 (using KDE 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu2)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.23-nuevo

K3b 1.0.3 with kernel 2.6.23 (it happens with default Kubuntu kernel too). When it finishes recording disk the system halts (the mouse is almost unresponsive) until you press eject in unit's button. Auto eject at finishing recording in k3b is disabled.
In dmesg this the tail:

hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: drive not ready for command
Clocksource tsc unstable (delta = 4686697968 ns)

If there is something more than I can do to help resolve this count with me.
Comment 1 David Losada 2007-10-20 12:38:17 UTC
I opened it in launchpad too, with logs attached:
https://bugs.launchpad.net/kdemultimedia/+bug/154823
Comment 2 Sebastian Trueg 2007-11-02 09:31:00 UTC
did you check the "verify" button?
Comment 3 David Losada 2007-11-02 18:25:58 UTC
No, It happens recording DVD's (I recorded various Cd's and all went fine; but the last DVD stopped the system again).
I am going to attach the k3b log.
Comment 4 David Losada 2007-11-02 18:27:24 UTC
Created attachment 21983 [details]
k3b recording DVD data log
Comment 5 David Losada 2008-04-25 23:18:06 UTC
The bug was relative to the Via hardware; now I changed motherboard and processor with a Athlon X2 (maintaining the DVD recorder) and this bug does not happens any more. Thank you.
Comment 6 Jonathan Thomas 2008-11-19 18:28:59 UTC
According to the reporter of the downstream bug this was either fixed in k3b 1.0.4 or 1.0.5 or it was an Ubuntu bug entirely. Bottom line, the downstream reporter can't reproduce the issue any more.
Comment 7 markuss 2010-03-16 16:04:47 UTC
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED.
If this bug is still valid for 2.0, please reopen it.