From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
BlueZ@sc8-sf-spam2.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Bluez-devel] Warnings and Bug on 2.6.23-rc6 closing rfcomm links (device_move() API ?)
Date: Fri, 28 Sep 2007 01:04:51 +0200 [thread overview]
Message-ID: <1190934291.6484.76.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20070927154804.17487b20@gondolin.boeblingen.de.ibm.com>
Hi Cornelia,
> > >> Yet another report, once again while putting rfcomm system under load.
> > >> Several USB adapters, several links.
> > >
> > > Is this a regression or does it happen with 2.6.22 too?
> >
> > I've not tested with 2.6.22, but have done it a few days ago with
> > 2.6.21-2-486 (stock debian package), and got the 2 Oops below. Maybe
> > that's a different problem, or maybe not?
> >
> >
> > kobject_add failed for rfcomm1 with -EEXIST, don't try to register
> > things with the same name in the same directory.
>
> There's something wrong with rfcomm trying to create objects with
> duplicate names...
that should have been fixed.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-09-27 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 15:13 [Bluez-devel] Warnings and Bug on 2.6.23-rc6 closing rfcomm links (device_move() API ?) Pierre-Yves Paulus
2007-09-27 12:29 ` Rafael J. Wysocki
2007-09-27 12:40 ` Pierre-Yves Paulus
2007-09-27 13:48 ` Cornelia Huck
2007-09-27 23:04 ` Marcel Holtmann [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=1190934291.6484.76.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=BlueZ@sc8-sf-spam2.sourceforge.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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