kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: kvm: repeatable kernel crash with Athlon II cpu
Date: Tue, 29 Mar 2016 17:37:25 +0200	[thread overview]
Message-ID: <56FAA135.1080600@redhat.com> (raw)
In-Reply-To: <56FA9DB1.4060704@list.ru>



On 29/03/2016 17:22, Stas Sergeev wrote:
> I've been running dosemu and found out that it hangs
> or reboots one of my PCs. This happens with any fedora-23
> kernels and hand-compiled kernels. The latest I tried, were:
> 4.4.6-300.fc23.x86_64
> 4.5.0-rc6

Can you check if 4.3 works?

> I tried to put the debug printfs into dosemu, and it seems
> the crash happens on KVM_RUN ioctl, but of course the one
> can't say for sure when an instant reboot happens. Yet if
> I disable the KVM use, or try on a different CPU, there is
> no crash too, so I am pretty sure it is the KVM bug.

Yes, that's likely.

> Hope someone can find such an old CPU an reproduce the problem.
> Please let me know what info should I provide or what debugging
> to do to help getting that fixed.

Do you have experience bisecting the kernel?  If so perhaps you can try
doing that.

Paolo

  reply	other threads:[~2016-03-29 15:37 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 [this message]
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
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=56FAA135.1080600@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 \
    /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).