From: Ben Greear <greearb@candelatech.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Tejun Heo <tj@kernel.org>, Pekka Enberg <penberg@kernel.org>,
Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
werner <w.landgraf@ru.ru>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH] slub: Fix the lockless code on 32-bit platforms with no 64-bit cmpxchg
Date: Wed, 04 May 2011 15:22:29 -0700 [thread overview]
Message-ID: <4DC1D1A5.7050408@candelatech.com> (raw)
In-Reply-To: <BANLkTim1L9Gz2kk_SjTe2g_SmKJV=FfuRQ@mail.gmail.com>
On 05/04/2011 03:00 PM, Linus Torvalds wrote:
> On Wed, May 4, 2011 at 2:52 PM, Ben Greear<greearb@candelatech.com> wrote:
>>
>> This patch appears to fix the crashes I was seeing on my 32-bit
>> Atom system.
>>
>> It would crash within 30 seconds of booting every time before this patch...
>
> Oh, well - I already committed it and pushed out, otherwise I'd have
> added that piece of information to the commit log.
No worries...I'm just happy to finally be able to boot .39 :)
> But it's good to know that others had seen this too, just never
> realized what was going on.
>
> Btw, that does seem to imply that your kernel config is somewhat odd.
> We _should_ be using cmpxchg8b natively if you compile for anything
> newer than PPro, and that includes atom.
>
> Did you perhaps say "compile for Pentium" (which is pretty close to
> Atom in some respects - but we don't trust that all Pentium-class
> CPU's have cmpxchg8b, even if the Intel ones all should).
Well, yes. I'm compiling for 'M586' it seems, plus SMP, pre-empt, etc.
Maybe it's time to move to a newer processor family!
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-04 22:25 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 22:28 2.6.39-rc5-git2 boot crashs werner
2011-05-02 23:24 ` Linus Torvalds
[not found] ` <web-516990066@zbackend1.aha.ru>
2011-05-03 15:22 ` Linus Torvalds
2011-05-03 19:08 ` Ingo Molnar
2011-05-03 20:17 ` Linus Torvalds
2011-05-03 20:20 ` H. Peter Anvin
2011-05-03 20:50 ` Ingo Molnar
2011-05-03 21:45 ` Linus Torvalds
2011-05-03 22:01 ` H. Peter Anvin
2011-05-04 7:19 ` Borislav Petkov
2011-05-04 7:38 ` Ingo Molnar
2011-05-04 7:55 ` Borislav Petkov
2011-05-04 8:35 ` [block IO crash] " Ingo Molnar
2011-05-04 9:52 ` Thomas Gleixner
2011-05-04 10:19 ` Ingo Molnar
2011-05-04 10:25 ` Ingo Molnar
2011-05-04 10:33 ` Ingo Molnar
2011-05-04 12:37 ` Ingo Molnar
2011-05-04 12:36 ` Ingo Molnar
2011-05-04 11:11 ` Thomas Gleixner
2011-05-04 11:16 ` Pekka Enberg
2011-05-04 11:27 ` Tejun Heo
2011-05-04 12:51 ` Pekka Enberg
2011-05-04 12:57 ` Ingo Molnar
2011-05-04 13:02 ` Thomas Gleixner
2011-05-04 13:00 ` Thomas Gleixner
2011-05-04 13:20 ` Tejun Heo
2011-05-04 14:10 ` Thomas Gleixner
2011-05-04 14:14 ` Ingo Molnar
2011-05-04 14:36 ` [PATCH] slub: Fix the lockless code on 32-bit platforms with no 64-bit cmpxchg Ingo Molnar
2011-05-04 14:42 ` Christoph Lameter
2011-05-04 16:30 ` Ingo Molnar
2011-05-04 21:52 ` Ben Greear
2011-05-04 22:00 ` Linus Torvalds
2011-05-04 22:22 ` Ben Greear [this message]
2011-05-04 14:19 ` [block IO crash] Re: 2.6.39-rc5-git2 boot crashs Christoph Lameter
2011-05-04 14:25 ` Tejun Heo
2011-05-04 14:35 ` Christoph Lameter
2011-05-04 15:20 ` Ingo Molnar
2011-05-04 14:46 ` Thomas Gleixner
2011-05-04 15:00 ` Christoph Lameter
2011-05-04 15:13 ` Linus Torvalds
2011-05-04 15:28 ` Christoph Lameter
2011-05-04 15:37 ` Pekka Enberg
2011-05-04 15:53 ` Linus Torvalds
2011-05-04 18:20 ` Linus Torvalds
2011-05-04 18:49 ` Christoph Lameter
2011-05-04 19:07 ` Linus Torvalds
2011-05-04 19:30 ` Christoph Lameter
2011-05-04 19:38 ` Linus Torvalds
2011-05-04 20:04 ` Christoph Lameter
2011-05-04 20:21 ` Valdis.Kletnieks
2011-05-04 20:32 ` Christoph Lameter
2011-05-04 20:49 ` Ingo Molnar
2011-05-04 21:06 ` Linus Torvalds
2011-05-04 21:19 ` Linus Torvalds
2011-05-04 21:40 ` Thomas Gleixner
2011-05-05 9:54 ` Tejun Heo
2011-05-05 10:18 ` Ingo Molnar
2011-05-05 10:45 ` Thomas Gleixner
2011-05-05 18:20 ` Christoph Lameter
2011-05-05 19:13 ` Ingo Molnar
2011-05-05 19:53 ` werner
2011-05-05 20:09 ` Christoph Lameter
2011-05-05 21:12 ` werner
2011-05-05 22:27 ` Thomas Gleixner
[not found] ` <web-518008166@zbackend1.aha.ru>
[not found] ` <web-518059420@zbackend1.aha.ru>
[not found] ` <20110505060204.GA28015@elte.hu>
2011-05-05 6:46 ` werner
2011-05-04 15:37 ` [block IO crash] " Linus Torvalds
2011-05-04 16:08 ` Christoph Lameter
2011-05-04 16:50 ` Ingo Molnar
2011-05-04 17:12 ` Thomas Gleixner
2011-05-04 15:41 ` Pekka Enberg
2011-05-04 13:22 ` Ingo Molnar
2011-05-04 14:21 ` Christoph Lameter
2011-05-04 14:04 ` Christoph Lameter
2011-05-04 14:07 ` Tejun Heo
2011-05-04 14:21 ` Thomas Gleixner
2011-05-04 10:13 ` Ingo Molnar
2011-05-04 10:41 ` Ingo Molnar
2011-05-04 10:45 ` Ingo Molnar
2011-05-04 11:06 ` Ingo Molnar
2011-05-04 12:37 ` Ingo Molnar
2011-05-04 12:47 ` Ingo Molnar
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=4DC1D1A5.7050408@candelatech.com \
--to=greearb@candelatech.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=cl@linux.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w.landgraf@ru.ru \
/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