From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: Re: Xen dom0 crash: "d0:v0: unhandled page fault
	(ec=0000)"
Date: Tue, 19 Oct 2010 15:15:58 +0200
Message-ID: <4CBD9A0E.5010606@hfp.de>
References: <19629.39326.337589.71778@wylie.me.uk> <4CB41800.7050806@hfp.de>
	<4CB4ADB9.2030704@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4CB4ADB9.2030704@goop.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Alan J. Wylie" <NDA5OWUy@wylie.me.uk>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 12.10.2010 20:49, Jeremy Fitzhardinge wrote:
>>> 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?

Jeremy, just tried the current 2472a9c snapshot. Still crashes.

Alan, any news?

Regards Andreas