New: kernel hangs when trying to read atip wiith cdrecord
Quoted 6 lines · Christian Lohmaier
I updated the bug-report with some info I collected from another bug.
Apparently my drive sends additional interrupts that confuses the kernel and make it hang.
The problem is triggered with newer versions of cdrecord (cdrtools 2.01a33 and newer) where cdrecord changed its driver interface.
cdrtools-2.01a33 is extremely old (2 years).
It did not introduce new SCSI commands (compared to prevuious versions) and I would be interested why this problem is discussed late.
The only new thing with cdrecord-2.01a33 is that it started to transfer more than 4 bytes with the "read buffer" command. As this is only issued in case that the "read buffer" command did succeed with 4 bytes transfer count and as cdrecord does not transfer more than the drive advertizes, I am just depending on a kernel that does not freeze from the SCSI command I am issuing.
Jörg
Signature · 4 lines
EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Quoted 8 lines · Joerg Schilling
Quoted 6 lines · Christian Lohmaier
I updated the bug-report with some info I collected from another bug.
Apparently my drive sends additional interrupts that confuses the kernel and make it hang.
The problem is triggered with newer versions of cdrecord (cdrtools 2.01a33 and newer) where cdrecord changed its driver interface.
Quoted 4 lines
cdrtools-2.01a33 is extremely old (2 years).
It did not introduce new SCSI commands (compared to prevuious versions) and I would be interested why this problem is discussed late.
Because that problems only occurs in the combination of recent cdrtools with kernel 2.6.x
I for myself have been using kernel 2.4.x until recently I switched to 2.6.x
Quoted 5 lines
The only new thing with cdrecord-2.01a33 is that it started to transfer more than 4 bytes with the "read buffer" command. As this is only issued in case that the "read buffer" command did succeed with 4 bytes transfer count and as cdrecord does not transfer more than the drive advertizes, I am just depending on a kernel that does not freeze from the SCSI command I am issuing.
OK - thats already a hint. Maybe this helps the kernel-devs.
ciao
Christian
Signature · 1 line
NP: Papa Roach - Between Angels And Insects