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 fail
From the commit message:
There are a handful of inexplicable 500ms delays introduced to the drive
detect path in this driver, slowing boot. They can be re-enabled with
options AHCISATA_EXTRA_DELAY, but should not be enabled for normal
kernels.
If a delay does need to be introduced in t
Yeah, I know that. But, we already have two problem reports. What I am
concerned about is similar problems will occur for a lot of machines.
(Thinking again...) But, yes, by this way, innocent people will be punished
forever by extra seconds per boot...
Hmm, if affected hardware is somehow limit
It's also possible that 2 full seconds of delays are unnecessary. Do those
delays really need to be 500ms each?
On Thu, 4 Nov 2021, Rin Okuyama wrote:
Yeah, I know that. But, we already have two problem reports. What I
am
concerned about is similar problems will occur for a lot of
machines.
Yeah. Patrick, Jun, experiment to adjust delays will be appreciated a lot,
if you have time. But, dmesg should be helpful enough :)
Thanks,
rin
On 2021/11/04 21:04, Jared McNeill wrote:
It's also possible that 2 full seconds of delays are unnecessary. Do those
delays really need to be 500ms ea
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 wor
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, Patrick, can you
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 , boot fine.
Updating src tree:
P src/etc/security
P src/sys/arch/arm/at91/at91emac.c
P src/sys/arch/arm/fdt/gic_fdt.c
P src/sys/dev/mii/ihphy.c
P src/sys/dev/pci/if_wm.c
P src/sys/stand/efiboot/boot.c
P src/tests/usr.bin/indent/token_binary_op.c
P src/tests/usr.bin/indent/token_comment.c
P src/tests/usr.bin/
