Date: Sat, 2 Oct 2010 15:50:03 GMT From: Juergen Lock <nox@jelal.kn-bremen.de> To: freebsd-xen@FreeBSD.org Subject: Re: kern/148262: [xen] [panic] HYPERVISOR_update_va_mapping Message-ID: <201010021550.o92Fo3Zw090572@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010021550.o92Fo3Zw090572>