On Tue, Jun 28, 2011 at 04:39:21PM -0700, Chandra Seetharaman wrote:
> On Thu, 2011-06-16 at 16:29 -0500, Alex Elder wrote:
> > On Tue, 2011-06-14 at 11:51 -0700, Chandra Seetharaman wrote:
> > > Hello All,
> > >
> > > test case 180 fails often (4 out of 5) in my x86_64 system.
> > > Any suggestions on how to proceed to debug ?
> > I have been seeing failures like that sometimes
> > (more often recently I think) for a while. I
> > have not had the chance to really chase it down.
> > If you can reproduce it pretty relibly you could
> > use "git bisect" to try to find out whether the
> > failures started to occur after a particular
> > commit.
> I tried git bisect and it ended up in a qla2xxx fix (and I do not even
> have qlogic card in that system).
> I did it couple more times and landed on different patches.
That indicates your test case is not 100% reliable. :/
I haven't seen a failure in 180 on any of my test machines for some
time (32 or 64 bit).
> My latest (fourth ot fifth, I forgot :) bisect landed on the patch with
> commit 546a1924224078c6f582e68f890b05b387b42653 ( writeback:
> write_cache_pages doesn't terminate at nr_to_write <= 0)
That was merged in 2.6.36-rc2, and shouldn't have any sync
implications at all....
> I verified that this is valid patch by running the test script 180 for
> nearly 500 times on the tree just prior to this patch.
Ok, more details about your test setup is needed. What kernel are
you running? What storage are you using? How much RAM/CPU, etc?
Also, what are the sizes of the files that had reported incorrect
PS: Please don't top post replies. Please quote and reply inline so
that the thread flow is easy to follow.