(no subject)

Darryl dts at mnsi.net
Tue May 24 12:11:39 PDT 2005


12345678901234567890123456789012345678901234567890123456789012345678901234567890

Hey all, I'm looking for some information on a problem i'm not sure where to take from here. Basically i've got a 50 pin scsi 2 cdwriter that when accessed causes sg kernel errors.  Otherwise the system works just fine and can even write cds ( although sometimes it hangs ) Here's some basic info

in dmesg:

ahc0: <Adaptec 2940 SCSI adapter> port 0xb800-0xb8ff mem 0xd6800000-0xd6800fff irq 7 at device 9.0 on pci0

cd0 at ahc0 bus 0 target 6 lun 0
cd0: <RICOH MP6200S 2.40> Removable CD-ROM SCSI-2 device
cd0: 3.300MB/s transfers
cd0: cd present [1 x 2048 byte records]


camcontrol devlist
<COMPAQPC FIREBALL1080S 1Q09>      at scbus0 target 0 lun 0 (pass0,da0)
<QUANTUM LIGHTNING 540S 241E>      at scbus0 target 1 lun 0 (pass1,da1)
<IBM DCAS-34330    !# S69D>        at scbus0 target 2 lun 0 (pass2,da2)
<RICOH MP6200S 2.40>               at scbus0 target 6 lun 0 (pass3,cd0)

cdrecord -scanbus
Cdrecord-Clone 2.01 (i386-unknown-freebsd4.11) Copyright (C) 1995-2004 Jörg Schilling
Using libscg version 'schily-0.8'.
scsibus0:
        0,0,0     0) 'COMPAQPC' 'FIREBALL1080S   ' '1Q09' Disk
        0,1,0     1) 'QUANTUM ' 'LIGHTNING 540S  ' '241E' Disk
        0,2,0     2) 'IBM     ' 'DCAS-34330    !#' 'S69D' Disk
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) 'RICOH   ' 'MP6200S         ' '2.40' Removable CD-ROM
        0,7,0     7) *


And here is the error itself that has stumped me, a simple " cdrecord - eject " can generate it.  It happens as soon as the command is issued

May 24 14:02:21 darryl /kernel: (pass3:ahc0:0:6:0): data overrun detected in Data-in phase.  Tag == 0xf.
May 24 14:02:21 darryl /kernel: (pass3:ahc0:0:6:0): Have seen Data Phase.  Length = 64512.  NumSGs = 14.
May 24 14:02:21 darryl /kernel: sg[0] - Addr 0x04ecb000 : Length 8192
May 24 14:02:21 darryl /kernel: sg[1] - Addr 0x04fcd000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[2] - Addr 0x0494e000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[3] - Addr 0x04def000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[4] - Addr 0x04c50000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[5] - Addr 0x04eb1000 : Length 8192
May 24 14:02:21 darryl /kernel: sg[6] - Addr 0x04693000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[7] - Addr 0x04dd4000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[8] - Addr 0x048d5000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[9] - Addr 0x04cb6000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[10] - Addr 0x04f77000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[11] - Addr 0x04b38000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[12] - Addr 0x04d39000 : Length 4096
May 24 14:02:21 darryl /kernel: sg[13] - Addr 0x0481a000 : Length 3072


Anyone know why this happens?  How to fix it.... where to look? I'm just starting here, i'm not totally sure its even a scsi problem.


More information about the freebsd-scsi mailing list