From owner-freebsd-current@FreeBSD.ORG Fri Dec 26 16:48:25 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 429ADFC3 for ; Fri, 26 Dec 2014 16:48:25 +0000 (UTC) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA9A72E65 for ; Fri, 26 Dec 2014 16:48:23 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id a1so14760804wgh.37 for ; Fri, 26 Dec 2014 08:48:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=H3A1TW41r7m2o1Xz6qJw7qt1dUQozhHW7FMsGjWE2AQ=; b=Q7yzGGjDvmf8uPIOD++bO+UOnQIR9j++ZpyK8+AttDGuWJK20/IJa9MVljyVkL3EoA WEEEgnHiecvIpRuCXdVf+uNp/UIkng+cSX7SOBiug0bumAAr476TvrCC+uYetMlplgNm q3FI50oVW7sdepCqvlYhJ06MSppkqUdPM8QM7iafmZqmWreGVXjB7MkxzuDyzSgeyMKa meZOPF86+Ztkd54FhHXGxaJaJ7QrwBCGgxn3ZQ9pWPOflMbhI/Vv4wKZleF2i1v3z2by bWbnfA4FmauYqMRBTVDALlqzMeXlOp7G4VOpb9OzKQlUuPwKp5VdcEWlks0qkaB0L3IR 4ICQ== MIME-Version: 1.0 X-Received: by 10.180.80.163 with SMTP id s3mr69000987wix.59.1419612502399; Fri, 26 Dec 2014 08:48:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Fri, 26 Dec 2014 08:48:22 -0800 (PST) In-Reply-To: <20141226130113.5200bfbb.ohartman@zedat.fu-berlin.de> References: <20141225194207.5dfd3636.ohartman@zedat.fu-berlin.de> <20141226130113.5200bfbb.ohartman@zedat.fu-berlin.de> Date: Fri, 26 Dec 2014 08:48:22 -0800 X-Google-Sender-Auth: rKPlzPrgIlSP7UdFtgcffKjHARU Message-ID: Subject: Re: r276200: EFI boot failure: kernel stops booting at pci0: on pcib0 From: Adrian Chadd To: "O. Hartmann" Content-Type: text/plain; charset=UTF-8 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 16:48:25 -0000 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 :( -adrian