[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46F90827.2060203@linux.vnet.ibm.com>
Date: Tue, 25 Sep 2007 18:37:51 +0530
From: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc7-mm1
Peter Zijlstra wrote:
> On Mon, 24 Sep 2007 21:20:58 +0200 Peter Zijlstra
> <a.p.zijlstra@...llo.nl> wrote:
>
>>>> Nope, and the stacktrace is utterly puzzling.
>>>>
>>>> /me goes read the lkml.org link
>>>>
>>>> Kamalesh Babulal: do you still get:
>>>> BUG: spinlock bad magic on
>>>>
>>>> msgs?
>>>>
>>>> Because those I could reproduce using fsx, and I fixed all that.
>>> Hi Peter,
>>>
>>> I do not get BUG: spinlock bad magic messages any more, but the softlock message is
>>> thrown more than 30 time, while running the ltp runall.
>> It would be good to know what function on_each_cpu is executing, could
>> you try something like:
>
> I've just completed 2 full ltp runs on a dual-core opteron machine but
> could not reproduce this problem.
>
> Kamalesh, would it be possible for you to reproduce with that patch, so
> we can see what function is holding up the cpu?
Hi Peter,
After running the test with the patch you provided, i observed an oops message
which was at the top of the these soft lockup message and the oops is the same as
the oops reported at http://lkml.org/lkml/2007/9/24/107.
And when i applied the patch for the oops proposed at
http://lkml.org/lkml/2007/9/25/57 the oops as well as the soft lockup's are not seen.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
-
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