On Wed, 30 Jan 2013, Tang Chen wrote: > The failure I'm trying to fix is that if all the memory is hotpluggable, and > user > specified movablemem_map, my code will set all the memory as ZONE_MOVABLE, and > kernel > will fail to allocate any memory, and it will fail to boot. > I'm curious, do you have a dmesg of the failure? Historically I've seen this panic as late as build_sched_domains() because of a bad mapping between pxms and apicids that assumes node 0 is online and results in node_distance() being inaccurate. I'm not sure if you're even getting that far in boot? > Are you saying your memory is not on node0, and your physical address > 0x0 is not on node0 ? And your /sys fs don't have a node0 interface, it is > node1 or something else ? > Exactly, there is a node 0 but it includes no online memory (and that should be the case as if it was solely hotpluggable memory) at the time of boot. The sysfs interfaces only get added if the memory is onlined later. > If so, I think I'd better find another way to fix this problem because node0 > may not be > the first node on the system. > I haven't tried it over the past year or so, but this used to work in the past. I think if we had some more information we'd be able to see if we really need to treat node 0 in a special way. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>