daily CVS update output

2019-05-13 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/xbase/shl.mi P src/distrib/sets/lists/xcomp/shl.mi P src/distrib/sets/lists/xdebug/mi P src/distrib/sets/lists/xdebug/shl.mi P src/distrib/sets/lists/xetc/mi P src/distrib/sets/lists/xserver/md.amd64 P src/distrib/sets/lists/xserver/md.cats P src/distri

Re: X Window issues

2019-05-13 Thread Chavdar Ivanov
На 2019-05-12 в 07:34, Kamil Rytarowski написа: > On 12.05.2019 08:09, Martin Husemann wrote: >> On Sat, May 11, 2019 at 11:25:42PM +0100, Chavdar Ivanov wrote: >>> There is definitely some recent problem with the new Intel driver. A few >>> days ago, still under 8.99.37, it worked very well for

Re: audio panic booting -current under vbox 6.0.6

2019-05-13 Thread Christoph Badura
On Fri, May 10, 2019 at 07:56:02PM +0200, Christoph Badura wrote: > Yesterday I tried booting an amd64 install iso from sources updated > around 16:00 UTC under virtualbox 6.0.6. The kernel paniced with > panic: audio_indexof_format: cannot find matched format Christos, hanks for fixing this.

Re: ipv6 broken

2019-05-13 Thread Christos Zoulas
On May 13, 1:55pm, r...@marples.name (Roy Marples) wrote: -- Subject: Re: ipv6 broken | On 13/05/2019 13:34, Christos Zoulas wrote: | > In article <332662e7-3c78-5d1b-ce05-8c86806f7...@marples.name>, | > Roy Marples wrote: | >> On 13/05/2019 03:00, Christos Zoulas wrote: | >>> dhcpcd says: | >>

Re: jemalloc fallout for i386 on amd64?

2019-05-13 Thread Valery Ushakov
On Sun, May 12, 2019 at 08:12:35 +0200, Martin Husemann wrote: > On Sun, May 12, 2019 at 04:43:45AM +0300, Valery Ushakov wrote: > > I have an old i386 kmk binary built on 6.1 > > > Core was generated by `kmk'. > > Program terminated with signal SIGSEGV, Segmentation fault. > > #0 0xf618abc9 in

Automated report: NetBSD-current/i386 test failure

2019-05-13 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/libcurses/t_curses:copywin 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: ipv6 broken

2019-05-13 Thread Roy Marples
On 13/05/2019 13:34, Christos Zoulas wrote: In article <332662e7-3c78-5d1b-ce05-8c86806f7...@marples.name>, Roy Marples wrote: On 13/05/2019 03:00, Christos Zoulas wrote: dhcpcd says: May 13 01:47:01 [79]: wm0: ipv6_start: Can't assign requested address dhcpcd should say duplicated adddres

Re: ipv6 broken

2019-05-13 Thread Christos Zoulas
In article <332662e7-3c78-5d1b-ce05-8c86806f7...@marples.name>, Roy Marples wrote: >On 13/05/2019 03:00, Christos Zoulas wrote: >> dhcpcd says: >> >> May 13 01:47:01 [79]: wm0: ipv6_start: Can't assign requested address > >dhcpcd should say duplicated adddress based on the below, but that's >ju

Re: ipv6 broken

2019-05-13 Thread Roy Marples
On 13/05/2019 03:00, Christos Zoulas wrote: dhcpcd says: May 13 01:47:01 [79]: wm0: ipv6_start: Can't assign requested address dhcpcd should say duplicated adddress based on the below, but that's just cosmetic really. Kernel says: [13.119958] wm0: link state DOWN (was UNKNOWN) [16