Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752687Ab3EWG4d (ORCPT ); Thu, 23 May 2013 02:56:33 -0400 Received: from cantor2.suse.de ([195.135.220.15]:44567 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751792Ab3EWG4b (ORCPT ); Thu, 23 May 2013 02:56:31 -0400 Date: Thu, 23 May 2013 08:56:51 +0200 Message-ID: From: Takashi Iwai To: Dave Jones Cc: "H. Peter Anvin" , Linux Kernel , x86@kernel.org, fenghua.yu@intel.com Subject: Re: microcode loading got really slow. In-Reply-To: <20130523033911.GA9411@redhat.com> References: <20130521230332.GC12713@redhat.com> <519D1668.6000601@zytor.com> <20130522200012.GA15456@redhat.com> <20130523033911.GA9411@redhat.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1478 Lines: 40 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 , 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/