Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On Sat, 21 Sep 2013 09:34:59 -0700 Davide Italiano dav...@freebsd.org wrote: On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery bdrew...@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 ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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. I hadn't enough time to let the systems in question run overnight, but from this morning, one of the boxes has been patched and is now under heavy load (buildworld and some other nasty stuff I artificially put onto the box, i.e. some numerical calculations). At least, the system lasted the buildworl for now over 35 minutes and it crashed before the patch after a minute or so under load. I put the patch now onto the second system in row and check whether the stability is the same on another CPU generation as well. Thanks for the fast response. Regards, Oliver signature.asc Description: PGP signature
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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. signature.asc Description: PGP signature
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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, -- Davide There are no solved problems; there are only problems that are more or less solved -- Henri Poincare ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On 09/21/13 09:41, Davide Italiano wrote: On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
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 ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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 signature.asc Description: OpenPGP digital signature
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery bdrew...@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 ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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. -- Davide There are no solved problems; there are only problems that are more or less solved -- Henri Poincare ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On Sat, 21 Sep 2013 09:34:59 -0700 Davide Italiano dav...@freebsd.org wrote: On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery bdrew...@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 ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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. At the moment all systems are under load and duty, I can patch earliest tonight and report tomorrow after the boxes stayed up overnight. signature.asc Description: PGP signature
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
In message 523d8c39.4050...@freebsd.org, Bryan Drewery writes: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bTOWMsw68o4sI8l0qJIHm7QU0StCi2OQm Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 9/21/2013 7:06 AM, Bjoern A. Zeeb wrote: On Sat, 21 Sep 2013, Bryan Drewery wrote: =20 Unread portion of the kernel message buffer: panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140 cpuid =3D 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef= 9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb= 10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip =3D 0, rsp =3D 0xfe118aeefcb0, rbp =3D 0 --- =20 =20 +1 from me; I guess introduced somwhere between 255569 and 255758, as these are my edges of kernel.old and kernel. =20 r255726 was stable for me. r255759 is not. r255755 converted ipfilter to callout, but I am unsure if that is the problem. I've been running the r255755 code locally on a couple of r255665 systems for about a week with no problems but I'll check it again. -- Cheers, Cy Schubert cy.schub...@komquats.com FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On 9/21/2013 2:14 PM, Cy Schubert wrote: In message 523d8c39.4050...@freebsd.org, Bryan Drewery writes: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bTOWMsw68o4sI8l0qJIHm7QU0StCi2OQm Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 9/21/2013 7:06 AM, Bjoern A. Zeeb wrote: On Sat, 21 Sep 2013, Bryan Drewery wrote: =20 Unread portion of the kernel message buffer: panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140 cpuid =3D 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef= 9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb= 10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip =3D 0, rsp =3D 0xfe118aeefcb0, rbp =3D 0 --- =20 =20 +1 from me; I guess introduced somwhere between 255569 and 255758, as these are my edges of kernel.old and kernel. =20 r255726 was stable for me. r255759 is not. r255755 converted ipfilter to callout, but I am unsure if that is the problem. I've been running the r255755 code locally on a couple of r255665 systems for about a week with no problems but I'll check it again. It's ok, the problem wasn't your commit afterall. I missed that another made more impactful callout changes recently. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]
On 09/21/13 12:34, Davide Italiano wrote: On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery bdrew...@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 ohart...@zedat.fu-berlin.de wrote: On Sat, 21 Sep 2013 07:08:25 -0500 Bryan Drewery bdrew...@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 0xfe118aeef820 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0 vpanic() at vpanic+0x126/frame 0xfe118aeef910 panic() at panic+0x43/frame 0xfe118aeef970 __rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980 _callout_stop_safe() at _callout_stop_safe+0x54/frame 0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame 0xfe118aeefa30 softclock_call_cc() at softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at softclock+0x47/frame 0xfe118aeefb30 intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 0xfe118aeefb70 ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0 fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0 --- trap 0, rip = 0, rsp = 0xfe118aeefcb0, 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org