linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Kevin Baradon <kevin.baradon@gmail.com>
Subject: Re: [Bluez-devel] Lockdep: possible recursive locking detected in	hidd
Date: Wed, 26 Jul 2006 09:35:29 +0200	[thread overview]
Message-ID: <1153899329.746.24.camel@localhost> (raw)
In-Reply-To: <200607181921.52647.Kevin.Baradon@gmail.com>

Hi Kevin,

> I've got a Logitech Bluetooth keyboard. 
> With lockdep enabled, I've got the following message just after boot, after 

this looks like a lock problem in L2CAP. We fixed one, but I am not sure
if it already made it into 2.6.18-rc2 or not. Can you give the latest
tree from Linus repository a try?

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-07-26  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 17:21 [Bluez-devel] Lockdep: possible recursive locking detected in hidd Kevin Baradon
2006-07-26  7:35 ` Marcel Holtmann [this message]
2006-07-26 22:04   ` Kevin Baradon

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=1153899329.746.24.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=kevin.baradon@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).