Re: head/amd64 @r288358: panic: lock (sleep mutex) iwn0_com_lock not locked @ /usr/src/sys/dev/iwn/if_iwn.c:5356

On Tue, Sep 29, 2015 at 12:12:02PM -0700, Adrian Chadd wrote: > hi > > (please subscribe and email freebsd-wireless@ these things, I'm more > likely to notice!) > > It looks due to my recent taskqueue change for updateedca. I'll go fix > that today. > > Thanks, > ... Looks as if you did:

Re: head/amd64 @r288358: panic: lock (sleep mutex) iwn0_com_lock not locked @ /usr/src/sys/dev/iwn/if_iwn.c:5356

Thanks for being quick and on the ball. I did another review of the drivers to see which others needed fixing and luckily it was only if_iwn. -a On 30 September 2015 at 05:54, David Wolfskill wrote: > On Tue, Sep 29, 2015 at 12:12:02PM -0700, Adrian Chadd wrote: >> hi

head/amd64 @r288358: panic: lock (sleep mutex) iwn0_com_lock not locked @ /usr/src/sys/dev/iwn/if_iwn.c:5356

No known/observed issues with: FreeBSD localhost 11.0-CURRENT FreeBSD 11.0-CURRENT #197 r288335M/288335:1100079: Mon Sep 28 04:14:47 PDT 2015 root@localhost:/common/S4/obj/usr/src/sys/CANARY amd64 on my laptop, but: FreeBSD localhost 11.0-CURRENT FreeBSD 11.0-CURRENT #198

Re: head/amd64 @r288358: panic: lock (sleep mutex) iwn0_com_lock not locked @ /usr/src/sys/dev/iwn/if_iwn.c:5356

hi (please subscribe and email freebsd-wireless@ these things, I'm more likely to notice!) It looks due to my recent taskqueue change for updateedca. I'll go fix that today. Thanks, -a On 29 September 2015 at 06:05, David Wolfskill wrote: > No known/observed issues