netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: netdev@vger.kernel.org
Subject: Re: hang after "registering protocol family 2" in linux-next
Date: Sat, 03 Jan 2009 04:20:40 +0100	[thread overview]
Message-ID: <87eizljcs7.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090101043310.GA23765@basil.nowhere.org> (Andi Kleen's message of "Thu, 1 Jan 2009 05:33:10 +0100")

Andi Kleen <andi@firstfloor.org> writes:

> FYI,
>
> I booted today's linux-next and I got a hang somewhere in inet_init 
> (according to initcalL_debug) after Registering protocol family 2
>
> Haven't investigated further.

I did some investigation now and it seems to be related to TREE_RCU.
Goes away with CLASSIC. I'll report it to Paul.

-Andi

-- 
ak@linux.intel.com

      reply	other threads:[~2009-01-03  3:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01  4:33 hang after "registering protocol family 2" in linux-next Andi Kleen
2009-01-03  3:20 ` Andi Kleen [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=87eizljcs7.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=netdev@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).