[lkml]   [2008]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bug #10815] 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0

* Paul E. McKenney <> wrote:

> > > Also Core 2 Duo, x86_64 [1]
> > >
> > > Race is wide -- 60 seconds of rcutorture is enough.
> This is rcutorture by itself, or in parallel with LTP/kernbench?
> (I have mostly been running on 4-CPU boxes without failure either way,
> so will try a dual-CPU box.)

FYI, i've been running rcutorture for days on lots of testboxes ranging
all across the x86 spectrum from single CPU, through dual-core, to
dual-socket, dual-socket HT, 8-way and 16-way - both 32-bit and 64-bit

Not a single failure has been detected in thousands of bootups of random
kernels (rcu-preempt + rcutorture was a frequent combination tested). I
added a WARN_ON() to rcutorture failures so it should show up very

This makes me suspect that it might be some special environment issue -
gcc for example. I'm using gcc 4.2.2 on most of the testboxes.


 \ /
  Last update: 2008-06-24 23:23    [W:0.076 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site