All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Martin Ebourne <fedora@ebourne.me.uk>,
	Zou Nan hai <nanhai.zou@intel.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Andi Kleen <ak@suse.de>,
	stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [stable] 2.6.23 boot failures on x86-64.
Date: Mon, 29 Oct 2007 11:07:39 -0700	[thread overview]
Message-ID: <20071029180739.GA17595@kroah.com> (raw)
In-Reply-To: <20071029175014.GH7793@redhat.com>

On Mon, Oct 29, 2007 at 01:50:14PM -0400, Dave Jones wrote:
> We've had a number of people reporting that their x86-64s stopped booting
> when they moved to 2.6.23.  It rebooted just after discovering the AGP bridge
> as a result of the IOMMU init.
> 
> Martin tracked this down to the following commit.
> 
> 
> commit 2e1c49db4c640b35df13889b86b9d62215ade4b6
> Author: Zou Nan hai <nanhai.zou@intel.com>
> Date:   Fri Jun 1 00:46:28 2007 -0700
> 
>     x86_64: allocate sparsemem memmap above 4G
>     
>     On systems with huge amount of physical memory, VFS cache and memory memmap
>     may eat all available system memory under 4G, then the system may fail to
>     allocate swiotlb bounce buffer.
>     
>     There was a fix for this issue in arch/x86_64/mm/numa.c, but that fix dose
>     not cover sparsemem model.
>     
>     This patch add fix to sparsemem model by first try to allocate memmap above
>     4G.
>     
>     Signed-off-by: Zou Nan hai <nanhai.zou@intel.com>
>     Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
>     Cc: Andi Kleen <ak@suse.de>
>     Cc: <stable@kernel.org>
>     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> 
> 
> This should be probably be reverted for 2.6.23-stable, and either fixed
> properly in .24, or reverted there too.

I'll be glad to revert it in -stable, if it's also reverted in Linus's
tree first :)

thanks,

greg k-h

  reply	other threads:[~2007-10-29 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 17:50 2.6.23 boot failures on x86-64 Dave Jones
2007-10-29 18:07 ` Greg KH [this message]
2007-10-29 18:37   ` [stable] " Linus Torvalds
2007-10-29 19:51     ` Christoph Lameter
2007-10-29 19:52     ` Siddha, Suresh B
2007-10-29 20:09       ` Christoph Lameter
2007-10-29 20:23     ` Andy Whitcroft
2007-10-29 20:27     ` Martin Ebourne
2007-10-29 18:18 ` Andi Kleen
2007-10-29 18:47   ` Dave Jones
2007-10-29 19:03     ` Andi Kleen
2007-10-29 19:43       ` Dave Jones
2007-10-29 19:56         ` Andi Kleen
2007-10-29 21:21         ` Martin Ebourne
2007-10-31  6:04           ` Zou Nan hai
2007-10-31  6:19             ` Zou Nan hai
2007-10-29 20:06       ` Dave Jones

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=20071029180739.GA17595@kroah.com \
    --to=greg@kroah.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=fedora@ebourne.me.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nanhai.zou@intel.com \
    --cc=stable@kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.