From: Mark Lord <kernel@teksavvy.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jacob Shin <jacob.shin@amd.com>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: Regression from 3.4.9 to 3.4.16 "stable" kernel
Date: Mon, 29 Oct 2012 10:22:53 -0400 [thread overview]
Message-ID: <508E913D.2080104@teksavvy.com> (raw)
In-Reply-To: <20121029064643.GE574@1wt.eu>
On 12-10-29 02:46 AM, Willy Tarreau wrote:
> On Mon, Oct 29, 2012 at 12:03:55AM -0400, Mark Lord wrote:
>> My server here runs the 3.4.xx series of "stable" kernels.
>> Until today, it was running 3.4.9.
>> Today I tried to upgrade it to 3.4.16.
>> It hangs in setup.c.
>>
>> I've isolated the fault down to this specific change
>> that was made between 3.4.9 and 3.4.16.
>> Reverting this change allows the system to boot/run normally again.
>>
>>
>> --- linux-3.4.9/arch/x86/kernel/setup.c 2012-08-15 11:17:17.000000000 -0400
>> +++ linux-3.4.16/arch/x86/kernel/setup.c 2012-10-28 13:36:33.000000000 -0400
>> @@ -927,8 +927,21 @@
>>
>> #ifdef CONFIG_X86_64
>> if (max_pfn > max_low_pfn) {
>> - max_pfn_mapped = init_memory_mapping(1UL<<32,
>> - max_pfn<<PAGE_SHIFT);
>> + int i;
>> + for (i = 0; i < e820.nr_map; i++) {
>> + struct e820entry *ei = &e820.map[i];
>> +
>> + if (ei->addr + ei->size <= 1UL << 32)
>> + continue;
>> +
>> + if (ei->type == E820_RESERVED)
>> + continue;
>> +
>> + max_pfn_mapped = init_memory_mapping(
>> + ei->addr < 1UL << 32 ? 1UL << 32 : ei->addr,
>> + ei->addr + ei->size);
>> + }
>> +
>> /* can we preseve max_low_pfn ?*/
>> max_low_pfn = max_pfn;
>> }
>
> For the record, it is this commit introduced in 3.4.16 :
>
> commit efd5fa0c1a1d1b46846ea6e8d1a783d0d8a6a721
> Author: Jacob Shin <jacob.shin@amd.com>
> Date: Thu Oct 20 16:15:26 2011 -0500
>
> x86: Exclude E820_RESERVED regions and memory holes above 4 GB from direct mapping.
>
> commit 1bbbbe779aabe1f0768c2bf8f8c0a5583679b54a upstream.
>
> On systems with very large memory (1 TB in our case), BIOS may report a
> reserved region or a hole in the E820 map, even above the 4 GB range. Exclude
> these from the direct mapping.
>
> [ hpa: this should be done not just for > 4 GB but for everything above the legacy
> region (1 MB), at the very least. That, however, turns out to require significant
> restructuring. That work is well underway, but is not suitable for rc/stable. ]
>
> Signed-off-by: Jacob Shin <jacob.shin@amd.com>
> Link: http://lkml.kernel.org/r/1319145326-13902-1-git-send-email-jacob.shin@amd.com
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Willy
Thanks, Willy.
I've also now downloaded linux-3.7.0-rc3, and it boots/runs without need for patching.
So there's a fix somewhere in between that perhaps could also get backported to -stable.
-ml
next prev parent reply other threads:[~2012-10-29 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 4:03 Regression from 3.4.9 to 3.4.16 "stable" kernel Mark Lord
2012-10-29 6:46 ` Willy Tarreau
2012-10-29 14:22 ` Mark Lord [this message]
2012-10-29 14:37 ` Mark Lord
2012-10-29 14:40 ` Ben Hutchings
2012-10-29 14:47 ` Jacob Shin
2012-10-29 16:58 ` Greg Kroah-Hartman
2012-10-29 17:04 ` Jacob Shin
2012-10-29 23:00 ` Mark Lord
2012-10-29 23:03 ` Greg Kroah-Hartman
2012-10-30 1:20 ` Yinghai Lu
2012-10-30 4:53 ` Mark Lord
2012-10-30 16:30 ` Greg Kroah-Hartman
2012-10-29 16:37 ` Yinghai Lu
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=508E913D.2080104@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@linux.intel.com \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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;
as well as URLs for NNTP newsgroup(s).