From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: bugme-daemon@bugzilla.kernel.org,
Yannick Dirou <yannick.dirou@axetic.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bug 10071] kernel hang in inet_init (PREEMPT_RCU problem)
Date: Thu, 28 Feb 2008 16:58:23 -0800 [thread overview]
Message-ID: <20080229005823.GF14104@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080228213457.GA2770@ami.dom.local>
On Thu, Feb 28, 2008 at 10:34:57PM +0100, Jarek Poplawski wrote:
> On Thu, Feb 28, 2008 at 12:53:03PM -0800, bugme-daemon@bugzilla.kernel.org wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=10071
> ...
> > ------- Comment #17 from yannick.dirou@axetic.com 2008-02-28 12:53 -------
> > bingo with classic rcu
>
> Congratulations Yannick!
>
> So, it seems mainly RCU vs. timer(?) problem. I send CC of this message
> to RCU author, linux-kernel and netdev lists.
Interesting! Any chance of a pointer to the original messages?
A quick Google search and a look at LKML showed me nothing. :-/
Thanx, Paul
> I'm not sure how much time you could/will to offer for this debugging.
> Anyway, if it's possible I think it would be interesting to check with
> CONFIG_PREEMPT_RCU = y again, but CONFIG_HOTPLUG_CPU = n ("Processor
> type and features --> Support for suspend on SMP and ...") in the
> meantime.
>
> Many thanks,
> Jarek P.
>
>
> > [ 0.770854] NET: Registered protocol family 2
> > [ 0.770868] 4294668327 net/ipv4/af_inet.c 1387
> > [ 0.770884] 4294668327 net/ipv4/af_inet.c 1390
> > [ 0.770888] 4294668327 net/ipv4/af_inet.c 1393
> > [ 0.770891] 4294668327 net/ipv4/af_inet.c 1402
> > [ 0.770893] 4294668327 net/ipv4/af_inet.c 1407
> > [ 0.773078] 0 4294668328l
> > [ 0.774036] 0 4294668329l
> > [ 0.775037] 0 4294668330l
> > [ 0.775040] 4294668330 net/ipv4/af_inet.c 1419
> > [ 0.775077] 4294668330 net/ipv4/af_inet.c 1426
> > [ 0.775077] 4294668330 net/ipv4/route.c 2998
> > [ 0.775077] 4294668330 net/ipv4/route.c 3009
> > [ 0.775077] 4294668330 net/ipv4/route.c 3016
> > [ 0.775077] IP route cache hash table entries: 32768 (order: 5, 131072
> > bytes)
> > [ 0.775077] 4294668330 net/ipv4/route.c 3027
> > [ 0.775492] TCP established hash table entries: 131072 (order: 8, 1048576
> > bytes)
> > [ 0.776318] TCP bind hash table entries: 65536 (order: 9, 2359296 bytes)
> > [ 0.785670] TCP: Hash tables configured (established 131072 bind 65536)
> > [ 0.785715] TCP reno registered
> >
> >
> > --
> > Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> > ------- You are receiving this mail because: -------
> > You are on the CC list for the bug, or are watching someone who is.
> > You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-02-29 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10071-11547@http.bugzilla.kernel.org/>
[not found] ` <20080228205303.261D311D108@picon.linux-foundation.org>
2008-02-28 21:34 ` [Bug 10071] kernel hang in inet_init (PREEMPT_RCU problem) Jarek Poplawski
2008-02-29 0:58 ` Paul E. McKenney [this message]
2008-02-29 4:32 ` Paul E. McKenney
2008-02-29 6:53 ` Yannick
2008-02-29 16:58 ` Paul E. McKenney
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=20080229005823.GF14104@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yannick.dirou@axetic.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.