From: Yves-Alexis Perez <corsac@debian.org>
To: Luca Barbato <lu_zero@gentoo.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Matthew Thode <prometheanfire@gentoo.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
kernel@gentoo.org, hardened-kernel@gentoo.org
Subject: Re: 3.9.7, 3.10-rc7 - UEFI stalls at boot (nothing displayed), when booting with mem=300M
Date: Thu, 04 Jul 2013 10:53:47 +0200 [thread overview]
Message-ID: <1372928027.26307.5.camel@oban> (raw)
In-Reply-To: <1372927060.26307.0.camel@oban>
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
next prev parent reply other threads:[~2013-07-04 8:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 16:47 3.9.7, 3.10-rc7 - UEFI stalls at boot (nothing displayed), when booting with mem=300M Matthew Thode
2013-06-27 17:27 ` Matthew Garrett
2013-06-27 17:39 ` Matthew Thode
2013-06-27 17:43 ` Matthew Garrett
2013-06-27 18:00 ` Matthew Thode
2013-06-27 18:17 ` Luca Barbato
2013-07-01 4:30 ` Matthew Thode
2013-07-01 4:41 ` Luca Barbato
2013-07-01 4:43 ` Matthew Thode
2013-07-01 5:13 ` Matthew Garrett
2013-07-01 5:22 ` Luca Barbato
2013-07-01 6:25 ` Matthew Garrett
2013-07-01 13:05 ` Matthew Thode
2013-07-01 13:07 ` Luca Barbato
2013-07-04 5:53 ` Luca Barbato
2013-07-04 8:37 ` Yves-Alexis Perez
2013-07-04 8:53 ` Yves-Alexis Perez [this message]
2013-07-16 14:23 ` Matthew Thode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1372928027.26307.5.camel@oban \
--to=corsac@debian.org \
--cc=hardened-kernel@gentoo.org \
--cc=kernel@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lu_zero@gentoo.org \
--cc=mjg59@srcf.ucam.org \
--cc=prometheanfire@gentoo.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox