From owner-freebsd-current@FreeBSD.ORG Mon Dec 29 17:32:45 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 20EC41DE; Mon, 29 Dec 2014 17:32:45 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B507C3A05; Mon, 29 Dec 2014 17:32:42 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.07,659,1413244800"; d="scan'208";a="208938042" Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.3.210.2; Mon, 29 Dec 2014 11:55:30 -0500 Message-ID: <54A18780.7080601@citrix.com> Date: Mon, 29 Dec 2014 17:55:28 +0100 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: =?windows-1252?Q?Roger_Pau_Monn=E9?= , Adrian Chadd , Ian Lepore Subject: Re: r276200: EFI boot failure: kernel stops booting at pci0: on pcib0 References: <20141225194207.5dfd3636.ohartman@zedat.fu-berlin.de> <20141226130113.5200bfbb.ohartman@zedat.fu-berlin.de> <1419621822.1018.187.camel@freebsd.org> <20141228205739.154243d8.ohartman@zedat.fu-berlin.de> <1419797387.1018.215.camel@freebsd.org> <54A13DDB.2040206@FreeBSD.org> In-Reply-To: <54A13DDB.2040206@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------010801070003060309090206" X-DLP: MIA1 Cc: FreeBSD CURRENT , "O. Hartmann" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2014 17:32:45 -0000 --------------010801070003060309090206 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit El 29/12/14 a les 12.41, Roger Pau Monné ha escrit: > Hello, > > Sorry for not noticing this earlier, I've been without a computer for > some days. Do you get a panic message, or the system just freezes? > > Can you please post the full boot output with boot_verbose enabled? I'm not able to reproduce the problem with Qemu and OVMF, and I don't have any box right now that uses UEFI. I'm guessing that this is due to some memory reservation conflict, so I'm attaching a patch that should help diagnose it. Could you provide the information requested above with this patch applied? Thanks, Roger. --------------010801070003060309090206 Content-Type: text/plain; charset="UTF-8"; name="uefi_debug.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="uefi_debug.patch" diff --git a/sys/x86/x86/nexus.c b/sys/x86/x86/nexus.c index 0663602..d563c36 100644 --- a/sys/x86/x86/nexus.c +++ b/sys/x86/x86/nexus.c @@ -367,6 +367,10 @@ nexus_alloc_resource(device_t bus, device_t child, int type, int *rid, struct rman *rm; int needactivate = flags & RF_ACTIVE; + if (type == SYS_RES_MEMORY) + printf("%s: RSV range 0x%lx - 0x%lx size %lu\n", + device_get_name(child), start, end, count); + /* * If this is an allocation of the "default" range for a given * RID, and we know what the resources for this device are --------------010801070003060309090206--