From: Mark Knecht <markknecht@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, 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 12:10:31 -0700 [thread overview]
Message-ID: <5bdc1c8b0510131210i64f7f289q557368b056e59e18@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0510130844070.13098@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On 10/13/05, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Thu, 13 Oct 2005, Mark Knecht wrote:
>
> >
> > Question: Is a 'null modem' cable just a plain serial cable, or is it
> > a special serial cable I need to go buy?
> >
>
> Also make sure that you get a cable with two female ends. If the computer
> guy has half a clue, asking for a 'null modem cable' with two female ends
> to connect two computers together. Should be enough info for him to get
> you the right cable. Although he might ask "9 pin or 25?". Which you
> would say 9. :-)
>
> -- Steve
>
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.
Hope this helps!
Cheers,
Mark
[-- Attachment #2: minicom.cap.bz2 --]
[-- Type: application/x-bzip2, Size: 10874 bytes --]
next prev parent reply other threads:[~2005-10-13 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 17:00 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 [this message]
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=5bdc1c8b0510131210i64f7f289q557368b056e59e18@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®