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

[Andrius V <vezhlys%gmail.com@localhost>]

Yes, "WDCTL_RST failed" message doesn't seem to be related to the
issue. boot -vx only adds "ahcisata0 port 5: timeout sending FIS" and
"autoconfiguration error: ahcisata0 port 5: drive 15 reset failed,
disabling PMP" messages, but I also see those once for the first port
as well ("FIS" one twice for the failing one). I will try to
investigate issue a bit deeper, maybe I will be able to understand at
least the place or pattern. I may have been incorrect stating that
NetBSD 8.1 had been not affected: I don't see IDENTIFY errors but I
noticed that sometimes it just silently doesn't attach any wd drives
(NetBSD 8.1 I am booting from USB drive). So it can be actually an old
issue. Also partially I believe that it can related to NetBSD reboot
issue as well (UEFI BIOS hangs for a long time on A2 error code, which
if I am right, identifies drive detection issues, and slowly loads
bootloader of any drive after). Misidentification may happen on the
first boot already and it just usually keeps failing on every
subsequent reboot until machine is turned off. Unfortunately, it is
difficult to investigate this issue.

On Sun, Jun 9, 2019 at 5:30 AM David H. Gutteridge <david%gutteridge.ca@localhost> wrote:
>
> The following reply was made to PR kern/54289; it has been noted by GNATS.
>
> From: "David H. Gutteridge" <david%gutteridge.ca@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc:
> Subject: Re: kern/54289: wd1 fails to be identified properly
> Date: Sat, 08 Jun 2019 22:25:45 -0400
>
>  FWIW, I get similar error messages on both 8.x and HEAD on various
>  laptops when resuming from suspension. E.g., on a T420:
>
>  ahcisata0 channel 0: clearing WDCTL_RST failed for drive 0
>
>  However, this generally doesn't seem to cause any issues, beyond perhaps
>  an initial lag when disk activity resumes. (And I'm not even sure that's
>  related.)
>
>  Dave
>
>