From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: OpenBSD 5.0 kernel panic in AMD K10 cpu power state
Date: Wed, 09 Nov 2011 12:39:04 +0200
Message-ID: <4EBA5848.7070404@redhat.com>
References: <4EB8F576.9040203@gmx.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Walter Haidinger <walter.haidinger@gmx.at>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:64815 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753109Ab1KIKjI (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 9 Nov 2011 05:39:08 -0500
In-Reply-To: <4EB8F576.9040203@gmx.at>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 11/08/2011 11:25 AM, Walter Haidinger wrote:
> 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.

Thanks.

> 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.

It doesn't actually follow, but happens to be correct.

> Can somebody reproduce this?

I'll try it out and see.

-- 
error compiling committee.c: too many arguments to function