From: Marcel Holtmann <marcel@holtmann.org>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: bluez-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Jiri Kosina <jikos@jikos.cz>
Subject: Re: [Bluez-devel] [BUG] rfcomm]
Date: Tue, 23 Oct 2007 20:30:10 +0200 [thread overview]
Message-ID: <1193164210.6184.221.camel@violet> (raw)
In-Reply-To: <9e0cf0bf0710231127o485a52e1sc7a06df7c8bc0189@mail.gmail.com>
Hi Alon,
> > nice. I've never used it. Currently I am using what comes with Ubuntu
> > 7.10 and that seems to work.
>
> Have you tried to suspend while pppd is using rfcomm?
>
> The fact that it happens with suspend2 and uswsusp means that the
> issue is suspend blind.
> Do you need any more information in order to determine what is the problem?
the code in net/bluetooth/rfcomm/tty.c contains two calls to
device_move(). Please comment these out and try again. At least then we
know that it is in issue on how we use the driver model.
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
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: Jiri Kosina <jikos@jikos.cz>,
linux-kernel@vger.kernel.org, bluez-devel@lists.sourceforge.net
Subject: Re: [BUG] rfcomm]
Date: Tue, 23 Oct 2007 20:30:10 +0200 [thread overview]
Message-ID: <1193164210.6184.221.camel@violet> (raw)
In-Reply-To: <9e0cf0bf0710231127o485a52e1sc7a06df7c8bc0189@mail.gmail.com>
Hi Alon,
> > nice. I've never used it. Currently I am using what comes with Ubuntu
> > 7.10 and that seems to work.
>
> Have you tried to suspend while pppd is using rfcomm?
>
> The fact that it happens with suspend2 and uswsusp means that the
> issue is suspend blind.
> Do you need any more information in order to determine what is the problem?
the code in net/bluetooth/rfcomm/tty.c contains two calls to
device_move(). Please comment these out and try again. At least then we
know that it is in issue on how we use the driver model.
Regards
Marcel
next prev parent reply other threads:[~2007-10-23 18:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 17:50 [BUG] rfcomm] Alon Bar-Lev
2007-10-23 17:55 ` Marcel Holtmann
2007-10-23 17:57 ` Alon Bar-Lev
2007-10-23 18:26 ` [Bluez-devel] " Marcel Holtmann
2007-10-23 18:26 ` Marcel Holtmann
2007-10-23 18:28 ` Alon Bar-Lev
2007-10-23 22:10 ` [Bluez-devel] " Rafael J. Wysocki
2007-10-23 22:10 ` Rafael J. Wysocki
2007-10-23 18:06 ` Jiri Kosina
2007-10-23 18:25 ` [Bluez-devel] " Marcel Holtmann
2007-10-23 18:25 ` Marcel Holtmann
2007-10-23 18:27 ` Alon Bar-Lev
2007-10-23 18:30 ` Marcel Holtmann [this message]
2007-10-23 18:30 ` 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
2007-10-24 9:56 ` Pavel Machek
2007-11-05 5:08 ` [Bluez-devel] " Dave Young
2007-11-05 15:46 ` Alon Bar-Lev
2007-11-06 1:48 ` Dave Young
2007-11-06 2:49 ` Dave Young
2007-11-06 5:49 ` Alon Bar-Lev
2008-02-11 15:57 ` [BUG] rfcomm Alon Bar-Lev
2008-02-11 22:48 ` Frederik Deweerdt
2008-02-13 7:58 ` 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-16 21:49 ` Alon Bar-Lev
2008-02-20 10:36 ` Dave Young
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=1193164210.6184.221.camel@violet \
--to=marcel@holtmann.org \
--cc=alon.barlev@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jikos@jikos.cz \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.