Messages in this thread | | | Date | Tue, 19 Oct 2004 18:31:25 +0200 | From | Ingo Molnar <> | Subject | Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U6 |
| |
* Ingo Molnar <mingo@elte.hu> wrote:
> > i found older .config's from you and i tried your desktop one and it > > didnt crash. But when i tried your laptop's U3 .config then i got the > > bootup crash immediately. Debugging it ... > > one difference in your config is that you have 4K stacks enabled. > Could you disable them? Especially with rwsem-detection and tracing > enabled the stack footprint can get pretty large ...
indeed, this is what triggers with your .config:
testing NMI watchdog ... OK. ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 mcount: stack overflow: 1008 [<c012cd9f>] ___trace+0x105/0x117 [<c012cdd7>] __mcount+0x1d/0x1f [<c013e015>] cache_grow+0xe/0x1ab [<c013e3cd>] cache_alloc_refill+0x21b/0x253
enabling 8K stacks ought to help this one. I've made the limit a bit too conservative - there's still 1000 bytes left and the assert hits. Here's the full trace, the large footprint seems to be in zlib initialization:
mcount: stack overflow: 1008 [<c012cd9f>] ___trace+0x105/0x117 [<c012cdd7>] __mcount+0x1d/0x1f [<c013e015>] cache_grow+0xe/0x1ab [<c013e3cd>] cache_alloc_refill+0x21b/0x253 [<c010efec>] mcount+0x14/0x18 [<c013e015>] cache_grow+0xe/0x1ab [<c013e3cd>] cache_alloc_refill+0x21b/0x253 [<c013e730>] __kmalloc+0x82/0x9f [<c03607c8>] malloc+0x1e/0x20 [<c01008c9>] huft_build+0x309/0x5e8 [<c0101bec>] inflate+0x4c/0xb0 [<c010efec>] mcount+0x14/0x18 [<c0101279>] inflate_fixed+0xcb/0x1a4 [<c0101bec>] inflate+0x4c/0xb0 [<c010efec>] mcount+0x14/0x18 [<c0101eae>] gunzip+0x1d4/0x396 [<c036130e>] unpack_to_rootfs+0x162/0x225 [<c010efec>] mcount+0x14/0x18 [<c0100434>] init+0x0/0x124 [<c03613fe>] populate_rootfs+0x2d/0x3f [<c010046b>] init+0x37/0x124 [<c0102365>] kernel_thread_helper+0x5/0xb
Ingo - 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/
| |