Messages in this thread | | | Date | Tue, 22 Oct 2002 17:10:49 -0700 | From | Andrew Morton <> | Subject | Re: New panic (io-apic / timer?) going from 2.5.44 to 2.5.44-mm1 |
| |
"Martin J. Bligh" wrote: > > Hmmm ... 2.5.43-mm2 and 2.5.44 work fine, but 2.5.44-mm1 (and mm2) > panic consistently on boot for a 16 way NUMA-Q. > > Normally this box will boot with TSC on or off. If anyone has any pointers as > to what's changed in the mm patchset going from 43-mm2 to 44-mm1 that > might have touched this area (I can't see anything), please poke me in the > eye. Otherwise I'll just keep digging into it .... >
Is possibly the code which defers the allocation of the per-cpu memory until the secondary processors are being brought online.
I've decided to toss that. It's causing some grief for architectures, and only buys us 10k * (NR_CPUS - nr-cpus) worth of memory anyway.
Well. It would be useful for NUMA to be able to place the per-cpu storage into node-local memory. But the code doesn't do that. It just uses kmalloc on the boot cpu, and we don't have an alloc_pages_for_another_cpu() API.. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |