IA64 Kdump patch V3
Quoted 6 lines · Jay Lan
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.
Quoted 6 lines
I modified the
efi_initialize_iomem_resources()routine inarch/ia64/kernel/efi.cto 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.
Quoted 3 lines
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
Quoted 3 lines
Regards,
- jay
Quoted 28 lines · Jay Lan
Quoted 6 lines · Jay Lan
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.
Quoted 6 lines
I modified the
efi_initialize_iomem_resources()routine inarch/ia64/kernel/efi.cto 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.
Quoted 3 lines
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:
(quoted diff) +2
-0+ elf_rel_set_symbol(&info->rhdr, "__boot_param_base", + &boot_param_base, sizeof(long));
Quoted 1 line
of
elf_ia64_load()inkexec/arch/ia64/kexec-elf-ia64.c.
Well, need a bit of clarification. :) The code hits a die() since elf_rel_find_symbol() returned -1. The die() routine would do an exit(1), but i changed die() to force a core dump to examine the memory.
Regards,
- jay
Quoted 13 lines
Examing the memory i found "
__boot_param_base" indeed not present in the symbol table.It seems that
purgatory/arch/ia64/entry.Sdoes 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
Quoted 20 lines
-----Original Message-----
From: Jay Lan [mailto:[email protected]]
Sent: 2006Äê8ÔÂ30ÈÕ 9:27
To: Zou, Nanhai
Cc: Linux-IA64; fastboot; Luck, Tony; Dave Anderson; Eric W. Biederman; Horms
Subject: Re: [Fastboot] IA64 Kdump patch V3Quoted 11 lines · Jay Lan
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 inarch/ia64/kernel/efi.cto 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.
Quoted 5 lines
Quoted 1 line
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.
Hi, Jay
It is possible to have only A option and let kernel determine the B address at startup time. Horms has patch to do that, I will merge it.
Quoted 10 lines
Quoted 3 lines
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:
(quoted diff) +2
-0+ elf_rel_set_symbol(&info->rhdr, "__boot_param_base", + &boot_param_base, sizeof(long));of
elf_ia64_load()inkexec/arch/ia64/kexec-elf-ia64.c.
Quoted 7 lines
Examing the memory i found "
__boot_param_base" indeed not present in the symbol table.It seems that
purgatory/arch/ia64/entry.Sdoes not have a line +DECLARE_DATAB(____boot_param_base).
Is it not needed in other ia64 machines? How does it work in HP machines?
There is a DECLARE_DATA8(__boot_param_base) in purgatory/arch/ia64/entry.S Are you using kexec-tools-kdump10 patch?
Thanks
Zou Nan hai
Quoted 4 lines
Thanks,
- jay
Quoted 22 lines · Nanhai
Quoted 22 lines
-----Original Message-----
From: Jay Lan [mailto:[email protected]]
Sent: 2006年8月30日 9:27
To: Zou, Nanhai
Cc: Linux-IA64; fastboot; Luck, Tony; Dave Anderson; Eric W. Biederman; Horms
Subject: Re: [Fastboot] IA64 Kdump patch V3Quoted 12 lines · Jay Lan
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 inarch/ia64/kernel/efi.cto 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?
Quoted 8 lines
Quoted 3 lines
The "B" part of the crashkernel boot option is meaningless to sn2 machine and can be very confusing to sn2 users.
Hi, Jay
It is possible to have only A option and let kernel determine the B address at startup time. Horms has patch to do that, I will merge it.
That would be great!
Quoted 13 lines
Quoted 13 lines
Quoted 3 lines
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:
(quoted diff) +2
-0+ elf_rel_set_symbol(&info->rhdr, "__boot_param_base", + &boot_param_base, sizeof(long));of
elf_ia64_load()inkexec/arch/ia64/kexec-elf-ia64.c.Examing the memory i found "
__boot_param_base" indeed not present in the symbol table.
Quoted 7 lines
Quoted 4 lines
It seems that
purgatory/arch/ia64/entry.Sdoes not have a line +DECLARE_DATAB(____boot_param_base).
Is it not needed in other ia64 machines? How does it work in HP machines?There is a
DECLARE_DATA8(__boot_param_base)inpurgatory/arch/ia64/entry.SAre you using kexec-tools-kdump10 patch?
Yes, i apply the kexec-tools-kdump10 patch and the "reserve efi memmap and boot param" patch from you. Only these two. Did i miss any?
Thanks,
- jay
Quoted 7 lines
Thanks
Zou Nan haiQuoted 3 lines
Thanks,
- jay
Quoted 61 lines
-----Original Message-----
From: Jay Lan [mailto:[email protected]]
Sent: 2006年8月30日 9:46
To: Zou, Nanhai
Cc: Linux-IA64; fastboot; Luck, Tony; Dave Anderson; Eric W. Biederman; Horms
Subject: Re: [Fastboot] IA64 Kdump patch V3Quoted 22 lines · Nanhai
Quoted 22 lines
-----Original Message-----
From: Jay Lan [mailto:[email protected]]
Sent: 2006年8月30日 9:27
To: Zou, Nanhai
Cc: Linux-IA64; fastboot; Luck, Tony; Dave Anderson; Eric W. Biederman; Horms
Subject: Re: [Fastboot] IA64 Kdump patch V3Quoted 12 lines · Jay Lan
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 inarch/ia64/kernel/efi.cto 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?
Quoted 7 lines
Quoted 3 lines
The "B" part of the crashkernel boot option is meaningless to sn2 machine and can be very confusing to sn2 users.
Hi, Jay
It is possible to have only A option and let kernel determine the B addressat startup time. Horms has patch to do that, I will merge it.
Quoted 1 line
That would be great!
Quoted 18 lines
Quoted 17 lines
Quoted 3 lines
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:
(quoted diff) +2
-0+ elf_rel_set_symbol(&info->rhdr, "__boot_param_base", + &boot_param_base, sizeof(long));of
elf_ia64_load()inkexec/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.Sdoes not have a line +DECLARE_DATAB(____boot_param_base).
Is it not needed in other ia64 machines? How does it work in HP machines?
Quoted 7 lines
Quoted 1 line
There is a
DECLARE_DATA8(__boot_param_base)in
purgatory/arch/ia64/entry.SQuoted 1 line
Are you using kexec-tools-kdump10 patch?
Yes, i apply the kexec-tools-kdump10 patch and the "reserve efi memmap and boot param" patch from you. Only these two. Did i miss any?
Then there should be a lineDECLARE_DATA8(__boot_param_base) in purgatory/arch/ia64/entry.S...
If it is hang in kernel, maybe there is something wrong with the physical destination address of reserved region, have you checked the /proc/iomem?
Thanks
Zou Nan hai
Quoted 11 lines
Thanks,
- jayQuoted 7 lines
Thanks
Zou Nan haiQuoted 3 lines
Thanks,
- jay
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html