"parity error detected in DT Data-out phase" during kernel boot encountered.

[David Landgren]

Wilko Bulte wrote:

> On Tue, Aug 19, 2003 at 05:34:40PM +0200, David Landgren wrote:
> 
>>Greetings,
>>
>>I have an HP Proliant 380GL-D3 running 4.8-STABLE and, for the time 
> 
> 
> DL380-G3 I suppose ;)

Ah yes, one of them :)

> 
>>being, a GENERIC kernel. I also have an external Compaq Storageworks 
>>DLT bay. Both the server and the tape bay both have two SCSI ports, 
>>and of course it was only the final combination that made anything happen.
> 
> 
> Tape bay.. what exactly do you have? Can you give me a part# of the
> enclosure?

Well here's the thing. When the machine arrived, it came with an HP 
StorageWorks DLT VS 40/80, which is an external stand-alone unit that 
allows you to select the SCSI ID and daisy chain to another peripheral.

It also came with a huge 3U rackable affair simply marked Compaq 
StorageWorks (no other details) with the room for installing 4 
devices, but it was empty, apart from power supply and internal SCSI 
cables. (I did specify that I wanted to be able to rack the tape drive).

So I extracted the DLT unit out of the first enclosure and put it in 
this enclosure, but the DL380 didn't see it at the BIOS level.

Since then, I have come back to the initial setup: the device is now 
sitting back in its non-rackable external enclosure, and the DL380 
BIOS sees it just fine. Curiously enough, the external unit selector 
was on 6, and the BIOS reported it as ID 12. I changed the selector to 
2 and the BIOS now reports it as 4 (i.e. BIOS == selector * 2).

In either case, when I run 'camcontrol devlist' it does not show up.

As it turns out, I've cleared up the parity error messages. The server 
has a PCI-X card installed with two SCSI ports (the new thin type). I 
was trying these ports. What I didn't notice is that there was also a 
port on the chassis, connected, I guess, directly to the motherboard. 
The external device is connected to this third port and that cleared 
up the boot error messages.

One suspicious item is that the unit was not delivered with a 
terminator. Reading the docs, however, hints that it may not be 
necessary if it's the only device on the chain.

Be that as it may, I rustled up an old HP SureStore Tape 5000+ which 
is a DAT affair (4Gb I think), and daisy chained it onto the back of 
the StorageWorks unit. And it has a terminator on it, so this strikes 
me as being a more kosher setup.

Indeed, the BIOS correctly reports seeing both tape drives. The 
initial boot prints out something like:

Slot0 Smart Array 5i Controller
   Tape Drives Detected:
     SCSI Port1:  SCSI IDs 3,4

The 3 is the SureStore (DAT) and the 4 is the StorageWorks (DLT). In 
this case too, I still don't see either appear when I run 'camcontrol 
devlist', only the SCSI disk.

Here is the entire dmesg:

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD 4.8-STABLE #0: Thu Jun 12 11:00:14 CEST 2003
     root at bechet.bpinet.com:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2785.13-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
 
Features=0xbfebf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
   Hyperthreading: 2 logical CPUs
