From: Jarek Poplawski <jarkao2@gmail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, stable@kernel.org,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [Bugme-new] [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing
Date: Tue, 15 Dec 2009 07:54:52 +0000 [thread overview]
Message-ID: <20091215075452.GA6488@ff.dom.local> (raw)
In-Reply-To: <755510.33826.qm@web52905.mail.re2.yahoo.com>
On Tue, Dec 08, 2009 at 05:35:40AM -0800, Chris Rankin wrote:
> --- On Tue, 8/12/09, Jarek Poplawski <jarkao2@gmail.com> wrote:
> > Is it the same .config?
>
> Similar, but no. I'll attach the .config to the bug tonight.
I can see quite a lot of differences, and some could matter here, e.g.
like these:
-# CONFIG_PREEMPT_RCU is not set
+# CONFIG_TREE_RCU is not set
+CONFIG_PREEMPT_RCU=y
...
-CONFIG_PREEMPT_VOLUNTARY=y
-# CONFIG_PREEMPT is not set
+# CONFIG_PREEMPT_VOLUNTARY is not set
+CONFIG_PREEMPT=y
It's hard to guess, but at least this second patch mentioned by you
(ipv4: additional update of dev_net(dev) to struct *net in
ip_fragment.c) shouldn't matter here. Anyway, now 2.6.32.1 should be
preferred for testing (if possible).
Jarek P.
next prev parent reply other threads:[~2009-12-15 7:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14749-10286@http.bugzilla.kernel.org/>
2009-12-07 21:53 ` [Bugme-new] [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing Andrew Morton
2009-12-08 0:19 ` Chris Rankin
2009-12-08 3:03 ` Eric Dumazet
2009-12-08 9:03 ` Chris Rankin
2009-12-08 11:21 ` Eric Dumazet
2009-12-08 11:36 ` Jarek Poplawski
2009-12-08 13:35 ` Chris Rankin
2009-12-08 13:47 ` Jarek Poplawski
2009-12-15 7:54 ` Jarek Poplawski [this message]
2009-12-08 12:00 ` Neil Horman
2009-12-08 13:39 ` Chris Rankin
2009-12-08 13:41 ` Neil Horman
2009-12-08 14:39 ` Eric Dumazet
2009-12-08 9:17 ` Chris Rankin
2009-12-08 0:31 ` Chris Rankin
2009-12-08 0:44 ` Andrew Morton
2009-12-08 0:38 ` Chris Rankin
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=20091215075452.GA6488@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rankincj@yahoo.com \
--cc=stable@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).