From: Paolo Bonzini <pbonzini@redhat.com>
To: Stas Sergeev <stsp@list.ru>, kvm@vger.kernel.org
Cc: Stas Sergeev <stsp@users.sourceforge.net>,
Linux kernel <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: kvm: repeatable kernel crash with Athlon II cpu
Date: Tue, 29 Mar 2016 19:13:49 +0200 [thread overview]
Message-ID: <56FAB7CD.7060900@redhat.com> (raw)
In-Reply-To: <56FAB6FC.2000204@list.ru>
On 29/03/2016 19:10, Stas Sergeev wrote:
> Same on 3.18, and that's the oldest kernel that can be built
> on f23 (gcc5).
Can you try getting even older kernel directly from Koji? Worst case it
doesn't boot. :)
Paolo
> So that's a genuine bug after all, not a regression.
> So does anyone have the AMD AthlonII X2 245 to try reproducing this?
next prev parent reply other threads:[~2016-03-29 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 15:22 kvm: repeatable kernel crash with Athlon II cpu Stas Sergeev
2016-03-29 15:37 ` Paolo Bonzini
2016-03-29 16:08 ` Stas Sergeev
2016-03-29 16:27 ` Paolo Bonzini
2016-03-29 17:10 ` Stas Sergeev
2016-03-29 17:13 ` Paolo Bonzini [this message]
2016-03-30 13:28 ` Stas Sergeev
2016-03-30 14:10 ` Paolo Bonzini
2016-03-31 13:24 ` Stas Sergeev
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=56FAB7CD.7060900@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@list.ru \
--cc=stsp@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.