[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39



On Wed, May 04, 2011 at 04:17:51PM -0400, Scott Garron wrote:
> On 05/04/2011 03:35 PM, Konrad Rzeszutek Wilk wrote:
> >>>[..] Should give us some ideas. Not compile tested.
> >.................................   ^^^^^^^^^^
> 
>      I was tracking down why it wouldn't compile, but fired off an
> e-mail because I figured that if at least 2 of us were working on it,
> we'd figure it out faster.
> 
> >The __func__ can be just __FUNCTION__ and the reset can be ignored (I
> >think)
> 
>   It turned out that there were three underscores in front of "func"
> instead of two in that one line.  I removed one of the underscores, got
> it to compile, and the resulting messages at boot time are a seemingly
> neverending spew of:
> 
> [    0.000000] pte_pfn_to_mfn: 0x110e01 is INVALID for 8000000110e01063
> 
> ... where 0x110e01 and 8000000110e01063 are ever-increasing values.
> The 8000000110e01063 number always ends in "63", though.

Ok, maybe take out the debug for the pte_pfn_to_mfn. And see what the pgd
debug gives us.
> 
> Here's the serial console output from the time Xen starts the Linux
> kernel until the spew of repetitive messages:
> 
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Linux version 2.6.32.39 (root@hailstorm) (gcc version
> 4.5.2 (Debian 4.5.2-8) ) #26 SMP Wed May 4 15:4
> 7:34 EDT 2011
> [    0.000000] Command line: placeholder
> root=UUID=be3507b9-015f-4ac6-9b4a-914a9c774421 ro console=hvc0
> earlyprintk=
> xen nomodeset initcall_debug loglevel=8
> [    0.000000] KERNEL supported cpus:
> [    0.000000]   Intel GenuineIntel
> [    0.000000]   AMD AuthenticAMD
> [    0.000000]   Centaur CentaurHauls
> [    0.000000] released 0 pages of unused memory
> [    0.000000] BIOS-provided physical RAM map:
> [    0.000000]  Xen: 0000000000000000 - 000000000009f000 (usable)
> [    0.000000]  Xen: 000000000009f400 - 0000000000100000 (reserved)
> [    0.000000]  Xen: 0000000000100000 - 0000000020000000 (usable)
> [    0.000000]  Xen: 0000000020000000 - 00000000f9ff0000 (unusable)
> [    0.000000]  Xen: 00000000f9ff0000 - 00000000f9fff000 (ACPI data)
> [    0.000000]  Xen: 00000000f9fff000 - 00000000fa000000 (ACPI NVS)
> [    0.000000]  Xen: 00000000febfe000 - 00000000fec01000 (reserved)
> [    0.000000]  Xen: 00000000fee00000 - 00000000fee01000 (reserved)
> [    0.000000]  Xen: 00000000ff780000 - 0000000100000000 (reserved)
> [    0.000000]  Xen: 0000000100000000 - 00000001d9ff0000 (usable)
> [    0.000000] bootconsole [xenboot0] enabled
> [    0.000000] DMI 2.3 present.
> [    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working
> around it.
> [    0.000000] e820 update range: 0000000000000000 -
> 0000000000010000 (usable) ==> (reserved)
> [    0.000000] last_pfn = 0x1d9ff0 max_arch_pfn = 0x400000000
> [    0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new
> 0x7010600070106
> [    0.000000] last_pfn = 0x20000 max_arch_pfn = 0x400000000
> [    0.000000] Scanning 0 areas for low memory corruption
> [    0.000000] modified physical RAM map:
> [    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
> [    0.000000]  modified: 0000000000010000 - 000000000009f000 (usable)
> [    0.000000]  modified: 000000000009f400 - 0000000000100000 (reserved)
> [    0.000000]  modified: 0000000000100000 - 0000000020000000 (usable)
> [    0.000000]  modified: 0000000020000000 - 00000000f9ff0000 (unusable)
> [    0.000000]  modified: 00000000f9ff0000 - 00000000f9fff000 (ACPI data)
> [    0.000000]  modified: 00000000f9fff000 - 00000000fa000000 (ACPI NVS)
> [    0.000000]  modified: 00000000febfe000 - 00000000fec01000 (reserved)
> [    0.000000]  modified: 00000000fee00000 - 00000000fee01000 (reserved)
> [    0.000000]  modified: 00000000ff780000 - 0000000100000000 (reserved)
> [    0.000000]  modified: 0000000100000000 - 00000001d9ff0000 (usable)
> [    0.000000] initial memory mapped : 0 - 0d919000
> [    0.000000] init_memory_mapping: 0000000000000000-0000000020000000
> [    0.000000]  0000000000 - 0020000000 page 4k
> [    0.000000] kernel direct mapping tables up to 20000000 @ 100000-202000
> [    0.000000] init_memory_mapping: 0000000100000000-00000001d9ff0000
> [    0.000000]  0100000000 - 01d9ff0000 page 4k
> [    0.000000] kernel direct mapping tables up to 1d9ff0000 @
> da8b000-e964000
> [    0.000000] pte_pfn_to_mfn: 0x100000 is INVALID for 8000000100000063
> [    0.000000] pte_pfn_to_mfn: 0x100001 is INVALID for 8000000100001063
> [    0.000000] pte_pfn_to_mfn: 0x100002 is INVALID for 8000000100002063
> [    0.000000] pte_pfn_to_mfn: 0x100003 is INVALID for 8000000100003063
> 
> 
> [ .. and so on - if it ever ends, I'll send you the tail of it .. ]
> 
> -- 
> Scott Garron

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.