The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.12.11.05.50.03 yamaguchi src/sys/dev/pci/if_ixl.c,v 1.3
Log files can be found at:
Oops, sorry, didn't see you had already fixed it.
kre
Date:Wed, 11 Dec 2019 03:32:14 + (UTC)
From:NetBSD Test Fixture
Message-ID: <157603513391.21247.13604030706332828...@babylon5.netbsd.org>
| This is an automatically generated notice of a NetBSD-current/i386
| build failure.
This build failure was caused by
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 2019.12.11.01.51.22.
An extract from the build.sh output follows:
rm -f assym.dep
--- .depend ---
#
Updating src tree:
P src/bin/sh/parser.c
P src/distrib/sets/lists/man/mi
P src/distrib/sets/lists/modules/mi
P src/doc/CHANGES
P src/lib/libedit/filecomplete.c
P src/lib/libkvm/kvm_proc.c
P src/share/man/man4/Makefile
U src/share/man/man4/ixl.4
P src/sys/arch/aarch64/aarch64/pmap.c
P
On Sat, Sep 21, 2019 at 5:26 PM Shoichi Yamaguchi wrote:
>
> I'm porting the ixl driver from OpenBSD. But It will take some time.
I committed ixl(4) to HEAD.
Although it can handle packets, it lacks some features.
I'm going to implement them.
TODO:
- support VLAN filter and VLAN HW tagging
-
It seems that amd64 booting is broken, likely as a result of the
recent addition of support for multiboot2.
See [1] and [2]
[1] http://mail-index.netbsd.org/source-changes-d/2019/12/10/msg011875.html
[2] http://mail-index.netbsd.org/source-changes/2019/12/10/msg111777.html
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.12.10.13.07.28 yamaguchi src/share/man/man4/ixl.4,v 1.1
2019.12.10.13.36.44 kre src/sys/kern/kern_mutex.c,v 1.84
Log files can be found at:
I'm seeing a boot issue where the initial boot screen loops forever
without actually booting.
By that, I mean after "Option 1 will be chosen in 5, 4, 3, 2, 1, 0
seconds", it goes back to "Option 1 will be chosen in 5, 4, 3, 2, 1, 0
seconds" again and repeats.
This didn't happen with the -current
Hi Robert,
On Tue, Dec 10, 2019 at 08:54:12AM +0700, Robert Elz wrote:
> Date:Tue, 10 Dec 2019 00:49:43 + (UTC)
> From:NetBSD Test Fixture
> Message-ID: <157593898298.13655.3447375934086628...@babylon5.netbsd.org>
>
> | This is an automatically generated
10 matches
Mail list logo
