From owner-freebsd-xen@FreeBSD.ORG  Sat Oct  2 15:50:03 2010
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CCF01106566B
	for <freebsd-xen@hub.freebsd.org>; Sat,  2 Oct 2010 15:50:03 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id A214B8FC13
	for <freebsd-xen@hub.freebsd.org>; Sat,  2 Oct 2010 15:50:03 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o92Fo3JZ090573
	for <freebsd-xen@freefall.freebsd.org>; Sat, 2 Oct 2010 15:50:03 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o92Fo3Zw090572;
	Sat, 2 Oct 2010 15:50:03 GMT (envelope-from gnats)
Date: Sat, 2 Oct 2010 15:50:03 GMT
Message-Id: <201010021550.o92Fo3Zw090572@freefall.freebsd.org>
To: freebsd-xen@FreeBSD.org
From: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: 
Subject: Re: kern/148262: [xen] [panic] HYPERVISOR_update_va_mapping
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Juergen Lock <nox@jelal.kn-bremen.de>
List-Id: Discussion of the freebsd port to xen - implementation and usage
	<freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Oct 2010 15:50:03 -0000

The following reply was made to PR kern/148262; it has been noted by GNATS.

From: Juergen Lock <nox@jelal.kn-bremen.de>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: kern/148262: [xen] [panic] HYPERVISOR_update_va_mapping
Date: Sat, 2 Oct 2010 17:31:51 +0200

 Oops forgot to Cc bug-followup@ ...
 
 Subject: Re: kern/148262: [xen] [panic] HYPERVISOR_update_va_mapping
 In-Reply-To: <201007031118.o63BIvvB062963@freefall.freebsd.org>
 Cc: freebsd-bugs@FreeBSD.org, freebsd-xen@FreeBSD.org,
         Yuriy Kohut <ykohut@onapp.com>, jkim@FreeBSD.org
 
 [kern/149853 is a duplicate of this]
 
 I don't use xen myself here but I helped someone on irc troubleshoot
 the same crash (before I saw these PRs), and found out the reason it
 didn't happen on 8.0 is the x86bios code is new in 8.1 and xen doesn't
 like this call in x86bios_map_mem():
 
 	x86bios_ivt = pmap_mapbios(X86BIOS_IVT_BASE, X86BIOS_IVT_SIZE);
 
 see:
 
 	http://fxr.watson.org/fxr/source/compat/x86bios/x86bios.c?v=FREEBSD8#L498
 
 It seems the only consumers of x86bios are atkbd(4), dpms(4), and
 vesa(4), and indeed removing atkbd(4) from the xen kernel got his
 domU running.
 
 (And now that I just looked at /sys/i386/conf/XEN in svn I see this
 was already fixed in r204157, it only never got MFCd.)