mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@dsv.su.se>
To: Michael Thonke <iogl64nx@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc1-bk does not boot x86_64
Date: Sun, 03 Apr 2005 15:02:01 +0200	[thread overview]
Message-ID: <1112533321.2369.1.camel@localhost.localdomain> (raw)
In-Reply-To: <424FE590.5060507@gmail.com>

> I tried the recent 2.6.12-rc1-bk5 snapshot from kernel.org.
> When I want to boot my x86_64 system only a green line appears on screen.
> The config is the same as in 2.6.12-rc1-bk4 which works flawlessly on my
> system.
> 
> I only saw the message that CPU0 and CPU1 where initialized. And then
> there was
> Brinnging up CPUs and it stopped.
> 
> Its an Intel Pentium4 640 with (EMT64,HT,EIST,CIE enabled).
> The graphic card is an Nvidia 6600GT PCIe device.

I had the same nasty surprise this morning, this will probably help:


Well, this is a brown paper bag for someone.  The new protocol
registration locking uses a rwlock to limit access to the protocol list.
Unfortunately, the initialisation:

static rwlock_t proto_list_lock;

Only works to initialise the lock as unlocked on platforms whose unlock
signal is all zeros.  On other platforms, they think it's already locked
and hang forever.

Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>


===== net/core/sock.c 1.67 vs edited =====
--- 1.67/net/core/sock.c	2005-03-26 17:04:35 -06:00
+++ edited/net/core/sock.c	2005-04-02 13:37:20 -06:00
@@ -1352,7 +1352,7 @@
 
 EXPORT_SYMBOL(sk_common_release);
 
-static rwlock_t proto_list_lock;
+static DEFINE_RWLOCK(proto_list_lock);
 static LIST_HEAD(proto_list);
 
 int proto_register(struct proto *prot, int alloc_slab)


-



  reply	other threads:[~2005-04-03 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-03 12:46 Michael Thonke
2005-04-03 13:02 ` Alexander Nyberg [this message]
2005-04-03 13:48   ` Michael Thonke

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=1112533321.2369.1.camel@localhost.localdomain \
    --to=alexn@dsv.su.se \
    --cc=iogl64nx@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®