[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cdrecord and "get performance" scsi errors



Giulio Orsero <giulioo@gmail.com> wrote:

> 1)
> The problems about get_performance, read_disco_info, read_track_info and
> similar on the GSA-E10L are gone, no more errors.

fine

> 3)
> There's still an issue on 2166D:
>
> ===== DVD+RW and -atip, see very big pbuf size
> Profile: Removable Disk
> Using generic SCSI-3/mmc-3 DVD+RW driver (mmc_dvdplusrw).
> Driver flags   : DVD MMC-3 SWABAUDIO BURNFREE
> Supported modes: PACKET SAO
> Drive buf size : 1409024 = 1376 KB
> Drive pbuf size: 1711468224 = 1671355 KB        <=========
> Drive DMA Speed: 18808 kB/s 106x CD 13x DVD
> Current Secsize: 2048
> book type:       DVD+RW, Version (9.2)
> disc size:       120mm (0)
> maximum rate:    Not specified (15)
> number of layers:1
> track path:      Parallel Track Path (0)

This looks like a bug in the firmware of the drive.
The first 4 bytes of the buffer need to have a size field inside....
but ut seems that there is just junk.


> ===== DVD-RW and -atip, see very big pbuf size and "read buffer" error
> Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
> Driver flags   : DVD MMC-3 SWABAUDIO BURNFREE
> Supported modes: PACKET SAO
> Drive buf size : 1409024 = 1376 KB
> Drive pbuf size: 637726720 = 622780 KB
> ./cdrecord.bin: Input/output error. read buffer: scsi sendcmd: no error
> CDB:  3C 00 00 00 00 00 00 FC 00 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 0.002s timeout 100s
> Current Secsize: 2048
> last rma sector: 0
> rzone size:         36
> rzone number:       1
> border number:      1
> ljrs:               0
> track mode:         4 copy: 0
> damage:             0
> reserved track:     0 blank: 0 incremental: 0 fp: 0
>
> Note that pbuf size was not constant:
> Drive buf size : 1409024 = 1376 KB
> Drive pbuf size: 1325400064 = 1294336 KB     <=========
> ./cdrecord.bin: Input/output error. read buffer: scsi sendcmd: no error
> CDB:  3C 00 00 00 00 00 00 FC 00 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 0.002s timeout 100s
> FIFO size      : 4194304 = 4096 KB
> Track 01: data     1 MB
> Total size:        1 MB = 1017 sectors
> Current Secsize: 2048

The read buffer command may be a result of this problem and may have caused a 
DMA overrun.


> 4) 2166D and warning on DVD-RW
> I get this
> WARNING: Phys disk size 1017 differs from rzone size 0! Prerecorded disk?
> WARNING: Phys start: 196608 Phys end 197624
> even when the previous burning was done by cdrecord itself.

This seems to be a result of the prerecorded DVD- disks for @general purpose".
I'll check this later this year....


> 5) Not specific to a burner, minor issues regarding output differences
> between DVD-RW and DVD+RW:
>
> cdrecord.bin dev=4,0,0 -v -data -sao 
> 	driveropts=burnfree  test.iso
>
> === DVD-RW (I see messages about burnfree and track number 1)
> BURN-Free is OFF.
> Turning BURN-Free on
> Starting new track at sector: 0
> Track 01:   76 of   76 MB written (fifo 100%) [buf  98%]   4.1x.
> Track 01: Total bytes read/written: 80637952/80637952 (39374 sectors).
> Writing  time:   40.038s
> Average write speed   1.5x.
> Min drive buffer fill was 97%
> Fixating...
> Fixating time:  184.438s
>
> === DVD+RW (no message about burnfree, track starting from 02)
> FIFO size      : 4194304 = 4096 KB
> Track 01: data    76 MB
> Total size:       76 MB = 39374 sectors
> Current Secsize: 2048
> Trying to clear drive status.
> Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: 2255730
> Starting to write CD/DVD at speed 4 in real SAO 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.
> Starting new track at sector: 0
> Track 02:   76 of   76 MB written (fifo 100%) [buf  98%]   4.1x.
> Track 02: Total bytes read/written: 80637952/80637952 (39374 sectors).
> Writing  time:   21.985s
> Average write speed   2.6x.
> Min drive buffer fill was 97%

DVD+ cannot switch burnfree.

I need to check where the track number comes from....

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       schilling@fokus.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily



Reply to: