From owner-freebsd-bugs@FreeBSD.ORG Sat Oct 2 14:04:55 2010 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 209DF1065673; Sat, 2 Oct 2010 14:04:55 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id D68E08FC0C; Sat, 2 Oct 2010 14:04:54 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id DEA871E00228; Sat, 2 Oct 2010 15:45:37 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.4/8.14.3) with ESMTP id o92Dhx0K062169; Sat, 2 Oct 2010 15:43:59 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.4/8.14.3/Submit) id o92Dhw0p062168; Sat, 2 Oct 2010 15:43:58 +0200 (CEST) (envelope-from nox) Date: Sat, 2 Oct 2010 15:43:58 +0200 (CEST) From: Juergen Lock Message-Id: <201010021343.o92Dhw0p062168@triton8.kn-bremen.de> To: linimon@FreeBSD.org X-Newsgroups: gmane.os.freebsd.xen,gmane.os.freebsd.bugs In-Reply-To: <201007031118.o63BIvvB062963@freefall.freebsd.org> Organization: home Cc: freebsd-xen@FreeBSD.org, freebsd-bugs@FreeBSD.org, jkim@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: Sat, 02 Oct 2010 14:04:55 -0000 [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.)