From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: INIT dumps broken?
Date: Wed, 15 Sep 2004 07:16:47 +0000 [thread overview]
Message-ID: <16344.1095232607@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <200409141450.i8EEotfk029379@napali.hpl.hp.com>
On Tue, 14 Sep 2004 07:50:55 -0700,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>I noticed that with kernel v2.6.9-rc1 INIT dumps appear not to work
>anymore. The machine just hangs, without ever (visibly) control
>reaching the OS INIT handler. v2.6.7-rc3 was OK. Anybody know what
>broke?
cpu 0 is using init_task's original address.
2.6.7-rc3, kdb ps A
Task Addr Pid Parent [*] cpu State Thread Command
0xe0000430148dc000 0 0 1 0 I 0xe0000430148dc4b0 *swapper
0xe00004b43be70000 0 1 1 1 I 0xe00004b43be704b0 swapper
0xe00004b43bd68000 0 1 1 2 I 0xe00004b43bd684b0 swapper
0xe0000430067b0000 0 1 1 3 I 0xe0000430067b04b0 swapper
2.6.8.1, kdb ps A
Task Addr Pid Parent [*] cpu State Thread Command
0xa0000001008e8000 0 0 1 0 I 0xa0000001008e84d0 *swapper <=0xe00004b43bd38000 0 1 1 1 I 0xe00004b43bd384d0 swapper
0xe00004b43bd00000 0 1 1 2 I 0xe00004b43bd004d0 swapper
0xe00004b0037e0000 0 1 1 3 I 0xe00004b0037e04d0 swapper
The use of 0xa.. for cpu 0 is causing an MCA when cpu 0 receives INIT.
next prev parent reply other threads:[~2004-09-15 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 14:50 INIT dumps broken? David Mosberger
2004-09-14 18:42 ` Luck, Tony
2004-09-15 7:16 ` Keith Owens [this message]
2004-09-15 7:56 ` David Mosberger
2004-09-15 14:14 ` Keith Owens
2004-09-15 15:35 ` Luck, Tony
2004-09-15 16:00 ` Kazuto Miyoshi
2004-09-15 17:35 ` Luck, Tony
2004-09-15 21:38 ` Russ Anderson
2004-09-15 22:23 ` Luck, Tony
2004-09-16 6:49 ` Christian Hildner
2004-09-16 13:51 ` Kazuto Miyoshi
2004-09-27 13:34 ` Takao Indoh
2004-09-27 23:03 ` Keith Owens
2004-09-28 0:03 ` Takao Indoh
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=16344.1095232607@kao2.melbourne.sgi.com \
--to=kaos@sgi.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