Re: nfs/pcix-bridge problem (was: Re: NetBSD/Xen-amd Dom0 crash)

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

On Wednesday 06 February 2008 17:39:48 Christoph Egger wrote:
> On Wednesday 06 February 2008 16:36:05 Joerg Sonnenberger wrote:
> > On Wed, Feb 06, 2008 at 03:56:02PM +0100, Christoph Egger wrote:
> > > On an AMD machine with 16 CPUs and 8GB RAM,  I get a panic triggered by
> > > an ASSERT in NetBSD/Xen-amd64 Dom0:
> >
> > Please try with the attached patch.
> >
> > Joerg
>
> Tnx, that was fast. Now the machine boots further:
>
> [...]
> bnx0 at pci8 dev 0 function 0: Broadcom NetXtreme II BCM5708 1000Base-T
> ioapic1: int10 1a0b8<vector=b8,delmode=0,actlo,level,masked,dest=0>
> 4000000<target=4>
> bnx0: Ethernet address 00:10:18:03:fe:2c
> ukphy0 at bnx0 phy 1: Generic IEEE 802.3u media interface
> ukphy0: OUI 0x001018, model 0x0036, rev. 5
> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> pchb1 at pci0 dev 24 function 0
> pchb1: vendor 0x1022 product 0x1200 (rev. 0x00)
> pchb2 at pci0 dev 24 function 1
> pchb2: vendor 0x1022 product 0x1201 (rev. 0x00)
> pchb3 at pci0 dev 24 function 2
> pchb3: vendor 0x1022 product 0x1202 (rev. 0x00)
> pchb4 at pci0 dev 24 function 3
> pchb4: vendor 0x1022 product 0x1203 (rev. 0x00)
> pchb5 at pci0 dev 24 function 4
> pchb5: vendor 0x1022 product 0x1204 (rev. 0x00)
> pchb6 at pci0 dev 25 function 0
> pchb6: vendor 0x1022 product 0x1200 (rev. 0x00)
> pchb7 at pci0 dev 25 function 1
> pchb7: vendor 0x1022 product 0x1201 (rev. 0x00)
> pchb8 at pci0 dev 25 function 2
> pchb8: vendor 0x1022 product 0x1202 (rev. 0x00)
> pchb9 at pci0 dev 25 function 3
> pchb9: vendor 0x1022 product 0x1203 (rev. 0x00)
> pchb10 at pci0 dev 25 function 4
> pchb10: vendor 0x1022 product 0x1204 (rev. 0x00)
> pchb11 at pci0 dev 26 function 0
> pchb11: vendor 0x1022 product 0x1200 (rev. 0x00)
> pchb12 at pci0 dev 26 function 1
> pchb12: vendor 0x1022 product 0x1201 (rev. 0x00)
> pchb13 at pci0 dev 26 function 2
> pchb13: vendor 0x1022 product 0x1202 (rev. 0x00)
> pchb14 at pci0 dev 26 function 3
> pchb14: vendor 0x1022 product 0x1203 (rev. 0x00)
> pchb15 at pci0 dev 26 function 4
> pchb15: vendor 0x1022 product 0x1204 (rev. 0x00)
> pchb16 at pci0 dev 27 function 0
> pchb16: vendor 0x1022 product 0x1200 (rev. 0x00)
> pchb17 at pci0 dev 27 function 1
> pchb17: vendor 0x1022 product 0x1201 (rev. 0x00)
> pchb18 at pci0 dev 27 function 2
> pchb18: vendor 0x1022 product 0x1202 (rev. 0x00)
> pchb19 at pci0 dev 27 function 3
> pchb19: vendor 0x1022 product 0x1203 (rev. 0x00)
> pchb20 at pci0 dev 27 function 4
> pchb20: vendor 0x1022 product 0x1204 (rev. 0x00)
> isa0 at pcib0
> com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
> ioapic0: int3 c0<vector=c0,delmode=0,dest=0> 4000000<target=4>
> pckbc0 at isa0 port 0x60-0x64
> pckbdprobe: reset error 5
> pmsprobe: reset error 5
> Link Device LNKU:
> Index  IRQ  Rtd  Ref  IRQs
>     0    5   Y     4  5 10 11 polarity 1 trigger 0
>
> Link Device LNKS:
> Index  IRQ  Rtd  Ref  IRQs
>     0    5   Y     4  5 10 11 polarity 1 trigger 0
>
> raidattach: Asked for 8 units
> Kernelized RAIDframe activated
> xenbus0: using event channel 10
> svwsata0 port 1: device present, speed: 1.5Gb/s
> svwsata0 port 0: PHY offline
> svwsata0 port 2: PHY offline
> svwsata0 port 3: PHY offline
> wd0 at atabus1 drive 0: <ST3120813AS>
> wd0: 111 GB, 232581 cyl, 16 head, 63 sec, 512 bytes/sect x 234441648
> sectors uhub3 at uhub2 port 1
> uhub3: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.07, addr 2
> uhub3: multiple transaction translators
> uhub4 at uhub2 port 2
> uhub4: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.09, addr 3
> uhub4: multiple transaction translators
> atapibus0 at atabus4: 2 targets
> cd0 at atapibus0 drive 0: <DV-W28EA, , 1.0A> cdrom removable
> Searching for RAID components...
> boot device: <unknown>
> root device: bnx0
> dump device:
> file system (default generic):
> root on bnx0
> mountroot: trying lfs...
> mountroot: trying ffs...
> mountroot: trying ext2fs...
> mountroot: trying nfs...
> nfs_boot: trying static
> nfs_boot: getfh - no pathname
>
> That's strange. I passed the ip= and nfsroot= options with all parameters
> to the netbsd kernel and works on 2-cpu machine with an ex0 network device.
>

Finally I figured out, why NFS fails:   NetBSD fails to find bnx1 and bnx2 on 
that machine. The network cable is plugged in one of them. :-)
These two are behind a PCI-Express Bridge.

Oh and completing pcidevs would also be nice to see what the pchb devices 
actually are. They may be the key to find bnx1 and bnx2.

Christoph