cdrecord problems
                                                               
   From: Nate Eldredge (neldredge@hmc.edu)
   Date: Mon Mar 20 2000 - 23:48:12 EST
   
     Next message: Thomas Molina: "sound problem persist in 2.3.99pre3"
     * Previous message: Mr. James W. Laferriere: "Re: Slot based PCI device probing"
     * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
     _________________________________________________________________________________________________________________
   
   I'm having a few apparently kernel-related problems with cdrecord.
   Current versions:
   
   cdrecord: 1.8.1a01
   kernel: 2.2.15pre3
   drive: Sony CRX100E (IDE with ide-scsi)
   
   These have persisted through many past versions of kernel and cdrecord.
   
   Problem 1: During some operations (erasing a CD-RW, finalizing a
   disc), a lot of other processes on the system hang in the D state,
   with wchan __wait_on_page. When the operation finishes, they resume.
   This is rather irritating.
   
   Problem 2: Very often, I will try to burn a CD and get output like the
   following (voluminous, sorry):
   
   -------------------------------------------------------------------
   mercury:/spare# /usr/local/bin/cdrecord speed=2 dev=0,0 -v -eject foo.iso
   Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling
   TOC Type: 1 = CD-ROM
   scsidev: '0,0'
   scsibus: 0 target: 0 lun: 0
   atapi: 1
   Device type : Removable CD-ROM
   Version : 0
   Response Format: 1
   Vendor_info : 'SONY '
   Identifikation : 'CD-RW CRX100E '
   Revision : '1.0j'
   Device seems to be: Generic mmc CD-RW.
   Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
   Driver flags : SWABAUDIO
   Drive buf size : 1040128 = 1015 KB
   FIFO size : 4194304 = 4096 KB
   Track 01: data 544 MB
   Total size: 625 MB (62:00.54) = 279041 sectors
   Lout start: 626 MB (62:02/41) = 279041 sectors
   Current Secsize: -1
     ATIP start of lead in: -11597 (97:27/28)
     ATIP start of lead out: 336601 (74:50/01)
   Disk type: phase change
   Manuf. index: 20
   Manufacturer: Princo Corporation
   Blocks total: 336601 Blocks current: 336601 Blocks remaining: 57560
   RBlocks total: 346489 RBlocks current: 346489 RBlocks remaining: 67448
   Starting to write CD/DVD at speed 2 in write mode for single session.
   Last chance to quit, starting real write in 1 seconds.
   Waiting for reader process to fill input-buffer ... input-buffer ready.
   Starting new track at sector: 0
   Track 01: 524 of 544 MB written (fifo 100%)./usr/local/bin/cdrecord: Input/output error. write_g1: scsi sendcmd:
   retryable error
   CDB: 2A 00 00 04 18 F0 00 00 10 00
   status: 0x2 (CHECK CONDITION)
   Sense Bytes: 70 00 03 00 00 00 00 12 00 00 00 00 0C 09 00 00
   Sense Key: 0x3 Medium Error, Segment 0
   Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
   Sense flags: Blk 0 (not valid)
   cmd finished after 4.969s timeout 40s
   
   write track data: error after 549945344 bytes
   Sense Bytes: 70 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00
   Writing time: 1798.883s
   Fixating...
   Fixating time: 123.376s
   /usr/local/bin/cdrecord: fifo had 16911 puts and 16784 gets.
   /usr/local/bin/cdrecord: fifo was 0 times empty and 16688 times full, min fill was 96%.
   -------------------------------------------------------------------
   
   i.e. it fails partway through the burn with the "loss of streaming"
   error and I have a frisbee. Also note that the fifo does NOT become
   empty, so this shouldn't be attributable to over load.
   
   I've tried making the system quiet with no particular changes. It
   fails the same whether burning at 2x or 4x. I HAVE noticed, however,
   that I have a much better success rate if I reboot and then burn the
   CD immediately after booting. In fact, I don't think it's ever failed
   under those circumstances.
   
   I found an old message to linux-kernel from Joerg Schilling (author of
   cdrecord) where he responds to a report very much like this (same
   error). He suggests that it could be a scheduling problem in the
   kernel, which seems plausible to me (i.e. cdrecord doesn't get to run
   in time to write to the drive). Unfortunately, I can't find this
   message now, but does this seem possible? Can it be fixed?
   
   I think the drive itself is okay. As I say, it seems to work okay
   right after booting, and it works without any trouble under MS Windows
   :(
   
   Does anyone have any ideas for what I could do about these two
   problems? Are they kernel bugs, known problems, ??
   
   Thanks.
   
--
Nate Eldredge
neldredge@hmc.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
     _________________________________________________________________________________________________________________
   
     * Next message: Thomas Molina: "sound problem persist in 2.3.99pre3"
     * Previous message: Mr. James W. Laferriere: "Re: Slot based PCI device probing"
     * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
     _________________________________________________________________________________________________________________
   
   This archive was generated by hypermail 2b29 : Tue Mar 21 2000 - 01:31:32 EST