Skip site navigation (1)Skip section navigation (2)
Date:      22 Jul 1999 19:06:31 +0200
From:      Thierry.Besancon@lps.ens.fr
To:        scsi@freebsd.org
Cc:        besancon@lps.ens.fr
Subject:   tagged openings
Message-ID:  <wnnn1woobqg.fsf@excalibur.lps.ens.fr>

next in thread | raw e-mail | index | archive | help

        Hello

I'm running FreeBSD 3.1 and whenever my workstation reboots I get the
message :

        (da0:ncr0:0:0:0): tagged openings now 15

What does it mean ?


I must say that I encounter scsi problems with this host but I can't
find where they're coming from.
Generally the machine freezes with messages saying ncr1 is on timeout.

For example :

        ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb).
        ncr1: script cmd = 89030000
        ncr1: regdump: da 10 80 13 47 08 05 1f 03 09 85 ae 80 00 06 00.
        ncr1: have to clear fifos.
        ncr1: restart (fatal error).
        (sa0:ncr1:0:5:0): COMMAND FAILED (9 ff) @0xf0af9200.
        ncr1: timeout nccb=0xf0c79600 (skip)
        ncr1: timeout nccb=0xf0c79800 (skip)
        ncr1: timeout nccb=0xf0c79a00 (skip)

Another one :

        ncr1:4:ERROR (81:0) (f-aa-0) (0/3) @ (script 3f0: 48000000)
        ncr1: script cmd = 7210000
        ncr1: regdump: da 10 00 03 47 00 04 1f ff 0f 06 aa 80 00 0a 00
        ncr1: target 4 doesn't release the bus
        ncr1:4: ERROR (0:41) (f-aa-00) (0/3) @ (script 3f0: 48000000)
        ncr1: script smd = 72100000
        ncr1: regdump: da 10 00 03 47 00 04 1f ff 0f 06 aa 80 00 0a 00
        ncr1: have to clear fifos
        ncr1: restrt (fatal error)
        (probe13:ncr1:0:6:0): COMMAND FAILED (9ff) @ 0xf0af9000
        (probe13:ncr1:0:5:0): COMMAND FAILED (9ff) @ 0xf0af9000
        (probe13:ncr1:0:4:0): COMMAND FAILED (9ff) @ 0xf0af9000
        (probe13:ncr1:0:3:0): COMMAND FAILED (9ff) @ 0xf0af9000
        (probe13:ncr1:0:2:0): COMMAND FAILED (9ff) @ 0xf0af9000
        ncr1: timeout nccb=0xf0af9000 (skip)
        ncr1: timeout nccb=0xf0af9020 (skip)
        ncr1: timeout nccb=0xf0af9040 (skip)
        ncr1: timeout nccb=0xf0af9060 (skip)
        ncr1: timeout nccb=0xf0af9080 (skip)

The precise configuration is 2 Tekram 390F cards + 2 towers of disks
(4 disks each, IBM 9.1 Go), one DLT and one QUANTUM for the system :

ncr0: <ncr 53c875 fast20 wide scsi> rev 0x26 int a irq 9 on pci0.9.0
ncr1: <ncr 53c875 fast20 wide scsi> rev 0x26 int a irq 12 on pci0.10.0
...
Waiting 3 seconds for SCSI devices to settle
sa0 at ncr1 bus 0 target 5 lun 0
sa0: <Quantum DLT4000 D578> Removable Sequential Access SCSI-2 device 
sa0: 10.0MB/s transfers (10.0MHz, offset 15)
da0 at ncr0 bus 0 target 0 lun 0
da0: <QUANTUM FIREBALL_TM1280S 300X> Fixed Direct Access SCSI-2 device 
da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da0: 1222MB (2503872 512 byte sectors: 255H 63S/T 155C)
changing root device to da0s1a
da9 at ncr1 bus 0 target 1 lun 0
da9: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da9: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da9: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da1 at ncr0 bus 0 target 1 lun 0
da1: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da12 at ncr1 bus 0 target 4 lun 0
da12: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da12: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da12: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da11 at ncr1 bus 0 target 3 lun 0
da11: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da11: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da11: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da10 at ncr1 bus 0 target 2 lun 0
da10: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da10: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da10: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da2 at ncr0 bus 0 target 2 lun 0
da2: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da2: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da3 at ncr0 bus 0 target 3 lun 0
da3: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da3: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
da4 at ncr0 bus 0 target 4 lun 0
da4: <IBM DDRS-39130D DC1B> Fixed Direct Access SCSI-2 device 
da4: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled
da4: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)

The DLT is daisy chained with one UW tower and I don't use the narrow
connector on the tekram 390F. If I do so, the workstation just freezes
during the boot with an error like :

        ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb).
        ncr1: script cmd = 89030000
        ncr1: regdump: da 10 80 13 47 08 05 1f 03 09 85 ae 80 00 06 00.
        ncr1: have to clear fifos.
        ncr1: restart (fatal error).
        (sa0:ncr1:0:5:0): COMMAND FAILED (9 ff) @0xf0af9200.
        ncr1: timeout nccb=0xf0c79600 (skip)
        ncr1: timeout nccb=0xf0c79800 (skip)
        ncr1: timeout nccb=0xf0c79a00 (skip)



I must say too that I had the same problems with the same PC in
another configuration : the DLT was the same, the system disk was the
same, all other disks were different and not UW, the scsi cards were
NCR 810.

The scsi bus goinf timeout is always the one with the DLT.
Might it be faulty ?

        Thierry


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?wnnn1woobqg.fsf>