public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Zou Nan hai <nanhai.zou@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 Kexec-Kdump kernel patch
Date: Thu, 17 Aug 2006 03:56:16 +0000	[thread overview]
Message-ID: <1155786976.2585.97.camel@linux-znh> (raw)
In-Reply-To: <1155538073.2585.44.camel@linux-znh>

On Thu, 2006-08-17 at 02:25, Bob Montgomery wrote:
> On Wed, 2006-08-16 at 06:40 +0800, Zou Nan hai wrote:
> > On Wed, 2006-08-16 at 01:39, Bob Montgomery wrote:
> > > On Tue, 2006-08-15 at 08:47 +0800, Zou Nan hai wrote:
> 
> > 
> >   If you are not seeing "I am in purgatory" in console, that probably
> > means crash kernel segments and purgatory code was copied into some
> > wrong physical address.
> > 
> >   Can you check the crashkernel="..." parameter
> >   Thanks
> 
> Today, we have had success by changing the configuration of our kernels
> from zx1 to tiger.  Now we'll try to figure out what it is about the zx1
> config parameters that causes the crash_kexec path to break.
> 
> Bob Montgomery
Hi Bob,
	Could you take a look at the ioc_iova_disable code in crash path?

That piece of code is from HP. 
It will only execute if CONFIG_IA64_HP_ZX1 is defined.

I don't have much knowledge of the I/O MMU stuff on HP machines....   	

Thanks
Zou Nan hai

  parent reply	other threads:[~2006-08-17  3:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14  6:47 IA64 Kexec-Kdump kernel patch Zou Nan hai
2006-08-14 21:24 ` Bob Montgomery
2006-08-15  0:47 ` Zou Nan hai
2006-08-15  1:56 ` Jay Lan
2006-08-15 17:39 ` Bob Montgomery
2006-08-15 19:15 ` Jay Lan
2006-08-15 19:31 ` Bob Montgomery
2006-08-15 19:46 ` Keshavamurthy Anil S
2006-08-15 22:36 ` Zou Nan hai
2006-08-15 22:40 ` Zou Nan hai
2006-08-16 18:25 ` Bob Montgomery
2006-08-16 22:34 ` Jay Lan
2006-08-16 22:46 ` Jay Lan
2006-08-17  0:34 ` Jay Lan
2006-08-17  0:38 ` Jack Steiner
2006-08-17  2:57 ` Horms
2006-08-17  3:56 ` Zou Nan hai [this message]
2006-08-17 18:53 ` 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=1155786976.2585.97.camel@linux-znh \
    --to=nanhai.zou@intel.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