linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: divya <dipraksh@linux.vnet.ibm.com>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>,
	Subrata Modak <subrata@linux.vnet.ibm.com>
Subject: Re: BUG with the kernel version 2.6.36-rc1 on power machine
Date: Mon, 25 Oct 2010 16:32:01 +0530	[thread overview]
Message-ID: <4CC563A9.3020308@linux.vnet.ibm.com> (raw)
In-Reply-To: <20101023093630.GA3036@zhy>

On Saturday 23 October 2010 03:06 PM, Yong Zhang wrote:
> On Sat, Oct 23, 2010 at 12:43:21AM +0530, Subrata Modak wrote:
>    
>> This is equally seen for both Power6 and Power7 machines.
>>      
> Seems resolved by part of http://lkml.org/lkml/2010/10/13/67
>
> Thanks,
> Yong
>
>    
>> Regards--
>> Subrata
>>
>> On Sat, 2010-10-23 at 00:37 +0530, Subrata Modak wrote:
>>      
>>>
>>> ---------- Forwarded message ----------
>>> From: divya<dipraksh@linux.vnet.ibm.com>
>>> 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<linux-kernel@vger.kernel.org>, benh@kernel.crashing.org,
>>> linuxppc-dev@ozlabs.org
>>>
>>>
>>>
>>> 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:
>>>          [c00000000e0bfb60] [c0000000000119a0] .show_stack+0x6c/0x16c
>>>          (unreliable)
>>>          [c00000000e0bfc10] [c0000000000c39b8] .lockdep_init_map
>>>          +0x194/0x630
>>>          [c00000000e0bfcf0] [c0000000005524f8] .mousedev_create
>>>          +0xcc/0x234
>>>          [c00000000e0bfda0] [c00000000093fb58] .mousedev_init+0x38/0xa0
>>>          [c00000000e0bfe30] [c0000000000097e4] .do_one_initcall
>>>          +0xd8/0x1c8
>>>          [c00000000e0bfee0] [c0000000009004ac] .kernel_init+0x23c/0x2f8
>>>          [c00000000e0bff90] [c00000000002ad30] .kernel_thread+0x54/0x70
>>>
>>>          The config file used for make oldconfig is being attached
>>>
>>>          Thanks
>>>          Divya
>>>
>>>
>>>
>>>
>>> I meant 2.6.36-git1(b5153163ed580e) , and not 2.6.36-rc1.
>>> Sorry for the confusion.
>>>
>>> Thanks
>>> Divya
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>> linux-kernel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at  http://www.tux.org/lkml/
>>>
>>>
>>>
>>>
>>> -- 
>>> Regards&  Thanks--
>>> Subrata
>>>        
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>>      
The patch at
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?

Thanks
Divya

  reply	other threads:[~2010-10-25 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  7:20 BUG with the kernel version 2.6.36-rc1 on power machine divya
2010-10-22  7:40 ` divya
2010-10-22 19:04   ` Subrata Modak
     [not found]   ` <AANLkTikmpohofzO_dV_Dv8EfcEMsyy4cdhGMUD-PAFO3@mail.gmail.com>
2010-10-22 19:13     ` Subrata Modak
2010-10-23  9:36       ` Yong Zhang
2010-10-25 11:02         ` divya [this message]
2010-10-25 13:57           ` Yong Zhang
2010-10-25 14:15             ` Yong Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CC563A9.3020308@linux.vnet.ibm.com \
    --to=dipraksh@linux.vnet.ibm.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=subrata@linux.vnet.ibm.com \
    --cc=yong.zhang0@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).