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
Date: Thu, 10 Aug 2006 20:11:52 +0000	[thread overview]
Message-ID: <44DB9308.9070804@sgi.com> (raw)
In-Reply-To: <20060608083516.GH28607@verge.net.au>

Jay Lan wrote:
> Jay Lan wrote:
> 
>> Hi Nanhai and horms,
>>
> 
> [snip]
> 
>> However, the second kernel was not booted and system remained
>> alive.
>>
>> The /proc/{sysrq-trigger,iomem} after the trigger were as below:
>> (holism,9) ls -l /proc/{sysrq-trigger,iomem}
>> -r--r--r-- 1 root root 0 Aug  9 08:10 /proc/iomem
>> --w------- 1 root root 0 Aug  9 08:10 /proc/sysrq-trigger
>> (holism,10)
>>
>> I built the kernel based on 2.6.18-rc2 with Nanhai's
>> kexec-kdump-ia64-2.6.16.patch and my fixes to
>>   - replace  irq_descp(dev->irq) with irq_desc + dev->irq
>>   - replace  desc->handle with desc-chip
>> for compilation.
>>
>> As to kexec-tools, i use kdump9 with Nanhai's
>> kexec-tools-kdump9-ia64-zou.patch.
> 
> 
> Hi,
> 
> I forgot to mention that i ran kexec with these parameters:
> [root@holism redhat]# kexec -p <dump-capture-kernel> \
>  --initrd=,initrd-for-dump-capture-kernel> \
>  --append="root=LABEL=/ init 1 irqpoll console=ttyS0,38400n8 maxcpus=1"
> [root@holism redhat]#
> 
> The command was executed without an error or warning.

And, the first kernel was booted with this append:
append="rhgb quiet root=LABEL=/ console=ttyS0,38400n8 \
  crashkernel\x128M@256M"

I should have provided all these info at my 1st email :(

Regards,
  - jay

> 
> Thanks,
>  - jay
> 
> 
>> What did i miss here? Do i miss any patch(es)?
>> My machine is a HP zx6000 loaded with FC5.
>>
>> Thanks!
>>  - jay
>>
>>>
>>> Thanks
>>> Zou Nan hai
> 
> 


      parent reply	other threads:[~2006-08-10 20:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  8:35 [Fastboot] Ia64 kdump patch Horms
2006-06-08 22:47 ` Zou Nan hai
2006-06-12  0:16 ` Zou Nan hai
2006-06-12  1:50 ` Takao Indoh
2006-06-14 23:30 ` Luck, Tony
2006-06-26  7:47 ` Horms
2006-06-26  8:10 ` Zou, Nanhai
2006-06-26  8:37 ` Horms
2006-06-26  8:49 ` Zou, Nanhai
2006-07-27 21:23 ` Zou Nan hai
2006-07-27 21:41 ` Jay Lan
2006-08-04  1:47 ` Jay Lan
2006-08-04  2:06 ` Zou, Nanhai
2006-08-04  2:08 ` Zou, Nanhai
2006-08-10 19:28 ` Jay Lan
2006-08-10 19:58 ` Jay Lan
2006-08-10 20:11 ` Jay Lan [this message]

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=44DB9308.9070804@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