netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Sami Farin <hvtaifwkbgefbaei@gmail.com>,
	netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: (ipt_log_packet, sb_add) 3.6.0-rc2 kernel panic - not syncing; Fatal exception in interrupt
Date: Sun, 2 Sep 2012 15:28:34 +0200	[thread overview]
Message-ID: <20120902132834.GB7456@breakpoint.cc> (raw)
In-Reply-To: <20120902122008.jgdhwowbuke6by7h@m.safari.iki.fi>

Sami Farin <hvtaifwkbgefbaei@gmail.com> wrote:
> I get this panic every 1-2 days.
> Also with 7a611e69b26069a511d9d5251c6a28af6c521121 (commit before 3.6.0-rc4).

Could you please post iptables-save output?
My guess is you're using NFLOG in INPUT?

If so, I bet its caused by the tcp early demux stuff.
Does that crash go away with ip_early_demux sysctl off?

My guess is its assigning skb->sk with TIMEWAIT sockets, which
would explain the crash.

  reply	other threads:[~2012-09-02 13:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 13:49 (ipt_log_packet, sb_add) 3.6.0-rc2 kernel panic - not syncing; Fatal exception in interrupt Sami Farin
2012-09-02 12:20 ` Sami Farin
2012-09-02 13:28   ` Florian Westphal [this message]
2012-09-02 13:45     ` Sami Farin
2012-09-02 22:53     ` Eric Dumazet
2012-09-02 23:37       ` Eric Dumazet
2012-09-02 23:48       ` [PATCH v2] netfilter: take care of timewait sockets Eric Dumazet
2012-09-03  7:47         ` Florian Westphal
2012-09-03  9:57           ` Eric Dumazet
2012-09-03 17:23             ` David Miller
2012-09-04  7:55         ` Eric Dumazet
2012-09-04 16:16           ` David Miller
2012-09-14  9:30         ` Sami Farin
2012-09-10  5:02       ` (ipt_log_packet, sb_add) 3.6.0-rc2 kernel panic - not syncing; Fatal exception in interrupt Jan Engelhardt
2012-09-10  6:00         ` Eric Dumazet

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=20120902132834.GB7456@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=hvtaifwkbgefbaei@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).