All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Sims <derek@interdart.co.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] iptables and  BUG: soft lockup detected
Date: Wed, 21 Nov 2007 17:31:21 +0000	[thread overview]
Message-ID: <47446B69.7090403@interdart.co.uk> (raw)

Apologies if this is not relevant to this list.

I am seeing errors when loading a large iptables file

Using iptables-restore containing more than out 1000 rules reports 
errors shown below in the system log:
I am using Centos5 and have tried various processors and memory from 
Celeron 2.4 to Core2Duo and 500Mb to 2Gb

The problem appears to be related to the size of the ruleset being 
loaded - loading the full ruleset of 3000 rules takes about 30 seconds.

My questions are:

1. Should I be worried by these messages
2. Is it likely the rules are not being loaded properly
3. Is there anything I can do to get rid of the errors

Best regards,
Derek

 BUG: soft lockup detected on CPU#0!
 [<c044a05f>] softlockup_tick+0x98/0xa6
 [<c042ccd4>] update_process_times+0x39/0x5c
 [<c04176ec>] smp_apic_timer_interrupt+0x5c/0x64
 [<c04049bf>] apic_timer_interrupt+0x1f/0x24
 [<e09aa7e3>] translate_table+0x22d/0x717 [ip_tables]
 [<c0406406>] do_IRQ+0xa5/0xae
 [<e09aadbb>] do_ipt_set_ctl+0xee/0x607 [ip_tables]
 [<c0453dfd>] get_page_from_freelist+0x2a6/0x310
 [<c05b94bc>] nf_sockopt+0xac/0xda
 [<c05b950e>] nf_setsockopt+0x11/0x16
 [<c05c375f>] ip_setsockopt+0x9fe/0xa1d
 [<c047e1cb>] __d_lookup+0x98/0xdb
 [<c0475bc4>] do_lookup+0x53/0x157
 [<c04db822>] _atomic_dec_and_lock+0x2a/0x44
 [<c0482140>] mntput_no_expire+0x11/0x6a
 [<c0477e37>] __link_path_walk+0xd11/0xd33
 [<c0480a65>] touch_atime+0x60/0x8f
 [<c04049bf>] apic_timer_interrupt+0x1f/0x24
 [<c0453dfd>] get_page_from_freelist+0x2a6/0x310
 [<c0453ebe>] __alloc_pages+0x57/0x27e
 [<c045fdad>] anon_vma_prepare+0x11/0xa5
 [<c045afae>] __handle_mm_fault+0x85e/0x87b
 [<c059c57e>] sock_common_setsockopt+0x12/0x16
 [<c059b020>] sys_setsockopt+0x76/0x95
 [<c059c190>] sys_socketcall+0x15c/0x19e
 [<c0403eff>] syscall_call+0x7/0xb
 ===========


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2007-11-21 17:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47446B69.7090403@interdart.co.uk \
    --to=derek@interdart.co.uk \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.