public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: Jacob Shin <jacob.shin@amd.com>,
	linux-kernel@vger.kernel.org, Jacob Shin <jacob.w.shin@gmail.com>
Subject: Re: early microcode on amd is broken when no initramfs provided
Date: Tue, 16 Jul 2013 19:00:55 +0200	[thread overview]
Message-ID: <20130716170055.GG4402@pd.tnic> (raw)
In-Reply-To: <20130711230525.40bc6491@fem.tu-ilmenau.de>

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.
--

  reply	other threads:[~2013-07-16 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 16:36 early microcode on amd is broken when no initramfs provided Johannes Hirte
2013-07-09 18:47 ` Borislav Petkov
     [not found]   ` <CAOPg7FsgstsjEpVVQERr6m0fYcSko0Q8PcDkq5XrRNX=2QVNmg@mail.gmail.com>
2013-07-10  3:59     ` Borislav Petkov
2013-07-10  7:30 ` Borislav Petkov
2013-07-11 21:05   ` Johannes Hirte
2013-07-16 17:00     ` Borislav Petkov [this message]
2013-07-20 19:01       ` Torsten Kaiser
2013-07-20 22:59         ` Borislav Petkov
2013-07-21  4:01           ` Torsten Kaiser
2013-07-21 11:53           ` Johannes Hirte

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=20130716170055.GG4402@pd.tnic \
    --to=bp@alien8.de \
    --cc=jacob.shin@amd.com \
    --cc=jacob.w.shin@gmail.com \
    --cc=johannes.hirte@fem.tu-ilmenau.de \
    --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