From: Jay Lan <jlan@sgi.com>
To: Bernhard Walle <bwalle@suse.de>
Cc: linux-ia64@vger.kernel.org, "Luck, Tony" <tony.luck@intel.com>,
kexec@lists.infradead.org, Simon Horman <horms@verge.net.au>
Subject: Re: kdump broken on Altix 350
Date: Wed, 10 Sep 2008 20:21:35 +0000 [thread overview]
Message-ID: <48C82C4F.1050002@sgi.com> (raw)
In-Reply-To: <20080910134805.488b43f9@kepler.site>
Bernhard Walle wrote:
> * "Luck, Tony" <tony.luck@intel.com> [2008-08-29]:
>
>>> your commit
>>>
>>> commit 10617bbe84628eb18ab5f723d3ba35005adde143
>>> Author: Tony Luck <tony.luck@intel.com>
>>> Date: Tue Aug 12 10:34:20 2008 -0700
>>>
>>> [IA64] Ensure cpu0 can access per-cpu variables in early boot
>>> code
>>>
>>> broke kdump on our Altix 350. I get following early crash in kdump
>>> kernel
>> Sorry about that. I'll try to reproduce it here.
>
> I had some discussion about that with Jay Lan that he could not
> reproduce that on his machine. We thought it was different config, but
> now I can verify that the problem is reproducible here with the default
> configuration (plus CONFIG_SATA_VITESSE).
Hi Bernhard and Tony,
I started seeing this problem, and it affected A4700 in addition to
A350.
It was not clear the system hang was related to this problem. I saw a
kdump kernel hang at cpu_init() at an A350, and a hang in find_memory
on handling pernode space thing at an A4700. No error records and no
backtrace, so i did not relate my problem to this one at first.
Out of curiosity, i backed out Tony's patch mentioned from 2.6.27-rc5
and the kdump kernel hangs were gone on both systems.
Also, i had a kdump kernel MCA problem that was caused by kexec
underallocating kernel memory for the kdump kernel. The problem
does not happen again after i backed out the patch.
Regards,
jay
>
>
> Bernhard
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-09-10 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 16:03 kdump broken on Altix 350 Bernhard Walle
2008-08-29 16:05 ` Bernhard Walle
2008-08-29 20:42 ` Luck, Tony
2008-08-29 20:48 ` Bernhard Walle
2008-09-10 11:48 ` Bernhard Walle
2008-09-10 20:21 ` Jay Lan [this message]
2008-09-27 1:00 ` Jay Lan
2008-09-29 20:55 ` Luck, Tony
2008-09-10 12:19 ` Bernhard Walle
2008-09-29 23:42 ` Luck, Tony
2008-09-30 0:30 ` Jay Lan
2008-10-02 5:13 ` Simon Horman
2008-10-02 17:04 ` Jay Lan
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=48C82C4F.1050002@sgi.com \
--to=jlan@sgi.com \
--cc=bwalle@suse.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=tony.luck@intel.com \
/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