From owner-freebsd-current@FreeBSD.ORG Fri Dec 26 12:01:16 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EEA78DA9; Fri, 26 Dec 2014 12:01:16 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8C9A6487E; Fri, 26 Dec 2014 12:01:16 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from ) id <1Y4TZx-000udC-QB>; Fri, 26 Dec 2014 13:01:13 +0100 Received: from f052129157.adsl.alicedsl.de ([78.52.129.157] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1Y4TZx-0003fv-Nx>; Fri, 26 Dec 2014 13:01:13 +0100 Date: Fri, 26 Dec 2014 13:01:13 +0100 From: "O. Hartmann" To: Adrian Chadd Subject: Re: r276200: EFI boot failure: kernel stops booting at pci0: on pcib0 Message-ID: <20141226130113.5200bfbb.ohartman@zedat.fu-berlin.de> In-Reply-To: References: <20141225194207.5dfd3636.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 78.52.129.157 Cc: FreeBSD CURRENT 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: Fri, 26 Dec 2014 12:01:17 -0000 Am Thu, 25 Dec 2014 11:40:47 -0800 Adrian Chadd schrieb: > Would you be able to narrow it down to a small range of commits? > that'll make it easier to chase down. :) > > Thanks! > > > > -adrian > > > On 25 December 2014 at 10:42, O. Hartmann wrote: > > > > Since 23rd's update of CURRENT, the kernel fails to boot on systems that boot via EFI. > > Systems with legacy booting seem not to be affected. > > > > I just ran today into the problem updating a notebook with a Intel Haswell Intel > > i5-4200M CPU (Haswell) on a Lenovo ThinkPad E540, bboting via UEFI, CURRENT r276200. > > The very same caode base is running on several other boxes which boot via legacy > > method. The very same failure showed up at the lab on an older HP Compaq 8300 system, > > based on H81 chipset equipted with an Ivy-Bridge CPU, booting also via EFI. That box > > stops at the exact same spot as the notebook does. > > > > The systems in question, also the legacy booting systems (aka the oldstyle loader boot > > method), load drm2, i915kms. > > > > Booting old kernel/modules (via "boot kernel.old"), at CURRENT r275896 is all right. > > > > What is happening here? > > > > Merry christmas day, > > > > oh I narrowed down the culprit commit to be between r276060 (works) and r276075 (works not). To avoid interferences from rogue modules, I disabled all modules loaded by the loader, including drm2 and i915kms, but the picture is always the same. I'm sorry, I have some duties to perform, so intersecting further is possible later only ... I performed the iterative search of the foul commit by "svn update -r 276XXX" and then build kernel only via "make kernel" - this just for the record in case some world-dependencies might have effects. oh