From: WANG Cong <xiyou.wangcong@gmail.com>
To: kexec@lists.infradead.org
Subject: Re: Crash during vmcore_init
Date: Mon, 14 Nov 2011 13:39:17 +0000 (UTC) [thread overview]
Message-ID: <j9r5m5$b18$1@dough.gmane.org> (raw)
In-Reply-To: 1318376345.2050.20.camel@boudreau
On Tue, 11 Oct 2011 16:39:05 -0700, Tim Hartrick wrote:
> Kexec,
>
> I have been experiencing the crash below on Ubuntu 10.04 running
> 2.6.32-34-server and 2.6.38-8-server as the crashkernel on X86_64. The
> tools are:
>
> kexec-tools 1:2.0.2-1ubuntu3
> makedumpfile 1.3.7-2
> kdump-tools 1.3.7-2
>
> I would be interested to know if this is a known problem and if so
> whether or not there is a patch in the pipeline to correct the problem.
>
> I will be happy to provide any other details that are required including
> debug builds if necessary.
....
>
> [ 1.322100] ioremap: invalid physical address db74000000000000 [
> 1.327919] ------------[ cut here ]------------ [ 1.332530] WARNING:
> at /build/buildd/linux-2.6.32/arch/x86/mm/ioremap.c:120 __ioremap_caller
> +0x360/0x3d0()
This probably means that kexec-tools passed some incorrect
kernel parameter to the second kernel.
So, what is the cmdline of your second kernel? And what is your
/proc/iomem of your first kernel?
Cheers.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-11-14 13:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 23:39 Crash during vmcore_init Tim Hartrick
2011-11-14 13:39 ` WANG Cong [this message]
2011-11-14 18:50 ` Tim Hartrick
2011-11-15 8:14 ` Dave Young
2011-11-15 13:47 ` Américo Wang
2011-11-15 13:50 ` Américo Wang
2011-11-15 22:32 ` Tim Hartrick
2011-11-16 2:22 ` Dave Young
2011-11-16 18:20 ` Tim Hartrick
2011-11-17 3:30 ` Dave Young
2011-11-17 4:34 ` Tejun Heo
2011-11-17 4:46 ` Dave Young
2011-11-17 5:22 ` Tim Hartrick
2011-11-17 7:21 ` Dave Young
2011-11-17 7:23 ` Tejun Heo
2011-11-17 7:42 ` Américo Wang
2011-11-17 16:40 ` Tim Hartrick
2011-11-18 8:43 ` Dave Young
2011-11-18 8:45 ` Dave Young
2011-11-18 18:55 ` [PATCH] percpu: fix chunk range calculation Tejun Heo
2011-11-21 1:45 ` Dave Young
2011-11-21 16:20 ` Tim Hartrick
2011-11-22 2:52 ` Dave Young
2011-11-21 17:01 ` Tejun Heo
2011-11-22 3:00 ` Dave Young
2011-11-22 16:02 ` Tejun Heo
2011-11-21 21:10 ` Tejun Heo
2011-11-22 2:48 ` Dave Young
2011-11-22 16:19 ` Tejun Heo
2011-11-15 14:13 ` Crash during vmcore_init Américo Wang
2011-11-15 22:57 ` Tim Hartrick
2011-11-16 12:47 ` Américo Wang
2011-11-16 13:19 ` Tim Hartrick
2011-11-16 13:31 ` Américo Wang
2011-11-16 13:44 ` Tim Hartrick
[not found] ` <1321462343.4198.29.camel@boudreau>
2011-11-17 6:48 ` Américo Wang
2011-11-17 16:08 ` Tim Hartrick
2011-11-17 16:31 ` Tim Hartrick
2011-11-16 15:52 ` Tim Hartrick
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='j9r5m5$b18$1@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox