[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Dom0 crash with old style AMD NUMA detection
> > > [ 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 <asm/e820.h> > #include <asm/setup.h> > #include <asm/acpi.h> > +#include <asm/numa.h> > #include <asm/xen/hypervisor.h> > #include <asm/xen/hypercall.h> > > @@ -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 > } _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |