From: Patrick McHardy <kaber@trash.net>
To: Jon Masters <jonathan@jonmasters.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: PROBLEM: reproducible crash KVM+nf_conntrack all recent 2.6 kernels
Date: Thu, 28 Jan 2010 13:19:29 +0100 [thread overview]
Message-ID: <4B6180D1.6050609@trash.net> (raw)
In-Reply-To: <1264658364.2793.105.camel@tonnant>
Jon Masters wrote:
> On Thu, 2010-01-28 at 00:46 -0500, Jon Masters wrote:
>
>> A number of people seem to have reported this crash in various forms,
>> but I have yet to see a solution, and can reproduce on 2.6.33-rc5 this
>> evening so I know it's still present in the latest upstream kernels too.
>> Userspace is Fedora 12, and this happens on both all recent F12 kernels
>> (sporadic in 2.6.31 until recently, solidly reproducible on 2.6.32) and
>> upstream 2.6.32, and 2.6.33-rc5 also - hard to find a "known good".
>
> Now I can capture the panic()s, I'm rebuilding the 2.6.33-rc5 kernel
> with some better debugging options to at least get some more data.
Could you try "ip6tables -t raw -I PREROUTING -j TRACE" after loading
the ip6t_LOG module? That way we can hopefully see the entire packet
paths through netfilter.
next prev parent reply other threads:[~2010-01-28 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 5:45 PROBLEM: reproducible crash KVM+nf_conntrack all recent 2.6 kernels Jon Masters
2010-01-28 5:59 ` Jon Masters
2010-01-28 12:19 ` Patrick McHardy [this message]
2010-01-28 21:05 ` Jon Masters
2010-01-28 21:49 ` Jon Masters
2010-01-28 23:21 ` Jon Masters
2010-01-29 1:11 ` Jon Masters
2010-01-29 8:42 ` Jon Masters
2010-01-29 9:10 ` Eric Dumazet
2010-01-29 10:57 ` Jon Masters
2010-01-29 21:51 ` Jon Masters
2010-01-28 7:20 ` Jon Masters
2010-01-28 8:07 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2010-01-28 9:19 Alexey Dobriyan
2010-01-28 11:21 ` Jon Masters
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=4B6180D1.6050609@trash.net \
--to=kaber@trash.net \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).