Re: Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"

[Valtteri Kiviniemi <mailinglists@dataproof.fi>]

Hi,

I just compiled Xen 4.0.0.1 with 2.6.32.24 and I stuck on this same 
problem with my own compiled kernel. However the default kernel with 
comes from "make world" boots fine. I traced the problem down to some 
settings in kernel's menuconfig "Kernel hacking" menu. I dont exactly 
know what the option needs to be enabled in the "Kernel hacking" to get 
the kernel booting. In my own compiled kernels I have almost all the 
options in that "Kernel hacking" menu disabled, and when I enabled the 
same options in that menu that are in the default kernel which comes 
when you do "make world" the system booted fine.

You probably know the problem already but I just thought that I should 
share this information with you anyway.

- Valtteri Kiviniemi

Jeremy Fitzhardinge kirjoitti:
>  On 10/12/2010 01:10 AM, Andreas Kinzler wrote:
>> On 07.10.2010 11:57, Alan J. Wylie wrote:
>>> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM
>>> Motherboard: X8DTL
>>> Processor: 1 x Intel XEON E5506 quad core
>>> RAID controller: LSI MegaRAID SAS 8708
>>>
>>> Bisected (by hand) to between
>>> 69e50db2 (good) 2.6.32.21  "Merge commit 'v2.6.32.21' into
>>> xen/next-2.6.32"
>>> and
>>> dda56688 (bad)             "Merge branch 'xen/next' into
>>> xen/next-2.6.32"
>>>
>>> ffffffff8100bd10 T get_phys_to_machine
>>> ffffffff8100bd4c t pin_pagetable_pfn
>> I am afflicted by this problem for a long while now. Should look very
>> familiar to you. See
>> http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00758.html
>>
>> No solution till now.
> 
> Is it not fixed by current xen/stable-2.6.32.x kernels?
> 
>     J
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel