I just built and booted a Xen DomU system (kernel and system from sources
from a few hours ago) and the result is a seemingly infinite stream of:
[ 2.0131873] Process (pid 1) got sig 11
(with the time increasing, of course).
Anyone care to guess what the cause of that one might be?
(Joerg's c
On Fri, Jul 13, 2018 at 04:07:01PM +0700, Robert Elz wrote:
> I just built and booted a Xen DomU system (kernel and system from sources
> from a few hours ago) and the result is a seemingly infinite stream of:
>
> [ 2.0131873] Process (pid 1) got sig 11
>
> (with the time increasing, of course)
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 2018.07.13.09.58.49.
An extract from the build.sh output follows:
--- cleandir-pmc ---
--- cleandir-sys ---
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2018.07.13.10.49.17 maya src/external/gpl3/binutils.old/dist/bfd/elf.c,v 1.7
2018.07.13.10.49.17 maya src/external/gpl3/binutils/dist/bfd/elf.c,v 1.11
For a tiny box, I comment out SVS and friends in the kernel config. I now
see:
../../../../arch/amd64/amd64/amd64_trap.S:264: Error: no such instruction:
`svs_enter_nmi'
../../../../arch/amd64/amd64/amd64_trap.S:284: Error: no such instruction:
`svs_leave_nmi'
Cheers,
Patrick
Date:Fri, 13 Jul 2018 14:33:34 +0100
From:Patrick Welche
Message-ID: <2018071314.GC28719@quartz>
| ../../../../arch/amd64/amd64/amd64_trap.S:264: Error: no such instruction:
`svs_enter_nmi'
| ../../../../arch/amd64/amd64/amd64_trap.S:284: Error: no such instr
Updating src tree:
P src/bin/sh/histedit.c
P src/bin/sh/mystring.c
P src/bin/sh/options.c
P src/bin/sh/parser.c
P src/bin/sh/var.c
P src/distrib/sets/lists/base/md.amd64
P src/distrib/sets/lists/base/md.i386
P src/distrib/sets/lists/base/mi
P src/distrib/sets/lists/debug/md.amd64
P src/distrib/se
I am (soon -- perhaps it will have happened before you
read this for some of you) going to commit changes to /bin/sh
to (finally!) get rid of internal uses of atoi() - completely.
Mostly this will have no visible effect, but there may be a few
places where sh will now report a "number out of range
