From: Marcel Holtmann <marcel@holtmann.org>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Oliver Neukum <oliver@neukum.org>,
linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org,
Arjan Van De Ven <arjan@linux.intel.com>,
saharabeara@gmail.com
Subject: Re: btusb autosuspend and circular lock dep
Date: Mon, 24 Aug 2009 16:07:11 -0700 [thread overview]
Message-ID: <1251155231.2950.74.camel@localhost.localdomain> (raw)
In-Reply-To: <20090824224924.GA30024@gamba.jf.intel.com>
Hi Sara,
> > I just tested this patch (against 2.6.31-rc7) on my X200s laptop, and it
> > works fine with the Broadcom USB bluetooth device with VID:PID
> > 0a5c:2145. I tested transmitting audio to a bluetooth headset, so the
> > isoc transfers to work fine. ISTR you were concerned about them.
> >
> > I'm still testing on my T61 (Broadcom 0a5c:2110). The autosuspend patch
> > seems to work fine, but I'm getting a circular lock dependency warning.
> > I'm recompiling a vanilla 2.6.31-rc7 to see if the lock warning is still
> > there.
>
> The lock dep warning is still present in 2.6.31-rc7, so it's not your
> auto-suspend patch. The dmesg is attached. The warning came right
> after I stopped mplayer streaming audio to the bluetooth headset (with
> CTRL+c). I'm running an older gnome bluetooth stack from June 14
> (from commit 7b1f2782). I haven't tested whether updating the userspace
> bits makes the lock dep warning go way.
can you try the bluetooth-testing.git tree from kernel.org with the
patch from Oliver. The SCO shutdown patch might fix this.
Regards
Marcel
next prev parent reply other threads:[~2009-08-24 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090615175435.GA4772@gamba.jf.intel.com>
[not found] ` <200906210034.42481.oliver@neukum.org>
[not found] ` <1251102046.2950.28.camel@localhost.localdomain>
2009-08-24 9:49 ` btusb autosuspend and circular lock dep Oliver Neukum
2009-08-24 10:16 ` Marcel Holtmann
2009-08-24 12:29 ` Oliver Neukum
2009-08-24 16:56 ` Marcel Holtmann
2009-08-24 13:59 ` Oliver Neukum
2009-08-24 17:03 ` Marcel Holtmann
2009-08-24 19:49 ` Oliver Neukum
2009-08-24 19:59 ` Marcel Holtmann
2009-08-24 21:26 ` Oliver Neukum
2009-08-24 21:36 ` Marcel Holtmann
2009-08-24 21:44 ` Oliver Neukum
2009-08-24 21:58 ` Sarah Sharp
2009-08-24 22:49 ` Sarah Sharp
2009-08-24 23:07 ` Marcel Holtmann [this message]
2009-08-24 23:30 ` Marcel Holtmann
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=1251155231.2950.74.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=arjan@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=saharabeara@gmail.com \
--cc=sarah.a.sharp@linux.intel.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