From: Jay Lan <jlan@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: A regression in IA64 kexec/kdump patch for 2.6.18?
Date: Tue, 17 Oct 2006 00:21:03 +0000 [thread overview]
Message-ID: <453421EF.6040205@engr.sgi.com> (raw)
In-Reply-To: <4533F2BE.3070300@engr.sgi.com>
Zou Nan hai wrote:
> On Tue, 2006-10-17 at 04:59, Jay Lan wrote:
>> I ran into a problem not seen in kexec/dkump 2.6.17rc5 ia64 patch.
>> The system on test was an Altix.
>>
> You mean 2.6.18rc5 patch?
Oops, yes, i meant 2.6.18rc5... although i found the kernel patch
was not the cause. See below.
>> The system was booted up fine; however, after loading 'kexec -p'
>> and "echo c >/proc/sysrq-triggeŕ", the crashdump kernel would try
>> to boot up and restarted the system near the end of init().
>>
>> The extraodinary message observed on the console was
>> Warning: unable to open an initial console
>>
>> but the actual reboot seems to be invoked in running /sbin/init:
>> run_init_process("/sbin/init");
>>
>> The problem is 100% reproducible. I have disabled all cpus except
>> cpu0 in my testing.
>>
>> Is this a known problem? Anyone else runs into this?
>>
> It seems to be an incorrect initrd problem
No, i used the correct initrd. I would not be able to boot the
kernel/initrd pair as the 1st kernel (sytstem kernel) if the
initrd was incorrect.
Well, i built 2.6.18 kernel and 2.6.18rc5 kernels.
I also built 2 kexec-tools based on kdump10 patch. I have been
associating the kexec-tools tree that i built at the rc5 time with
the rc5 kernel and the newer kexec-tools tree with the 2.6.18
kernel.
I just ran a few tests with different combination of kexec-tools
and kernels. Well, it showed that the rc5 version of kexec-tools
worked correctly with both kernels, but the newer version of
kexec-tools displayed the system restart problem with both kernels.
So, it was the kexec-tools that caused the problem. Not the kernel
side. I will diff the patches i applied to both trees...
Later,
- jay
>
> Zou Nan hai
>> Thanks,
>> - jay
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-10-17 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 20:59 A regression in IA64 kexec/kdump patch for 2.6.18? Jay Lan
2006-10-16 21:21 ` Jay Lan
2006-10-16 21:39 ` Zou Nan hai
2006-10-17 0:21 ` Jay Lan [this message]
2006-10-17 1:51 ` Jay Lan
2006-10-17 2:50 ` Zou Nan hai
2006-10-17 15:55 ` 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=453421EF.6040205@engr.sgi.com \
--to=jlan@engr.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