public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] IA64 Kdump patch V3
Date: Wed, 30 Aug 2006 01:26:38 +0000	[thread overview]
Message-ID: <44F4E94E.8090700@sgi.com> (raw)

Jay Lan wrote:
> Hi Nanhai,
> 
> There is a problem in sn2. The sn2 does not have any memory with
> a predictible offset. It is not possible to specify a memory location
> at boot.
> 
> I modified the efi_initialize_iomem_resources() routine in
> arch/ia64/kernel/efi.c to calculate crashk_res.start and .end on the
> fly and uses the "A" of crashkernel=A@B as size to find a region
> that fits.
> 
> Maybe we should separate A and B as two options?

The "B" part of the crashkernel boot option is meaningless to sn2
machine and can be very confusing to sn2 users.

> 
> I now have memory reserved, but kernal hanged when executing 'kexec'
> command. There must be similar issues in kexec.

On further debugging, the kexec dumped core instead at this statement:
+        elf_rel_set_symbol(&info->rhdr, "__boot_param_base",
+                        &boot_param_base, sizeof(long));

of elf_ia64_load() in kexec/arch/ia64/kexec-elf-ia64.c.

Examing the memory i found "__boot_param_base" indeed not present in
the symbol table.

It seems that purgatory/arch/ia64/entry.S does not have a line
+DECLARE_DATAB(____boot_param_base).
Is it not needed in other ia64 machines? How does it work in HP
machines?

Thanks,
  - jay





> 
> Regards,
>  - jay


             reply	other threads:[~2006-08-30  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  1:26 Jay Lan [this message]
2006-08-30  1:37 ` [Fastboot] IA64 Kdump patch V3 Jay Lan
2006-08-30  1:38 ` Zou, Nanhai
2006-08-30  1:45 ` Jay Lan
2006-08-30  1:54 ` Zou, Nanhai

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=44F4E94E.8090700@sgi.com \
    --to=jlan@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