Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755541Ab2FNU4L (ORCPT <rfc822;w@1wt.eu>);
	Thu, 14 Jun 2012 16:56:11 -0400
Received: from mail-pb0-f46.google.com ([209.85.160.46]:33571 "EHLO
	mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753835Ab2FNU4K convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 14 Jun 2012 16:56:10 -0400
MIME-Version: 1.0
In-Reply-To: <1339667440.3321.7.camel@lappy>
References: <1339623535.3321.4.camel@lappy>
	<20120614032005.GC3766@dhcp-172-17-108-109.mtv.corp.google.com>
	<1339667440.3321.7.camel@lappy>
Date: Thu, 14 Jun 2012 13:56:09 -0700
X-Google-Sender-Auth: 3VmPLTZ-VmpukIDERIDTgtOaNSU
Message-ID: <CAE9FiQVJ-q3gQxfBqfRnG+RvEh2bZ2-Ki=CRUATmCKjJp8MNuw@mail.gmail.com>
Subject: Re: Early boot panic on machine with lots of memory
From: Yinghai Lu <yinghai@kernel.org>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Andrew Morton <akpm@linux-foundation.org>,
        David Miller <davem@davemloft.net>, hpa@linux.intel.com,
        linux-mm <linux-mm@kvack.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1355
Lines: 37

On Thu, Jun 14, 2012 at 2:50 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> On Thu, 2012-06-14 at 12:20 +0900, Tejun Heo wrote:
>> On Wed, Jun 13, 2012 at 11:38:55PM +0200, Sasha Levin wrote:
>> > Hi all,
>> >
>> > I'm seeing the following when booting a KVM guest with 65gb of RAM, on latest linux-next.
>> >
>> > Note that it happens with numa=off.
>> >
>> > [ ? ?0.000000] BUG: unable to handle kernel paging request at ffff88102febd948
>> > [ ? ?0.000000] IP: [<ffffffff836a6f37>] __next_free_mem_range+0x9b/0x155
>>
>> Can you map it back to the source line please?
>
> mm/memblock.c:583
>
> ? ? ? ? ? ? ? ? ? ? ? ?phys_addr_t r_start = ri ? r[-1].base + r[-1].size : 0;
> ?97: ? 85 d2 ? ? ? ? ? ? ? ? ? test ? %edx,%edx
> ?99: ? 74 08 ? ? ? ? ? ? ? ? ? je ? ? a3 <__next_free_mem_range+0xa3>
> ?9b: ? 49 8b 48 f0 ? ? ? ? ? ? mov ? ?-0x10(%r8),%rcx
> ?9f: ? 49 03 48 e8 ? ? ? ? ? ? add ? ?-0x18(%r8),%rcx
>
> It's the deref on 9b (r8=ffff88102febd958).

that reserved.region is allocated by memblock.

can you boot with "memblock=debug debug ignore_loglevel" and post
whole boot log?

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/