Re: kern/54289: wd1 fails to be identified properly

["John D. Baker" <jdbaker%consolidated.net@localhost>]

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

From: "John D. Baker" <jdbaker%consolidated.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/54289: wd1 fails to be identified properly
Date: Tue, 24 Mar 2020 00:32:52 -0500 (CDT)

 I've begun bisecting -current between the release of netbsd-8 and netbsd-9.
 So far, 8.99.21 (2 Jul 2018) appears to work--the disks attached to the
 siisata(4) device are all detected.
 
 8.99.30 (16 Jan 2019) fails in the manner previously described in this
 PR.
 
 I have a suspicion that changes to siisata(4) dating from 22-25 Oct 2018
 may be the culprit (enabling MSI and related cleanup).  If bisection
 leads me back to there, the changes look to be too involved to merely
 roll back in netbsd-9 or -current.
 
 Pondering forking a new PR as this particular problem is on siisata(4)
 while another machine has a similar problem with atasata(4)
 
 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]consolidated[flyspeck]net  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