All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Release of new BlueZ libs and utils
Date: Tue, 06 Jan 2004 15:15:29 +0100	[thread overview]
Message-ID: <1073398529.2508.92.camel@pegasus> (raw)
In-Reply-To: <1073397739.8735.243.camel@saag>

Hi Edd,

> > maybe the P800 is buggy. Run a second dund on channel 1 to see if it
> > connects.
> 
> Well, that worked once or twice!  Now  we're back to the problem of
> being stalled at this stage...
> 
> > ACL data: handle 0x0029 flags 0x02 dlen 18
>     L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 4
>     MTU 672
> > ACL data: handle 0x0029 flags 0x02 dlen 8
>     L2CAP(d): cid 0x41 len 4 [psm 3]
>       RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> 
> Maybe the P800's just gone crazy :(  Oh well.

I don't think so, because if the ACL link is still connected we should
answer the SABM command. Looks for me like a scheduling bug in our
implementation. You got this with 2.4.23-mh1 and 2.6.0-mh2, right? I
think I had some similar problem, but I can't remember where I got it or
how to reproduce it.

BTW is the P800 so stupid that it searches for the SP record, but
connects back to channel 1. To what channel do you connect on the P800
to trigger the callback.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-01-06 14:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 23:55 [Bluez-users] Release of new BlueZ libs and utils Marcel Holtmann
2003-12-19  0:28 ` Michal Semler (volny.cz)
2003-12-19  9:19   ` Marcel Holtmann
2003-12-19 10:22     ` Michal Semler (volny.cz)
2003-12-20  7:14       ` Charles Bueche
2003-12-20 14:39         ` Marcel Holtmann
2003-12-19 10:15 ` Stephen Crane
2004-01-01 20:39 ` Edd Dumbill
2004-01-02 11:04   ` [Bluez-users] " Marcel Holtmann
2004-01-02 11:09     ` Edd Dumbill
2004-01-02 11:24       ` [Bluez-users] " Marcel Holtmann
2004-01-02 17:18         ` Michal Semler (volny.cz)
2004-01-02 23:35           ` Marcel Holtmann
2004-01-03 19:54             ` Michal Semler (volny.cz)
2004-01-04 10:35               ` Marcel Holtmann
2004-01-03 16:32 ` [Bluez-users] " Edd Dumbill
2004-01-03 16:47   ` Edd Dumbill
2004-01-03 17:10     ` Marcel Holtmann
2004-01-03 18:33       ` Edd Dumbill
2004-01-04 10:38         ` Marcel Holtmann
2004-01-06 11:26           ` Edd Dumbill
2004-01-06 12:37             ` Marcel Holtmann
2004-01-06 13:11               ` Edd Dumbill
2004-01-06 13:20                 ` Marcel Holtmann
2004-01-06 14:02                   ` Edd Dumbill
2004-01-06 14:15                     ` Marcel Holtmann [this message]
2004-01-06 14:30                       ` Edd Dumbill
2004-01-06 14:18                     ` Xavier Garreau
2004-01-06 12:54             ` Xavier Garreau
2004-01-06 13:06               ` Marcel Holtmann

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=1073398529.2508.92.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=edd@usefulinc.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 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.