From: Greg KH <greg@kroah.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable <stable@vger.kernel.org>,
hpa@linux.intel.com, Mel Gorman <mgorman@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Dave Hansen <dave@linux.vnet.ibm.com>
Subject: Re: [stable 3.0 revert request] x86-32, mm: Remove reference to resume_map_numa_kva()
Date: Wed, 10 Apr 2013 15:23:33 -0700 [thread overview]
Message-ID: <20130410222333.GA2139@kroah.com> (raw)
In-Reply-To: <515EB8B6.3070900@suse.cz>
On Fri, Apr 05, 2013 at 01:42:46PM +0200, Jiri Slaby wrote:
> Hi,
>
> in 3.0.67 there is this commit:
> commit dbb694e810c87e7e1760527a783437f26ac5a547
> Author: H. Peter Anvin <hpa@linux.intel.com>
> Date: Thu Jan 31 13:53:10 2013 -0800
>
> x86-32, mm: Remove reference to resume_map_numa_kva()
>
> commit bb112aec5ee41427e9b9726e3d57b896709598ed upstream.
>
> Remove reference to removed function resume_map_numa_kva().
>
>
>
> But it depends on f03574f2 (which was applied to 3.2, 3.4, 3.7 and 3.8
> stable trees, but not to 3.0). Now, when f03574f2 is not there, resume
> from suspend dies terrible death on 32-bit:
> Enabling non-boot CPUs ...
> ------------[ cut here ]------------
> kernel BUG at mm/slab.c:532!
> invalid opcode: 0000 [#1] SMP
>
>
> In 3.0, we need either f03574f2:
> commit f03574f2d5b2d6229dcdf2d322848065f72953c7
> Author: Dave Hansen <dave@linux.vnet.ibm.com>
> Date: Wed Jan 30 16:56:16 2013 -0800
>
> x86-32, mm: Rip out x86_32 NUMA remapping code
>
> or revert the commit above...
I've applied f03574f2 to the 3.0-stable tree, thanks for letting me
know.
greg k-h
prev parent reply other threads:[~2013-04-10 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 11:42 [stable 3.0 revert request] x86-32, mm: Remove reference to resume_map_numa_kva() Jiri Slaby
2013-04-10 22:23 ` Greg KH [this message]
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=20130410222333.GA2139@kroah.com \
--to=greg@kroah.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@linux.intel.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=stable@vger.kernel.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.