From owner-freebsd-current@FreeBSD.ORG Sun Dec 28 21:37:51 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 CAA03BB; Sun, 28 Dec 2014 21:37:51 +0000 (UTC) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (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 5729919DC; Sun, 28 Dec 2014 21:37:51 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id k14so17735552wgh.1; Sun, 28 Dec 2014 13:37:49 -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=BwvE46z51lCkfWXHDMKz0kvv244As131N36JhRkC8qM=; b=oUbqsYW9pyGhPHJmFuyKqo80hqrOqggsecWsnX9dR5kOWw98kcrNkGR3P1kEMluvjH lDkX4bjWguSOFLIOogc8FGiXT4XmClqEvquVe6jylKEkxJ5g03x7pfX2XpAuLxTdz4RU n/+KCJl3aIWzp+PaiHKeC18yOWeRznHEKzGD+NUXCuiqaoM1CvppQd3ZoJTkYWbOfg8+ JaoraMmtX6L1ztPxOKZT9eU9tVcD2ZojX4p4P9U+uq58iCUz7HRq/em/BcqQG4BKuDFJ QaKAUDFdYer5DPJ3uoFZs/HoDtLqi47x/KNupuqByQt/7xu3gysko8MBwMUpoDFlxCoC wkJw== MIME-Version: 1.0 X-Received: by 10.194.85.83 with SMTP id f19mr105773758wjz.20.1419802669843; Sun, 28 Dec 2014 13:37:49 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Sun, 28 Dec 2014 13:37:49 -0800 (PST) In-Reply-To: <1419797387.1018.215.camel@freebsd.org> 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> Date: Sun, 28 Dec 2014 13:37:49 -0800 X-Google-Sender-Auth: Pb1CkviWvsMSVIuYmRnT4fSvw9o Message-ID: Subject: Re: r276200: EFI boot failure: kernel stops booting at pci0: on pcib0 From: Adrian Chadd To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD CURRENT , "O. Hartmann" , =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= 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: Sun, 28 Dec 2014 21:37:51 -0000 Hah sweet! You found the commit! Would you please file a PR so it doesn't get lost? Thanks! -adrian On 28 December 2014 at 12:09, Ian Lepore wrote: > On Sun, 2014-12-28 at 20:57 +0100, O. Hartmann wrote: >> Am Fri, 26 Dec 2014 12:23:42 -0700 >> Ian Lepore schrieb: >> >> > 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 >> >> Well, r276063 works, but r2766064 doesn't. >> >> oh > > cc'ing the author of r276064, since spotting the fact that 'efi' was > involved in that revision used up 100% of my expertise in efi stuff. :) > > -- Ian > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"