From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-arm-kernel@lists.infradead.org
Subject: reboot/kexec in 2.6.38
Date: Thu, 17 Mar 2011 10:07:12 -0700 [thread overview]
Message-ID: <m1d3lpbrr3.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110317125839.GB21290@atrey.karlin.mff.cuni.cz> (Cyril Hrubis's message of "Thu, 17 Mar 2011 13:58:39 +0100")
Cyril Hrubis <metan@ucw.cz> writes:
> Hi!
>> > I got report that ?reboot/kexec does not work in recent kernels.
>> >
>> > I tried both kexec and reboot in 2.6.38, and it worked ok. Maybe
>> > config issue?
>>
>> I think it's config issue. Never heard of this.
>>
>
> I've seen that on my zaurus a month or two ago. When kexeced to pxa-linux-2.6
> then tried to kexec again. The last thing I've seen was Bye on the framebuffer
> console and the machine freezed.
The basic kexec code has been stable and solid for a long time so kexec
failures are almost always hardware interaction problems.
Someone not stopping dma, or someone not putting the hardware in a state
that the next kernel can figure out how to initialize it.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Cyril Hrubis <metan@ucw.cz>
Cc: Eric Miao <eric.y.miao@gmail.com>, Pavel Machek <pavel@ucw.cz>,
rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
arminlitzel@web.de, thommycheck@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
dbaryshkov@gmail.com, omegamoon@gmail.com, utx@penguin.cz,
zaurus-devel@www.linuxtogo.org,
Marek Vasut <marek.vasut@gmail.com>
Subject: Re: reboot/kexec in 2.6.38
Date: Thu, 17 Mar 2011 10:07:12 -0700 [thread overview]
Message-ID: <m1d3lpbrr3.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110317125839.GB21290@atrey.karlin.mff.cuni.cz> (Cyril Hrubis's message of "Thu, 17 Mar 2011 13:58:39 +0100")
Cyril Hrubis <metan@ucw.cz> writes:
> Hi!
>> > I got report that reboot/kexec does not work in recent kernels.
>> >
>> > I tried both kexec and reboot in 2.6.38, and it worked ok. Maybe
>> > config issue?
>>
>> I think it's config issue. Never heard of this.
>>
>
> I've seen that on my zaurus a month or two ago. When kexeced to pxa-linux-2.6
> then tried to kexec again. The last thing I've seen was Bye on the framebuffer
> console and the machine freezed.
The basic kexec code has been stable and solid for a long time so kexec
failures are almost always hardware interaction problems.
Someone not stopping dma, or someone not putting the hardware in a state
that the next kernel can figure out how to initialize it.
Eric
next prev parent reply other threads:[~2011-03-17 17:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 6:45 reboot/kexec in 2.6.38 Pavel Machek
2011-03-17 6:45 ` Pavel Machek
2011-03-17 10:58 ` Eric Miao
2011-03-17 10:58 ` Eric Miao
2011-03-17 12:58 ` Cyril Hrubis
2011-03-17 12:58 ` Cyril Hrubis
2011-03-17 17:07 ` Eric W. Biederman [this message]
2011-03-17 17:07 ` Eric W. Biederman
2011-03-22 13:30 ` Cyril Hrubis
2011-03-22 13:30 ` Cyril Hrubis
2011-03-25 20:49 ` Eric W. Biederman
2011-03-25 20:49 ` Eric W. Biederman
2011-03-25 20:49 ` Eric W. Biederman
2011-04-12 14:43 ` Cyril Hrubis
2011-04-12 14:43 ` Cyril Hrubis
2011-04-12 14:43 ` Cyril Hrubis
2011-04-12 14:46 ` Eric Miao
2011-04-12 14:46 ` Eric Miao
2011-04-12 14:46 ` Eric Miao
2011-04-12 18:13 ` Cyril Hrubis
2011-04-12 18:13 ` Cyril Hrubis
2011-04-12 18:13 ` Cyril Hrubis
2011-03-17 10:58 ` WANG Cong
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=m1d3lpbrr3.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-arm-kernel@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.