en
running the initialization or hardware detection, there is then a problem with
the initialization of wd0:
```
WDCTL_RST failed for drive 0
wd0: IDENTIFY failed
```
The error pattern seems to be not quite rare and probably the closest to it is
this post:
http://mail-index.netbsd.org/current-u
The boot issue I’m seeing on a VM in Linux with 9.99.96 was with a build from
2022-05-11, so I need to download a new set of file and try again. May take me
a week or so to get some results but I’ll report back when I get them.
Thanks for the hint!
-bob
On May 25, 2022, at 2:44 PM, matthew
Well, test went quicker than I expected. I downloaded the amd64 image for
9.99.97 (assuming it had the fix since it was built 2022-05-25). When I tried
booting the CD in a new VM it shows the same issue - the log shows it found the
cd but then it claims it can’t find the root device.
[ .. ]
> install 9.99.96 in a Virtual Machine (on Linux using KVM) I noticed that
> after installing to a qcow2 disk any attempt to boot the disk results in
> not being about to find the boot device. However, the boot log shows
was this between 2022-05-08 and 2022-05-22? i accidentally
broke
I first saw this issue on a system trying to install and run 9.92, and adding
the suggested AHCISATA_EXTRA_DELAY and disabling TPM seemed to fix it for me.
But then I tried 9.99.96 and saw the same problems and the fixes had no effect.
However I may have stumbled onto something that could be
nto memory.
However, when running the initialization or hardware detection, there
is then a problem with the initialization of wd0:
```
WDCTL_RST failed for drive 0
wd0: IDENTIFY failed
```
The error pattern seems to be not quite rare and probably the closest
to it is this post:
http://mail-index.
hard drive, I get through the boot loader
fine, which also still loads the kernel correctly into memory. However, when
running the initialization or hardware detection, there is then a problem with
the initialization of wd0:
```
WDCTL_RST failed for drive 0
wd0: IDENTIFY failed
```
The error pat
detection, there is
then a problem with the initialization of wd0:
```
WDCTL_RST failed for drive 0
wd0: IDENTIFY failed
```
The error pattern seems to be not quite rare and probably the closest to
it is this post:
http://mail-index.netbsd.org/current-users/2022/03/01/msg042073.html
Recent changes t
, there is
then a problem with the initialization of wd0:
```
WDCTL_RST failed for drive 0
wd0: IDENTIFY failed
```
The error pattern seems to be not quite rare and probably the closest to
it is this post:
http://mail-index.netbsd.org/current-users/2022/03/01/msg042073.html
Recent changes
Sorry for the late reply.
Patrick, Jun, thank you very much for testing!
I've committed the patch:
http://mail-index.netbsd.org/source-changes/2021/11/19/msg133924.html
Thanks,
rin
On 2021/11/10 1:10, Patrick Welche wrote:
On Mon, Nov 08, 2021 at 08:42:44PM +0900, Rin Okuyama wrote:
Jun,
On Mon, Nov 08, 2021 at 08:42:44PM +0900, Rin Okuyama wrote:
> Jun, Patrick, thank you for dmesg (and discussion offlist).
>
> For Jun, the problem is no longer reproducible even with the original
> copy of kernel, which failed before.
>
> So, I've just added AHCI_QUIRK_EXTRA_DELAY quirk for
From: Rin Okuyama
Subject: Re: IDENTIFY failed
Date: Mon, 8 Nov 2021 20:42:44 +0900
> So, I've just added AHCI_QUIRK_EXTRA_DELAY quirk for Patrick's
> machine:
> https://gist.github.com/rokuyama/7535594fc42a7867e3890702aee34c5c
> With this patch, AHCISATA_EXTRA_DELAY option is no lon
On Nov 4, 2021, at 08:00, Rin Okuyama wrote:
>
> Hmm, if affected hardware is somehow limited, we can just introduce something
> like AHCI_QUIRK_EXTRADELAY. Otherwise, we can reconsider, for example, before
> NetBSD 10 is released.
>
> Jun, Patrick, can you please provide full dmesg for your
Jun, Patrick, thank you for dmesg (and discussion offlist).
For Jun, the problem is no longer reproducible even with the original
copy of kernel, which failed before.
So, I've just added AHCI_QUIRK_EXTRA_DELAY quirk for Patrick's machine:
On 2021/11/04 23:28, Brian Buhrow wrote:
Hello. Without going and reading the probe routines, I wonder if we
can create some sort
of hybrid approach? Specifically, probe with the shorter delays, then, if we
get a timeout,
reset and probe with the longer delays? That wil cause
From: Rin Okuyama
Subject: Re: IDENTIFY failed
Date: Thu, 4 Nov 2021 21:18:35 +0900
> Yeah. Patrick, Jun, experiment to adjust delays will be appreciated a
> lot,
> if you have time. But, dmesg should be helpful enough :)
On my environment,
1. after that,back to the original kernel ,
From: Rin Okuyama
Subject: Re: IDENTIFY failed
Date: Thu, 4 Nov 2021 21:00:58 +0900
> Hmm, if affected hardware is somehow limited, we can just introduce
> something
> like AHCI_QUIRK_EXTRADELAY. Otherwise, we can reconsider, for example,
> before
> NetBSD 10 is released.
> Jun
Hello. Without going and reading the probe routines, I wonder if we
can create some sort
of hybrid approach? Specifically, probe with the shorter delays, then, if we
get a timeout,
reset and probe with the longer delays? That wil cause hardware that doesn't
exhibit the
behavior to
,
rin
On 2021/11/01 21:19, Patrick Welche wrote:
On Fri, Oct 29, 2021 at 01:05:26PM +0900, Jun Ebihara wrote:
From: matthew green
Subject: re: IDENTIFY failed
Date: Fri, 29 Oct 2021 07:18:09 +1100
autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for drive 0
https://mail
back AHCISATA_EXTRA_DELAY by default?
IIUC, the option affects only probe/reset; no bad effects for
I/O performance.
Thanks,
rin
On 2021/11/01 21:19, Patrick Welche wrote:
On Fri, Oct 29, 2021 at 01:05:26PM +0900, Jun Ebihara wrote:
From: matthew green
Subject: re: IDENTIFY failed
Date: Fri, 29
:
On Fri, Oct 29, 2021 at 01:05:26PM +0900, Jun Ebihara wrote:
From: matthew green
Subject: re: IDENTIFY failed
Date: Fri, 29 Oct 2021 07:18:09 +1100
autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for drive 0
https://mail-index.netbsd.org/current-users/2021/10/27/msg041615
/11/01 21:19, Patrick Welche wrote:
On Fri, Oct 29, 2021 at 01:05:26PM +0900, Jun Ebihara wrote:
From: matthew green
Subject: re: IDENTIFY failed
Date: Fri, 29 Oct 2021 07:18:09 +1100
autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for
drive 0
https://mail-index.netbsd.org
Can't we put back AHCISATA_EXTRA_DELAY by default?
IIUC, the option affects only probe/reset; no bad effects for
I/O performance.
Thanks,
rin
On 2021/11/01 21:19, Patrick Welche wrote:
On Fri, Oct 29, 2021 at 01:05:26PM +0900, Jun Ebihara wrote:
From: matthew green
Subject: re: IDENTIFY
On Fri, Oct 29, 2021 at 01:05:26PM +0900, Jun Ebihara wrote:
> From: matthew green
> Subject: re: IDENTIFY failed
> Date: Fri, 29 Oct 2021 07:18:09 +1100
>
> >> > autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for
> >> > drive 0
> &
From: matthew green
Subject: re: IDENTIFY failed
Date: Fri, 29 Oct 2021 07:18:09 +1100
>> > autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for
>> > drive 0
>> https://mail-index.netbsd.org/current-users/2021/10/27/msg041615.html
> this one
> > 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
On Thu, 28 Oct 2021 at 14:11, Patrick Welche wrote:
>
> Updating from NetBSD-9.99.90/amd64 to 9.99.92, I get the following failure:
>
> wd1 at atabus1 drive 0
> autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for drive > 0
> wd1: autoconfiguration error:
Updating from NetBSD-9.99.90/amd64 to 9.99.92, I get the following failure:
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
28 matches
Mail list logo
