On Wed, 2003-10-22 at 11:10, David S. Miller wrote: > On Tue, 21 Oct 2003 23:46:37 +0200 > Karl Vogel <karl.vogel@seagha.com> wrote: > > > Got the following call trace when running an ipsec connection between my > > 2.6.0-test8-mm1 box and a Checkpoint FW-1 NG firewall: > > > > Uninitialised timer! > > This is just a warning. Your computer is OK > > function=0x00030004, data=0x0 > > Call Trace: > > [<c0124288>] check_timer_failed+0x40/0x4f > > [<c0124567>] del_timer+0x17/0x9a > > [<c02ccdfb>] xfrm_policy_gc_kill+0x4f/0x7d > > Looks like something in the kernel is trying to kill a policy twice > or something unrelated to this code is corrupting the policy structure > triggering the debugging check in del_timer(). Just had an oops on 2.6.0-test9 which, I believe, is related to this. I have been having these lockups for some time, but this was the first time I was not in X, so I was able to see the oops. Wrote it down partly: EIP is at __xfrm_policy_destroy+0x27/0x60 Call trace: run_timer_softirq+0xce/0x1b0 do_softirq+0x96/0xa0 do_IRQ+0x109/0x140 _stext+0x0/0x60 common_interrupt+0x18/0x20 _stext+0x0/0x60 default_idle+0x26/0x30 cpu_idle+0x34/0x40 start_kernel+0x17b/0x1b0 unknown_bootoption+0x0/0x100 Code : 0f 0b ed 00 e3 b4 37 c0 8d 43 10 89 04 24 e8 16 60 e0 ff 85 Fatal exception in interrupt Alt-SysRq+P showed: error_code+0x2d/0x38 xfrm_policy_timer+0x0/0x220 __xfrm_policy_destroy+0x27/0x60 (not sure about the order anymore.. sorry) It takes a while before I hit this.. I can usually run the ipsec connection for a while before getting the lockup. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
