All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walter Haidinger <walter.haidinger@gmx.at>
To: kvm@vger.kernel.org
Subject: OpenBSD 5.0 kernel panic in AMD K10 cpu power state
Date: Tue, 08 Nov 2011 10:25:10 +0100	[thread overview]
Message-ID: <4EB8F576.9040203@gmx.at> (raw)

Hi!

OpenBSD 5.0/i386 throws a kernel panic when I try to
boot it inside a Linux KVM (host: vanilla 3.0.4,
openSUSE 11.4/x86_64) unter qemu-kvm 0.14.1 and 0.15.1. 
Note that OpenBSD 4.9/i386 works.

The OpenBSD developers say:
"the virtual machine emulator you are using has a bug.  it declares
a cpu type from upstream and then does not emulate certain functions
of that cpu."

Therefore I'm reporting this here.

More from misc@openbsd.org:
  > OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011
  >   deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
  > cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB L2 cache) 3.31 GHz
  > ...
  > kernel: protection fault trap, code=0
  > Stopped at      k1x_init+0x56:  rdmsr
  > k1x_init(d0ad7540,d09ae620,d0b8ce58,d059ce20,30000002) at k1x_init+0x56

  k1x_init() is not related to vmt, it is from k1x-pstate.c, which
  is cpu power state driver for K10 processors. 

Thread on misc@openbsd.org with full OpenBSD dmesg:
http://marc.info/?l=openbsd-misc&m=132067866208188&w=2

Since both qemu-kvm 0.14.1 and 0.15.1 show identical
symptoms, I assume this is in deed a KVM kernel bug.

Can somebody reproduce this?

Please CC: me when replying, thanks.
I'll follow the kvm@vger archives, though.

Regards,
Walter

             reply	other threads:[~2011-11-08  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  9:25 Walter Haidinger [this message]
2011-11-09 10:39 ` OpenBSD 5.0 kernel panic in AMD K10 cpu power state Avi Kivity
2011-11-09 13:40   ` Avi Kivity
2011-11-09 14:19     ` Walter Haidinger
     [not found]     ` <4EBAD609.4050307@gmx.at>
2011-11-10  8:46       ` Avi Kivity
2011-11-10 22:52         ` Andre Przywara

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=4EB8F576.9040203@gmx.at \
    --to=walter.haidinger@gmx.at \
    --cc=kvm@vger.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.