On Mon, 2006-01-30 at 09:24 -0800, chris perkins wrote: > >> i'm trying to use ingo's 2.6.15-rt16 patch on an x86_64 machine but it > >> keeps crashing in kmem_cache_init during bootup. i've tried older > >> 2.6.15-rtX patches and they all crash during startup but vanilla 2.6.15 > >> works fine for me. anyone else seen this happen with realtime-preempt > >> patches? here's the message: > > > > Can you please send me your .config file ? > > <snip> > CONFIG_LATENCY_TIMING=y I'm betting this is the same thing I'm seeing. Are you running on a uniprocessor x86_64? And if so are you seeing messages similar to the following? init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp 00007fffffdacfc8 If so, then I suspect that you're getting a segfault in ld.so (at least that's the furthest I've gotten so far). Something about how the kernel sets up the memory map is upsetting dynamically loaded executables. I can boot with init=/sbin/sash, but when I try and run a dynamically linked program, I get segfaults. You might try turning off LATENCY_TRACING and see if that allows you to boot and run (works for me). Meanwhile, I'm going to try and pin this down to something better than "somewhere in ld.so..." Clark - Clark Williams <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: 2.6.15-rt16
- From: chris perkins <[email protected]>
- Re: 2.6.15-rt16
- References:
- 2.6.15-rt16
- From: chris <[email protected]>
- Re: 2.6.15-rt16
- From: Thomas Gleixner <[email protected]>
- Re: 2.6.15-rt16
- From: chris perkins <[email protected]>
- 2.6.15-rt16
- Prev by Date: Re: [PATCH] exec: Cleanup exec from a non thread group leader.
- Next by Date: Re: [PATCH] record last user if malloc request is exact 4k
- Previous by thread: Re: 2.6.15-rt16
- Next by thread: Re: 2.6.15-rt16
- Index(es):