From: Andrew Benton <b3nt@supanet.com>
To: Arjan van de Ven <arjan@infradead.org>
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:05:27 +0000 [thread overview]
Message-ID: <454FBFB7.10102@supanet.com> (raw)
In-Reply-To: <1162850624.3138.83.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> 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(µcode_mutex);
> collect_cpu_info(cpu);
> - if (uci->valid)
> + if (uci->valid && system_state==SYSTEM_RUNNING)
> cpu_request_microcode(cpu);
> mutex_unlock(µcode_mutex);
> set_cpus_allowed(current, old);
>
Thanks, that patch fixes the problem for me.
Andy
prev parent reply other threads:[~2006-11-06 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 21:33 2.6.19 Microcode Update causes a ten second wait Andrew Benton
2006-11-06 22:03 ` Arjan van de Ven
2006-11-06 23:05 ` Andrew Benton [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=454FBFB7.10102@supanet.com \
--to=b3nt@supanet.com \
--cc=arjan@infradead.org \
--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