From owner-freebsd-xen@freebsd.org  Wed Oct 21 09:11:19 2015
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1BAAA1B7BB
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Wed, 21 Oct 2015 09:11:19 +0000 (UTC)
 (envelope-from prvs=72919e7bd=roger.pau@citrix.com)
Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 7DDED90;
 Wed, 21 Oct 2015 09:11:19 +0000 (UTC)
 (envelope-from prvs=72919e7bd=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.17,711,1437436800"; d="scan'208";a="311853372"
Subject: Re: Xen dom0 crash
To: "Eggert, Lars" <lars@netapp.com>
References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com>
 <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba>
 <555F58DC.2040807@citrix.com>
 <46625CAE-750E-4ECE-8B39-DF8EDDFA912F@netapp.com>
 <55642229.9020106@citrix.com>
 <E8FB00CE-C65F-4A54-973D-4962C4463FE6@netapp.com> <5627417A.20304@citrix.com>
 <A1220AC9-230A-4ECE-86BD-FA042A571735@netapp.com>
 <56275284.1070108@citrix.com>
 <7501F178-400B-43F8-9FBC-69F566A7BD11@netapp.com>
CC: Roman Bogorodskiy <novel@FreeBSD.org>, "freebsd-xen@freebsd.org"
 <freebsd-xen@freebsd.org>
From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
Message-ID: <562756B3.7050804@citrix.com>
Date: Wed, 21 Oct 2015 11:11:15 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <7501F178-400B-43F8-9FBC-69F566A7BD11@netapp.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-DLP: MIA2
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2015 09:11:20 -0000

El 21/10/15 a les 11.02, Eggert, Lars ha escrit:
> On 2015-10-21, at 10:53, Roger Pau Monné <roger.pau@citrix.com> wrote:
>> hw.pci.mcfg=0
> 
> Thanks! That gets me a bit further, but it now crashes with:
> 
> ...
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #14 Launched!
> SMP: AP CPU #11 Launched!
> SMP: AP CPU #21 Launched!
> SMP: AP CPU #30 Launched!
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #20 Launched!
> panic: xen_pv_lapic_enable_pmc: not available in Xen PV port.
> cpuid = 0
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff81fd5990
> vpanic() at vpanic+0x182/frame 0xffffffff81fd5a10
> panic() at panic+0x43/frame 0xffffffff81fd5a70
> xen_pv_lapic_enable_pmc() at xen_pv_lapic_enable_pmc+0x19/frame 0xffffffff81fd5a80
> pmc_md_initialize() at pmc_md_initialize+0x3c/frame 0xffffffff81fd5aa0
> load() at load+0x41e/frame 0xffffffff81fd5af0
> syscall_module_handler() at syscall_module_handler+0x290/frame 0xffffffff81fd5b20
> module_register_init() at module_register_init+0xfb/frame 0xffffffff81fd5b50
> mi_startup() at mi_startup+0x108/frame 0xffffffff81fd5b70
> xen_start() at xen_start+0x1f
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at      kdb_enter+0x3b: movq    $0,kdb_why
> db>

Hello,

Are you loading hwpmc by default? Performance monitor counters are not
yet implemented in the FreeBSD PVH port, so you should not load hwpmc. I
have to look at providing an error message here rather than panicking.

Roger.