From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Dom0 crash with old style AMD NUMA detection Date: Fri, 14 Sep 2012 14:58:22 -0400 Message-ID: <20120914185822.GA7495@phenom.dumpdata.com> References: <501BC20F.3040205@amd.com> <20120803123628.GB10670@andromeda.dapyr.net> <20120817142237.GA8467@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120817142237.GA8467@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Andre Przywara , Jeremy Fitzhardinge , xen-devel List-Id: xen-devel@lists.xenproject.org > > > [ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task! > > > (XEN) Domain 0 crashed: 'noreboot' set - not rebooting. > > > > > > > > > > > > The obvious solution would be to explicitly deny northbridge scanning > > > when running as Dom0, though I am not sure how to implement this without > > > upsetting the other kernel folks about "that crappy Xen thing" again ;-) > > > > Heh. > > Is there a numa=0 option that could be used to override it to turn it > > off? > > Not compile tested.. but was thinking something like this: ping? > > diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c > index 43fd630..838cc1f 100644 > --- a/arch/x86/xen/setup.c > +++ b/arch/x86/xen/setup.c > @@ -17,6 +17,7 @@ > #include > #include > #include > +#include > #include > #include > > @@ -528,4 +529,7 @@ void __init xen_arch_setup(void) > disable_cpufreq(); > WARN_ON(set_pm_idle_to_default()); > fiddle_vdso(); > +#ifdef CONFIG_NUMA > + numa_off = 1; > +#endif > }