From: Mark Knecht <markknecht@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc4-rt1 - enable IRQ-off tracing causes kernel to fault at boot
Date: Thu, 13 Oct 2005 05:26:17 -0700 [thread overview]
Message-ID: <5bdc1c8b0510130526k6064c640pecded9ccb0ef7dde@mail.gmail.com> (raw)
In-Reply-To: <20051013073029.GA12801@elte.hu>
On 10/13/05, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Mark Knecht <markknecht@gmail.com> wrote:
>
> > Config file attached. The only change was to enable IRQ-off latency
> > tracing using make menuconfig. Rebuild and reboot. I got a message
> > about the kernel not syncing, lots of stuff above that message about
> > do_futex, etc.
>
> i cannot reproduce your problems - your .config works fine on my x64
> box. A log of the crash would be needed - do you have a null-modem cable
> to connect this box to some other nearby box to do serial logging? If
> yes then there is a mini-howto below. (for x86, but it works the same
> for x64)
>
> Ingo
>
>
Guitar player doesn't do serial ports? ;-)
OK, I've never done anything like this before, but I'm motivated so
I'll give it a shot. Hopefully I can make some headway without having
to ask too many stupid questions, such as the one that follows:
Question: Is a 'null modem' cable just a plain serial cable, or is it
a special serial cable I need to go buy?
Cheers,
Mark
next prev parent reply other threads:[~2005-10-13 12:26 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 [this message]
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
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=5bdc1c8b0510130526k6064c640pecded9ccb0ef7dde@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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