Re: Panic on 8-node system in memblock_virt_alloc_try_nid()

From: Santosh Shilimkar
Date: Thu Jan 23 2014 - 22:45:22 EST


On Thursday 23 January 2014 05:49 PM, Dave Hansen wrote:
> Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
> have. Its reboots are *LONG*, so I haven't fully bisected it, but it's
> down to a just a few commits, most of which are changes to the memblock
> code. Since the panic is in the memblock code, it looks like a
> no-brainer. It's almost certainly the code from Santosh or Grygorii
> that's triggering this.
> Config and good/bad dmesg with memblock=debug are here:
> Please let me know if you need it bisected further than this.
Thanks a lot for debug information. Its pretty useful. The oops
seems to be actually side effect of not setting up the numa nodes
correctly first place. At least the setup_node_data() results
indicate that. Actually setup_node_data() operates on the physical
memblock interfaces which are untouched except the alignment change
and thats potentially reason for the change in behavior.

Will you be able revert below commit and give a quick try to see
if the behavior changes ? It might impact other APIs since they
assume the default alignment as SMP_CACHE_BYTES but at least
I want to see if with below revert at least setup_node_data()
reserves correct memory space.

79f40fa mm/memblock: drop WARN and use SMP_CACHE_BYTES as a default alignment

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at