Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1629491
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [BUG] x86: failed to boot a kernel on a Ryzen machine |
| Date | 2017-04-24 14:50 +0200 |
| Message-ID | <tzLBf-72B-1@gated-at.bofh.it> (permalink) |
| References | <tzG8y-3DA-19@gated-at.bofh.it> <tzK2u-6io-21@gated-at.bofh.it> <tzLrA-6Zn-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-24 13:10 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-24 14:40 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Borislav Petkov <bp@alien8.de> - 2017-04-24 14:50 +0200
Re: [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi <satoru.takeuchi@gmail.com> - 2017-04-24 15:10 +0200
csiph-web