From: Ingo Molnar <mingo@elte.hu>
To: Mark Knecht <markknecht@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc4-rt1 - enable IRQ-off tracing causes kernel to fault at boot
Date: Fri, 14 Oct 2005 05:52:30 +0200 [thread overview]
Message-ID: <20051014035230.GB6513@elte.hu> (raw)
In-Reply-To: <5bdc1c8b0510131210i64f7f289q557368b056e59e18@mail.gmail.com>
* Mark Knecht <markknecht@gmail.com> wrote:
> Ingo & Steve,
> Thank you for your great instructions that even a guitar player
> could basically follow. After about an hour of messing around I did
> manage to capture the crash. The console file is attached.
>
> NOTE: The first time I booted the kernel it got to the crash point and
> the machine rebooted. The second time it booted I got the trace. Both
> boots are in the capture file.
thanks, this log is much more informative. No smoking gun though, but it
seems something fundamental (probably lowlevel x64 code) has been broken
by -rt1.
Do the crashes go away if you take the -rc3-rt13 version of
arch/x86_64/kernel/entry.S and copy it over into the -rc4-rt1 tree?
[this undoes a particular set of CONFIG_CRITICAL_IRQSOFF_TIMING fixes
from the x64 code, which i did during -rc3-rt13 => -rc4-rt1]
(Note that doing this will re-introduce tracing bugs, which can result
in false-positive latency readings - but it should fix any related
lowlevel bug in the assembly code.)
if this indeed solves the crash then i'd suggest to restore the -rt1
version of entry.S, and i'd suggest to disable CRITICAL_IRQSOFF_TIMING
until i fix it. You should be able to get pretty good latency tracing
info even without CRITICAL_IRQSOFF_TIMING.
Ingo
next prev parent reply other threads:[~2005-10-14 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 17:00 2.6.14-rc4-rt1 - enable IRQ-off tracing causes kernel to fault at boot Mark Knecht
2005-10-13 7:30 ` Ingo Molnar
2005-10-13 12:26 ` Mark Knecht
2005-10-13 12:41 ` Steven Rostedt
2005-10-13 12:47 ` Steven Rostedt
2005-10-13 19:10 ` Mark Knecht
2005-10-14 3:52 ` Ingo Molnar [this message]
2005-10-14 14:56 ` Mark Knecht
2005-10-14 19:40 ` Mark Knecht
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=20051014035230.GB6513@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=rostedt@goodmis.org \
/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