lkml.org 
[lkml]   [2008]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.26-rc1-$sha1: RIP __d_lookup+0x8c/0x160
On Thu, May 29, 2008 at 11:54:27PM -0700, Paul E. McKenney wrote:
> On Fri, May 30, 2008 at 09:54:06AM +0400, Alexey Dobriyan wrote:
> > On Fri, May 09, 2008 at 03:12:38AM -0700, Paul E. McKenney wrote:
> > > On Fri, May 09, 2008 at 01:22:47PM +0400, Alexey Dobriyan wrote:
> > > > On Sun, May 04, 2008 at 11:58:30PM -0700, Paul E. McKenney wrote:
> > > > > On Mon, May 05, 2008 at 09:59:40AM +0400, Alexey Dobriyan wrote:
> > > > > > Workload is build all arm defconfigs and all powerpc defconfigs and
> > > > > > something else in parallel from one source tree using O= and with
> > > > > > empty .ccache on ext2/noatime partition.
> > > > > >
> > > > > > PREEMPT_RCU was again in use to do final check of Jens's patch (see URL)
> > > > > >
> > > > > > Kernel is afa26be86b65a7183ceac29bdf1f51d6fc6932f0 + CFQ fixlet
> > > > > > http://marc.info/?l=linux-kernel&m=120946003120291&w=2 .
> > > > > >
> > > > > > Oops, disassembly and .config (DEBUG_INFO was turned off) below.
> > > > > >
> > > > > > Should we add PREEMPT_RCU to oops reports, BTW?
> > > > >
> > > > > Given that you see it with PREEMPT_RCU, but not classic RCU, that would
> > > > > make sense...
> > > > >
> > > > > I presume that this version of the kernel has the fixes from this thread
> > > > > applied?
> > > > >
> > > > > http://lkml.org/lkml/2008/4/19/85
> > > >
> > > > I recall two fixes from this thread: list.h one and text_poke() one. And
> > > > they were applied before 2.6.26-rc1. Were there anything else?
> > >
> > > Those are the two I am aware of.
> >
> > Triggered second time with 2.6.24-rc4.
> >
> > FWIW, workload was LTP in infinite loop + parallel compiling on 170 configs
> > with make O=../ on ext2
> > Core 2 Duo, 4G RAM, PREEMPT/PREEMPT_RCU, HZ=1000
>
> Thank you for the info!
>
> So you have 170 concurrent "make O=../" builds running, with them all
> putting their .o files in a common directory?

No, of course, not. :-) It's like this:

src
build/config-1/
build/config-2/
...
.ccache/
[.ccache stuff]
all in one ext2/noatime disk.

So the command line is like O=../build/$TARGET

> Are you using 170 specific configurations, or are the all running randconfig?

Very specific but this shouldn't matter. Some are fat (sparc64 allmodconfig),
some are nimble (arm defconfigs). loadavg is around 210 at the start.



\
 
 \ /
  Last update: 2008-05-30 20:59    [W:0.053 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site