From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: victor.shcherbatyuk@tomtom.com
Subject: Re: [Bluez-devel] RFCOMM related oops
Date: Mon, 28 Mar 2005 23:37:16 +0200 [thread overview]
Message-ID: <1112045836.9016.56.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.44.0503282103070.7184-201000@antilope>
Hi Victor,
> Some more problems...
>
> The following holds for Motorola V3 (RAZR) and Nokia 6310i (i hope i'm not
> mistaking), and prob. some more phones I've never seen ;)
>
> The sequence leading to the oops (oops.txt):
> Open RFCOMM channel exposed as HF channel. Try to open RFCOMM channel
> exposed as DUN channel for 3 times (first 2 fail, and finally attempt 3
> gives success). Close RFCOMM channel for DUN. Close RFCOMM channel for HF ->
> oops.
>
> Looks like those phones allow only 1 RFCOMM channel to be opened. But
> strange things happen if you try to connect, when there is
> already a RFCOMM connection open on another channel (all this story with
> 3 attempts).
>
> What I see from the log (motov3.bin):
> On attempt 2 bluez stack DISC on dlci 0 (for the reason I don't know)
> where there are still active RFCOMM connections (HF channel, dlci 14 in
> the log). So when I try to close HF it oops'es...
>
> Have it reproducible on 2 platforms (arm and i386):
> 2.6.11.4 + 2.6.11-mh2 (i386)
I hope this is not because of my fix for the reference counting problem
you found. Check if this still happens with a vanilla 2.6.11 kernel.
If it still happens try to reproduce it without the ndiswrapper. This
taints your kernel and I am not willing to fix buggy Windows drivers.
Next thing is to try it without PREEMPT enabled.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-28 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 20:55 [Bluez-devel] RFCOMM related oops Victor Shcherbatyuk
2005-03-28 21:37 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-06 9:20 Victor Shcherbatyuk
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=1112045836.9016.56.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=victor.shcherbatyuk@tomtom.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