From: Dave Jones <davej@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
x86@kernel.org, fenghua.yu@intel.com
Subject: Re: microcode loading got really slow.
Date: Wed, 22 May 2013 20:19:58 -0400 [thread overview]
Message-ID: <20130523001957.GA32651@redhat.com> (raw)
In-Reply-To: <ebdf0a48-4f93-48da-a0a2-b601268c8fb2@email.android.com>
On Wed, May 22, 2013 at 01:09:52PM -0700, H. Peter Anvin wrote:
> Dave Jones <davej@redhat.com> wrote:
>
> >On Wed, May 22, 2013 at 12:03:04PM -0700, H. Peter Anvin wrote:
> > > On 05/21/2013 04:03 PM, Dave Jones wrote:
> > > > In 3.10-rc2 I see this happening..
> > > >
> > > > [ 72.318133] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x6
> > > > [ 132.446449] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x6
> > > > [ 192.573101] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x6
> >> > [ 252.702055] microcode: Microcode Update Driver: v2.00
> ><tigran@aivazian.fsnet.co.uk>, Peter Oruba
> > > >
> >> > For some reason the events for udev seem to be getting delayed 60s
> >for each core.
> > > >
> > > > Dave
> > > >
> > >
> > > Is this a regression from -rc1?
> >
> >No. Looks like it was introduced between 3.9 and 3.10-rc1
> >
> >I see bisecting in my future.
> >
> A bisect would be appreciated. Cc Fenghua.
Turns out that I can reproduce this on 3.9 too (and likely earlier) with the right
config file. I'm not sure what option causes the delay yet. Isolating differences
between configs now.
Dave
next prev parent reply other threads:[~2013-05-23 1:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 23:03 microcode loading got really slow Dave Jones
2013-05-22 19:03 ` H. Peter Anvin
2013-05-22 20:00 ` Dave Jones
2013-05-22 20:09 ` H. Peter Anvin
2013-05-23 0:19 ` Dave Jones [this message]
2013-05-23 3:39 ` Dave Jones
2013-05-23 6:56 ` Takashi Iwai
2013-05-23 7:45 ` Ming Lei
2013-05-23 8:06 ` Takashi Iwai
2013-05-23 10:16 ` Takashi Iwai
2013-05-23 10:18 ` anish singh
2013-05-23 10:28 ` Takashi Iwai
2013-05-23 10:27 ` Ming Lei
2013-05-23 10:36 ` Takashi Iwai
2013-05-23 10:45 ` Ming Lei
2013-05-23 12:05 ` Takashi Iwai
2013-05-23 13:04 ` Ming Lei
2013-05-23 13:21 ` Takashi Iwai
2013-05-23 14:28 ` Ming Lei
2013-05-23 14:36 ` Takashi Iwai
2013-05-23 14:48 ` Dave Jones
2013-05-23 15:06 ` Takashi Iwai
2013-05-23 15:27 ` Ming Lei
2013-05-23 15:55 ` Dave Jones
2013-05-23 15:21 ` Ming Lei
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=20130523001957.GA32651@redhat.com \
--to=davej@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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