NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/51102: ipintr may double-release mutex?



Can you try LOCKDEBUG?

  ozaki-r

2016/04/29 7:50 pm <martin%netbsd.org@localhost>:
>
> >Number:         51102
> >Category:       kern
> >Synopsis:       ipintr may double-release mutex?
> >Confidential:   no
> >Severity:       critical
> >Priority:       high
> >Responsible:    kern-bug-people
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   net
> >Arrival-Date:   Fri Apr 29 10:50:00 +0000 2016
> >Originator:     Martin Husemann
> >Release:        NetBSD 7.99.29
> >Organization:
> The NetBSD Foundation, Inc.
> >Environment:
> System: NetBSD whoever-brings-the-night.aprisoft.de 7.99.29 NetBSD 7.99.29 (WHOEVER) #5: Fri Apr 29 10:19:22 CEST 2016 martin%martins.aprisoft.de@localhost:/ssd/src/sys/arch/sparc64/compile/WHOEVER sparc64
> Architecture: sparc64
> Machine: sparc64
> >Description:
>
> I got a KASSERT failing:
>
> panic: kernel diagnostic assertion "curcpu()->ci_mtx_count == 0" failed: file "../../../../kern/kern_softint.c", line 594 softint_execute: ci_mtx_count (-1) != 0, sh_func 0x12ff2a0
>
> and sh_func (0x12ff2a0) is ipintr.
>
> Backtrace is:
>
> #2  0x000000000153c63c in vpanic ()
> #3  0x000000000162d05c in kern_assert ()
> #4  0x00000000015114a8 in softint_dispatch ()
> #5  0x0000000001012014 in softint_fastintr ()
> #6  0x0000000001510ad8 in softint_schedule ()
>
>
> >How-To-Repeat:
> n/a
>
> >Fix:
> n/a
>



Home | Main Index | Thread Index | Old Index