lo(4) interfaces and rdomains breakage

2017-01-13 Thread Sebastian Benoit
On current, there seem to be two problems with lo(4) interfaces: 1. "ifconfig lo6 up" fails # ifconfig lo6 create # ifconfig lo6 up ifconfig: SIOCSIFFLAGS: Inappropriate ioctl for device # ifconfig lo6 destroy # The sys/net/rdomains regress test fails because of this, and i think sys/

Re: lo(4) interfaces and rdomains breakage

2017-01-13 Thread Mike Belopuhov
On 13 January 2017 at 13:11, Sebastian Benoit wrote: > On current, there seem to be two problems with lo(4) interfaces: > > 1. "ifconfig lo6 up" fails > > # ifconfig lo6 create > # ifconfig lo6 up > ifconfig: SIOCSIFFLAGS: Inappropriate ioctl for device > # ifconfig lo6 destroy > # > > The sy

Re: lo(4) interfaces and rdomains breakage

2017-01-13 Thread Mike Belopuhov
On Fri, Jan 13, 2017 at 13:15 +0100, Mike Belopuhov wrote: > On 13 January 2017 at 13:11, Sebastian Benoit wrote: > > On current, there seem to be two problems with lo(4) interfaces: > > > > 1. "ifconfig lo6 up" fails > > > > # ifconfig lo6 create > > # ifconfig lo6 up > > ifconfig: SIOCSIFFLAG

Re: lo(4) interfaces and rdomains breakage

2017-01-13 Thread Sebastien Marie
On Fri, Jan 13, 2017 at 01:11:07PM +0100, Sebastian Benoit wrote: > On current, there seem to be two problems with lo(4) interfaces: > > 1. "ifconfig lo6 up" fails > > # ifconfig lo6 create > # ifconfig lo6 up > ifconfig: SIOCSIFFLAGS: Inappropriate ioctl for device > # ifconfig lo6 des

pmap_remove_ptes_86: unmanaged page marked PG_PVLIST caused 1 panic on OpenBSD 6.0

2017-01-13 Thread Skinner
>Synopsis: pmap_remove_ptes_86: unmanaged page marked PG_PVLIST >Category: i386 kernel >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0 (GENERIC) #1917: Tue Jul 26 12:48:33 MDT 2016 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/

Re: lo(4) interfaces and rdomains breakage

2017-01-13 Thread Sebastian Benoit
Mike Belopuhov(m...@belopuhov.com) on 2017.01.13 13:28:01 +0100: > On Fri, Jan 13, 2017 at 13:15 +0100, Mike Belopuhov wrote: > > On 13 January 2017 at 13:11, Sebastian Benoit wrote: > > > On current, there seem to be two problems with lo(4) interfaces: > > > > > > 1. "ifconfig lo6 up" fails > > >

Re: pmap_remove_ptes_86: unmanaged page marked PG_PVLIST caused 1 panic on OpenBSD 6.0

2017-01-13 Thread Mike Larkin
On Fri, Jan 13, 2017 at 12:54:27PM +, skin...@britvault.co.uk wrote: > >Synopsis:pmap_remove_ptes_86: unmanaged page marked PG_PVLIST > >Category:i386 kernel > >Environment: > System : OpenBSD 6.0 > Details : OpenBSD 6.0 (GENERIC) #1917: Tue Jul 26 12:48:33 MDT 2016

Re: pmap_remove_ptes_86: unmanaged page marked PG_PVLIST caused 1 panic on OpenBSD 6.0

2017-01-13 Thread Craig Skinner
On Fri, 13 Jan 2017 12:54:27 + (GMT) skin...@britvault.co.uk wrote: > savecore: writing compressed core to /var/crash/bsd.0.core.Z > savecore: writing compressed kernel to /var/crash/bsd.0.Z These are now in http://web.Britvault.Co.UK/tmp/

Re: pmap_remove_ptes_86: unmanaged page marked PG_PVLIST caused 1 panic on OpenBSD 6.0

2017-01-13 Thread Craig Skinner
Mike Larkin wrote: > > Did this machine work well before? I've never seen a machine that can reliably > mix ECC and not-ECC modules. > Yes, fine. 24x7 for years. 1st crash/panic seen.

Re: pmap_remove_ptes_86: unmanaged page marked PG_PVLIST caused 1 panic on OpenBSD 6.0

2017-01-13 Thread Mike Larkin
On Fri, Jan 13, 2017 at 09:26:33PM +, Craig Skinner wrote: > On Fri, 13 Jan 2017 12:54:27 + (GMT) skin...@britvault.co.uk wrote: > > > savecore: writing compressed core to /var/crash/bsd.0.core.Z > > savecore: writing compressed kernel to /var/crash/bsd.0.Z > > These are now in http://web