From: Marcel Holtmann <marcel@holtmann.org>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] [BUG] rfcomm]
Date: Tue, 23 Oct 2007 20:26:46 +0200 [thread overview]
Message-ID: <1193164006.6184.217.camel@violet> (raw)
In-Reply-To: <9e0cf0bf0710231057lf60ce17ldd38489850cdf7c5@mail.gmail.com>
Hi Alon,
> > first of all, please check if this still happens with 2.6.23, because we
> > had some patches in the area of the RFCOMM TTY code that might have
> > fixed this.
>
> These messages are of 2.6.23.
still another one to go :( Anyway since you have experience and you have
a way to reproduce it, please test the latest kernel from Linus' Git
tree.
I can also whip up a patch that disables the device_move() usage and see
if that is the reason for the falling over.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-23 18:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710231950.31313.alon.barlev@gmail.com>
[not found] ` <1193162106.6184.208.camel@violet>
2007-10-23 18:06 ` [BUG] rfcomm] Jiri Kosina
2007-10-23 18:25 ` [Bluez-devel] " Marcel Holtmann
2007-10-23 18:27 ` Alon Bar-Lev
2007-10-23 18:30 ` [Bluez-devel] " Marcel Holtmann
2007-10-23 18:55 ` Alon Bar-Lev
2007-10-24 8:43 ` Cornelia Huck
2007-10-23 18:28 ` Jiri Kosina
2007-10-24 9:56 ` [Bluez-devel] " Pavel Machek
[not found] ` <9e0cf0bf0710231057lf60ce17ldd38489850cdf7c5@mail.gmail.com>
2007-10-23 18:26 ` Marcel Holtmann [this message]
2007-10-23 22:10 ` Rafael J. Wysocki
[not found] ` <a8e1da0711051849ma591d4k6a816e2de7390347@mail.gmail.com>
[not found] ` <9e0cf0bf0711052149t5c9fe50j19d13e368690efb@mail.gmail.com>
[not found] ` <200802111757.56537.alon.barlev@gmail.com>
2008-02-13 7:58 ` [BUG] rfcomm Andrew Morton
2008-02-13 16:58 ` Mark Lord
2008-02-15 3:28 ` Dave Young
2008-02-15 23:13 ` Dave Young
2008-02-15 23:40 ` [Bluez-devel] sdptool segfault Nelson Murilo
2008-02-18 13:47 ` Claudio Takahasi
2008-02-21 11:40 ` Nelson Murilo
2008-02-16 21:49 ` [BUG] rfcomm Alon Bar-Lev
2008-02-20 10:36 ` Dave Young
2008-02-20 11:16 ` [Bluez-devel] " Stefan Seyfried
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=1193164006.6184.217.camel@violet \
--to=marcel@holtmann.org \
--cc=alon.barlev@gmail.com \
--cc=bluez-devel@lists.sf.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