linux-kernel - Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

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: <20170424124846.6jkjjywt5gsoxuy3@pd.tnic>
Date:   Mon, 24 Apr 2017 14:48:46 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Satoru Takeuchi <satoru.takeuchi@...il.com>
Cc:     x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote:
> I used the following auto-test tool (its backend is ktest).
> 
> https://github.com/satoru-takeuchi/elkdat
> 
> This problem can be reproduced by the following command on Ubuntu 16.04.
> 
> ```
> $ sudo apt-get install git vagrant libvirt-bin libvirt-dev kernel-package qemu-kvm libssl-dev libncurses5-dev

Can you minimize that reproducer? I.e, can you dump only the qemu
command line options from this setup?

They're enough to be able to start a guest with your config without me
having to install all that other stuff.

Thanks.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.