Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Sep 2013 19:06:56 -0400
From:      Adam McDougall <mcdouga9@egr.msu.edu>
To:        freebsd-current@freebsd.org
Subject:   Re: Panic on head (r255759) [_callout_stop_safe()-> panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
Message-ID:  <523E2690.7010709@egr.msu.edu>
In-Reply-To: <CACYV=-FoyYhenExozTsazLCL7_2FXo=J-1D9DT4eCsPpK%2BGzLQ@mail.gmail.com>
References:  <523D8AAD.5080900@FreeBSD.org> <alpine.BSF.2.00.1309211205160.4210@ai.fobar.qr> <523D8C39.4050307@FreeBSD.org> <20130921145139.23e3007a@thor.walstatt.dyndns.org> <CACYV=-FXZwzHgBkRPFay4Ktx3H-DKOmfmTpVKe4Z4VTnWmAm0g@mail.gmail.com> <523DC6D1.6050903@egr.msu.edu> <523DC9C7.1020708@FreeBSD.org> <CACYV=-FoyYhenExozTsazLCL7_2FXo=J-1D9DT4eCsPpK%2BGzLQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 09/21/13 12:34, Davide Italiano wrote:
> On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery <bdrewery@freebsd.org> wrote:
>> On 9/21/2013 11:18 AM, Adam McDougall wrote:
>>> On 09/21/13 09:41, Davide Italiano wrote:
>>>> On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann
>>>> <ohartman@zedat.fu-berlin.de> wrote:
>>>>> On Sat, 21 Sep 2013 07:08:25 -0500
>>>>> Bryan Drewery <bdrewery@FreeBSD.org> wrote:
>>>>>
>>>>>> On 9/21/2013 7:06 AM, Bjoern A. Zeeb wrote:
>>>>>>> On Sat, 21 Sep 2013, Bryan Drewery wrote:
>>>>>>>
>>>>>>>>> Unread portion of the kernel message buffer:
>>>>>>>>> panic: Lock lle not exclusively locked @
>>>>>>>>> /usr/src/sys/kern/kern_rwlock.c:140
>>>>>>>>>
>>>>>>>>> cpuid = 0
>>>>>>>>> KDB: stack backtrace:
>>>>>>>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>>>>>>>> 0xfffffe118aeef820
>>>>>>>>> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe118aeef8d0
>>>>>>>>> vpanic() at vpanic+0x126/frame 0xfffffe118aeef910
>>>>>>>>> panic() at panic+0x43/frame 0xfffffe118aeef970
>>>>>>>>> __rw_assert() at __rw_assert+0xa3/frame 0xfffffe118aeef980
>>>>>>>>> _callout_stop_safe() at _callout_stop_safe+0x54/frame
>>>>>>>>> 0xfffffe118aeef9f0 arptimer() at arptimer+0x14e/frame
>>>>>>>>> 0xfffffe118aeefa30 softclock_call_cc() at
>>>>>>>>> softclock_call_cc+0x188/frame 0xfffffe118aeefb10 softclock() at
>>>>>>>>> softclock+0x47/frame 0xfffffe118aeefb30
>>>>>>>>> intr_event_execute_handlers() at
>>>>>>>>> intr_event_execute_handlers+0x93/frame 0xfffffe118aeefb70
>>>>>>>>> ithread_loop() at ithread_loop+0xa6/frame 0xfffffe118aeefbb0
>>>>>>>>> fork_exit() at fork_exit+0x84/frame 0xfffffe118aeefbf0
>>>>>>>>> fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe118aeefbf0
>>>>>>>>> --- trap 0, rip = 0, rsp = 0xfffffe118aeefcb0, rbp = 0 ---
>>>>>>> +1 from me;  I  guess introduced somwhere between 255569 and 255758,
>>>>>>> as these are my edges of kernel.old and kernel.
>>>>>>>
>>>>>> r255726 was stable for me. r255759 is not.
>>>>>>
>>>>>> r255755 converted ipfilter to callout, but I am unsure if that is the
>>>>>> problem.
>>>>>>
>>>>> r255729 is also stable for me - I'm with r255729 again, since r255757
>>>>> crashed.
>>>> Let me know if this fixes the problem for you:
>>>> http://people.freebsd.org/~davide/review/lc_calloutfix.diff
>>>>
>>>> Thanks,
>>>>
>>> Worked for me so far. I generally couldn't stay up more than 30 minutes
>>> before the patch and now my uptime is 90 minutes. Thanks!
>> Same here.
>>
>>
>> --
>> Regards,
>> Bryan Drewery
>>
> I would wait another couple of hours before the commit, but still I'm
> confident this fixed the problem.
>
  7:05PM  up  8:18, 1 user, load averages: 0.08, 0.18, 0.21




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?523E2690.7010709>