From: Patrick McHardy <kaber@trash.net>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org, tore@linpro.no
Subject: Re: [BUG] CPU lockup detected
Date: Wed, 17 Oct 2007 18:41:09 +0200 [thread overview]
Message-ID: <47163B25.9060701@trash.net> (raw)
In-Reply-To: <20071017083554.5a4e1f16@freepuppy.rosehill>
Please CC either Bug submitter or bugzilla on forwarded
reports.
Stephen Hemminger wrote:
> Possible suspects TCP MD5 and/or netfilter conntrack.
Conntrack is very unlikely, it has already completely exited
the netfilter codepath when the packet reaches TCP.
prev parent reply other threads:[~2007-10-17 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 15:35 [BUG] CPU lockup detected Stephen Hemminger
2007-10-17 16:41 ` 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=47163B25.9060701@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=tore@linpro.no \
/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).