Re: athn panic: invalid key cipher 0x0

2018-11-29 Thread Stefan Sperling
On Wed, Nov 28, 2018 at 10:04:52PM +, Kevin Chadwick wrote: > > >Synopsis: > >Category: > >Environment: > System : OpenBSD 6.4 > Details : OpenBSD 6.4-stable i386 > > Architecture: OpenBSD.i386 IBM T42 pci athn > Machine : i386 > >Descr

Re: athn panic: invalid key cipher 0x0

2018-11-29 Thread Kevin Chadwick
On 11/29/18 8:12 AM, Stefan Sperling wrote: > Similar panics have been reported to me against this driver in private. > > No clue what's wrong yet. > I suspect there is a memory (mbuf) corruption bug that triggers this. Ok, I rebooted, thanks. Probably doesn't help but just in case. My /etc/hos

Re: athn panic: invalid key cipher 0x0

2018-11-29 Thread Stefan Sperling
On Thu, Nov 29, 2018 at 10:35:03AM +, Kevin Chadwick wrote: > My /etc/hostname.athn0 has the following possibly relevant lines. > > wpaciphers ccmp > wpagroupcipher ccmp > wpa wpaprotos wpa2 This matches the default settings. You don't need to set those options.

Re: Thinkpad x230 hardware/software mute out of sync

2018-11-29 Thread Stefan Hagen
Theo de Raadt wrote: You've re-identified a problem known for about 5 years. There have been multiple attempts to fix it. Hmm, I could have figured, that this is the case. I fixed the symptom by making keycode 0x1008ff12 (the mute button) always trigger: "mixerctl outputs.spkr_mute=off" It's

Re: iked - pfkey_write: writev failed: -> issue found

2018-11-29 Thread David Hill
On Wed, Nov 28, 2018 at 07:12:56PM -0200, Martin Pieuchot wrote: > On 25/11/18(Sun) 10:52, David Hill wrote: > > On Sat, Oct 27, 2018 at 05:35:16PM +0200, Mark Patruck wrote: > > > I've found the reason for the error message > > > > > > iked[24455]: pfkey_write: writev failed: Invalid argument > >

Re: iked - pfkey_write: writev failed: -> issue found

2018-11-29 Thread Mark Patruck
Thanks David. Didn't have time to look into this. On Thu, Nov 29, 2018 at 06:44:52PM -0500, David Hill wrote: > On Wed, Nov 28, 2018 at 07:12:56PM -0200, Martin Pieuchot wrote: > > On 25/11/18(Sun) 10:52, David Hill wrote: > > > On Sat, Oct 27, 2018 at 05:35:16PM +0200, Mark Patruck wrote: > > > >