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: Fri, 18 Oct 2019 14:49:02 -0500 (CDT)

 On Fri, 18 Oct 2019, Andrius V wrote:
 
 > In this case our issues are unrelated after all, despite our initial
 > assumption. Just recently I attached DVD-ROM device for testing
 > purposes, but it also was recognized properly with the latest
 > ahcisata_core.c revision. Probably I should try to use second hard
 > drive more heavily to see if it behaves OK, but at least it is always
 > recognized properly now and I don't have any reboot issues anymore.
 
 The symptoms are the same, but the latest revision didn't help me.  So
 far, I have only encountered two machines which exhibit the problem and
 I don't dare test on the second one any further as I nearly lost my
 fileserver's RAID from booting a netbsd-9 kernel on it.
 
 I had a locally-applied patch for additional debugging, but in case
 it was interfering, I've moved it aside.  As soon as I can rebuild
 -current again I'll test again.
 
 > Btw, is there any plan to pull up these changes to netbsd-9 branch,
 > since I need to patch it manually every time I rebuild the netbsd-9
 > based kernel?
 
 I recently booted netbsd-9 from a live-usb stick on the one affected
 machine on which I can test.  It seems to alternately work, then fail,
 then work, then fail, etc. on each successive reboot.
 
 -- 
 |/"\ 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