From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] print backtrace from OS INIT handler
Date: Mon, 21 Apr 2003 17:21:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705578@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705506@msgid-missing>
On Tuesday 15 April 2003 2:24 pm, David Mosberger wrote:
> The patch below is relative to 2.5.67 and adds support to print a
> backtrace from the OS INIT handler. The complete INIT output looks
> now something like shown below. The example is for the case when INIT
> is received while a CPU is idle in PAL_LIGHT_HALT. Caveat: at the
> moment, the INIT handler doing this dumping is called only on the
> bootstrap CPU. Hopefully, this can be extended to cover the other
> CPUs without too much trouble (hint hint... ;-).
I applied this (without extension to other CPUs ;-) for 2.4, although
we don't have print_symbol() in 2.4, so we don't get the nice IP decoding.
I also picked up the earlier min-state dump changes.
Bjorn
prev parent reply other threads:[~2003-04-21 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 20:24 [Linux-ia64] print backtrace from OS INIT handler David Mosberger
2003-04-21 17:21 ` Bjorn Helgaas [this message]
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=marc-linux-ia64-105590723705578@msgid-missing \
--to=bjorn_helgaas@hp.com \
--cc=linux-ia64@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