From owner-freebsd-xen@freebsd.org  Wed Oct 21 08:53:29 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 45B26A1B275
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Wed, 21 Oct 2015 08:53:29 +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 DC01017E6;
 Wed, 21 Oct 2015 08:53:28 +0000 (UTC)
 (envelope-from prvs=72919e7bd=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.17,711,1437436800"; d="scan'208";a="311850424"
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>
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: <56275284.1070108@citrix.com>
Date: Wed, 21 Oct 2015 10:53:24 +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: <A1220AC9-230A-4ECE-86BD-FA042A571735@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 08:53:29 -0000

El 21/10/15 a les 10.33, Eggert, Lars ha escrit:
> On 2015-10-21, at 9:40, Roger Pau Monné <roger.pau@citrix.com> wrote:
>> Can you execute:
>>
>> # addr2line -e /boot/kernel/kernel ffffffff8097bf80
>>
>> In order to get the file and line where the failure happens?
> 
> I guess you meant kernel.debug? Then I get:
> 
> /usr/home/elars/src/sys/amd64/pci/pci_cfgreg.c:365
> 
> Which is the __asm line in case 1 in pciereg_cfgwrite().

Hello,

Yes, I knew about this, sorry, with Xen 4.6 you need to add:

hw.pci.mcfg=0

to your /boot/loader.conf. This is because Xen prevents us from writing
at the PCI-e memory mapped config and we need to switch back to using
the IO ports.

Roger.