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, 8 Oct 2019 22:19:30 -0500 (CDT)

 On Tue, 8 Oct 2019, John D. Baker wrote:
 
 > On Tue, 8 Oct 2019, Andrius V wrote:
 > 
 > > This commit fixes the bug:
 > > http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/ic/ahcisata_core.c.diff?r1=1.75&r2=1.76&only_with_tag=MAIN&f=h
 > > , thus current branch already always recognize second hard drive
 > > properly and there's no slow down on hard drive detection on POST BIOS
 > 
 > I have just built and updated to the latest -current (9.99.15) and the
 > problem is NOT fixed for my nVidia-based HP Pavilion test system.
 > It exhibits the same problem as before.
 > 
 > Additionally, the 'nfe' driver appears to have gone missing so it reports
 > "not configured" for the ethernet device and subsequently can't identify
 > the boot device nor find its root device (which should be "nfe0").
 
 Mystery solved.  I was booting the wrong kernel (a custom kernel for
 a different machine instead of GENERIC).  "nfe" is there, no problem.
 
 But the ahcisata issue remains unsolved.  It managed to see wd0 correctly,
 but mis-identifies "cd0" as "wd1" with the errors logged previously.
 
 -- 
 |/"\ 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