All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Deti Fliegl <deti@fliegl.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: kernel oops in 2.6.17.7 (smp)
Date: Mon, 09 Oct 2006 17:04:28 +0200	[thread overview]
Message-ID: <452A64FC.5060001@trash.net> (raw)
In-Reply-To: <45260F5A.60700@fliegl.de>

Deti Fliegl wrote:
> Hi there,
> 
> a kernel oops happens since ages with this setup with all recent kernels
> (since 2.6.12) - and most probably even with the latest versions. Here
> it takes about 60 days to reproduce:
> 
> ----------------------------------------------------------------
> Unable to handle kernel paging request at ffffc2000031d103 RIP:
> <ffffffff88103e83>{:ip_tables:ipt_do_table+194}
> PGD 11fc42067 PUD 11fc43067 PMD 11f72b067 PTE 0
> Oops: 0000 [1] SMP
> CPU 2
> Modules linked in: ipt_ipp2p ipt_REDIRECT af_packet i8xx_tco xt_CLASSIFY
> sch_htb xt_mark xt_CONNMARK ipt_SAME xt_state xt_pkttype xt_NOTRACK
> iptable_raw edd ipt_LOG xt_limit ipt_hashlimit xt_tcpudp
>  ip_conntrack_netlink ip_nat_ftp ip_conntrack_ftp thermal processor fan
> button iptable_nat battery ip_nat ac xt_MARK ip_conntrack nfnetlink
> iptable_filter iptable_mangle ip_tables x_tables ipmi_si ipmi_devintf
> ipmi_msghandler ext3 jbd ide_cd cdrom e1000 piix sg megaraid_mbox
> megaraid_mm sd_mod scsi_mod ide_disk ide_core
> Pid: 4709, comm: syslog-ng Not tainted 2.6.17.7-smp #1
> RIP: 0010:[<ffffffff88103e83>]
> <ffffffff88103e83>{:ip_tables:ipt_do_table+194}

This should be fixed in the latest 2.6.17-stable kernel. Please try and
report in case it still crashes.

      reply	other threads:[~2006-10-09 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  8:10 kernel oops in 2.6.17.7 (smp) Deti Fliegl
2006-10-09 15:04 ` Patrick McHardy [this message]

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=452A64FC.5060001@trash.net \
    --to=kaber@trash.net \
    --cc=deti@fliegl.de \
    --cc=netfilter-devel@lists.netfilter.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.