From owner-freebsd-current@FreeBSD.ORG Fri Dec 26 19:23:46 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 66F05D1E; Fri, 26 Dec 2014 19:23:46 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.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 38B7964366; Fri, 26 Dec 2014 19:23:45 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Y4aUC-0007NJ-0r; Fri, 26 Dec 2014 19:23:44 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sBQJNgZN041757; Fri, 26 Dec 2014 12:23:42 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19Y7YngtK0x3mWBD782jkPJ Message-ID: <1419621822.1018.187.camel@freebsd.org> Subject: Re: r276200: EFI boot failure: kernel stops booting at pci0: on pcib0 From: Ian Lepore To: Adrian Chadd Date: Fri, 26 Dec 2014 12:23:42 -0700 In-Reply-To: References: <20141225194207.5dfd3636.ohartman@zedat.fu-berlin.de> <20141226130113.5200bfbb.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.8 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: Fri, 26 Dec 2014 19:23:46 -0000 On Fri, 2014-12-26 at 08:48 -0800, Adrian Chadd wrote: > On 26 December 2014 at 04:01, O. Hartmann wrote: > > 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. > > Hi! > > Thanks for that. Would you please file a PR with the details and what > you've done? > > I hope you can narrow it down further. You've done a great job > already, I just can't see any clear winner there for a commit to back > out :( r276064 looks like a candidate. At least, it has 'efi' in the name. :) -- Ian