From: Steven Rostedt <rostedt@goodmis.org>
To: John Rigg <lk@sound-man.co.uk>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.13-rt13 SMP crashes on boot
Date: Mon, 19 Sep 2005 16:49:15 -0400 [thread overview]
Message-ID: <1127162955.5097.25.camel@localhost.localdomain> (raw)
In-Reply-To: <E1EHQmY-0001MS-8L@localhost.localdomain>
Hi John,
First, always CC Ingo on all issues related to the -rt patch. Although
I think he's on vacation now, but even so, he will probably miss this
email.
On Mon, 2005-09-19 at 19:54 +0100, John Rigg wrote:
> I've been trying to get 2.6.13 with RT-preempt patch to run on my
> dual Opteron with debugging code (with CONFIG_PREEMPT_RT=y).
> It crashes on boot if I enable latency tracing in .config. This happens
> with -rt13, -rt12, and -rt4 versions of the patch. Unfortunately it
What was the last release that it worked on? If you could try older
releases, that would really help to know when the problem occurred.
Lots of things have gone on recently since -rt1 and it would help if we
can pin point when this happened, so we would have a good idea of what
happened.
> occurs before any logging, so I can't provide any log data.
Do you have a serial output? Or compile your network driver into the
kernel and turn on netconsole. Usually when someone says "before any
logging", I think of before there's output to the screen. But your next
statements seems to show that that is not the case.
> The crash appears to happen just after drive hda is
> detected, while it's trying to mount my ext3 / filesystem (on hda7).
> The mount fails then the screen fills with a segfault message in an
> infinite loop:
This may just be a 64bit issue as well somewhere.
-- Steve
next prev parent reply other threads:[~2005-09-19 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 18:54 John Rigg
2005-09-19 20:49 ` Steven Rostedt [this message]
2005-09-19 20:54 ` Thomas Gleixner
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=1127162955.5097.25.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@sound-man.co.uk \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®