daily CVS update output

2017-03-03 Thread NetBSD source update
Updating src tree: P src/doc/TODO.ptrace P src/external/mit/xorg/lib/libICE/Makefile P src/share/man/man4/wm.4 P src/sys/arch/i386/stand/efiboot/boot.c P src/sys/arch/shark/ofw/ofw.c P src/sys/arch/sparc64/dev/ldc.c P src/sys/arch/sparc64/dev/vdsk.c P src/sys/dev/marvell/mvsdio.c P

Re: if_wm panics on boot

2017-03-03 Thread Kengo NAKAHARA
Hi, On 2017/03/04 4:31, Tomohiro Kusumi wrote: > Hi > > Now I'm at > $NetBSD: if_wm.c,v 1.495 2017/03/03 07:57:49 > but still hits the same assertion located at L6622. Ahh, sorry, the newest revision is not r1.495 but r1.496... r1.495 is not fixed yet. The ident of r1.496 is

Re: if_wm panics on boot

2017-03-03 Thread Tomohiro Kusumi
Hi Now I'm at $NetBSD: if_wm.c,v 1.495 2017/03/03 07:57:49 but still hits the same assertion located at L6622. Btw I'm running this on a vm guest. Haven't looked into any detail of this panic, but is this a race that no one else is seeing ? - 6616 4b2db683293e (msaitoh 2010-01-14

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

2017-03-03 Thread Andreas Gustafsson
NetBSD Test Fixture wrote: > This is an automatically generated notice of new failures of the > NetBSD test suite. > > The newly failing test cases are: > > net/arp/t_dad:dad_basic > net/ndp/t_ra:ra_multiple_routers_maxifprefixes Please take this particular report with a grain of salt.

re(4) trouble

2017-03-03 Thread Patrick Welche
Netbooted a new box with this morning's -current/amd64, so its network interface is successfully configured. ftping the sets failed. I just typed dhcpcd to check, and: uvm_fault(0x815a7aa0, 0x0, 1) -> e fatal page fault in supervisor mode trap type 6 code 0 rip 8022de45 cs 8

Automated report: NetBSD-current/i386 test failure

2017-03-03 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/arp/t_dad:dad_basic net/ndp/t_ra:ra_multiple_routers_maxifprefixes The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs

Re: if_wm panics on boot

2017-03-03 Thread Kengo NAKAHARA
Hi, On 2017/03/04 0:29, Tomohiro Kusumi wrote: > Yes, the source says 1.492 which is very recent. > I guess I'll just revert to the one that was (safely)working for now. > > 1.492 2017/03/03 03:33:44 knakahara Sorry, it is my mistake as you point out. I fix it r1.495 just now. Could you try

Re: if_wm panics on boot

2017-03-03 Thread Tomohiro Kusumi
Hi Yes, the source says 1.492 which is very recent. I guess I'll just revert to the one that was (safely)working for now. 1.492 2017/03/03 03:33:44 knakahara From: Robert Elz Sent: Friday, March 3, 2017 17:16 To: Tomohiro Kusumi;

Re: if_wm panics on boot

2017-03-03 Thread Robert Elz
Date:Fri, 3 Mar 2017 12:13:36 + From:Tomohiro Kusumi Message-ID: <1488543216003.86...@tuxera.com> | I'm at the below commit (don't know the CVS revision as I don't use CVS), The cvs rev of the if_wm.c should still be available in the