re: IDENTIFY failed

[matthew green <mrg%eterna.com.au@localhost>]

> > wd1 at atabus1 drive 0
> > autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for drive 0
> > wd1: autoconfiguration error: IDENTIFY failed
> > wd1(ahcisata0:1:0): using PIO mode 0
> >
> > and booting fails. Reverting and booting with 9.99.90 gets me a working box:
> >
> > wd1 at atabus1 drive 0
> > wd1: <ST10000DM0004>
> > wd1: drive supports 16-sector PIO transfers, LBA48 addressing
> > wd1: 9314 GB, 19377850 cyl, 16 head, 63 sec, 512 bytes/sect...
> > ...
> > wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags)
> >
> > I'm sure someone else saw this too, but I can't find the original post...
>
> https://mail-index.netbsd.org/current-users/2021/10/27/msg041615.html

this one has reduced timeframe, too:

> between
> NetBSD 9.99.91 (GENERIC) #0: Tue Oct 12 19:57:53 UTC 2021 OK
> NetBSD 9.99.92 (GENERIC) #0: Mon Oct 25 20:32:38 UTC 2021 Failed 

two possible changes to test reverting:

   http://mail-index.netbsd.org/source-changes/2021/10/05/msg132733.html

which changed how some interrupt handling works, and:

   http://mail-index.netbsd.org/source-changes/2021/10/11/msg132941.html

which removed some delays in the probe path.  possibly this one
is more likely to be at fault since it touches the probe path
directly.


.mrg.