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>,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: reboot/kexec in 2.6.38
Date: Fri, 25 Mar 2011 13:49:35 -0700 [thread overview]
Message-ID: <m1bp0zylgg.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110322133034.GA15475@atrey.karlin.mff.cuni.cz> (Cyril Hrubis's message of "Tue, 22 Mar 2011 14:30:34 +0100")
Cyril Hrubis <metan@ucw.cz> writes:
> Hi!
>> I think it's config issue. Never heard of this.
>
> I've just compiled and booted 2.6.38. The kernel boots without problems when
> flashed in. But I've had no success with kexec, the last lines I see are:
>
> Starting new kernel
Enable early_printk to a serial port if you can.
There is definitely an issue in 2.6.38 where kdump doesn't work, that
right now looks like a memblock issue.
Eric
next prev parent reply other threads:[~2011-03-25 20:49 UTC|newest]
Thread overview: 10+ 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 10:58 ` Eric Miao
2011-03-17 12:58 ` Cyril Hrubis
2011-03-17 17:07 ` Eric W. Biederman
2011-03-22 13:30 ` Cyril Hrubis
2011-03-25 20:49 ` Eric W. Biederman [this message]
2011-04-12 14:43 ` Cyril Hrubis
2011-04-12 14:46 ` Eric Miao
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=m1bp0zylgg.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
--cc=zaurus-devel@www.linuxtogo.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