real memory  = 2147459072 (2097128K bytes)
avail memory = 2086350848 (2037452K bytes)
Preloaded elf kernel "kernel" at 0xc0537000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pci0: <ATI Mach64-GR graphics accelerator> at 3.0
pci0: <unknown card> (vendor=0x0e11, dev=0xb203) at 4.0 irq 3
pci0: <unknown card> (vendor=0x0e11, dev=0xb204) at 4.2 irq 5
isab0: <PCI to ISA bridge (vendor=1166 device=0201)> at device 15.0 on 
pci0
isa0: <ISA bus> on isab0
atapci0: <ServerWorks CSB5 ATA100 controller> port 
0x2000-0x200f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at 
device 15.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
ohci0: <OHCI (generic) USB controller> mem 0xf5ef0000-0xf5ef0fff irq 7 
at device 15.2 on pci0
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
pcib1: <Host to PCI bridge> on motherboard
pci1: <PCI bus> on pcib1
ciss0: <Compaq Smart Array 5i> port 0x3000-0x30ff mem 
0xf7bf0000-0xf7bf3fff,0xf7cc0000-0xf7cfffff irq 10 at device 3.0 on pci1
ciss0: using 256 of 1024 available commands
ciss0:   1 logical drive configured
ciss0:   firmware 1.92
ciss0:   2 SCSI channels
ciss0:   signature 'CISS'
ciss0:   valence 1
ciss0:   supported I/O methods 0xe<simple,performant,MEMQ>
ciss0:   active I/O method 0x3<simple>
ciss0:   4G page base 0x00000000
ciss0:   interrupt coalesce delay 1000us
ciss0:   interrupt coalesce count 16
ciss0:   max outstanding commands 1024
ciss0:   bus types 0x2<ultra3>
ciss0:   server name ''
ciss0:   heartbeat 0x10000043
ciss0: 1 logical drive
ciss0: logical drive 1: RAID 1, 69120MB online
pcib2: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib2
bge0: <Broadcom BCM5703X Gigabit Ethernet, ASIC rev. 0x1002> mem 
0xf7df0000-0xf7dfffff irq 11 at device 1.0 on pci2
bge0: Ethernet address: 00:0b:cd:03:bc:da
miibus0: <MII bus> on bge0
brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
bge1: <Broadcom BCM5703X Gigabit Ethernet, ASIC rev. 0x1002> mem 
0xf7de0000-0xf7deffff irq 15 at device 2.0 on pci2
bge1: Ethernet address: 00:0b:cd:0e:07:18
miibus1: <MII bus> on bge1
brgphy1: <BCM5703 10/100/1000baseTX PHY> on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
pcib3: <Host to PCI bridge> on motherboard
pci3: <PCI bus> on pcib3
ahc0: <Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter> port 
0x4000-0x40ff mem 0xf7ef0000-0xf7ef0fff irq 10 at device 1.0 on pci3
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
ahc1: <Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter> port 
0x4400-0x44ff mem 0xf7ee0000-0xf7ee0fff irq 10 at device 1.1 on pci3
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
pcib4: <ServerWorks host to PCI bridge(unknown chipset)> on motherboard
pci4: <PCI bus> on pcib4
pcib6: <ServerWorks host to PCI bridge(unknown chipset)> on motherboard
pci6: <PCI bus> on pcib6
pci6: <unknown card> (vendor=0x0e11, dev=0xa0f7) at 30.0 irq 15
pcib5: <ServerWorks host to PCI bridge(unknown chipset)> on motherboard
pci5: <PCI bus> on pcib5
pcib7: <ServerWorks host to PCI bridge(unknown chipset)> on motherboard
pci7: <PCI bus> on pcib7
eisa0: <EISA bus> on motherboard
mainboard0: <CPQ0727 (System Board)> on eisa0 slot 0
orm0: <Option ROMs> at iomem 
0xc0000-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcd7ff,0xee000-0xeffff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: parallel port not found.
ata0-slave: ATA identify retries exceeded
acd0: CDROM <COMPAQ CD-ROM SN-124> at ata0-master PIO4
Waiting 15 seconds for SCSI devices to settle
Mounting root from ufs:/dev/da0s1a
da0 at ciss0 bus 0 target 0 lun 0
da0: <COMPAQ RAID 1  VOLUME OK> Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 69459MB (142253280 512 byte sectors: 255H 32S/T 17433C)
bge0: gigabit link up

Looking at another machine, I see something like:

Waiting 15 seconds for SCSI devices to settle
(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
(noperiph:sym1:0:-1:-1): SCSI BUS reset delivered.
sa0 at sym0 bus 0 target 5 lun 0
sa0: <BNCHMARK DLT1 3E20> Removable Sequential Access SCSI-2 device
sa0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
da1 at sym0 bus 0 target 1 lun 0
da1: <HP 73.4G MAN3735MP HP04> Fixed Direct Access SCSI-2 device
da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged 
Queueing Enabled
da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C)
da0 at sym0 bus 0 target 0 lun 0
da0: <HP 18.2G ST318406LW HP04> Fixed Direct Access SCSI-2 device
da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged 
Queueing Enabled
da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
Mounting root from ufs:/dev/da0s1a

That is, I don't see an sa-type device being recognized by the kernel. 
Is there something I can do in userland to probe the SCSI chain, apart 
from 'camcontrol devlist'?

David.