Ingo Molnar <[email protected]> writes: > FYI, even on 2.6.17-rc3 i get the one below. v2.6.17 showstopper i > guess? Did you send a full boot log? If it's using ACPI NUMA try numa=noacpi - it might be some problem with the node discovery on your machine. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- From: Ingo Molnar <[email protected]>
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- References:
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- From: Nick Piggin <[email protected]>
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- From: Ingo Molnar <[email protected]>
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- From: Ingo Molnar <[email protected]>
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- From: Ingo Molnar <[email protected]>
- Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- Prev by Date: Re: [PATCH] kexec: Avoid overwriting the current pgd (x86_64)
- Next by Date: Re: [PATCH 7/7] uts namespaces: Implement CLONE_NEWUTS flag
- Previous by thread: Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- Next by thread: Re: assert/crash in __rmqueue() when enabling CONFIG_NUMA
- Index(es):
 |