Re: kern/53340: Device probe for hard drive randomly fails after boot

[Bob Nestor <rnestor%tx.rr.com@localhost>]

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

From: Bob Nestor <rnestor%tx.rr.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/53340: Device probe for hard drive randomly fails after boot
Date: Mon, 4 Jun 2018 14:57:32 -0500

 No problem.  Just tell me where it writes the DMESG log to when it can=92t=
  find the disk it=92s booting up from.
 
 
 On Jun 4, 2018, at 2:15 PM, John Nemeth <jnemeth%cue.bc.ca@localhost> wrote:
 
 > The following reply was made to PR kern/53340; it has been noted by =
 GNATS.
 >=20
 > From: John Nemeth <jnemeth%cue.bc.ca@localhost>
 > To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, =
 gnats-admin%netbsd.org@localhost,
 >        netbsd-bugs%netbsd.org@localhost
 > Cc:=20
 > Subject: Re: kern/53340: Device probe for hard drive randomly fails =
 after boot
 > Date: Mon, 4 Jun 2018 12:11:24 -0700
 >=20
 > On Jun 4,  2:05pm, rnestor%tx.rr.com@localhost wrote:
 > }
 > } >Number:         53340
 > } >Category:       kern
 > } >Synopsis:       Device probe for hard drive randomly fails after =
 boot
 > } >Severity:       serious
 > } >Priority:       medium
 > } >Arrival-Date:   Mon Jun 04 14:05:00 +0000 2018
 > } >Originator:     Robert Nestor
 > } >Release:        NetBSD_8.0_RC1
 > } >Organization:
 > } >Environment:
 > } NetBSD localhost 8.0_RC1 NetBSD 8.0_RC1 (GENERIC) #0: Tue May 22 =
 17:51:55 UTC 2018  =
 mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
 > }=20
 > } >Description:
 > } After installation on hard drive the newly installed system
 > } randomly fails to complete booting.  It fails during device
 > } enumeration where it can't always locate the hard disk that it
 > } is booting from.  This is using a BIOS boot on an HP 6200 MT
 > } where UEFI booting has been disabled.
 > }=20
 > } The failure to find the hard drive happens about 50% of the time.=20
 >=20
 >      Do you see a message that says WDCTL_RST failed?  If so, then
 > this a known problem and there are already multiple PRs for it.
 > If not, then you need to provide more information, such as a dmesg
 > (at least a snippet showing the hard drive part) of when it fails
 > and when it succeeds.  As is, you haven't provided enough information
 > to even have any idea what the problem is, much less diagnose and
 > repair it.
 >=20
 > } >How-To-Repeat:
 > } Reboot system
 > } >Fix:
 > } Unknown, but the workaround it to attempting to reboot the system.
 > }=20
 > }-- End of excerpt from rnestor%tx.rr.com@localhost
 >=20