From: Michael Ellerman <michael@ellerman.id.au>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Maxim Uvarov <muvarov@gmail.com>,
linuxppc-dev@lists.ozlabs.org, uvarov@dev.rtsoft.ru,
kexec@lists.infradead.org, horms@verge.net.au
Subject: Re: [PATCH 1/2] Fix kexec on powerpc32
Date: Thu, 13 May 2010 21:50:32 +1000 [thread overview]
Message-ID: <1273751432.8067.1.camel@concordia> (raw)
In-Reply-To: <alpine.DEB.2.01.1005130417590.3356@bogon.housecafe.de>
[-- Attachment #1.1: Type: text/plain, Size: 627 bytes --]
On Thu, 2010-05-13 at 04:19 -0700, Christian Kujau wrote:
> On Wed, 12 May 2010 at 00:22, Christian Kujau wrote:
> > # kexec -e
> > Starting new kernel
> > Bye!
> >
> > ....but then the system just hung there, no more messages, I had to
> > powercycle it.
>
> Are there any debug flags (or kernel options?) I can set, to find out why
> it hangs here? Or does kexec not understand zImages?
Not really. There's extra debugging on some systems (with a hypervisor
console). I think you're on 32-bit, which means I don't really know what
I'm talking about, but I don't think zImage works - use vmlinux.
cheers
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Maxim Uvarov <muvarov@gmail.com>,
linuxppc-dev@lists.ozlabs.org, uvarov@dev.rtsoft.ru,
kexec@lists.infradead.org, horms@verge.net.au
Subject: Re: [PATCH 1/2] Fix kexec on powerpc32
Date: Thu, 13 May 2010 21:50:32 +1000 [thread overview]
Message-ID: <1273751432.8067.1.camel@concordia> (raw)
In-Reply-To: <alpine.DEB.2.01.1005130417590.3356@bogon.housecafe.de>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
On Thu, 2010-05-13 at 04:19 -0700, Christian Kujau wrote:
> On Wed, 12 May 2010 at 00:22, Christian Kujau wrote:
> > # kexec -e
> > Starting new kernel
> > Bye!
> >
> > ....but then the system just hung there, no more messages, I had to
> > powercycle it.
>
> Are there any debug flags (or kernel options?) I can set, to find out why
> it hangs here? Or does kexec not understand zImages?
Not really. There's extra debugging on some systems (with a hypervisor
console). I think you're on 32-bit, which means I don't really know what
I'm talking about, but I don't think zImage works - use vmlinux.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-13 11:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 17:47 [PATCH 1/2] Fix kexec on powerpc32 Maxim Uvarov
2010-05-11 17:47 ` Maxim Uvarov
2010-05-11 17:47 ` [PATCH 2/2] powerpc new toolchains fix (crt.S) Maxim Uvarov
2010-05-11 17:47 ` Maxim Uvarov
2010-05-11 17:57 ` [PATCH 1/2] Fix kexec on powerpc32 Christian Kujau
2010-05-11 17:57 ` Christian Kujau
2010-05-12 3:44 ` Christian Kujau
2010-05-12 3:44 ` Christian Kujau
2010-05-12 6:31 ` Maxim Uvarov
2010-05-12 6:31 ` Maxim Uvarov
2010-05-12 6:56 ` Christian Kujau
2010-05-12 6:56 ` Christian Kujau
2010-05-12 7:28 ` Matt Evans
2010-05-12 8:30 ` Simon Horman
2010-05-12 8:45 ` Simon Horman
2010-05-12 13:19 ` Simon Horman
2010-05-12 13:19 ` Simon Horman
2010-05-12 7:22 ` Christian Kujau
2010-05-12 7:22 ` Christian Kujau
2010-05-12 12:12 ` Maxim Uvarov
2010-05-12 12:12 ` Maxim Uvarov
2010-05-13 11:19 ` Christian Kujau
2010-05-13 11:19 ` Christian Kujau
2010-05-13 11:50 ` Maxim Uvarov
2010-05-13 11:50 ` Maxim Uvarov
2010-05-14 0:43 ` Christian Kujau
2010-05-14 0:43 ` Christian Kujau
2010-05-13 11:50 ` Michael Ellerman [this message]
2010-05-13 11:50 ` Michael Ellerman
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=1273751432.8067.1.camel@concordia \
--to=michael@ellerman.id.au \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=muvarov@gmail.com \
--cc=uvarov@dev.rtsoft.ru \
/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.