>Number:         12799
>Category:       kern
>Synopsis:       PCI_CONFIG_DUMP prevents detection of pci1 and pci2
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 01 10:35:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Eric Mumpower
>Release:        Stock NetBSD 1.5 release
>Organization:
Into Networks
>Environment:
NetBSD floyd.arepa.com 1.5 NetBSD 1.5 (FLOYD) #1: Tue May  1 13:06:56 EDT 2001     root@floyd.arepa.com:/usr/src/sys/arch/i386/compile/FLOYD i386

>Description:

On a system which previously detected multiple PCI busses (e.g. pci0,
pci1, pci2), if you enable PCI_CONFIG_DUMP, the system boots without
noticing any of the PCI busses other than pci0.

FWIW, here are the pci-related devices configured with pci_config_dump
disabled:

> floyd# egrep '^(ppb|pci|mainbus)[0-9]' dmesg-sans
> mainbus0 (root)
> pci0 at mainbus0 bus 0: configuration mode 1
> pci0: i/o space, memory space enabled
> ppb0 at pci0 dev 1 function 0: Intel product 0x1131 (rev. 0x02)
> pci1 at ppb0 bus 2
> pci1: i/o space, memory space enabled
> ppb1 at pci0 dev 30 function 0: Intel 82801BA Hub-to-PCI Bridge (rev. 0x01)
> pci2 at ppb1 bus 1
> pci2: i/o space, memory space enabled

>How-To-Repeat:
I can either:
 * Build and boot from kernel with PCI_CONFIG_DUMP
 * 'boot -d', 'write pci_config_dump 1', 'c'

and observe this problem.

>Fix:

No clue. I didn't see any glaring problems in dev/pci/pci.c:pciprint()
>Release-Note:
>Audit-Trail:
>Unformatted: