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: Sun, 24 Aug 2014 21:20:20 -0500 (CDT)

 On Sun, 24 Aug 2014, msaitoh%NetBSD.org@localhost wrote:
 
 > Subject: Re: kern/49102 (wm detach panic on shutdown or reboot)
 > 
 > Synopsis: wm detach panic on shutdown or reboot
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: msaitoh%NetBSD.org@localhost
 > State-Changed-When: Sun, 24 Aug 2014 21:21:37 +0000
 > State-Changed-Why:
 > Could you test with the latest -current?
 
 It appears the problem is sucessfully circumvented.
 
 Secondary evidence suggests GENERIC kernel reboots cleanly (at least
 filesystems are unmounted) as 'dmesg' does not contain messages about
 replaying log on various filesystems.
 
 I will next have console access to the machine on 30 September 2014
 and can gather conclusive results then.  That is, unless I can get
 someone on-site to watch the console as I shut it down and report
 whether anything strange appears.
 
 The changes should be pulled up to NetBSD-7 and NetBSD-6.
 
 The real issue is the attachment of multiple PCI-Host Bridges that
 overlay the existing PCI bus with phantom busses causing duplicate enum-
 eration of already-attached devices.  That is out of scope for this PR.
 
 -- 
 |/"\ 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