[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0806231827330.2926@woody.linux-foundation.org>
Date: Mon, 23 Jun 2008 18:31:06 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alexey Dobriyan <adobriyan@...il.com>
cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Oleg Nesterov <oleg@...sign.ru>, Adrian Bunk <bunk@...nel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org
Subject: Re: [Bug #10815] 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0
On Tue, 24 Jun 2008, Alexey Dobriyan wrote:
>
> Status update:
> * bug is reproduced on another box with the very same symptoms:
> SMP=y, maxcpus=1 kernel occasionally fails, SMP=n is fine.
> Also Core 2 Duo, x86_64 [1]
>
> Race is wide -- 60 seconds of rcutorture is enough.
Very odd how you can reproduce it - now on two machines - but it doesn't
seem to happen for others. You've tried different compilers, you've tried
different config options, what the heck is left?
And it's not like Core 2 Duo is an "odd" setup. Even any timer differences
should have been largely flushed out with HIGH_RES_TIMERS=y/n.
Is there *anything* odd about those machines?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists