From: Steven Rostedt <rostedt@goodmis.org>
To: Clark Williams <williams@redhat.com>
Cc: linux-kernel@vger.kernel.org, chris perkins <cperkins@OCF.Berkeley.EDU>
Subject: Re: 2.6.15-rt16
Date: Wed, 01 Feb 2006 13:32:50 -0500 [thread overview]
Message-ID: <1138818770.6685.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1138730835.5959.3.camel@localhost.localdomain>
On Tue, 2006-01-31 at 12:07 -0600, Clark Williams wrote:
> On Tue, 2006-01-31 at 09:52 -0800, chris perkins wrote:
> > > <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>
> >
> > hi,
> > actually i'm running on a dual processor x86_64. with the problem i was
> > having, i never got far enough to see the message you asked about. Steven
> > Rostedt's suggestion to turn off NUMA worked and i am now able to boot.
> > However, if I turn LATENCY_TRACING on, i get an immediate reboot after the
> > kernel is uncompressed. this doesn't sound like the same problem you're
> > having, though.
>
> Man, I saw that LATENCY_TRACING and completely missed the NUMA
> parameter. Sorry about that...
>
> I must be the only person running a uniprocessor x86_64 that's working
> with the -rt patches and trying to trace latencies. If I turn off
> LATENCY_TRACING, I boot just fine.
>
> Are you getting any output from the kernel before the reboot?
I'm still curious to what's happening with your kernel. I'm currently
running my x86_64 (typing right now on it) with CONFIG_SMP=n and
CONFIG_LATENCY=y. I know you probably sent a config before, but could
you send it to me again. (probably best to send it to me off list)
Thanks,
-- Steve
next prev parent reply other threads:[~2006-02-01 18:33 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 ` 2.6.15-rt16 Clark Williams
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 ` Steven Rostedt [this message]
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=1138818770.6685.1.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=cperkins@OCF.Berkeley.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=williams@redhat.com \
/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
Powered by JetHome