From: Tim Hartrick <tim@edgecast.com>
To: Dave Young <dyoung@redhat.com>
Cc: tj@kernel.org, WANG Cong <xiyou.wangcong@gmail.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Crash during vmcore_init
Date: Wed, 16 Nov 2011 10:20:47 -0800 [thread overview]
Message-ID: <1321467647.2137.4.camel@boudreau> (raw)
In-Reply-To: <4EC31E55.6040809@redhat.com>
Dave,
On Wed, 2011-11-16 at 10:22 +0800, Dave Young wrote:
> On 11/16/2011 06:32 AM, Tim Hartrick wrote:
>
> >
> > Dave,
> >
> > I tested with
> >
> > linux-image-3.1.1-030101-generic_3.1.1-030101.201111111651_amd64.deb
> >
> > which, as far as I know, is the Ubuntu build of the latest stable.
> > Below are the results.
> >
> > [ 1.427457] ioremap: invalid physical address 5800000000000
>
>
> Hi, thanks for the testing
>
> Can you applied the debug patch to see if it's per cpu problem?
>
> Don't need test kdump, just
> cd /sys/devices/system/cpu
> cat cpu[x]/crash_notes
>
> probably cat crash notes of cpu number other than 0 will get the invalid
> address
>
Using 3.1.1 stable with your patch. See below.
tim
# for i in /sys/devices/system/cpu/cpu[0-9]*/crash_notes; do cat $i; done
5800000000000
5800000000000
5800000000000
5800000000000
5800000000000
5800000000000
5800000000000
5800000000000
dmesg:
[ 277.276349] per cpu addr ffff880c7fc19ad0
[ 277.276352] addr is not in vmalloc area
[ 277.277545] per cpu addr ffff880667c19ad0
[ 277.277548] addr is not in vmalloc area
[ 277.278832] per cpu addr ffff880c7fc39ad0
[ 277.278835] addr is not in vmalloc area
[ 277.280175] per cpu addr ffff880667c39ad0
[ 277.280178] addr is not in vmalloc area
[ 277.281406] per cpu addr ffff880c7fc59ad0
[ 277.281409] addr is not in vmalloc area
[ 277.282592] per cpu addr ffff880667c59ad0
[ 277.282594] addr is not in vmalloc area
[ 277.284019] per cpu addr ffff880c7fc79ad0
[ 277.284022] addr is not in vmalloc area
[ 277.285251] per cpu addr ffff880667c79ad0
[ 277.285254] addr is not in vmalloc area
next prev parent reply other threads:[~2011-11-16 18:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1318376345.2050.20.camel@boudreau>
[not found] ` <j9r5m5$b18$1@dough.gmane.org>
[not found] ` <1321296650.2066.17.camel@boudreau>
2011-11-15 8:14 ` Crash during vmcore_init 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 [this message]
2011-11-17 3:30 ` Dave Young
2011-11-17 4:34 ` Tejun Heo
2011-11-17 4:46 ` Dave Young
[not found] ` <CAMMEr5k_ynqg5-7Looar2DxXTGZcMqi5Lo+jtETn9awO_bsaGg@mail.gmail.com>
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 17:01 ` Tejun Heo
2011-11-22 3:00 ` Dave Young
2011-11-22 16:02 ` Tejun Heo
[not found] ` <CAMMEr5my3pt0HXWd1EdwAeZKAJ8JP04tM_WqvHdCNvW=Q3ifvg@mail.gmail.com>
2011-11-22 2:52 ` Dave Young
2011-11-21 21:10 ` Tejun Heo
2011-11-22 2:48 ` Dave Young
2011-11-22 16:19 ` Tejun Heo
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=1321467647.2137.4.camel@boudreau \
--to=tim@edgecast.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).