From: penberg@cs.helsinki.fi (Pekka Enberg)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression on UP ARM from commit e18d65f0500b95d8724b17d8ea9f1116cf390bbe
Date: Tue, 14 Sep 2010 08:49:44 +0300 [thread overview]
Message-ID: <4C8F0CF8.1050309@cs.helsinki.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.1009130855430.26275@router.home>
On 9/13/10 4:58 PM, Christoph Lameter wrote:
> On Sun, 12 Sep 2010, Linus Walleij wrote:
>
>> commit e18d65f0500b95d8724b17d8ea9f1116cf390bbe
>> "slub: Remove static kmem_cache_cpu array for boot"
>> made my ARM 926 UP system hang at boot, if I revert this (have
>> to back out a lot of SLUB patches for that) it comes back up. (Same if I
>> switch to SLAB.)
>>
>> Any hints on how I can get patch around this in a nice way?
>
> This is UP right? Any more details on this one? Does ARM have
> earlyprintk?
>
> Tejun also has some patches that make the percpu allocator work on UP so
> that we do not need the hack (you must have the hack which is commit
> c23e5ad729ac43f5e2fbc080f94cf61f07b4d45f as well to make UP work right!).
>
> I am not sure if they are already in -next though.
Yes, they should be in linux-next. I haven't pulled the changes to
slab.git, though. Linus, do things work in linux-next if you revert
commit 5249d039500f05a5ab379286b1d23ab9b04d3f2c ("Slub: UP bandaid")?
Pekka
next prev parent reply other threads:[~2010-09-14 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 21:47 Regression on UP ARM from commit e18d65f0500b95d8724b17d8ea9f1116cf390bbe Linus Walleij
2010-09-13 5:55 ` Baruch Siach
2010-09-13 8:41 ` Mark Brown
2010-09-13 13:58 ` Christoph Lameter
2010-09-14 5:49 ` Pekka Enberg [this message]
2010-09-20 7:42 ` Pekka Enberg
2010-09-20 13:12 ` Linus Walleij
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=4C8F0CF8.1050309@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=linux-arm-kernel@lists.infradead.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 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).