The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.02.17.04.57.09 kamil src/tests/lib/libc/sys/t_ptrace_wait.c,v 1.90
2019.02.17.05.06.16 nonaka src/sys/arch/x86/x86/lapic.c,v 1.70
Please show us more details, like:
- kernel messages how the devices attach
- maybe kernel messages from somewhere else (FreeBSD?)
You can use ktrace on the daemon process to see the communication it does
via the serial device. First important part: which device node is it opening?
E.g. it
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.02.17.04.19.39.
An extract from the build.sh output follows:
rip_call < sce->sce_user_end) ||
matthew green writes:
> Andreas Gustafsson writes:
> > Some days ago, matthew green wrote:
> > > hopefully the sparc testbed will fix itself now.
> >
> > It did, but MIPS is suffering from what looks like the same issue
>
> yeah - i commited the hack for it already, but i think i've just
>
"John D. Baker" writes:
> On Fri, 15 Feb 2019, John D. Baker wrote:
>
> > On Fri, 15 Feb 2019, Jaromir Dolecek wrote:
> >
> > > Maybe something like this?
> > >
> > > https://www.netbsd.org/~jdolecek/mac68k_intr_gcc7.diff
> >
> > With this the build succeeds.
> >
> > Will check Matthew
Updating src tree:
P src/external/gpl3/gcc/lib/libgcc/arch/m68000/defs.mk
P src/external/gpl3/gcc/lib/libgomp/arch/aarch64/config.h
P src/external/gpl3/gcc/lib/libgomp/arch/alpha/config.h
P src/external/gpl3/gcc/lib/libgomp/arch/arm/config.h
P
On Fri, 15 Feb 2019, John D. Baker wrote:
> On Fri, 15 Feb 2019, Jaromir Dolecek wrote:
>
> > Maybe something like this?
> >
> > https://www.netbsd.org/~jdolecek/mac68k_intr_gcc7.diff
>
> With this the build succeeds.
>
> Will check Matthew Green's version after the next round of updates.
(to finish what I intended to say above) and the break apparently is
not directly connected to the newly introduced Hyper-V devices in
GENERIC, which came to my mind earlier.
On Sun, 17 Feb 2019 at 00:00, Chavdar Ivanov wrote:
>
> I can confirm that the fix suggested in
>
I can confirm that the fix suggested in
https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53984 works
for me, reverting src/sys/arch/x86/x86/lapic.c to 1.68 gets me
% uname -a
NetBSD marge.lorien.lan 8.99.34 NetBSD 8.99.34 (GENERIC) #1: Sat Feb
16 23:52:16 GMT 2019
Thanks, I will try the suggested fix after the build completes.
On Sat, 16 Feb 2019 at 21:42, Cherry G.Mathew wrote:
>
> Chavdar Ivanov writes:
>
> > Mine is 8.99.34 from 09/02/2019, self build, works just fine. I'll
> > build a new kernel now to compare.
> >
>
> Just FYI in case this is
I am still building, but my guess is that some clever clogs has added
Microsoft Hyper-V devices to GENERIC:
..
% cvs diff -r 1.515 -r 1.516 GENERIC
19-02-16 - 21:52:48
Index: GENERIC
===
RCS file:
Chavdar Ivanov writes:
> Mine is 8.99.34 from 09/02/2019, self build, works just fine. I'll
> build a new kernel now to compare.
>
Just FYI in case this is relevant and can help you with bisecting:
https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53984
--
~cherry
Mine is 8.99.34 from 09/02/2019, self build, works just fine. I'll
build a new kernel now to compare.
On Sat, 16 Feb 2019 at 21:12, Ron Georgia wrote:
>
> Same here. Fails to boot on both my workstation and laptop, fell back to
> 8.99.33
>
> On 2/16/19, 3:15 PM, "Arto Huusko" of
Same here. Fails to boot on both my workstation and laptop, fell back to 8.99.33
On 2/16/19, 3:15 PM, "Arto Huusko" wrote:
Hello,
it seems latest -current amd64 kernel no longer boots on VirtualBox.
Booting GENERIC from
On Wed, Feb 13, 2019 at 09:14:51PM +, Patrick Welche wrote:
> On Tue, Feb 12, 2019 at 04:52:20PM +, Patrick Welche wrote:
> > On Tue, Feb 12, 2019 at 09:45:14AM +, Patrick Welche wrote:
> > > On Tue, Feb 12, 2019 at 07:22:26PM +1100, matthew green wrote:
> > > > hmm. can you try a
This is not necessarily limited to NetBSD-CURRENT, though the problem exists
there (that’s where I reproduced it). I’m happy to take it elsewhere or
offline — I just couldn’t figure out where the right eyes might see it. Please
point me elsewhere if I’m not in the right spot.
Short story:
Hello,
it seems latest -current amd64 kernel no longer boots on VirtualBox.
Booting GENERIC from
http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201902161050Z/amd64/binary/kernel/
stops after detecting CPUs and acpiacad0. After CPU detection there is
ERROR: 3591 cycle TSC drift observed.
CPU is
> MKX11MOTIF=yes
This is the first time that I hear of this make variable :) I'd file a PR.
--
Benny
In article <4559.1550263...@splode.eterna.com.au>,
matthew green wrote:
>this is my preferred change vs jarmoir's. please test it.
>
> https://www.netbsd.org/~mrg/mac68k-intr.diff
>
>i was also planning on adding an assert that MAX_INAME_LENGTH is
>less than (eintrnames - intrnames).
I would
19 matches
Mail list logo
