On Mon, Oct 25, 2010 at 09:57:10PM +0800, Yong Zhang wrote:
> On Mon, Oct 25, 2010 at 04:32:01PM +0530, divya wrote:
> > http://lkml.org/lkml/2010/10/13/67 resolves the issue.
> >
> > But this is not a part of 2.6.36-git6 , when will it be pulled into the
> > upstream?
>
> That patch is splited
On Mon, Oct 25, 2010 at 04:32:01PM +0530, divya wrote:
> http://lkml.org/lkml/2010/10/13/67 resolves the issue.
>
> But this is not a part of 2.6.36-git6 , when will it be pulled into the
> upstream?
That patch is splited into two parts.
The lockdep one is 4ba053c04aece1f4734056f21b751eee47ea3fb
, 2010-10-23 at 00:37 +0530, Subrata Modak wrote:
-- Forwarded message --
From: divya
Date: Fri, Oct 22, 2010 at 1:10 PM
Subject: Re: BUG with the kernel version 2.6.36-rc1 on power machine
To: LKML, b...@kernel.crashing.org,
linuxppc-...@ozlabs.org
On Friday 22 October
ubrata Modak wrote:
> >
> >
> > -- Forwarded message --
> > From: divya
> > Date: Fri, Oct 22, 2010 at 1:10 PM
> > Subject: Re: BUG with the kernel version 2.6.36-rc1 on power machine
> > To: LKML , b...@kernel.crashing.org,
> > linuxppc-...@ozlab
This is equally seen for both Power6 and Power7 machines.
Regards--
Subrata
On Sat, 2010-10-23 at 00:37 +0530, Subrata Modak wrote:
>
>
> -- Forwarded message --
> From: divya
> Date: Fri, Oct 22, 2010 at 1:10 PM
> Subject: Re: BUG with the kernel version 2
This is seen equally on Power6 & Power7 systems.
Regards--
Subrata
On Fri, Oct 22, 2010 at 1:10 PM, divya wrote:
> On Friday 22 October 2010 12:50 PM, divya wrote:
>
>> Hi ,
>>
>> With the latest version of kernel 2.6.36-rc1 running on the power machine,
>> came across the following call trace
On Friday 22 October 2010 12:50 PM, divya wrote:
Hi ,
With the latest version of kernel 2.6.36-rc1 running on the power
machine, came across the following call trace
BUG: looking up invalid subclass: 31
turning off the locking correctness validator.
Call Trace:
[ce0bfb60] [c00
Hi ,
With the latest version of kernel 2.6.36-rc1 running on the power machine, came
across the following call trace
BUG: looking up invalid subclass: 31
turning off the locking correctness validator.
Call Trace:
[ce0bfb60] [c00119a0] .show_stack+0x6c/0x16c (unreliable)
[c00
