Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933393Ab3GPRBW (ORCPT ); Tue, 16 Jul 2013 13:01:22 -0400 Received: from mail.skyhub.de ([78.46.96.112]:44461 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932889Ab3GPRBV (ORCPT ); Tue, 16 Jul 2013 13:01:21 -0400 Date: Tue, 16 Jul 2013 19:00:55 +0200 From: Borislav Petkov To: Johannes Hirte Cc: Jacob Shin , linux-kernel@vger.kernel.org, Jacob Shin Subject: Re: early microcode on amd is broken when no initramfs provided Message-ID: <20130716170055.GG4402@pd.tnic> References: <20130709183601.5d567a83@fem.tu-ilmenau.de> <20130710073049.GA15525@pd.tnic> <20130711230525.40bc6491@fem.tu-ilmenau.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20130711230525.40bc6491@fem.tu-ilmenau.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 29 On Thu, Jul 11, 2013 at 11:05:25PM +0200, Johannes Hirte wrote: > config is attached Ok, I can reproduce the hang with your config but even with: $ grep MICROCODE .config # CONFIG_MICROCODE is not set # CONFIG_MICROCODE_INTEL_EARLY is not set # CONFIG_MICROCODE_AMD_EARLY is not set which means, it cannot be microcode-related. And I'd bet if you wait a minute (yep, it should be exactly 60 seconds) the boot would probably continue. And if so, this is that 60 sec delay where the kernel tries to find firmware. Hmm... -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- 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/