From: Ville Tervo <ville.tervo@nokia.com>
To: ext Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: rfcomm oops
Date: Tue, 05 Jul 2005 10:41:17 +0300 [thread overview]
Message-ID: <1120549277.30194.55.camel@localhost.localdomain> (raw)
In-Reply-To: <1120490944.10273.164.camel@pegasus>
On Mon, 2005-07-04 at 17:29 +0200, ext Marcel Holtmann wrote:
> Hi Ville,
>
> > I found reproducible way to make rfcomm layer oops. I attached oops and
> > some notes how they were produced. I used several Nokia phones and IBM
> > T40 laptop in these tests.
>
> if the attached patch makes it go away, then I know what it is. Actually
> I introduced that problem when I tried to fix another bug with buggy
> phones that can't disconnect their DLCI 0 even if they established it.
>
Look like this patch helps. I tested with i386 and arm.
--
Ville
next prev parent reply other threads:[~2005-07-05 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 15:19 rfcomm oops Ville Tervo
2005-07-04 15:29 ` [Bluez-devel] " Marcel Holtmann
2005-07-05 7:41 ` Ville Tervo [this message]
2005-07-05 8:14 ` Marcel Holtmann
2005-07-04 15:37 ` [Bluez-devel] " Wolfram Quester
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=1120549277.30194.55.camel@localhost.localdomain \
--to=ville.tervo@nokia.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox