Re: cdrecord issues since 2.6 move
On Sun, Aug 29, 2004 at 06:29:45PM -0500, Kevin C. Smith wrote:
> Help!
> Running Debian Sid on Dell Inspiron 8200. Moved to Kernel 2.6.8 and
> started having failures.
>
> Cdwriter:
> scsibus: -2 target: -2 lun: -2
> Warning: Using badly designed ATAPI via /dev/hd* interface.
> Linux sg driver version: 3.5.27
> Using libscg version 'schily-0.8'.
> scsibus0:
> 0,0,0 0) *
> 0,1,0 1) 'TEAC ' 'CD-W216E ' 'L.0Q' Removable CD-ROM
>
> ####
> Cdwriting fails on ISOs greater then 150MB.
> TOC Type: 1 = CD-ROM
> scsidev: '/dev/cdrom'
> devname: '/dev/cdrom'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.
> Linux sg driver version: 3.5.27
> Using libscg version 'schily-0.8'.
> SCSI buffer size: 64512
> atapi: 1
> Device type : Removable CD-ROM
> Version : 0
> Response Format: 1
> Vendor_info : 'TEAC '
> Identifikation : 'CD-W216E '
> Revision : 'L.0Q'
> Device seems to be: Generic mmc CD-RW.
> Current: 0x0009
> Profile: 0x0008
> Profile: 0x0009 (current)
> Profile: 0x000A
> Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
> Driver flags : MMC-2 SWABAUDIO BURNFREE
> Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
> Drive buf size : 1493520 = 1458 KB
> FIFO size : 4194304 = 4096 KB
> Track 01: data 697 MB
> Total size: 801 MB (79:23.90) = 357293 sectors
> Lout start: 801 MB (79:25/68) = 357293 sectors
> Current Secsize: 2048
> ATIP info from disk:
> Indicated writing power: 5
> Is not unrestricted
> Is not erasable
> Disk sub type: Medium Type A, high Beta category (A+) (3)
> ATIP start of lead in: -11634 (97:26/66)
> ATIP start of lead out: 359846 (79:59/71)
> Disk type: Short strategy type (Phthalocyanine or similar)
> Manuf. index: 3
> Manufacturer: CMC Magnetics Corporation
> Blocks total: 359846 Blocks current: 359846 Blocks remaining: 2553
> Starting to write CD/DVD at speed 16 in real TAO mode for single session.
> Last chance to quit, starting real write 0 seconds. Operation starts.
> Waiting for reader process to fill input buffer ... input buffer ready.
> BURN-Free is OFF.
> Performing OPC...
> Starting new track at sector: 0
> Track 01: 259 of 697 MB written (fifo 100%) [buf 85%] |255 212ms|
> 2.5x.cdr ecord: Success. write_g1: scsi sendcmd: no errorCDB: 2A 00 00 02 06 0A 00 00 1F 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 00 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x2C Qual 0x00 (command sequence error) Fru 0x0
> Sense flags: Blk 0 (not valid)
> resid: 63488
> cmd finished after 0.000s timeout 40s
>
> write track data: error after 271601664 bytes
> cdrecord: A write error occured.
> cdrecord: Please properly read the error message above.
> cdrecord: Success. test unit ready: scsi sendcmd: no error
> CDB: 00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 07 00 00
> Sense Key: 0x2 Not Ready, Segment 0
> Sense Code: 0x04 Qual 0x07 (logical unit not ready, operation in progress)
> Fru 0 x0Sense flags: Blk 0 (not valid)
> cmd finished after 0.000s timeout 40s
> cdrecord: Success. flush cache: scsi sendcmd: no error
> CDB: 35 02 00 00 00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 13 0C 00 00 00
> Sense Key: 0x3 Medium Error, Segment 0
> Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 4.638s timeout 120s
> Trouble flushing the cache
> Writing time: 180.834s
> Average write speed 27.7x.
> Min drive buffer fill was 73%
> Fixating...
> Fixating time: 30.112s
> cdrecord: fifo had 4342 puts and 4279 gets.
> cdrecord: fifo was 0 times empty and 2179 times full, min fill was 92%.
>
I think there are "a lot of issues" with cdrecord, ide-scsi, and linux-kernel.
I do not understand what is happening, but it seems not good for "business as
usual". Think about how you can revert to 2.4.x.
In addition to the technical problems of making kernel, ide-scsi, and cdrecord
work together as software objects, there are issues about personal taste in
software design. This may sound silly, but I, myself, respect some peoples'
personal tasee more than I respect that of others. So, I'm expecting to wait
while the good guys vanquish the bad guys. But I don't know which is which.
HTH
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: