Updating src tree:
P src/common/lib/libc/gen/ptree.c
P src/common/lib/libc/gen/radixtree.c
P src/distrib/notes/hp300/upgrade
P src/doc/3RDPARTY
P src/external/mit/xorg/bin/xdm/config/Xresources.in
P src/games/phantasia/misc.c
P src/games/trek/dcrept.c
P src/games/trek/setwarp.c
P
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
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2022.05.24.15.51.10 bouyer src/sys/arch/xen/x86/pintr.c,v 1.23
2022.05.24.15.55.19 bouyer src/sys/arch/amd64/amd64/genassym.cf,v 1.86
Hi Rin,
thank you for your quick response. I can first confirm that the
controller installed in the system is ahcisata(4). I have two different
model variants where the problem occurs - on one very reliably at every
boot, and on the other almost after every cold start (and only two of
four
Hi,
The recent change for probe timing should only affect ahcisata(4).
Is your SATA controller ahcisata(4)? If so,
(1) please try kernel built with:
---
options AHCISATA_EXTRA_DELAY
---
If it works around the problem,
(2) please send us full dmesg of your machine.
Then, we can add your
A small addendum: disabling the Intel Platform Trust technology in the
BIOS did not help me (had read this in another post of the linked thread).
However, by plugging in additional USB devices (a mouse) I apparently
caused the necessary delay, which the disk would have needed in the
first
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2022.05.24.14.11.15.
An extract from the build.sh output follows:
--- kern-LEGACY ---
#create
Hello all,
with one of the newer builds of 9.99 (unfortunately I can't narrow it
down more) I have a problem on a NUC5 with a Seagate Firecuda SATA hard
drive (hybrid HDD/SSD).
As long as I boot from the USB stick (for installation, as well as later
for booting the kernel with root
Chuck Silvers writes:
> The introduction in NetBSD's implementation of UFS2 of the extended
> attribute code from FreeBSD has introduced a compatibility problem
> with previous releases of NetBSD. The explanation of this problem is
> a bit involved and requires knowing some history, so please
Here's one if anyone wants to try this on a physically local machine.
amd64, current from today, a simple "atf-run":
[ 119.516347] uhub8: at uhub1 port 6 (addr 1) disconnected
[21.00] cpu10 at mainbus0 apid 9
[ 1.03] cpu10: AMD784.0900672] cpu0: Begin traceback...
[
10 matches
Mail list logo
