Andi Kleen wrote: > > That's hard to believe or a serious bug/misconfiguration somewhere. > > Each per CPU data should be <100k (let's say 200k with some slack for modules), > so to fill vmalloc you would need hundreds of CPUs, which a 32bit > kernel doesn't really support anyways because it doesn't support > enough memory for that many CPUs. > > Perhaps you had firmware/hypervisor who passed a gigantic impossible > value here? If yes thy > I don't know why, but in the configuration I saw each percpu area was something like 1.8 MB. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html