linux-kernel - Re: microcode loading got really slow.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hhahu89qk.wl%tiwai@suse.de>
Date:	Thu, 23 May 2013 08:56:51 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Dave Jones <davej@...hat.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>, x86@...nel.org,
	fenghua.yu@...el.com
Subject: Re: microcode loading got really slow.

At Wed, 22 May 2013 23:39:11 -0400,
Dave Jones wrote:
> 
>  > On 05/21/2013 04:03 PM, Dave Jones wrote:
>  > 
>  > [   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@...azian.fsnet.co.uk>, Peter Oruba
>  > 
>  > For some reason the events for udev seem to be getting delayed 60s
>  > for each core.
> 
> Screwed up my .config, and had CONFIG_FW_LOADER_USER_HELPER inadvertantly set
> Odd though that it causes that 60 second delay, given that it's supposedly a
> 'fallback' when the direct loading fails.

The 60 seconds delay is just because it falls back to usermode
helper, ended in the default timeout.  By some reason, either udev
didn't return properly or the firmware loader didn't handle the
response properly.

Might be a regression in the firmware loader part, or might be
user-space side.  I'll take a look at this later.


thanks,

Takashi

> It seems I don't actually need to set that option, so I'm not bothered
> if there's an actual bug here or not, but the behaviour seems odd.
> 
> 	Dave
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/