linux-kernel - Re: [x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

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]

Date:   Mon, 3 Oct 2016 14:28:29 -0700
From:   Andi Kleen <andi@...stfloor.org>
To:     kernel test robot <xiaolong.ye@...el.com>
Cc:     Andi Kleen <andi@...stfloor.org>, lkp@...org, hmh@....eng.br,
        Andi Kleen <ak@...ux.intel.com>, linux-kernel@...r.kernel.org,
        x86@...nel.org
Subject: Re: [x86]  811565123a: BUG: kernel hang in early-boot stage, last
 printk: Probing EDD (edd=off to disable)... ok

On Sat, Oct 01, 2016 at 10:59:38AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
> 
> https://github.com/0day-ci/linux Andi-Kleen/x86-Report-Intel-platform_id-in-proc-cpuinfo/20160924-100841
> commit 811565123a194d9cc0b490719bef761e1730dbf4 ("x86: Report Intel platform_id in /proc/cpuinfo")
> 
> in testcase: boot
> 
> on test machine: qemu-system-x86_64 -enable-kvm -m 320M
> 
> caused below changes:

I tried to reproduce this, but can't. If I use the config with qemu it
boots until it panics for missing root file system.

The most likely cause would be the RDMSR failing.

Your config doesn't have the Intel microcode driver enabled.

With the change the MSR read will be done unconditional
(because I moved it to generic x86 code). But that should
have worked anyways because when the microcode driver is enabled
it would do the same thing. Also KVM supports this MSR, it
is in the code for single git has history.

So it is puzzling why it is failing.

> CONFIG_MICROCODE=y
> # CONFIG_MICROCODE_INTEL is not set
> CONFIG_MICROCODE_AMD=y
> CONFIG_MICROCODE_OLD_INTERFACE=y

Could you do two tests for me:

- Enable CONFIG_MICROCODE_INTEL and see if it boots then

- Add CONFIG_DEBUG_INFO to the config.
Add -s to the qemu command line and boot again. Then when it hangs 
connect gdb to see where it hangs

gdb -ex "target remote localhost:1234" vmlinux
bt

<show output>

-Andi