Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Jul 1998 01:46:17 -0700
From:      brian@worldcontrol.com
To:        freebsd-scsi@FreeBSD.ORG
Subject:   AIC 7880, CAM, CD-burning a failure too
Message-ID:  <19980706014617.A544@top.worldcontrol.com>

next in thread | raw e-mail | index | archive | help
I had previously posted of troubles using cdrecord 1.6 with an
aic7880 (Adaptec 2940UW) controller.  It basically failed in
the middle of burning 100% of the time, but the same
setup succeeded 100% of the time with an aic7870 (2940W) controller.
This all occured on a _non-CAM_ system.

Kenneth Merry <ken@plutotech.com>  was nice enough to point me to
ftp://ftp.kdm.org/pub/FreeBSD/cam/cdrecord-1.6-cam.980630.tar.gz

which I promptly compiled and then switched my system back to CAM
operation. (I had switched to non-CAM to use the existing cdrecord)

Sadly, similar problems occur.

With CAM and aic7870 (2940W)  I did 22 successful dummy burns.

With CAM and aic7880 (2940UW) it fails 100% of the time.

On the very first attempt cdrecord got to 152 out
of 442MB written and:

...
Track 01: 150 of 442 MB written (fifo 100%).
Track 01: 151 of 442 MB written (fifo 100%).
Track 01: 152 of 442 MB written (fifo 100%).
cdrecord: Invalid argument. CAM INTERFACE ERROR 
cdrecord: Invalid argument. write_g1: scsi sendcmd: no error
status: 0x0 (GOOD STATUS) 
CDB:  2A 00 00 01 30 EA 00 00 1F 00
cmd finished after 0.807s timeout 40s

write track data: error after 159862784 bytes 
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
Writing  time:  601.374s                                         
Fixating...            

There is also a great heaping pile of errors in /var/log/messages
generally of the following types:

Jul  6 00:30:11 bls2 /kernel: (pass1:ahc0:0:1:0): TEST UNIT READY. CDB: 0 0 0 0
0 0  
Jul  6 00:30:11 bls2 /kernel: (pass1:ahc0:0:1:0): NOT READY asc:3a,80 
Jul  6 00:30:11 bls2 /kernel: (pass1:ahc0:0:1:0): Vendor Specific ASCQ
....
Jul  6 00:30:36 bls2 /kernel: (pass1:ahc0:0:1:0): READ TOC/PMA/ATIP {MMC Propose
d}. CDB: 43 0 0 0 0 0 0 0 4 0
Jul  6 00:30:36 bls2 /kernel: (pass1:ahc0:0:1:0): ILLEGAL REQUEST asc:24,0
Jul  6 00:30:36 bls2 /kernel: (pass1:ahc0:0:1:0): Invalid field in CDB
Jul  6 00:39:28 bls2 /kernel: (da0:ahc0:0:0:0): SCB 0x13 - timed out in dataout
phase, SCSISIGI == 0xe6
Jul  6 00:40:13 bls2 /kernel: SEQADDR == 0x115
Jul  6 00:40:13 bls2 /kernel: SSTAT1 == 0x13
Jul  6 00:40:13 bls2 /kernel: (da0:ahc0:0:0:0): SCB 0x21 - timed out in dataout 
phase, SCSISIGI == 0xe6
...
Jul  6 00:40:14 bls2 ahc0: Issued Channel A Bus Reset. 9 SCBs aborted

There are lots of each type.

Also, unlike the non-CAM failures, the CAM version failure is unable
to ever recover once the problem occurs.  

With the non-CAM SCSI drivers I could start a new burn and all would
proceed until the next timeout in the middle of the burn.  With the
CAM SCSI drivers once the failure has occured, cdrecord is basically
unable to deal with the CD-R anymore.  It can get some of the
drive data still such as config info, but it can't fetch other info,
and the burns fail immediately.

For example (the errors are marked with ***):

    Cdrecord release 1.6 Copyright (C) 1995-1998 J\xf6rg Schilling
    TOC Type: 1 = CD-ROM
    scsidev: '0,1,0'
    scsibus: 0 target: 1 lun: 0
    Device type    : Removable CD-ROM
    Version        : 2
    Response Format: 2
    Capabilities   :
    Vendor_info    : 'RICOH   '
    Identifikation : 'MP6200S         '
    Revision       : '2.20'
    Device seems to be: Generic mmc CD-RW.
    Using generic SCSI-3/mmc CD-R driver (mmc_cdr). 
    Driver flags   : SWABAUDIO
    cdrecord: Drive needs to reload the media to return to proper status.
    cdrecord: Invalid argument. CAM INTERFACE ERROR
    cdrecord: Invalid argument. WARNING: RR-scheduler not available, disabling.
    Track 01: data  442 MB
    Total size:     508 MB (50:22.68) = 226701 sectors
    Lout start:     508 MB (50:24/51) = 226701 sectors
    ATIP info from disk:
      Indicated writing power: 6
      Is not unrestricted
      Is not erasable
***   ATIP start of lead in:  716730 (255:255/255)
***   ATIP start of lead out: 300 (00:06/00)
*** Disk type unknown 
*** Manufacturer unknown (not in table)











-- 
Brian Litzinger <brian@litzinger.com>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980706014617.A544>