__alloc_bootmem_core() has a couple of BUG_ON()'s. Since the handlers
aren't set up this early, if you hit it, you just get along stream of
"Unknown Interrupt" messages. It would be very nice to have a little
bit more information when something has decided to BUG() out this
early.
-- Dave Hansen haveblue@us.ibm.com
--- linux-2.5.70-clean/mm/bootmem.c Mon May 26 18:00:27 2003 +++ linux-2.5.70-early/mm/bootmem.c Fri Jun 6 06:58:46 2003 @@ -151,7 +151,11 @@ __alloc_bootmem_core(struct bootmem_data unsigned long i, start = 0, incr, eidx; void *ret; - BUG_ON(!size); + if(!size) { + printk("__alloc_bootmem_core(): zero-sized request\n"); + dump_stack(); + BUG(); + } BUG_ON(align & (align-1)); eidx = bdata->node_low_pfn - (bdata->node_boot_start >> PAGE_SHIFT); diff -rup linux-2.5.70-clean/mm/page_alloc.c linux-2.5.70-early/mm/page_alloc.c
- 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/
This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:30 EST