From: Steven Rostedt <rostedt@goodmis.org>
To: Clark Williams <williams@redhat.com>
Cc: chris perkins <cperkins@OCF.Berkeley.EDU>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rt16
Date: Wed, 01 Feb 2006 20:22:15 -0500 [thread overview]
Message-ID: <1138843335.6632.35.camel@localhost.localdomain> (raw)
In-Reply-To: <1138833380.18762.67.camel@localhost.localdomain>
Clark,
[...]
switchroot: exec'ing /sbin/init
init[1]: segfault at ffffffff8010fadc rip ffffffff8010fadc rsp 00007fffffdacfc8 error 15
Kernel panic - not syncing: Segfault in init
[...]
Could you find where that ffffffff8010fadc is. Compile with debug info,
and (what I do) is a "gdb vmlinux" and "li *0xffffffff8010fadc" to find
the location. The dump may be something that is done after the init
exits.
-- Steve
next prev parent reply other threads:[~2006-02-02 1:22 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 ` 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 ` Steven Rostedt [this message]
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=1138843335.6632.35.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.