mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Benton <b3nt@supanet.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19 Microcode Update causes a ten second wait
Date: Mon, 06 Nov 2006 23:03:44 +0100	[thread overview]
Message-ID: <1162850624.3138.83.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <454FAA44.1080000@supanet.com>

On Mon, 2006-11-06 at 21:33 +0000, Andrew Benton wrote:
> Hello World
> With the 2.6.19 kernels I've tried (2.6.19-rc1-git7 and 
> 2.6.19-rc4-git10), enabling the Intel Microcode Update Driver causes the 
> kernel to hang for more than ten seconds when I boot. The last thing it 
> shows on the screen is `TCP reno registered' and then it just stops like 
> its a kernel panic. But it isn't, after about ten seconds the text flies 
> up the screen again and the system boots normally. Disabling support for 
> the microcode update makes the problem go away.

you're lucky, for me it hangs forever until I add this patch:

--- linux-2.6.18/arch/i386/kernel/microcode.c.org	2006-11-06 14:50:37.000000000 +0100
+++ linux-2.6.18/arch/i386/kernel/microcode.c	2006-11-06 14:52:30.000000000 +0100
@@ -577,7 +577,7 @@ static void microcode_init_cpu(int cpu)
 	set_cpus_allowed(current, cpumask_of_cpu(cpu));
 	mutex_lock(&microcode_mutex);
 	collect_cpu_info(cpu);
-	if (uci->valid)
+	if (uci->valid && system_state==SYSTEM_RUNNING)
 		cpu_request_microcode(cpu);
 	mutex_unlock(&microcode_mutex);
 	set_cpus_allowed(current, old);


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


  reply	other threads:[~2006-11-06 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 21:33 Andrew Benton
2006-11-06 22:03 ` Arjan van de Ven [this message]
2006-11-06 23:05   ` Andrew Benton

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=1162850624.3138.83.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=b3nt@supanet.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®