All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Caron <vcaron@bearstech.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Vincent CARON <zerodeux@zerodeux.net>,
	603632@bugs.debian.org, Cris Daniluk <cris.daniluk@gmail.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>, Keir Fraser <keir@xen.org>
Subject: Bug#603632: PVops domain 0 crash on NUMA system only Node==1 present (Was: Re: Bug#603632: linux-image-2.6.32-5-xen-amd64: Linux kernel 2.6.32/xen/amd64 booting fine on bare metal, but not as dom0 with Xen 4.0.1 (Dell R410))
Date: Thu, 25 Nov 2010 14:29:46 +0100	[thread overview]
Message-ID: <1290691786.14372.505.camel@zerohal> (raw)
In-Reply-To: <1290513067.31507.7699.camel@zakaz.uk.xensource.com>

On Tue, 2010-11-23 at 11:51 +0000, Ian Campbell wrote:
>
> One thing I notice when googling R410 issues is that they apparently
> have a "Cores per CPU" BIOS option which might be worth playing with,
> since configuring a reduced number of cores might remove node 0 but not
> node 1 (odd but not invalid?). Presumably it is also worth making sure
> you have the latest BIOS etc.

  Indeed, I tweaked one BIOS setting, I disabled hyperthreading.

  The R410 BIOS has a CPU menu with (among other options):

  - Logical Processor: this is 'HT', default is enabled, I have disabled
it.
  - Virtualization Technology: default is disabled. Kept disabled.
  - Number of Cores per Processor: default is 'All'. Options are
single/dual/all. Kept 'all' defalut.

  I just tried to boot Xen 4.0 hypervisor after reverting to the factory
default 'HT enabled' (aka Logical Processor: Yes), same bug.

  Then I swithed off HT again, and enabled 'Virtualization
Technology' (setting which I totally overlooked, but why is it disabled
as default ?). Same bug.


> It's very much an outside possibility but it is also worth trying the
> packages at http://xenbits.xen.org/people/ianc/ which reinstates the
> changesets from bcf16b6b4f34fb40a7aaf637947c7d3bce0be671

  OK, should I pick the one in
http://xenbits.xen.org/people/ianc/squeeze/ ? (I'm running Debian
Squeeze on this machine)

  parent reply	other threads:[~2010-11-25 13:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101115233253.11935.35707.reportbug@zerohal>
2010-11-23 11:51 ` PVops domain 0 crash on NUMA system only Node==1 present (Was: Re: Bug#603632: linux-image-2.6.32-5-xen-amd64: Linux kernel 2.6.32/xen/amd64 booting fine on bare metal, but not as dom0 with Xen 4.0.1 (Dell R410)) Ian Campbell
2010-11-23 12:44   ` Bug#603632: " Cris Daniluk
2010-11-23 18:24   ` Jeremy Fitzhardinge
2010-11-25 12:51     ` Bug#603632: [Xen-devel] " Vincent Caron
2010-11-25 15:01       ` Ian Campbell
2010-11-25 15:49         ` Bug#603632: [Xen-devel] " Vincent Caron
2010-11-23 18:52   ` Ian Campbell
2010-11-23 22:12     ` Ian Campbell
2010-11-23 22:18       ` Ian Campbell
2010-12-02 23:47         ` Bug#603632: [Xen-devel] " Vincent Caron
2010-12-03  0:12           ` Jeremy Fitzhardinge
2010-12-03  0:27             ` Bug#603632: [Xen-devel] " Vincent Caron
2010-12-03  8:54               ` Ian Campbell
2010-12-03  8:52             ` Ian Campbell
2010-12-03  9:20               ` Ian Campbell
2010-12-03  9:49               ` Ian Campbell
2010-12-03  9:54                 ` [PATCH] xen: disable ACPI NUMA for PV guests Ian Campbell
2010-12-13 22:17                   ` Vincent Caron
2010-12-03  8:51           ` PVops domain 0 crash on NUMA system only Node==1 present (Was: Re: Bug#603632: linux-image-2.6.32-5-xen-amd64: Linux kernel 2.6.32/xen/amd64 booting fine on bare metal, but not as dom0 with Xen 4.0.1 (Dell R410)) Ian Campbell
2010-12-03 10:30             ` Bug#603632: [Xen-devel] " Vincent Caron
2010-11-25 13:29   ` Vincent Caron [this message]
2010-11-25 14:44     ` Ian Campbell
2010-11-25 16:38       ` Bug#603632: " Vincent Caron

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=1290691786.14372.505.camel@zerohal \
    --to=vcaron@bearstech.com \
    --cc=603632@bugs.debian.org \
    --cc=cris.daniluk@gmail.com \
    --cc=ijc@hellion.org.uk \
    --cc=jeremy@goop.org \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=zerodeux@zerodeux.net \
    /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.