From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 5 18:16:01 2010 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 368A31065670; Tue, 5 Oct 2010 18:16:00 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Juergen Lock Date: Tue, 5 Oct 2010 14:15:50 -0400 User-Agent: KMail/1.6.2 References: <201010021343.o92Dhw0p062168@triton8.kn-bremen.de> In-Reply-To: <201010021343.o92Dhw0p062168@triton8.kn-bremen.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010051415.52662.jkim@FreeBSD.org> Cc: freebsd-xen@FreeBSD.org, freebsd-bugs@FreeBSD.org, linimon@FreeBSD.org, Yuriy Kohut Subject: Re: kern/148262: [xen] [panic] HYPERVISOR_update_va_mapping X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2010 18:16:01 -0000 On Saturday 02 October 2010 09:43 am, Juergen Lock wrote: > [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=FREEBS >D8#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.) Can you please revert r204157 and test -CURRENT? It shouldn't necessary because HEAD uses vm86 as a backend for i386 now. Thanks! Jung-uk Kim