Re: Crash during vmcore_init
From: Tim Hartrick
Date: Wed Nov 16 2011 - 13:20:52 EST
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/