Automated report: NetBSD-current/i386 build success

2018-09-03 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: 2018.09.03.21.17.09 christos src/distrib/sets/lists/comp/mi,v 1.2224 2018.09.03.21.26.19 kre src/distrib/sets/lists/comp/mi,v 1.2225

Re: usb panic

2018-09-03 Thread maya
On Sat, Sep 01, 2018 at 05:45:48PM +0100, Patrick Welche wrote: > On Sat, Sep 01, 2018 at 04:47:32PM +0100, Patrick Welche wrote: > > Just tried today's source on the usual -current/amd64 laptop, and: > > > > fatal breakpoint trap in supervisor mode > > trap type 1 code 0 rip 0x8021cd05

Automated report: NetBSD-current/i386 build failure

2018-09-03 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 2018.09.03.14.44.31. An extract from the build.sh output follows: --- sf-pcap.d --- #create lib/sf-pcap.d

Re: new kernel fails to boot due to DRM lock issue (intel)

2018-09-03 Thread Riccardo Mottola
Hi, m...@netbsd.org wrote: Yeah, I've seen this too. BTW, it does work if you disable 'options LOCKDEBUG'. not that it's not a bug, but it gives a usable setup. well, you are saying.. to shut eyes and go straight :) Anyway.. I tried disabling i815drmkms and the kernel boots and X runs