From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question regarding call trace.
Date: Mon, 27 Feb 2006 17:38:20 -0600 [thread overview]
Message-ID: <44038D6C.3080907@shaw.ca> (raw)
In-Reply-To: <5KW4H-13v-11@gated-at.bofh.it>
Justin Piszcz wrote:
> I have a trace that looks like the following, my question is, are the
> process(es) at the top of the call trace responible for the actual crash
> of the machine? Are they the root cause?
This looks like a dump from a SysRq-T keypress to dump the stack on all
threads.. where is the crash?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-02-27 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5KW4H-13v-11@gated-at.bofh.it>
2006-02-27 23:38 ` Robert Hancock [this message]
2006-02-27 19:12 Question regarding call trace Justin Piszcz
2006-02-27 19:33 ` Jesper Juhl
2006-02-27 19:52 ` Justin Piszcz
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=44038D6C.3080907@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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