From: Jon Masters <jonathan@jonmasters.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: reproducible crash KVM+nf_conntrack all recent 2.6 kernels
Date: Thu, 28 Jan 2010 06:21:00 -0500 [thread overview]
Message-ID: <1264677660.2793.128.camel@tonnant> (raw)
In-Reply-To: <b6fcc0a1001280119t1394d956paa4865c078b52c9f@mail.gmail.com>
On Thu, 2010-01-28 at 11:19 +0200, Alexey Dobriyan wrote:
> > RIP: 0010:[<ffffffff813b4115>] [<ffffffff813b4115>] destroy_conntrack+0x82/0x114
>
> Rebuild kernel with CONFIG_DEBUG_INFO=y.
> Double sure conntracking is compiled-in.
> Then run
>
> addr2line -e vmlinux $RIP
>
> it will tell exact line where kernel is oopsing.
I posted a followup with that detail later in the thread. In every case
the kernel has CONFIG_DEBUG_INFO set, and in the latter example I posted
I had turned on almost every other debugging option. I currently have a
kernel with netfilter debugging turned on but that's proving harder to
cause to fall over (likely because I changed several other options, so I
will rebuild it to be identical to earlier with just NF debug on).
Jon.
next prev parent reply other threads:[~2010-01-28 11:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 9:19 PROBLEM: reproducible crash KVM+nf_conntrack all recent 2.6 kernels Alexey Dobriyan
2010-01-28 11:21 ` Jon Masters [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-28 5:45 Jon Masters
2010-01-28 5:59 ` Jon Masters
2010-01-28 12:19 ` Patrick McHardy
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
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=1264677660.2793.128.camel@tonnant \
--to=jonathan@jonmasters.org \
--cc=adobriyan@gmail.com \
--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).