public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Pierre Lord <jeanplord@videotron.ca>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Connection dropped or cannot connect
Date: Fri, 09 Apr 2004 21:10:27 -0400	[thread overview]
Message-ID: <000801c41e98$9e75d080$0100a8c0@terre> (raw)

[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]

My Linux box has a Anycom usb-220 bluetooth adapter connected to it which is used to serve my iPAQ1940.  Works "superbly great" except those times it won't work at all ;-).  Either a long connection (like a download) will be cut or i will not be able to open a new connection.  When it happens, i have 2 choices: unplung the bluetooth adapter for a few seconds (which requires no other intervention on the software side) and replug it or reset the device using hciconfig.  Except that doing this reset will sometimes crash the hole Linux box.  I then get a stack dump and once i got a message that looked like this: "...killing interrupt handler...".  Sorry i wasn't fast enough to write down the message.

I'm running "Kernel 2.4.24-mh2 on an i586" with bluez-libs-2.5, bluez-sdp-1.5, bluez-utils-2.5.  I normally run hcid, sdpd, "dund --listen --msdun call dun".  It seems to me that enabling authentification and encryption has made the whole thing less reliable.

What can i do to improve reliability?

Thank you

An lsmod shows the following:
Module                  Size  Used by
bnep                    8912   0  (autoclean)
ppdev                   6960   0  (autoclean)
ppp_deflate             3120   0  (autoclean)
zlib_inflate           19648   0  (autoclean) [ppp_deflate]
zlib_deflate           18688   0  (autoclean) [ppp_deflate]
bsd_comp                4416   0  (autoclean)
ppp_async               6544   0  (autoclean)
ppp_generic            16960   0  (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc                    4736   0  (autoclean) [ppp_generic]
crc32                   2848   0  [bnep]
sco                     7936   0  (unused)
hci_usb                 6336   1
usb-ohci               16816   0  (unused)
rfcomm                 29040   1  (autoclean)
l2cap                  15632   2  (autoclean) [bnep rfcomm]
bluez                  28224   3  (autoclean) [bnep sco hci_usb rfcomm l2cap]
ipt_MASQUERADE          1344   1  (autoclean)
ipt_state                576   2  (autoclean)
ip_nat_ftp              2912   0  (unused)
iptable_nat            16592   2  [ipt_MASQUERADE ip_nat_ftp]
ip_conntrack_ftp        3760   1
ip_conntrack           18752   3  [ipt_MASQUERADE ipt_state ip_nat_ftp iptable_nat ip_conntrack_ftp]
iptable_filter          1680   1
ip_tables              12000   6  [ipt_MASQUERADE ipt_state iptable_nat iptable_filter]
3c509                   8304   2
rtc                     6112   0  (autoclean)

[-- Attachment #2: Type: text/html, Size: 5673 bytes --]

             reply	other threads:[~2004-04-10  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  1:10 Jean-Pierre Lord [this message]
2004-04-10 10:28 ` [Bluez-users] Connection dropped or cannot connect Marcel Holtmann
2004-04-16  1:17   ` Jean-Pierre Lord
2004-04-10 20:42 ` Richard Cox
2004-04-10 21:09   ` Marcel Holtmann
2004-04-10 21:15     ` Richard Cox
2004-04-10 21:25       ` Marcel Holtmann
2004-04-10 21:31         ` Richard Cox
2004-04-11 15:38         ` [Bluez-users] Connection dropped or cannot connect (Solved!!!!!!) Richard Cox
2004-04-11 15:46           ` Richard Cox
2004-04-11 16:37             ` Marcel Holtmann
2004-04-11 19:54               ` Richard Cox

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='000801c41e98$9e75d080$0100a8c0@terre' \
    --to=jeanplord@videotron.ca \
    --cc=bluez-users@lists.sourceforge.net \
    /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