From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-scsi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: MPTSAS problems in 2.6.26-rc2-mm1
Date: Wed, 28 May 2008 20:26:27 +0530 [thread overview]
Message-ID: <483D729B.1000706@linux.vnet.ibm.com> (raw)
In-Reply-To: <1211986063.3445.18.camel@localhost.localdomain>
James Bottomley wrote:
> On Wed, 2008-05-28 at 11:45 +0200, Peter Zijlstra wrote:
>> On Wed, 2008-05-28 at 15:11 +0530, Balbir Singh wrote:
>>> I have 2.6.26-rc2-mm1 with Rik's splitvm patches. While booting the kernel, I
>>> ran into the following. I searched my email quickly to see that no one else has
>>> reported this problem. Lockdep seems to be complaining about the same lock being
>>> held at the same location (the message is a bit confusing to me).
>> looks like device_add() recursing - most likely with a different device
>> though.
>
> This is another instance of a problem being caused by semaphore to mutex
> conversion in struct class;
>
> There's another thread on this here:
>
> http://marc.info/?t=121074904600001
Thanks for pointer, it does indeed look like a variant of the same problem
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
prev parent reply other threads:[~2008-05-28 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 9:41 MPTSAS problems in 2.6.26-rc2-mm1 Balbir Singh
2008-05-28 9:45 ` Peter Zijlstra
2008-05-28 14:47 ` James Bottomley
2008-05-28 14:56 ` Balbir Singh [this message]
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=483D729B.1000706@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).