From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: kernel 3.10.1 - "NMI received for unknown reason" Date: Mon, 29 Jul 2013 12:16:37 +0300 Message-ID: <20130729091637.GA18009@redhat.com> References: <51F2BF0F.5060404@sp.consulting.lsexperts.de> <20130726183910.GC3482@redhat.com> <51F6315F.4050205@sp.consulting.lsexperts.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: Stefan Pietsch Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22664 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750904Ab3G2JQn (ORCPT ); Mon, 29 Jul 2013 05:16:43 -0400 Content-Disposition: inline In-Reply-To: <51F6315F.4050205@sp.consulting.lsexperts.de> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Jul 29, 2013 at 11:09:51AM +0200, Stefan Pietsch wrote: > On 26.07.2013 20:39, Gleb Natapov wrote: > > On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote: > >> Hi all, > >> > >> starting a virtual machine (Debian sid) with KVM on my host running > >> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages: > >> > > Are those messages printed by a host or a guest? > > The host shows the messages. > > >> [ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0. > >> [ 765.522927] Do you have a strange power saving mode enabled? > >> [ 765.522930] Dazed and confused, but trying to continue > >> [ 770.487732] Uhhuh. NMI received for unknown reason 21 on CPU 0. > >> [ 770.487740] Do you have a strange power saving mode enabled? > >> [ 770.487742] Dazed and confused, but trying to continue > >> [ 846.340966] Uhhuh. NMI received for unknown reason 31 on CPU 1. > >> [ 846.340973] Do you have a strange power saving mode enabled? > >> [ 846.340976] Dazed and confused, but trying to continue > >> [ 847.563023] Uhhuh. NMI received for unknown reason 31 on CPU 0. > >> [ 847.563029] Do you have a strange power saving mode enabled? > >> [ 847.563032] Dazed and confused, but trying to continue > > Is it safe to ignore them? > They should not happen. What is the last kernel version you tried that does not produce them? Can you verify that they do not happen without guest running? What is the qemu command line you are using to start the guest and what "cat /proc/cpuinfo" looks like in the guest? -- Gleb.