In article ,
Paul Goyette wrote:
>With sources updated a few hours ago (2021-01-21 at 17:17:48 UTC) I am
>getting the following crash as soon as it tries to start syslogd:
>
> breakpoint() at breakpoint+0x5
> vpanic() at vpanic+0x156
> snprintf() at snprintf
>
With sources updated a few hours ago (2021-01-21 at 17:17:48 UTC) I am
getting the following crash as soon as it tries to start syslogd:
breakpoint() at breakpoint+0x5
vpanic() at vpanic+0x156
snprintf() at snprintf
kqueue_check() at kqueue_check+0x183
Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/share/man/man9/Makefile
U src/share/man/man9/strlist.9
P src/share/misc/acronyms.comp
P src/sys/arch/amiga/conf/DRACO
P src/sys/arch/amiga/conf/GENERIC
P src/sys/arch/amiga/conf/GENERIC.in
P src/sys/arch/amigappc/conf/GENERIC
P
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.01.21.20.48.33 reinoud src/sys/dev/pci/virtio_pci.c,v 1.18
Logs can be found at:
On Thu, Jan 21, 2021 at 11:45:25AM +, Chavdar Ivanov wrote:
> On Sat, 21 Nov 2020 at 16:37, Chavdar Ivanov wrote:
> I see there were a few recent commits around sys/dev/pci/virtio*. Just
> to mention that the presence of a virtio scsi device in a -current
> (from yesterday) vm under
On Thu, Jan 21, 2021 at 04:33:40PM +0100, Reinoud Zandijk wrote:
> I'd like to fix this ASAP but what is the correct way of dealing with this? Is
> this an i386 failure or should code just not use bus_space_read_8() or
> bus_space_write_8() ?
Unless the spec requires it, you should just avoid
I'd like to fix this ASAP but what is the correct way of dealing with this? Is
this an i386 failure or should code just not use bus_space_read_8() or
bus_space_write_8() ?
In the VirtIO case, it doesn't have to be written atomically though.
What I could do is define a bus_space_write_8()
Date:Wed, 20 Jan 2021 21:17:40 + (UTC)
From:NetBSD Test Fixture
Message-ID: <161117746032.12857.1128493575446...@babylon5.netbsd.org>
| This is an automatically generated notice of a NetBSD-current/i386
| build failure.
|
| The failure occurred on
On Sat, 21 Nov 2020 at 16:37, Chavdar Ivanov wrote:
>
> Ok, thanks. That's what I thought, but knowing it is SCSI after all,
> thought it wouldn't take much to get them working...
>
> On Sat, 21 Nov 2020 at 15:49, Martin Husemann wrote:
> >
> > On Sat, Nov 21, 2020 at 02:44:35PM +, Chavdar
