All of lore.kernel.org
 help / color / mirror / Atom feed
* possible Bug in ip_conntrack
@ 2006-08-14  8:58 Maik Hentsche
  2006-08-14 12:50 ` Patrick McHardy
  0 siblings, 1 reply; 5+ messages in thread
From: Maik Hentsche @ 2006-08-14  8:58 UTC (permalink / raw)
  To: netfilter-devel

Hi!
While debugging a new version of conntrackd, I (nearly) every time get
athe following error "BUG: soft lockup detected on CPU#1!" which
completely hangs the system. Here is, what I do to reproduce the error:
I ue keepalived to manage a virtual IP, that is default gw for two other
machines, which communicate over this IP. I use a client-server-program
to count connections, which simply opens a tcp-socket and immediately
closes it. The gateway uses keepalived and conntrackd-0.8.3 for hot
standby. The HS-master (thta produces the error) has kernel 2.6.18-rc4
running (with no other patches), the slave is a 2.6.17.3 (also
vanilla).  I use valgrind --leak-check=yes for debugging. After some
time, usually between 1 and 5 minutes, the system hangs and writes
something like this out on the serial console.

BUG: soft lockup detected on CPU#1!
Call Trace:
 <IRQ> [<ffffffff80252bc9>] softlockup_tick+0xf9/0x140
 [<ffffffff80239367>] update_process_times+0x57/0x90
 [<ffffffff80216243>] smp_local_timer_interrupt+0x23/0x50
 [<ffffffff802167a8>] smp_apic_timer_interrupt+0x38/0x40
 [<ffffffff8020a962>] apic_timer_interrupt+0x66/0x6c
 <EOI> [<ffffffff8042028d>] _write_lock_irqsave+0x6d/0x90
 [<ffffffff8042026a>] _write_lock_irqsave+0x4a/0x90
 [<ffffffff80420416>] _write_lock_bh+0x6/0x20
 [<ffffffff8811b2a9>] :ip_conntrack:destroy_conntrack+0x69/0x100
 [<ffffffff88137da6>]
:ip_conntrack_netlink:ctnetlink_dump_table+0x116/0x160
 [<ffffffff803c5582>] netlink_dump+0x82/0x1c0
 [<ffffffff803c6ff7>] netlink_recvmsg+0x197/0x2a0
 [<ffffffff803ab13e>] sock_recvmsg+0xde/0x100
 [<ffffffff802264fc>] task_rq_lock+0x4c/0x90
 [<ffffffff80244580>] autoremove_wake_function+0x0/0x30
 [<ffffffff802346db>] current_fs_time+0x3b/0x40
 [<ffffffff80226433>] __wake_up+0x43/0x70
 [<ffffffff8027e3ae>] fget_light+0xae/0xe0
 [<ffffffff803acf7a>] sys_recvfrom+0xfa/0x190
 [<ffffffff80209dbe>] system_call+0x7e/0x83

The calltrace differs every time, but ip_conntrack is always included,
therefore and because it only occured yet when I was debugging
conntrackd I assume its a ip_conntrack problem.

More logmessages and the buggy version of conntrackd can be found here:
http://www-user.tu-chemnitz.de/~hmai/ip_conntrack/

If you need more informations, please let me know.

so long
Maik

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-08-16 14:29 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-14  8:58 possible Bug in ip_conntrack Maik Hentsche
2006-08-14 12:50 ` Patrick McHardy
2006-08-15  8:29   ` Maik Hentsche
2006-08-16 11:31     ` Patrick McHardy
2006-08-16 14:29       ` Maik Hentsche

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.