From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)" Date: Tue, 12 Oct 2010 11:49:29 -0700 Message-ID: <4CB4ADB9.2030704@goop.org> References: <19629.39326.337589.71778@wylie.me.uk> <4CB41800.7050806@hfp.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CB41800.7050806@hfp.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andreas Kinzler Cc: "Alan J. Wylie" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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