daily CVS update output

2022-05-29 Thread NetBSD source update
Updating src tree: P src/common/lib/libc/atomic/atomic_and_64_nv_cas.c P src/common/lib/libc/atomic/atomic_swap_64_cas.c P src/compat/Makefile P src/distrib/sets/lists/base/mi P src/distrib/sets/lists/debug/mi P src/distrib/sets/lists/etc/mi P src/distrib/sets/lists/man/mi P

Re: kernel deadlock on fstchg with vnd

2022-05-29 Thread Manuel Bouyer
On Sun, May 29, 2022 at 01:18:16PM +0200, J. Hannken-Illjes wrote: > > On 29. May 2022, at 08:30, Michael van Elst wrote: > > > > bou...@antioche.eu.org (Manuel Bouyer) writes: > > > >> Hello, > >> do you have an idea on the problem in this thread: > >>

Re: kernel deadlock on fstchg with vnd

2022-05-29 Thread J. Hannken-Illjes
> On 29. May 2022, at 08:30, Michael van Elst wrote: > > bou...@antioche.eu.org (Manuel Bouyer) writes: > >> Hello, >> do you have an idea on the problem in this thread: >> http://mail-index.netbsd.org/port-xen/2022/05/27/msg010213.html > [...] >> I can't reproduce this when using vnd from

Re: sysutils/ovmf build failure

2022-05-29 Thread Thomas Klausner
I see the same breakage. There's a newer version out, you could try updating to that to check if that fixes the problem. Thomas On Sun, May 29, 2022 at 06:03:27PM +0100, Chavdar Ivanov wrote: > Anyone getting the same problem on -current? > > On Sun, 9 Jan 2022 at 23:09, Chavdar Ivanov

Re: sysutils/ovmf build failure

2022-05-29 Thread Chavdar Ivanov
Anyone getting the same problem on -current? On Sun, 9 Jan 2022 at 23:09, Chavdar Ivanov wrote: > > Hi, > > The last time I was able to build this package was around August 2021, > on then's -current amd64. Since that time it always fails for me the > same way: > . > > "gcc" -o >

Automated report: NetBSD-current/i386 build success

2022-05-29 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2022.05.29.12.15.00 martin src/lib/libcrypt/crypt-argon2.c,v 1.19 Logs can be found at:

Automated report: NetBSD-current/i386 build failure

2022-05-29 Thread NetBSD Test Fixture
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.29.11.18.33. An extract from the build.sh output follows: =>

Re: WDCTL_RST failed for drive 0 / wd0: IDENTIFY failed (SATA autodetection issue after installation)

2022-05-29 Thread Rin Okuyama
Thank you for the detailed report! I've added these controllers for the quirk list. With ahcisata_pci.c rev 1.63 and later, AHCISATA_EXTRA_DELAY kernel option is no longer required. Thanks, rin On 2022/05/27 15:02, Matthias Petermann wrote: Hello Rin, the option AHCISATA_EXTRA_DELAY seems to

Re: kernel deadlock on fstchg with vnd

2022-05-29 Thread Michael van Elst
bou...@antioche.eu.org (Manuel Bouyer) writes: >Hello, >do you have an idea on the problem in this thread: >http://mail-index.netbsd.org/port-xen/2022/05/27/msg010213.html [...] >I can't reproduce this when using vnd from userland. You can replicate it by addressing the block device with