Re: kern/37996: NetBSD does not scan PCI-Express busses for devices

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

> The following reply was made to PR kern/37996; it has been noted by GNATS.
> 
> From: Matthias Drochner <M.Drochner%fz-juelich.de@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
>       netbsd-bugs%NetBSD.org@localhost
> Subject: Re: kern/37996: NetBSD does not scan PCI-Express busses
> for devices
>        
> Date: Mon, 11 Feb 2008 13:29:10 +0100
> 
>  I don't use xen nor amd64 myself, but my impression is
>  that ACPI_SCANPCI is not defined for your kernel.
>  Can you either try amd64 GENERIC or build one
>  with "options ACPI_SCANPCI" defined?

I am booting is sys/arch/amd64/conf/XEN3_DOM0.
And yes, from a fresh cvs checkout

    fgrep -Hn "ACPI_SCANPCI" sys/arch/amd64/conf/XEN3_DOM0

prints no results.

So I added "options ACPI_SCANPCI" locally and rebooted.
The boot messages really look different now:

[...]
pci8 at ppb7 bus 8ppb7: added to list as bus 8
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
pci9 at hypervisor0 bus 128hypervisor0: added to list as bus 128
ppb8 at pci9 dev 6 function 0: vendor 0x1166 product 0x0140 (rev. 0xa2)
pci10 at ppb8 bus 129ppb8: added to list as bus 129
ppb9 at pci9 dev 7 function 0: vendor 0x1166 product 0x0142 (rev. 0xa2)
pci11 at ppb9 bus 130ppb9: added to list as bus 130
ppb10 at pci9 dev 8 function 0: vendor 0x1166 product 0x0144 (rev. 0xa2)
pci12 at ppb10 bus 131ppb10: added to list as bus 131
ppb11 at pci9 dev 9 function 0: vendor 0x1166 product 0x0142 (rev. 0xa2)
pci13 at ppb11 bus 132ppb11: added to list as bus 132
bge0 at pci13 dev 0 function 0: Broadcom BCM5751 Gigabit Ethernet
ioapic2: int9 1a0c8<vector=c8,delmode=0,actlo,level,masked,dest=0> 
4000000<target=4>
bge0: interrupting at ioapic2 pin 9, event channel 10
bge0: ASIC BCM5750 A1 (0x4001), Ethernet address 00:10:18:14:5d:9e
brgphy0 at bge0 phy 1: BCM5750 1000BASE-T media interface, rev. 0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
ppb12 at pci9 dev 10 function 0: vendor 0x1166 product 0x0144 (rev. 0xa2)
pci14 at ppb12 bus 133ppb12: added to list as bus 133
ppb13 at pci14 dev 0 function 0: vendor 0x1166 product 0x0103 (rev. 0xc2)
ppb13: disabling notification events
pci15 at ppb13 bus 134ppb13: added to list as bus 134
bnx1 at pci15 dev 0 function 0: Broadcom NetXtreme II BCM5708 1000Base-T
ioapic2: int10 1a0d0<vector=d0,delmode=0,actlo,level,masked,dest=0> 
4000000<target=4>
bnx1: Ethernet address 00:10:18:03:fd:a2
ukphy1 at bnx1 phy 1: Generic IEEE 802.3u media interface
ukphy1: OUI 0x001018, model 0x0036, rev. 5
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
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 13
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: 
use one of: bnx0 bge0 bnx1 wd0[a-p] cd0[a-p] ddb halt reboot


According to the Ethernet address, the network cable is plugged
in bnx1 which is now there.

So can you add "options ACPI_SCANPCI" to
sys/arch/amd64/conf/XEN3_DOM0 and commit, please?
Maybe you should also do that for sys/arch/amd64/conf/GENERIC.



Now I can say, there is a driver bug:

root device: bnx1
dump device: none
file system (default generic): nfs
root on bnx1
nfs_boot: trying static
nfs_boot: getfh - no pathname
cannot mount root, error = 5
root device (default bnx1):


On an _other_ machine, NFS boot works using _the same_
kernel binary with _the same_ kernel parameters:

[...]
boot device: <unknown>
root device: ex0
dump device: none
file system (default generic): nfs
root on ex0
nfs_boot: trying static
nfs_boot: client_addr=192.168.85.12
nfs_boot: gateway=192.168.85.254
nfs_boot: netmask=192.168.85.0
nfs_boot: server=192.168.85.14
nfs_boot: root=192.168.85.14:/nfsroot/netbsd-amd64-cegger
root on 192.168.85.14:/nfsroot/netbsd-amd64-cegger
root time: 0x47b04fd3
warning: no /dev/console
init path (default /sbin/init):



-- 
Greetings,

Christoph