From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933743Ab3GDIxz (ORCPT ); Thu, 4 Jul 2013 04:53:55 -0400 Received: from pyr75-3-78-192-68-46.fbxo.proxad.net ([78.192.68.46]:53130 "EHLO molly.corsac.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933661Ab3GDIxu (ORCPT ); Thu, 4 Jul 2013 04:53:50 -0400 Message-ID: <1372928027.26307.5.camel@oban> Subject: Re: 3.9.7, 3.10-rc7 - UEFI stalls at boot (nothing displayed), when booting with mem=300M From: Yves-Alexis Perez To: Luca Barbato Cc: Matthew Garrett , Matthew Thode , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, kernel@gentoo.org, hardened-kernel@gentoo.org Date: Thu, 04 Jul 2013 10:53:47 +0200 In-Reply-To: <1372927060.26307.0.camel@oban> References: <51CC6CAE.6070401@gentoo.org> <51CC81A2.8040305@gentoo.org> <51D10603.1080403@gentoo.org> <20130701051320.GA6840@srcf.ucam.org> <51D11218.5040601@gentoo.org> <20130701062530.GA7423@srcf.ucam.org> <51D17F15.4080000@gentoo.org> <51D50DEE.4080903@gentoo.org> <1372927060.26307.0.camel@oban> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On jeu., 2013-07-04 at 10:37 +0200, Yves-Alexis Perez wrote: > On jeu., 2013-07-04 at 07:53 +0200, Luca Barbato wrote: > > On 07/01/2013 03:07 PM, Luca Barbato wrote: > > > Hopefully I will carve some time next weekend to play the restricted > > > bisect game. > > > > Release 3.10 apparently doesn't show the problem, I guess problem solved > > for me =) > > > > lu > > > I've just tried 3.10.0 with CONFIG_EFI=y and I still can't boot with > mem=300M. And to be a little more specific, and with a bit of fun, I've tryied “bisecting” the amount of ram needed to make a successful boot. Platform is a Lenovo Thinkpad x230 with 4G of ram. mem=300M bad mem=4000M good mem=2000M bad mem=3000M bad mem=3500M good mem=3250M bad mem=3375M bad mem=3437M good mem=3406M bad mem=3421M bad mem=3429M bad mem=3433M good mem=3431M bad mem=3432M bad So I'm not sure what happens at the 3433M boundary, but there's definitely something fishy. And 3.5G ram doesn't look like a very specific machine (although I can't test without artificially setting the memory limit (I only have one 4096M sodimm). I'll try to git bisect between 3.8 and 3.10 and using mem=3432M when I have more time. Regards, -- Yves-Alexis