From: Borislav Petkov <bp@alien8.de>
To: Satoru Takeuchi <satoru.takeuchi@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] x86: failed to boot a kernel on a Ryzen machine
Date: Mon, 24 Apr 2017 13:07:53 +0200 [thread overview]
Message-ID: <20170424110753.y332daaxxkwiipog@pd.tnic> (raw)
In-Reply-To: <87pog21ede.wl-satoru.takeuchi@gmail.com>
On Mon, Apr 24, 2017 at 03:58:05PM +0900, Satoru Takeuchi wrote:
> Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, it failed to boot
> with the following panic log.
>
> ```
> ...
> [ 0.227720] raid6: sse2x1 gen() 7985 MB/s
> [ 0.295709] raid6: sse2x1 xor() 8181 MB/s
> [ 0.363706] raid6: sse2x2 gen() 17531 MB/s
> [ 0.431699] raid6: sse2x2 xor() 11098 MB/s
> [ 0.499693] raid6: sse2x4 gen() 18509 MB/s
> [ 0.567688] raid6: sse2x4 xor() 10177 MB/s
> [ 0.571692] invalid opcode: 0000 [#1] SMP
> [ 0.572312] Modules linked in:
> [ 0.572822] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.11.0-rc8-ktest #1
> [ 0.573734] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
^^^^^^^^^^^^^^
Next time your report a bug, say it is a guest on the *very* first line
of your report.
Now, how do you start your guest exactly? Full cmdline pls.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-04-24 11:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 6:58 [BUG] x86: failed to boot a kernel on a Ryzen machine Satoru Takeuchi
2017-04-24 11:07 ` Borislav Petkov [this message]
2017-04-24 12:39 ` Satoru Takeuchi
2017-04-24 12:48 ` Borislav Petkov
2017-04-24 13:09 ` Satoru Takeuchi
2017-04-25 9:36 ` Borislav Petkov
2017-04-26 7:48 ` Paolo Bonzini
2017-04-26 8:14 ` Borislav Petkov
2017-04-26 11:47 ` Satoru Takeuchi
2017-04-26 16:58 ` Paolo Bonzini
2017-04-27 0:42 ` Satoru Takeuchi
2017-04-28 13:34 ` Paolo Bonzini
2017-04-29 21:08 ` Satoru Takeuchi
2017-04-25 14:58 ` Masami Hiramatsu
2017-04-26 11:56 ` Satoru Takeuchi
2017-04-26 12:51 ` Borislav Petkov
2017-04-24 11:27 ` Satoru Takeuchi
2017-04-25 7:45 ` Jon Masters
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=20170424110753.y332daaxxkwiipog@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=satoru.takeuchi@gmail.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).