From: "Håvard Skinnemoen" <hskinnemoen@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Haavard Skinnemoen" <hskinnemoen@atmel.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"David Brownell" <david-b@pacbell.net>
Subject: Re: kernel BUG at mm/slub.c:3689!
Date: Mon, 11 Jun 2007 21:53:32 +0200 [thread overview]
Message-ID: <1defaf580706111253q2a4910b1v4802436e32e94953@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706111239230.19654@schroedinger.engr.sgi.com>
On 6/11/07, Christoph Lameter <clameter@sgi.com> wrote:
> Trouble is that ARCH_KMALLOC_MINALIGN is in bytes whereas we would need a
> shift value for KMALLOC_MIN_SHIFT.
Ah, of course. Hrm...I just thought I had an idea, but it wouldn't work...
> Does the latest patch work?
I'm sorry, but I haven't tested it yet. My board needs a hard reset,
and I can't do that over VPN. I'll test it first thing in the morning.
Håvard
next prev parent reply other threads:[~2007-06-11 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 14:19 Haavard Skinnemoen
2007-06-11 15:38 ` Paul Mundt
2007-06-11 15:58 ` Håvard Skinnemoen
2007-06-11 16:19 ` Christoph Lameter
2007-06-11 16:43 ` Håvard Skinnemoen
2007-06-11 16:49 ` Christoph Lameter
2007-06-11 17:11 ` Håvard Skinnemoen
2007-06-11 17:52 ` Christoph Lameter
2007-06-11 18:22 ` Håvard Skinnemoen
2007-06-11 18:32 ` Christoph Lameter
2007-06-11 19:04 ` Håvard Skinnemoen
2007-06-11 19:11 ` Christoph Lameter
2007-06-11 19:35 ` Håvard Skinnemoen
2007-06-11 19:40 ` Christoph Lameter
2007-06-11 19:53 ` Håvard Skinnemoen [this message]
2007-06-12 3:16 ` Christoph Lameter
2007-06-12 8:55 ` Haavard Skinnemoen
2007-06-12 10:16 ` Haavard Skinnemoen
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=1defaf580706111253q2a4910b1v4802436e32e94953@mail.gmail.com \
--to=hskinnemoen@gmail.com \
--cc=clameter@sgi.com \
--cc=david-b@pacbell.net \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®