From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
Subject: Re: Xen 4.0.1 freezes with no output
Date: Wed, 8 Sep 2010 14:17:37 +0300
Message-ID: <20100908111737.GG2804@reaktio.net>
References: <4C864321.3070302@anduras.de> <20100907172401.GA2804@reaktio.net>
	<4C868962.7040305@anduras.de> <20100907185310.GB2804@reaktio.net>
	<4C875C13.7030501@anduras.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-users-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <4C875C13.7030501@anduras.de>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-users@lists.xensource.com>
List-Help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xensource.com?subject=subscribe>
Sender: xen-users-bounces@lists.xensource.com
Errors-To: xen-users-bounces@lists.xensource.com
To: Sven Anders <anders@anduras.de>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Wed, Sep 08, 2010 at 11:49:07AM +0200, Sven Anders wrote:
> Pasi K=E4rkk=E4inen schrieb:
> > On Tue, Sep 07, 2010 at 08:50:10PM +0200, Sven Anders wrote:
> >
> >>> Also 2.6.32.21 is the latest pvops dom0 kernel atm.
> >=20
> > Yep, that'll give you 2.6.32.21 atm.
>=20
> Ok, I tested the latest one. It crashes too. Same phenomenon.
>=20

Ok, I added xen-devel to CC.


> I assume the problem lies in the Xen code, not the pvops dom0 kernel.
> Should I try a newer version of Xen? (Currently using 4.0.1 from tar-fi=
le).
>=20
> But just to be sure:
>  Are there any kernel options which I should NOT use at all?
>  (Please take a look at my kernel config in the first post.)
>=20
> I'm still uncertain about this error message:
>  XENBUS: Unable to read cpu state
>=20
> Are these harmless and can I ignore them? What can be the cause?
> Maybe I should disable some of the BIOS options?
>=20
> Here are some of the options I enabled in the BIOS:
> - MPS and ACPI MADT ordering: Modern ordering
> - Intel(R) Virtualization Tech: Enabled
> - Execute-Disable Bit Capability: Enabled
> - Simultaneous Multi-Threading: Enabled
> - Intel(R) EIST Technologie: Enabled
> - Intel(R) Turbo Boost: Enabled
> - C1E Support: Enabled
> - Intel(R) C-STATE tech: Enabled
> - C State package limit setting: Auto
> - C1 Auto Demotion: Enabled
> - C3 Auto Demotion: Enabled
> - Intel VT-d: Enabled
> - Active State Power Managment: Enabled
> - Remote Access Configuration: Enabled
> - ACPI Aware O/S: Yes
> - ACPI APIC support: Enabled
> - APIC ACPI SCI IRQ: Disabled
> - ACPI Version Features: ACPI v2.0
>=20
> Any other (further) suggestions?
> I'm wondering, because I did not get ANY output at all.
> I enabled full debug output, compiled with debug enabled and I
> still get nothing...
>=20

How long does it take before it silently crashes?

-- Pasi