From: Clark Williams <williams@redhat.com>
To: chris perkins <cperkins@OCF.Berkeley.EDU>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 2.6.15-rt16
Date: Mon, 30 Jan 2006 14:33:55 -0600 [thread overview]
Message-ID: <1138653235.26657.7.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.SOL.4.63.0601300917120.8546@conquest.OCF.Berkeley.EDU>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
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 <williams@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-30 20:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 16:49 2.6.15-rt16 chris
2006-01-30 17:03 ` 2.6.15-rt16 Thomas Gleixner
2006-01-30 17:09 ` 2.6.15-rt16 Steven Rostedt
2006-01-30 17:24 ` 2.6.15-rt16 chris perkins
2006-01-30 18:42 ` 2.6.15-rt16 Steven Rostedt
2006-01-31 17:45 ` 2.6.15-rt16 chris perkins
2006-01-30 20:33 ` Clark Williams [this message]
2006-01-31 17:52 ` 2.6.15-rt16 chris perkins
2006-01-31 18:07 ` 2.6.15-rt16 Clark Williams
2006-02-01 18:32 ` 2.6.15-rt16 Steven Rostedt
2006-02-01 18:39 ` 2.6.15-rt16 Clark Williams
2006-02-01 20:20 ` 2.6.15-rt16 Lee Revell
2006-02-01 21:47 ` 2.6.15-rt16 Steven Rostedt
2006-02-01 21:51 ` 2.6.15-rt16 Clark Williams
2006-02-01 22:16 ` 2.6.15-rt16 Steven Rostedt
2006-02-01 22:36 ` 2.6.15-rt16 Clark Williams
2006-02-02 1:10 ` 2.6.15-rt16 Steven Rostedt
2006-02-02 14:46 ` 2.6.15-rt16 Clark Williams
2006-02-02 1:22 ` 2.6.15-rt16 Steven Rostedt
2006-02-02 15:01 ` 2.6.15-rt16 Clark Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1138653235.26657.7.camel@localhost.localdomain \
--to=williams@redhat.com \
--cc=cperkins@OCF.Berkeley.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox