#include <hallo.h>
* Francois Gouget [Thu, Oct 26 2006, 08:39:55PM]:
> Package: wodim
> Version: 5:1.0~pre4-1.1
> Severity: important
> 
> Clicking on 'Rescan devices' in xcdroast, runs 'cdrecord dev=
> ATAPI:1,1,0 -v -checkdrive', which ends up in state 'D+' and thus
> remains frozen and unkillable. This also makes it impossible to access
> the drive in any way until the next reboot.
> 
> Since, on this system, cdrecord is a thin wrapper around wodim,
> I'm reporting the bug against wodim.

Fine.

> I have run cdrecord with debug traces and added them below. While
> at the same time syslog was showing the following messages:
> 
> ---
> Oct 26 18:39:03 amboise kernel: hdd: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Oct 26 18:39:03 amboise kernel: ide: failed opcode was: unknown
> Oct 26 18:39:03 amboise kernel: hdd: drive not ready for command
> Oct 26 18:39:03 amboise kernel: hdd: status timeout: status=0xd0 { Busy }
> Oct 26 18:39:03 amboise kernel: ide: failed opcode was: unknown
> Oct 26 18:39:03 amboise kernel: hdd: DMA disabled
> Oct 26 18:39:03 amboise kernel: hdd: drive not ready for command
> ---

This looks like a kernel bug. I assume that your drive freezes, and the
driver does not abort, ignoring the requested timeout.

> A couple more notes: I used to be able to write CDs with this burner. I 
> am sure it worked with a 2.4 kernel. It may have stopped working when I 
> switched to a 2.6 kernel, a long time ago.

Could you make the wodim binary suid-root and retry the same thing?

> Executing 'read buffer' command on Bus 1 Target 1, Lun 0 timeout 40s
> CDB:  3C 00 00 00 00 00 00 FC 00 00
> ---
> This is where cdrecord freezes and thus where the traces end.

It waits for the kernel to return. A program cannot abort a syscal just
so, so it's kernel's turn, no matter what the outcome is.

Eduard.

-- 
<Rhonda> maxx: Testing hat den Anspruch, jederzeit im Release-Fertigen Zustand
        zu sein.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to