All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: Does kexec on IA64 work?
Date: Sat, 12 May 2007 00:05:15 +0200	[thread overview]
Message-ID: <20070511220514.GA1625@suse.de> (raw)
In-Reply-To: <1178917927.10349.210.camel@ustr-shaha1-linux2.na.uis.unisys.com>

* Amul Shah <amul.shah@unisys.com> [2007-05-11 23:12]:
> I am using a redhat derived 2.6.18 linux kernel and I am experiencing a
> panic when the second kernel boots.  I can't find the exact set of
> emails that I want to tell me that kexec on IA64 isn't ready yet.

Well, it basically works ...

> Horms said this a month ago:
> https://lists.linux-foundation.org/pipermail/fastboot/2007-March/013286.html
>         My recommendation is that 2.6.21rc3 is a farily good release for
>         kexec,
>         and if you aren't worried about ia64 then 2.6.20 is probably
>         good too.
>         If you really need something against 2.6.9, then I guess you
>         will have
>         to try to pull the patches out of git, but that is going to be
>         really hard work given that 2.6.9 is quite old now.
> 
> For the curious, the panic log is below.  I did a cursory inspection of
> the kernel sources and found that the function start_secondary is called
> from head.S.  I don't know much about IA64 arch and assembly, so I
> thought I would ask first if the IA64 implementation works.

Did you try the 'maxpus=1' option for the panic kernel?


Thanks,
   Bernhard

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2007-05-11 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 21:12 Does kexec on IA64 work? Amul Shah
2007-05-11 22:05 ` Bernhard Walle [this message]
2007-05-14 17:13   ` TuskenTower

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=20070511220514.GA1625@suse.de \
    --to=bwalle@suse.de \
    --cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.