daily CVS update output

2019-04-27 Thread NetBSD source update
Updating src tree: P src/common/lib/libutil/snprintb.c P src/distrib/sets/lists/base/shl.mi P src/distrib/sets/lists/comp/mi P src/distrib/sets/lists/debug/shl.mi P src/doc/3RDPARTY P src/doc/CHANGES P src/external/bsd/top/dist/machine/m_netbsd.c P src/external/mpl/bind/dist/CHANGES P

Re: iwm driver leads to kernel crash

2019-04-27 Thread Martin Husemann
On Sat, Apr 27, 2019 at 04:18:20PM +, n...@n0.is wrote: > It's an T440s, so one module can be exchanged, the other is soldered > to the board. > > I can give exchanging the replacable one a try. I have had good experience with running memtest+ from pkgsrc (I had to use an older binary, newer

Re: iwm driver leads to kernel crash

2019-04-27 Thread Mathew, Cherry G.
On 27 April 2019 7:50:08 PM GMT+05:45, n...@n0.is wrote: >Ryota Ozaki transcribed 512 bytes: >> On Mon, Apr 1, 2019 at 6:53 AM wrote: >> > >> > Hi, >> > >> > would further dmesg outputs from the last 10 or so kernel crashes >> > still be useful? >> >> Yes, and if you have crashdumps, could you

Re: iwm driver leads to kernel crash

2019-04-27 Thread ng0
Ryota Ozaki transcribed 512 bytes: > On Mon, Apr 1, 2019 at 6:53 AM wrote: > > > > Hi, > > > > would further dmesg outputs from the last 10 or so kernel crashes > > still be useful? > > Yes, and if you have crashdumps, could you please provide detailed > information from them? (see

Unkillable process got stuck in uao_put()

2019-04-27 Thread Leonardo Taccari
Hello folks, on NetBSD/amd64 -current (2019-04-27 11:40 UTC) when trying to grep source code via ag (part of textproc/the_silver_searcher) on a tmpfs the ag process get stuck in uao_put() and become unkillable. I can easily reproduce^[0] that using libvirt-5.2.0 distfile^[1], extracting them on a

Automated report: NetBSD-current/i386 build success

2019-04-27 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: 2019.04.27.08.48.31 pgoyette src/sys/netcan/if_canloop.c,v 1.7 2019.04.27.08.49.19 pgoyette src/sys/netcan/if_canloop.c,v 1.8 2019.04.27.09.06.18

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

2019-04-27 Thread Paul Goyette
I just fixed this. sorry for the breakage. On Sat, 27 Apr 2019, 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 2019.04.27.06.18.15. An

Automated report: NetBSD-current/i386 build failure

2019-04-27 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 2019.04.27.06.18.15. An extract from the build.sh output follows:

Re: Branch for netbsd 9 upcoming, please help and test -current

2019-04-27 Thread Andreas Gustafsson
Kamil Rytarowski wrote: > >>> port-sparc/53277: Many ubsan tests fail on sparc [...] > This was assigned to me, my code in sanitizers is in GCC9 and the GCC7 > implementation is mostly independent from my work (initial code of my > work landed to GCC7, more of into GCC8 and almost all of it into