Automated report: NetBSD-current/i386 build success

2020-04-04 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: 2020.04.04.23.58.54 ad src/sys/sys/param.h,v 1.657 2020.04.05.00.21.11 ad src/sys/arch/x86/include/pmap.h,v 1.117 2020.04.05.00.21.11 ad

Re: panic and solid lockup on amd64

2020-04-04 Thread MLH
oskar wrote: > i just experienced some problems with a kernel from sources 10 hours old. > transcript from ilo console: > > fatal double fault in supervisor mode > rap type 13 code 0 rip 0x81ebeb39 cs 0x8 rflags 0x10286 cr2 > 0xa8892e56ed88 ilevel 0 rsp 0xa8892e56ed90 > curlwp

-current build failure - flist

2020-04-04 Thread Chavdar Ivanov
Hi, It appears a flist hasn't been updated after the bfd upgrade: === 8 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist is out of date ? -- ./usr/lib/i386/libbfd.so.16 ./usr/lib/i386/libbfd.so.16.0

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

2020-04-04 Thread Kamil Rytarowski
On 05.04.2020 01:14, NetBSD Test Fixture wrote: > 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 2020.04.04.21.36.15. > > An extract from the build.sh output

Automated report: NetBSD-current/i386 build failure

2020-04-04 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 2020.04.04.21.36.15. An extract from the build.sh output follows: # compile lib/parsewhoisline.o

panic and solid lockup on amd64

2020-04-04 Thread oskar
Hej, i just experienced some problems with a kernel from sources 10 hours old. transcript from ilo console: fatal double fault in supervisor mode trap type 13 code 0 rip 0x81ebeb39 cs 0x8 rflags 0x10286 cr2 0xa8892e56ed88 ilevel 0 rsp 0xa8892e56ed90 curlwp 0xfffe0bd79123c00pid

Re: wip/wine64 on amd64

2020-04-04 Thread Thomas Klausner
On Sat, Apr 04, 2020 at 10:13:16PM +0200, Kamil Rytarowski wrote: > You need to build a kernel with USER_LDT in the config. I didn't say so, but I've used one with USER_LDT for the tests. Thomas

Re: wip/wine64 on amd64

2020-04-04 Thread Kamil Rytarowski
On 04.04.2020 21:44, Thomas Klausner wrote: > Hi! > > I've just fixed the compat32* packages so that they built for me. Then > I tried running two programs with wip/wine64 (see > https://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1) > > The first one is a c# application. wine automatically

Re: wip/wine64 on amd64

2020-04-04 Thread Dave Tyson
On Saturday 04 Apr 2020 21:44:42 Thomas Klausner wrote: > Hi! > > I've just fixed the compat32* packages so that they built for me. Then > I tried running two programs with wip/wine64 (see > https://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1) > > The first one is a c# application. wine

wip/wine64 on amd64

2020-04-04 Thread Thomas Klausner
Hi! I've just fixed the compat32* packages so that they built for me. Then I tried running two programs with wip/wine64 (see https://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1) The first one is a c# application. wine automatically installed the mono and gecko packages for me, but then

Automated report: NetBSD-current/i386 build failure

2020-04-04 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 2020.04.04.09.57.13. An extract from the build.sh output follows: --- checkflist --- cd

Re: USB(xhci related) panic

2020-04-04 Thread Chavdar Ivanov
Ok, thanks, seems OK now, tested with a USB stick and DVD-RW. On Fri, 3 Apr 2020 at 07:06, Nick Hudson wrote: > > On 02/04/2020 10:10, Chavdar Ivanov wrote: > > Hi, > > > > On yesterday's -curreng 9.99.52, attaching an external usb DVD-RW device, I > > got: > > > > uvm_fault(0x81750240,

Re: HEADS UP: dhcpcd gains privilege separation support

2020-04-04 Thread Roy Marples
Hi Oskar On 04/04/2020 07:40, os...@fessel.org wrote: Am 02.04.2020 um 15:07 schrieb Roy Marples : could it be that this _dhcpcd has been added to master.passwd and group, so please update your local ones before upgrading. Once installed, you should stop dhcpcd running and then invoke

Re: HEADS UP: dhcpcd gains privilege separation support

2020-04-04 Thread Chavdar Ivanov
On Sat, 4 Apr 2020 at 07:41, wrote: > > Hej Roy, > > > Am 02.04.2020 um 15:07 schrieb Roy Marples : > > could it be that this > > _dhcpcd has been added to master.passwd and group, so please update your > > local ones before upgrading. > > Once installed, you should stop dhcpcd running and then

Re: HEADS UP: dhcpcd gains privilege separation support

2020-04-04 Thread oskar
Hej Roy, > Am 02.04.2020 um 15:07 schrieb Roy Marples : could it be that this > _dhcpcd has been added to master.passwd and group, so please update your > local ones before upgrading. > Once installed, you should stop dhcpcd running and then invoke postinstall so > that the old dhcpcd files