amd64 stuck in tstile

2017-11-29 Thread Patrick Welche
I have a netbooted old pentium running 20 November -current/amd64, that has been on and scrubbing a usb connected disk since that date. ddb works. I see that essentially everything is stuck in tstile. After a kill 1, I see that init too is in tstile... Any thoughts before I just reboot? Cheers,

Build failing on new gdb?

2017-11-29 Thread Tom Ivar Helbekkmo
Trying to update to a fresh current, I get: #create libgdb/ada-lang.d CC=/usr/tools/bin/x86_64--netbsd-c++\ -std=gnu++11\ -Wno-error=stack-protector /usr/tools/bin/nbmkdep -f ada-lang.d.tmp -- --sysroot=/usr/arena/amd64 -D_KERNTYPES -I/usr/src/external/gpl3/gdb/lib/libgdb -I/usr/src/

distrib/sets/sets.subr rev.1.181 fails build

2017-11-29 Thread Adam
Greetings, Seems like adding MAKEFLAGS= to distrib/sets/sets.subr has made building of -current failing with: makesetfiles ===> /dist/src/distrib/sets nbmake[4]: no system rules (sys.mk). /dist/tools.amd64/bin/nbawk: non-terminated string machine_cp... at source line 73 context is

Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/if_pppoe/t_pppoe:pppoe_chap The above test failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before that. The following commits were made

Re: amd64 stuck in tstile

2017-11-29 Thread Hisashi T Fujinaka
Old Pentium, to me, means i386. On Wed, 29 Nov 2017, Patrick Welche wrote: I have a netbooted old pentium running 20 November -current/amd64, that has been on and scrubbing a usb connected disk since that date. ddb works. I see that essentially everything is stuck in tstile. After a kill 1, I s

Re: amd64 stuck in tstile

2017-11-29 Thread Patrick Welche
OK, maybe not that old... On Wed, Nov 29, 2017 at 07:57:27AM -0800, Hisashi T Fujinaka wrote: > Old Pentium, to me, means i386. > > On Wed, 29 Nov 2017, Patrick Welche wrote: > > > I have a netbooted old pentium running 20 November -current/amd64, that > > has been on and scrubbing a usb connect

Re: amd64 stuck in tstile

2017-11-29 Thread Hisashi T Fujinaka
OK, so I guess it wouldn't boot if it was i386 and you were running amd64. On Wed, 29 Nov 2017, Patrick Welche wrote: OK, maybe not that old... On Wed, Nov 29, 2017 at 07:57:27AM -0800, Hisashi T Fujinaka wrote: Old Pentium, to me, means i386. On Wed, 29 Nov 2017, Patrick Welche wrote: I h

Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: lib/libc/locale/t_sprintf:strto The above test failed in each of the last 3 test runs, and passed in at least 24 consecutive runs before that. The following commits were made

Automated report: NetBSD-current/i386 build failure

2017-11-29 Thread NetBSD Test Fixture
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 2017.11.29.19.21.44. An extract from the build.sh output follows: --- dependall-external --- In file included fr

Re: Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread Robert Elz
Date:Wed, 29 Nov 2017 19:52:16 + (UTC) From:NetBSD Test Fixture Message-ID: <151198513515.5439.11050507388623818...@babylon5.netbsd.org> | The newly failing test case is: | | lib/libc/locale/t_sprintf:strto See the thread on source-changes-d: h

Re: distrib/sets/sets.subr rev.1.181 fails build

2017-11-29 Thread Robert Elz
Date:Wed, 29 Nov 2017 14:30:58 +0100 From:Adam Message-ID: | Greetings, | | Seems like adding MAKEFLAGS= to distrib/sets/sets.subr | has made building of -current failing with: | | | makesetfiles ===> /dist/src/distrib/sets | nbmake[4]: no system r

RE: netbsd 8 (beta) failing to load ixg device

2017-11-29 Thread Derrick Lobo
Opps Heres the error message Pad0: Virtual format configured - Format SLINEAR, precision 16, channels 2, uency 44100 Spkr1 at audio: PC speaker (synthesized) Uvm_fault(0xf815ad300, 0x0, 1) -> e Fatal page fault n supervisor mode Trap type 6 code 0 rip 0xfff8a1e1cc cs 0x8 rflags 0x10246

Automated report: NetBSD-current/i386 build success

2017-11-29 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2017.11.29.21.21.50 christos src/external/gpl3/gdb/lib/libgdb/Makefile,v 1.14 2017.11.29.21.22.36 christos src/external/gpl3/gdb/bin/gdb/Makefile,v 1.12

daily CVS update output

2017-11-29 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/base/md.amd64 P src/distrib/sets/lists/base/md.i386 P src/distrib/sets/lists/man/mi P src/doc/3RDPARTY P src/doc/CHANGES P src/external/gpl3/gdb/bin/gdb/Makefile P src/external/gpl3/gdb/bin/gdbtui/Makefile P src/external/gpl3/gdb/dist/bfd/elf32-arm.c P s

Re: Automated report: NetBSD-current/i386 test failure

2017-11-29 Thread Robert Elz
Date:Wed, 29 Nov 2017 02:48:22 + (UTC) From:NetBSD Test Fixture Message-ID: <151192370231.10146.3070298657628695...@babylon5.netbsd.org> | The newly failing test case is: | lib/libc/locale/t_strfmon:strfmon I have been looking into this new test failure,

Automated report: NetBSD-current/i386 build failure

2017-11-29 Thread NetBSD Test Fixture
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 2017.11.30.05.52.40. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . --- post