Bug#692067: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64

To: Robert Keevil <rkeevil+debian@gmail.com>
Cc: 692067@bugs.debian.org
Subject: Bug#692067: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
From: Jonathan Nieder <jrnieder@gmail.com>
Date: Thu, 1 Nov 2012 19:14:02 -0700
Message-id: <[🔎] 20121102021402.GA5371@elie.Belkin>
Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 692067@bugs.debian.org
In-reply-to: <[🔎] 50932981.1040206@gmail.com>
References: <[🔎] 20121101204442.8491.51188.reportbug@ares> <[🔎] 20121102011051.GB2984@elie.Belkin> <[🔎] 50932981.1040206@gmail.com>

tags 692067 + upstream fixed-upstream
quit

Robert Keevil wrote:
> On 01/11/12 20:10, Jonathan Nieder wrote:

>> Thanks for reporting it. If you pass "mem=4G" on the kernel command line,
>> does that change anything? Thanks and sorry for the trouble, Jonathan
>
> It boots and runs fine with that option.

Yay, thanks for the quick response.  I suspect this is fixed by

  844ab6f993b1 x86, mm: Find_early_table_space based on ranges that
               are actually being mapped

which is part of 3.6.5.

Reply to:

Follow-Ups:
- Processed: Re: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

References:
- Bug#692067: linux-image-3.6-trunk-amd64: Early panic with 3.6.4 on amd64
  - From: Robert Keevil <rkeevil+debian@gmail.com>
- Bug#692067: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
  - From: Jonathan Nieder <jrnieder@gmail.com>
- Bug#692067: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
  - From: Robert Keevil <rkeevil+debian@gmail.com>

Prev by Date: Bug#692067: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
Next by Date: Processed: Re: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
Previous by thread: Bug#692067: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
Next by thread: Processed: Re: [3.5.5->3.6.4 regression] Early panic with 3.6.4 on amd64
Index(es):
- Date
- Thread