> Date: Fri, 14 Feb 2020 09:19:13 +
> From: Taylor R Campbell
>
> > Date: Fri, 14 Feb 2020 11:03:25 +0200
> > From: Andreas Gustafsson
> >
> > The NetBSD Test Fixture wrote:
> > > nbmake[8]: stopped in
> > > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/modules/drmkms
> > >
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2020.02.14.07.21.02 skrll src/sys/arch/aarch64/include/types.h,v 1.14
2020.02.14.07.23.24 skrll src/sys/arch/arm/arm32/genassym.cf,v 1.86
On Wed, Feb 12, 2020 at 09:55:36AM +, Patrick Welche wrote:
> Just tried for the first time a kern-GENERIC_KASLR.tar.xz from yesterday's
> source on a working GENERIC-9.99.17/amd64 box, with serial console. All
> I see is
>
> >> NetBSD/x86 BIOS Boot, Revision 5.11 (Thu Nov 29 11:11:25 UTC
So I thought I would have a go at setting up ZFS on root.
Thanks to hannken@ it now boots :)
However, it panics at shutdown (or halt). Screen capture of the panic here:
http://www.netbsd.org/~roy/netbsd-zfs-panic.jpg
Now, what I did during the initial setup was to adjust the mountpoint of
Roy Marples writes:
> So I thought I would have a go at setting up ZFS on root.
>
> Thanks to hannken@ it now boots :)
> However, it panics at shutdown (or halt). Screen capture of the panic here:
> http://www.netbsd.org/~roy/netbsd-zfs-panic.jpg
>
> Now, what I did during the initial setup was
m...@goathill.org (MLH) writes:
>I had jsut (apparently) got that working, where the bootloader was
>comoing up from either of my wd2 or wd3 boot wedges and askign for
>the raid0 but then this happened, which is preventing the kernel
>from seeing either wd2 or wd3:
>[ 2.752630]
Michael van Elst wrote:
> MLH wrote:
> > I had jsut (apparently) got that working, where the bootloader was
> > comoing up from either of my wd2 or wd3 boot wedges and askign for
> > the raid0 but then this happened, which is preventing the kernel
> > from seeing either wd2 or wd3:
> >
> > [
Continuation of a long story...
Emmanuel has expended an immense amount of time trying to help me
solve this problem. I finally have accepted that while my motherboard
purports to support EFI booting of large drives, the bios doesn't
appear to support it in any way we can determine.
Nor does it
Updating src tree:
P src/etc/rc.d/ip6addrctl
P src/sys/arch/aarch64/include/types.h
P src/sys/arch/arm/arm32/genassym.cf
P src/sys/arch/mips/adm5120/dev/ahci.c
P src/sys/dev/audio/audio.c
P src/sys/dev/ic/sl811hs.c
P src/sys/dev/mii/dmphy.c
P src/sys/dev/mii/micphy.c
P src/sys/dev/usb/ehci.c
P
The NetBSD Test Fixture wrote:
> nbmake[8]: stopped in
> /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/modules/drmkms
> 1 error
--- dependall-sys ---
/tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/external/bsd/drm2/dist/drm/drm_bufs.c:958:40:
error: pointer of type 'void *'
> Date: Fri, 14 Feb 2020 11:03:25 +0200
> From: Andreas Gustafsson
>
> The NetBSD Test Fixture wrote:
> > nbmake[8]: stopped in
> > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/modules/drmkms
> > 1 error
>
> --- dependall-sys ---
>
11 matches
Mail list logo
