From: Cliff Larsen <clarsen@egenera.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] make INIT# handler call panic
Date: Thu, 11 Nov 2004 17:12:08 +0000 [thread overview]
Message-ID: <1100193128.16960.237.camel@clarsen> (raw)
In-Reply-To: <1099662943.913.180.camel@clarsen>
On Wed, 2004-11-10 at 19:55, Takao Indoh wrote:
> On Wed, 10 Nov 2004 10:53:38 -0500, Philip R Auld wrote:
> >
> >We are still mostly a working with 2.4 (rhel3 which has netdump_func hooks)
> >and this all worked fine. A crashdump hook, a call to panic, or a call
> >to BUG each worked.
>
> Crashdump itself succeeds, but isn't there any problem in analyzing
> dump? Backtrace of "current" on each cpu seem to not work because
> switch_stack is not saved correctly.
We are seeing the same behavior with our 2.4 - we can backtrace all
process but the active.
--
Cliff Larsen <clarsen@egenera.com>
next prev parent reply other threads:[~2004-11-11 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 13:55 [PATCH] make INIT# handler call panic Cliff Larsen
2004-11-05 16:26 ` Bjorn Helgaas
2004-11-05 21:04 ` Cliff Larsen
2004-11-05 22:04 ` Bjorn Helgaas
2004-11-05 22:57 ` Cliff Larsen
2004-11-05 23:04 ` Russ Anderson
2004-11-08 12:14 ` Takao Indoh
2004-11-10 15:53 ` Philip R Auld
2004-11-11 0:55 ` Takao Indoh
2004-11-11 1:14 ` Luck, Tony
2004-11-11 17:12 ` Cliff Larsen [this message]
2004-11-11 17:18 ` Cliff Larsen
2004-11-11 17:33 ` Luck, Tony
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=1100193128.16960.237.camel@clarsen \
--to=clarsen@egenera.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