From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: HVM crash system on AMD APU A8-6600K
Date: Tue, 8 Apr 2014 12:17:34 -0400
Message-ID: <20140408161734.GA32387@phenom.dumpdata.com>
References: <52EFB9FA.7010905@oracle.com>
	<CABPT1LvN7u4Et-jxAeUjBRAJZKh7DP1uA3eyRJbndKe28vGo-g@mail.gmail.com>
	<CAFLBxZZZ0VTEHjAbsH8F8GW3eGgzZ1n2oE6zgX9EVhiV6_KopA@mail.gmail.com>
	<5343CCEC02000078000066F8@nat28.tlf.novell.com>
	<CABPT1Lt6XabtnKM2OLH6KE4DehtPWkOrjVbF9BAQ-A4ODDrxmQ@mail.gmail.com>
	<5343DA1002000078000067E2@nat28.tlf.novell.com>
	<CABPT1Lu3ZX4QgdW0u=3B=HBgYsudFbhHXU+DEb5axsRSxMVthA@mail.gmail.com>
	<82947503.20140408160053@eikelenboom.it>
	<CABPT1LvJ5iFtnmXWY5ijbMQ8eVEaOgEZAFsesGBKhYGAqc_6eQ@mail.gmail.com>
	<1715555847.20140408181046@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <1715555847.20140408181046@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xensource.com, Vitaliy Tomin <highwaystar.ru@gmail.com>, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, Apr 08, 2014 at 06:10:46PM +0200, Sander Eikelenboom wrote:
> 
> Tuesday, April 8, 2014, 5:29:06 PM, you wrote:
> 
> >> Hmm from the logs you seem to have a serial console attached,
> >> perhaps wise to also add a "noreboot" to the xen line in grub so it doesn't automatically
> >> reboot on crash. There is a small chance it will print something usefull then.
> >>
> > I've tried noreboot option with last log, my system still reboots with
> > no notice.
> 
> Please keep people who try to help you CC'ed on replies, otherwise you probably won't
> get much response (added Jan again).
> 
> So that seems to imply it's not a Xen induced reboot.

Are you by any chance running your machine at 'overclocked' mode?

That bit me with unexplained reboots and crashes.
> 
> >> Another thing to check could be if you are running the latest bios, since the logs
> >> do report problems with setting up CPU's (APIC and MTRR warnings).
> 
> > I'm running latest bios.
> 
> OK, have you also done some basic other checks to try to rule out hardware?
> 
> - Doing a memtest with memtest86+ for example to see if everything is ok ?
> - Do some CPU burnin/stresstest on baremetal linux / dom0 ?
> 
> 
> >> medium == a disk specified in the config file with "disk=" ?
> >>
> >> The automatic restarts are by a script by you ?
> >> From http://wiki.xen.org/wiki/Xen_Configuration_File_Options#HVM:
> >> on_crash
> >>     Behavior when a domain exits with reason 'crash'
> 
> > Yes config without "disk=". All hvm config is next 3 lines:
> > name = 'blank'
> > builder = 'hvm'
> > memory = 1024
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel