Re: kern/49102 (wm detach panic on shutdown or reboot)

["John D. Baker" <jdbaker%mylinuxisp.com@localhost>]

The following reply was made to PR kern/49102; it has been noted by GNATS.

From: "John D. Baker" <jdbaker%mylinuxisp.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/49102 (wm detach panic on shutdown or reboot)
Date: Thu, 21 Aug 2014 07:34:43 -0500 (CDT)

 On Wed, 20 Aug 2014, John D. Baker wrote:
 
 > Looking at the 'dmesg' output more closely, a more comprehensive
 > workaround would be to enumerate "pchb0" only.
 
 Eliding the wildcard "pchb*" match and nailing down only "pchb0"
 eliminates the phantom PCI busses and their asscociated phantom devices.
 
 The attachment of these additional "pchb" functions that overlay the
 previously-attached PCI busses appears to be the source of the problem.
 While I know there are some machines that legitimately use multiple
 PCI-Host Bridges, the problem machine is not one of them:
 
 000:00:0: ServerWorks CNB20-HE PCI Bridge (host bridge, revision 0x23)
 000:00:1: ServerWorks CNB20-HE PCI Bridge (host bridge, revision 0x01)
 000:00:2: ServerWorks CNB30-LE PCI Bridge (host bridge, revision 0x01)
 000:00:3: ServerWorks CNB30-LE PCI Bridge (host bridge, revision 0x01)
 
 The only legitimate pchb is bus 0, device 0, function 0.  The rest
 overlay the first and create phantom busses/devices.
 
 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645