From: Kazuto Miyoshi <miyoshi@linux.bs1.fc.nec.co.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: INIT dumps broken?
Date: Wed, 15 Sep 2004 16:00:04 +0000 [thread overview]
Message-ID: <20040916.010004.846960466.miyoshi@linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <200409141450.i8EEotfk029379@napali.hpl.hp.com>
Hello,
> Can anybody describe why cpu 0 changed from 0xe... to 0xa... for the
> idle task between 2.6.7-rc3 and 2.6.8?
init_task is initialized by INIT_TASK macro and it fills the init_task
with 0xa.. value, which is computed at compilation time.
Thus, we observed 0xa.. link lists from 0xe.. mapping and it caused
panic with components which refer swapper.
Actually, there was different approach which is to initialize init_task
again with 0xe.. value after boot, but it requries future maintainance
of the re-initialization with the changes of task_struct.
That is the reason we proposed the patch to maintain coherent view of
task_struct.
Currently we do not have consistent way to solve the problem,
but we will try to think about fixing the problem.
BTW, I tried INIT on my box but it seemed to produce correct task
dump to the console. I will look at it more closely...
Best Regards,
--
Kazuto Miyoshi, NEC
miyoshi@hpc.bs1.fc.nec.co.jp
next prev parent reply other threads:[~2004-09-15 16:00 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
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 [this message]
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=20040916.010004.846960466.miyoshi@linux.bs1.fc.nec.co.jp \
--to=miyoshi@linux.bs1.fc.nec.co.jp \
--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