| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Xen dom0 crash in get_phys_to_machine
at 14:45 on Fri 22-Oct-2010 Gianni Tedesco (gianni.tedesco@xxxxxxxxxx) wrote:
> On Fri, 2010-10-22 at 14:33 +0100, Alan J. Wylie wrote:
>>> But then it looks like something is trampling max_pfn and possibly other
>>> important data structures.
>> I've just been reading through the Documentation/development-process
>> and discovered "sparse".
>> Five minutes ago I ran it on mmu.c and got the following interesting
>> output:
>> /usr/src/jeremy-git-xen/arch/x86/xen/mmu.c:385:23: warning: symbol 'max_pfn'
>> shadows an earlier one
>> /usr/src/jeremy-git-xen/arch/x86/include/asm/page_64_types.h:58:22:
>> originally declared here
>> Is it just a co-incidence that the first two lines refer to the
>> same symbol that you have just mentioned?
> Hmm, sort of, I assumed I was printing the global max_pfn but it
> looks like the shadowing is deliberate (if a little thoughtless in
> the naming). It does reverse my finding that 'max_pfn' (the global
> one) is getting corrupted.
>> I'm going to try renaming the local symbol and see if things still crash.
> Sadly, I'm almost certain things will still crash.
You are quite right - it still crashes.
>> At least I'll be able to leave it running undisturbed over the
>> weekend.
> This happens for you after a full boot then?
No - I have an old 2.6.32.18 kernel that boots fine.
--
Alan J. Wylie http://www.wylie.me.uk/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home