On Wed, Nov 28, 2018 at 10:04:52PM +0000, Kevin Chadwick wrote:
> 
> >Synopsis:      <athn0: device timeout - panic: invalid key cipher>
> >Category:      <PR Kernel Panic>
> >Environment:
>         System      : OpenBSD 6.4
>         Details     : OpenBSD 6.4-stable i386
> 
>         Architecture: OpenBSD.i386 IBM T42 pci athn
>         Machine     : i386
> >Description:
>         <panic: invalid key cipher 0x0>
> >How-To-Repeat:
>         <Only seen once so far, may have occurred shortly after ifconfig athn0
> down ifconfig athn0 up>
> >Fix:
>         <Restart/Unknown - panic message follows
> panic: invalid key cipher 0x0
> Stopped at db_enter+0x4: popl %ebp
> db_enter() at db_enter+0x4
> panic() at panic+0xcc
> ieee80211_encrypt(d21ca030,d29c3a00,d2867150) at ieee80211_encrypt+0x62
> ar5008_tx(d21ca000,d29c3a00,d2867000,0) at ar5008_tx+0x9b
> athn_start(d21ca030) at athn_start+0x111
> ar5008_intr(d21ca000) at ar5008_intr+0x1f7
> pccbbintr(d2197200) at pccbbintr+0x108
> intr_handler(f52b2a58, d218a880) at intr_handler+0x18
> Xintr_legacy1_untramp(8,200246,d06f6725,d06f65b0,0) at 
> Xintr_legacy1_untramp+0xf7
> cpu_idle_cycle(d0cd9ff8) at cpu_idle_cycle+0xf
> 
> Still in ddb for a while if any more info is sought?
> >

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.

Reply via email to