[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVvo+saJFpx=6A8O7GOns0cR302_GBe4A0a10a4Z0mZyw@mail.gmail.com>
Date: Fri, 9 Aug 2013 19:10:03 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Dave Hansen <dave@...1.net>
Cc: "the arch/x86 maintainers" <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: x86: early boot crash: "alloc_low_page: ran out of memory" (bisected)
On Fri, Aug 9, 2013 at 6:19 PM, Dave Hansen <dave@...1.net> wrote:
> On 08/09/2013 04:23 PM, Yinghai Lu wrote:
>> On Fri, Aug 9, 2013 at 4:18 PM, Dave Hansen <dave.hansen@...el.com> wrote:
>>> I'm getting a 100% reproducible panic early in boot:
> ...
>>>> early console in setup code
>>>> [ 0.000000] Initializing cgroup subsys cpuset
>>>> [ 0.000000] Initializing cgroup subsys cpu
>>>> [ 0.000000] Linux version 3.8.0-rc5-00059-g8170e6b
>>
>> so how about v3.10?
>>
>> We should have some fixes in 3.10 already.
>
> I was hitting it on Linus's current tree today (3.11-rcwhatever). I
> pasted the panic() from your patch's commit specifically, but the same
> behavior is happening on current kernels, and it looked consistent as I
> bisected between the 3.11-rc's and your commit.
Can you post 3.11-rc with "debug ignore_loglevel memblock=debug" ?
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists