[Bluez-users] Hci Reset Problem

[Bluez-users] Hci Reset Problem

[Lan Zhang]

Hi, 

I try to setup openobex on my linux, but each time I send out obex
connect request, instead of getting a connect response, the device will
be reset, HCIDUMP is like below:

...
...
...
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 6 pf 1 ilen 0 fcs 0x18
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 6 pf 1 ilen 0 fcs 0x93 credits 33
< ACL data: handle 41 flags 0x02 dlen 34
    L2CAP(d): cid 0x0040 len 30 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 6 pf 0 ilen 26 fcs 0x8f
        OBEX: Connect cmd(f): len 26 version 1.1 flags 0 mtu 1024
        Target (0x46) = Sequence length 16
< HCI Command: Reset (0x03|0x0003) plen 0

The system I have is Linux 2.6.9-34, bluez-lib-2.25 and bluez-util-2.25,
bluez-hcidump-1.30, and openobex-1.0.1 version. I don't know who send
this reset, and why. 

Thanks. 

Lan


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem

[Marcel Holtmann]

Hi Lan,

> I try to setup openobex on my linux, but each time I send out obex
> connect request, instead of getting a connect response, the device will
> be reset, HCIDUMP is like below:
> 
> ...
> ...
> ...
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 8
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): UA: cr 1 dlci 6 pf 1 ilen 0 fcs 0x18
> < ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
>       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> > ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
>       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> < ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
>       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > HCI Event: Number of Completed Packets (0x13) plen 5
> > ACL data: handle 41 flags 0x02 dlen 12
>     L2CAP(d): cid 0x0040 len 8 [psm 3]
>       RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
>       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> < ACL data: handle 41 flags 0x02 dlen 9
>     L2CAP(d): cid 0x0040 len 5 [psm 3]
>       RFCOMM(d): UIH: cr 1 dlci 6 pf 1 ilen 0 fcs 0x93 credits 33
> < ACL data: handle 41 flags 0x02 dlen 34
>     L2CAP(d): cid 0x0040 len 30 [psm 3]
>       RFCOMM(d): UIH: cr 1 dlci 6 pf 0 ilen 26 fcs 0x8f
>         OBEX: Connect cmd(f): len 26 version 1.1 flags 0 mtu 1024
>         Target (0x46) = Sequence length 16
> < HCI Command: Reset (0x03|0x0003) plen 0
> 
> The system I have is Linux 2.6.9-34, bluez-lib-2.25 and bluez-util-2.25,
> bluez-hcidump-1.30, and openobex-1.0.1 version. I don't know who send
> this reset, and why. 

the reset is really strange. It comes from our side. What does
"hciconfig -a" say about your dongle.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem

[Andreas Gaufer]

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

Hi,

I guess I'm approaching the same or at least a related problem. I don't
feel like getting close the root of the problem yet but maybe the
attached output helps marcel or someone else to see clearer.

I can't pretend that the reset in the attached log is not beeing sent from a
user-application but i felt like the oops is worth posting.

Kernel used is 2.6.8.1 but i know that the thing happens also with 2.6.17.6.

Hardware used:

hci1:   Type: USB
        BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8
        HCI 19.2
        Chip version: BlueCore4-ROM
        Max key size: 128 bit
        SCO mapping:  HCI
        BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
                <3-slot packets> <5-slot packets> <encryption> <slot offset> 
                <timing accuracy> <role switch> <hold mode> <sniff mode> 
                <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> 
                <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> 
                <power control> <transparent SCO> <broadcast encrypt> 
                <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> 
                <interlaced iscan> <interlaced pscan> <inquiry with RSSI> 
                <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave> 
                <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL> 
                <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps> 
                <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features> 

I don't expect any feedback on this, I'll post in this thread if I find anything..

Greetings

Andy


On Fri, 28 Jul 2006 03:56:09 +0200
Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Lan,
> 
> > I try to setup openobex on my linux, but each time I send out obex
> > connect request, instead of getting a connect response, the device will
> > be reset, HCIDUMP is like below:
> > 
> > ...
> > ...
> > ...
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > > ACL data: handle 41 flags 0x02 dlen 8
> >     L2CAP(d): cid 0x0040 len 4 [psm 3]
> >       RFCOMM(s): UA: cr 1 dlci 6 pf 1 ilen 0 fcs 0x18
> > < ACL data: handle 41 flags 0x02 dlen 12
> >     L2CAP(d): cid 0x0040 len 8 [psm 3]
> >       RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
> >       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> > > ACL data: handle 41 flags 0x02 dlen 12
> >     L2CAP(d): cid 0x0040 len 8 [psm 3]
> >       RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
> >       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> > < ACL data: handle 41 flags 0x02 dlen 12
> >     L2CAP(d): cid 0x0040 len 8 [psm 3]
> >       RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
> >       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > > ACL data: handle 41 flags 0x02 dlen 12
> >     L2CAP(d): cid 0x0040 len 8 [psm 3]
> >       RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
> >       dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 0
> > < ACL data: handle 41 flags 0x02 dlen 9
> >     L2CAP(d): cid 0x0040 len 5 [psm 3]
> >       RFCOMM(d): UIH: cr 1 dlci 6 pf 1 ilen 0 fcs 0x93 credits 33
> > < ACL data: handle 41 flags 0x02 dlen 34
> >     L2CAP(d): cid 0x0040 len 30 [psm 3]
> >       RFCOMM(d): UIH: cr 1 dlci 6 pf 0 ilen 26 fcs 0x8f
> >         OBEX: Connect cmd(f): len 26 version 1.1 flags 0 mtu 1024
> >         Target (0x46) = Sequence length 16
> > < HCI Command: Reset (0x03|0x0003) plen 0
> > 
> > The system I have is Linux 2.6.9-34, bluez-lib-2.25 and bluez-util-2.25,
> > bluez-hcidump-1.30, and openobex-1.0.1 version. I don't know who send
> > this reset, and why. 
> 
> the reset is really strange. It comes from our side. What does
> "hciconfig -a" say about your dongle.
> 
> Regards
> 
> Marcel
> 
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-- 
-- 
mit freundlichen Grüßen / best regards,

Andreas Gaufer

Office: +49 951-700428-91
Fax: 	+49 951-700428-87
Mail: 	Andreas.Gaufer@bluecellnetworks.com

I fully agree with RFC 1855


[-- Attachment #2: oops_TestHost.txt --]
[-- Type: text/plain, Size: 5642 bytes --]

########### dmesg        ###############

hci_acl_tx_to: hci2 ACL tx timeout
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c015531f
*pde = 00000000
Oops: 0000 [#3]
PREEMPT 
Modules linked in: ftdi_sio usbserial uhci_hcd agpgart cryptoloop loop rfcomm l2cap hci_usb bluetooth 
usbcore tun rtc
CPU:    0
EIP:    0060:[<c015531f>]    Not tainted VLI
EFLAGS: 00010246   (2.6.17.6 #3) 
EIP is at pipe_writev+0xdf/0x3f0
eax: 00000000   ebx: c38ba9e0   ecx: 00000000   edx: 00000000
esi: 00000016   edi: 00000016   ebp: c5972d28   esp: c46a9f18
ds: 007b   es: 007b   ss: 0068
Process sed (pid: 18895, threadinfo=c46a8000 task=c5464ab0)
Stack: c013af4e 00000000 c39a0b7c 00000000 00000000 00000016 00000000 00000000 
       c5972c00 c6464698 c38ba9e0 00000016 b7f81000 c46a9fa4 c0155655 c38ba9e0 
       c46a9f64 00000001 c46a9fa4 b7f81000 00000016 c0149cb8 c38ba9e0 b7f81000 
Call Trace:
 <c013af4e> do_anonymous_page+0x10e/0x140  <c0155655> pipe_write+0x25/0x30
 <c0149cb8> vfs_write+0x88/0x120  <c0149dfb> sys_write+0x3b/0x70
 <c0102d87> syscall_call+0x7/0xb 
Code: 0f 84 d5 00 00 00 03 42 0c 48 83 e0 0f 6b c0 14 8d 6c 10 10 8b 4d 0c 89 4c 24 10 8b 45 08 89 44 24 0c 
8b 55 04 01 d0 89 44 24 0c <83> 39 00 0f 84 a7 00 00 00 01 f8 3d 00 10 00 00 0f 87 9a 00 00 
EIP: [<c015531f>] pipe_writev+0xdf/0x3f0 SS:ESP 0068:c46a9f18
 <6>usb 1-1.3: configuration #1 chosen from 1 choice
hub 1-1:1.0: port 4 disabled by hub (EMI?), re-enabling...
usb 1-1.4: USB disconnect, address 18
usb 1-1.4: new full speed USB device using uhci_hcd and address 21
usb 1-1.4: configuration #1 chosen from 1 choice
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c015531f
*pde = 00000000
Oops: 0000 [#4]
PREEMPT 
Modules linked in: ftdi_sio usbserial uhci_hcd agpgart cryptoloop loop rfcomm l2cap hci_usb bluetooth 
usbcore tun rtc
CPU:    0
EIP:    0060:[<c015531f>]    Not tainted VLI
EFLAGS: 00010246   (2.6.17.6 #3) 
EIP is at pipe_writev+0xdf/0x3f0
eax: 00000000   ebx: c11834a0   ecx: 00000000   edx: 00000000
esi: 00000016   edi: 00000016   ebp: c4f4c728   esp: c4c37f18
ds: 007b   es: 007b   ss: 0068
Process sed (pid: 19026, threadinfo=c4c36000 task=c1155ad0)
Stack: c013af4e 00000000 c51d3b7c 00000000 00000000 00000016 00000000 00000000 
       c4f4c600 c6df3344 c11834a0 00000016 b7f72000 c4c37fa4 c0155655 c11834a0 
       c4c37f64 00000001 c4c37fa4 b7f72000 00000016 c0149cb8 c11834a0 b7f72000 
Call Trace:
 <c013af4e> do_anonymous_page+0x10e/0x140  <c0155655> pipe_write+0x25/0x30
 <c0149cb8> vfs_write+0x88/0x120  <c0149dfb> sys_write+0x3b/0x70
 <c0102d87> syscall_call+0x7/0xb 
Code: 0f 84 d5 00 00 00 03 42 0c 48 83 e0 0f 6b c0 14 8d 6c 10 10 8b 4d 0c 89 4c 24 10 8b 45 08 89 44 24 0c 
8b 55 04 01 d0 89 44 24 0c <83> 39 00 0f 84 a7 00 00 00 01 f8 3d 00 10 00 00 0f 87 9a 00 00 
EIP: [<c015531f>] pipe_writev+0xdf/0x3f0 SS:ESP 0068:c4c37f18


########### In the Shell ###############


< ACL data: handle 48 flags 0x02 dlen 339
    L2CAP(d): cid 0x03a1 len 335 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 12 pf 0 ilen 330 fcs 0x4f 
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
< HCI Command: Reset (0x03|0x0003) plen 0
Receive failed: Broken pipe
root@TestHost:~# 
Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: PREEMPT 

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: EIP is at pipe_writev+0xdf/0x3f0

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: Oops: 0000 [#1]

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: CPU:    0

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: eax: 00000000   ebx: c3d96da0   ecx: 00000000   edx: 00000000

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: esi: 00000016   edi: 00000016   ebp: c5972928   esp: c2d71f18

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: Process sed (pid: 18063, threadinfo=c2d70000 task=c3b495d0)

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: Stack: c013af4e 00000000 c4050b7c 00000000 00000000 00000016 00000000 000000
00 

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel:        c5972800 c6eb2228 c3d96da0 00000016 b7f8a000 c2d71fa4 c0155655 c3d96d
a0 

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel:        c2d71f64 00000001 c2d71fa4 b7f8a000 00000016 c0149cb8 c3d96da0 b7f8a0
00 

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: Call Trace:

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel:  <c013af4e> do_anonymous_page+0x10e/0x140  <c0155655> pipe_write+0x25/0x30

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel:  <c0149cb8> vfs_write+0x88/0x120  <c0149dfb> sys_write+0x3b/0x70

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel:  <c0102d87> syscall_call+0x7/0xb 

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: Code: 0f 84 d5 00 00 00 03 42 0c 48 83 e0 0f 6b c0 14 8d 6c 10 10 8b 4d 0c 8
9 4c 24 10 8b 45 08 89 44 24 0c 8b 55 04 01 d0 89 44 24 0c <83> 39 00 0f 84 a7 00 00 00 01 f8
 3d 00 10 00 00 0f 87 9a 00 00 

Message from syslogd@TestHost at Fri Jul 28 12:05:41 2006 ...
TestHost kernel: EIP: [<c015531f>] pipe_writev+0xdf/0x3f0 SS:ESP 0068:c2d71f18


[-- Attachment #3: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem

[Andreas Gaufer]

Hi,

I have evidence that this may be caused by the usb-part of these devices
(B-Speech, Model: DataSpeed). Other devices (Level One, MDU-0025USB)
don't show this problem on first sight. Both use BlueCore04, HCI 19.2.

The tests where run using USB 2 Hub with 4 bt-devices pumping obex
traffic at max possible speed and this Host Controller:

00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1e) (prog-if 00 [UH=
CI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        Flags: bus master, medium devsel, latency 32, IRQ 12
        I/O ports at d400 [size=3D32]
        Capabilities: [80] Power Management version 2

## dmesg ##
hub 1-1:1.0: port 2 disabled by hub (EMI?), re-enabling...
usb 1-1.2: USB disconnect, address 31
usb 1-1.2: new full speed USB device using address 34
hub 1-1:1.0: port 3 disabled by hub (EMI?), re-enabling...
usb 1-1.3: USB disconnect, address 32
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: cannot reset port 3 (err =3D -71)
hub 1-1:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 3 (err =3D -71)
hub 1-1:1.0: cannot disable port 3 (err =3D -71)
hub 1-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 1-1: USB disconnect, address 29
usb 1-1.1: USB disconnect, address 30
usb 1-1.2: USB disconnect, address 34
usb 1-1.4: USB disconnect, address 33
usb 1-1: new full speed USB device using address 37
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new full speed USB device using address 38

Do you want one of these for your "nightmare chamber" marcel? ;)

Lan, can you check your dmesg/syslog for usb related problems please.

Greetings

Andy

On Fri, 28 Jul 2006 12:37:24 +0200
Andreas Gaufer <Andreas.Gaufer@bluecellnetworks.com> wrote:

> Hi,
> =

> I guess I'm approaching the same or at least a related problem. I don't
> feel like getting close the root of the problem yet but maybe the
> attached output helps marcel or someone else to see clearer.
> =

> I can't pretend that the reset in the attached log is not beeing sent fro=
m a
> user-application but i felt like the oops is worth posting.
> =

> Kernel used is 2.6.8.1 but i know that the thing happens also with 2.6.17=
.6.
> =

> Hardware used:
> =

> hci1:   Type: USB
>         BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8
>         HCI 19.2
>         Chip version: BlueCore4-ROM
>         Max key size: 128 bit
>         SCO mapping:  HCI
>         BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8
>         Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
>                 <3-slot packets> <5-slot packets> <encryption> <slot offs=
et> =

>                 <timing accuracy> <role switch> <hold mode> <sniff mode> =

>                 <park state> <RSSI> <channel quality> <SCO link> <HV2 pac=
kets> =

>                 <HV3 packets> <u-law log> <A-law log> <CVSD> <paging sche=
me> =

>                 <power control> <transparent SCO> <broadcast encrypt> =

>                 <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> =

>                 <interlaced iscan> <interlaced pscan> <inquiry with RSSI> =

>                 <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slav=
e> =

>                 <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL> =

>                 <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps> =

>                 <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features> =

> =

> I don't expect any feedback on this, I'll post in this thread if I find a=
nything..
> =

> Greetings
> =

> Andy
> =

> =


-- =

mit freundlichen Gr=FC=DFen / best regards,

Andreas Gaufer

Office: +49 951-700428-91
Fax: 	+49 951-700428-87
Mail: 	Andreas.Gaufer@bluecellnetworks.com

I fully agree with RFC 1855


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem

[Lan Zhang]

Hi, Marcel: 

Here is the hciconfig result. 

hci0:	Type: USB
	BD Address: 00:0F:3D:49:05:13 ACL MTU: 192:8  SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:179 acl:0 sco:0 events:26 errors:0
	TX bytes:846 acl:0 sco:0 commands:25 errors:0
	Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF PARK 
	Link mode: SLAVE ACCEPT 
	Name: 'BlueZ (0)'
	Class: 0x3e0100
	Service Classes: Networking, Rendering, Capturing, Object
Transfer, Audio
	Device Class: Computer, Uncategorized
	HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
0x20d
	Manufacturer: Cambridge Silicon Radio (10)


Andy, below is the syslog, I believe the USB disconnect happens after
obexopen. Thanks. 

Jul 27 11:43:14 wsp171944wss kernel: Bluetooth: Core ver 2.6
Jul 27 11:43:14 wsp171944wss kernel: NET: Registered protocol family 31
Jul 27 11:43:14 wsp171944wss kernel: Bluetooth: HCI device and
connection manager initialized
Jul 27 11:43:14 wsp171944wss kernel: Bluetooth: HCI socket layer
initialized
Jul 27 11:43:14 wsp171944wss kernel: Bluetooth: HCI USB driver ver 2.7
Jul 27 11:43:14 wsp171944wss kernel: usbcore: registered new driver
hci_usb
Jul 27 11:43:21 wsp171944wss hcid[5812]: Bluetooth HCI daemon
Jul 27 11:43:21 wsp171944wss bluetooth: hcid startup succeeded
Jul 27 11:43:21 wsp171944wss bluetooth: sdpd startup succeeded
Jul 27 11:43:21 wsp171944wss kernel: Bluetooth: L2CAP ver 2.4
Jul 27 11:43:21 wsp171944wss kernel: Bluetooth: L2CAP socket layer
initialized
Jul 27 11:43:21 wsp171944wss sdpd[5816]: Bluetooth SDP daemon 
Jul 27 11:43:21 wsp171944wss hcid[5812]: HCI dev 0 up
Jul 27 11:43:21 wsp171944wss hcid[5812]: Starting security manager 0
Jul 27 11:43:22 wsp171944wss kernel: Bluetooth: RFCOMM ver 1.3
Jul 27 11:43:22 wsp171944wss kernel: Bluetooth: RFCOMM socket layer
initialized
Jul 27 11:43:22 wsp171944wss kernel: Bluetooth: RFCOMM TTY layer
initialized
Jul 27 11:43:46 wsp171944wss su(pam_unix)[5853]: session opened for user
root by bryant(uid=500)
Jul 27 11:45:58 wsp171944wss su(pam_unix)[3235]: session closed for user
root
Jul 27 11:47:03 wsp171944wss kernel: usb 1-1: USB disconnect, address 2
Jul 27 11:47:06 wsp171944wss hcid[5812]: HCI dev 0 down
Jul 27 11:47:06 wsp171944wss hcid[5812]: Stoping security manager 0
Jul 27 11:47:06 wsp171944wss hcid[5812]: HCI dev 0 unregistered
Jul 27 11:47:07 wsp171944wss kernel: usb 1-1: new full speed USB device
using address 3
Jul 27 11:47:07 wsp171944wss hcid[5812]: HCI dev 0 registered
Jul 27 11:47:08 wsp171944wss hcid[5812]: HCI dev 0 up
Jul 27 11:47:08 wsp171944wss hcid[5812]: Starting security manager 0
Jul 27 12:01:01 wsp171944wss crond(pam_unix)[6148]: session opened for
user root by (uid=0)
Jul 27 12:01:01 wsp171944wss crond(pam_unix)[6148]: session closed for
user root
Jul 27 13:01:01 wsp171944wss crond(pam_unix)[6152]: session opened for
user root by (uid=0)
Jul 27 13:01:01 wsp171944wss crond(pam_unix)[6152]: session closed for
user root
Jul 27 13:27:04 wsp171944wss kernel: usb 1-1: USB disconnect, address 3
Jul 27 13:27:06 wsp171944wss hcid[5812]: HCI dev 0 down
Jul 27 13:27:06 wsp171944wss hcid[5812]: Stoping security manager 0
Jul 27 13:27:06 wsp171944wss hcid[5812]: HCI dev 0 unregistered
Jul 27 13:27:07 wsp171944wss kernel: usb 1-1: new full speed USB device
using address 4
Jul 27 13:27:07 wsp171944wss hcid[5812]: HCI dev 0 registered
Jul 27 13:27:08 wsp171944wss hcid[5812]: HCI dev 0 up
Jul 27 13:27:08 wsp171944wss hcid[5812]: Starting security manager 0
Jul 27 14:01:01 wsp171944wss crond(pam_unix)[7865]: session opened for
user root by (uid=0)
Jul 27 14:01:01 wsp171944wss crond(pam_unix)[7865]: session closed for
user root
Jul 27 14:42:30 wsp171944wss kernel: hci_acldata_packet: hci0 ACL packet
for unknown connection handle 2
Jul 27 14:42:30 wsp171944wss kernel: hci_acldata_packet: hci0 ACL packet
for unknown connection handle 3
Jul 27 14:42:30 wsp171944wss kernel: hci_acldata_packet: hci0 ACL packet
for unknown connection handle 0
Jul 27 14:42:30 wsp171944wss kernel: usb 1-1: USB disconnect, address 4
Jul 27 14:42:34 wsp171944wss hcid[5812]: HCI dev 0 down
Jul 27 14:42:34 wsp171944wss hcid[5812]: Stoping security manager 0
Jul 27 14:42:34 wsp171944wss hcid[5812]: HCI dev 0 unregistered
Jul 27 14:42:35 wsp171944wss kernel: usb 1-1: new full speed USB device
using address 5
Jul 27 14:42:35 wsp171944wss hcid[5812]: HCI dev 0 registered
Jul 27 14:42:37 wsp171944wss hcid[5812]: HCI dev 0 up
Jul 27 14:42:37 wsp171944wss hcid[5812]: Starting security manager 0
Jul 27 14:42:54 wsp171944wss hcid[14483]: Bluetooth HCI daemon
Jul 27 14:42:54 wsp171944wss hcid[14483]: Starting security manager 0
Jul 27 14:42:54 wsp171944wss bluetooth: hcid startup succeeded
Jul 27 14:42:54 wsp171944wss sdpd[14489]: init_server: binding L2CAP
socket: Address already in use 
Jul 27 14:42:54 wsp171944wss sdpd[14489]: main: Server initialization
failed 
Jul 27 14:42:54 wsp171944wss bluetooth: sdpd startup succeeded
Jul 27 14:45:22 wsp171944wss kernel: usb 1-1: USB disconnect, address 5
Jul 27 14:45:25 wsp171944wss hcid[14483]: HCI dev 0 down
Jul 27 14:45:25 wsp171944wss hcid[14483]: Stoping security manager 0
Jul 27 14:45:25 wsp171944wss hcid[5812]: HCI dev 0 down
Jul 27 14:45:25 wsp171944wss hcid[5812]: Stoping security manager 0
Jul 27 14:45:25 wsp171944wss hcid[14483]: HCI dev 0 unregistered
Jul 27 14:45:25 wsp171944wss hcid[5812]: HCI dev 0 unregistered
Jul 27 14:45:26 wsp171944wss kernel: usb 1-1: new full speed USB device
using address 6
Jul 27 14:45:26 wsp171944wss hcid[14483]: HCI dev 0 registered
Jul 27 14:45:26 wsp171944wss hcid[5812]: HCI dev 0 registered
Jul 27 14:45:27 wsp171944wss hcid[14483]: HCI dev 0 up
Jul 27 14:45:27 wsp171944wss hcid[5812]: HCI dev 0 up
Jul 27 14:45:27 wsp171944wss hcid[14483]: Starting security manager 0
Jul 27 14:45:27 wsp171944wss hcid[5812]: Starting security manager 0
Jul 27 14:50:10 wsp171944wss hcid[14776]: Bluetooth HCI daemon
Jul 27 14:50:10 wsp171944wss hcid[14776]: Starting security manager 0
Jul 27 14:50:10 wsp171944wss bluetooth: hcid startup succeeded
Jul 27 14:50:10 wsp171944wss sdpd[14782]: init_server: binding L2CAP
socket: Address already in use 
Jul 27 14:50:10 wsp171944wss sdpd[14782]: main: Server initialization
failed 
Jul 27 14:50:10 wsp171944wss bluetooth: sdpd startup succeeded
Jul 27 14:52:30 wsp171944wss kernel: usb 1-1: USB disconnect, address 6
Jul 27 14:52:33 wsp171944wss hcid[14776]: HCI dev 0 down
Jul 27 14:52:33 wsp171944wss hcid[14776]: Stoping security manager 0
Jul 27 14:52:33 wsp171944wss hcid[14483]: HCI dev 0 down
Jul 27 14:52:33 wsp171944wss hcid[14483]: Stoping security manager 0
Jul 27 14:52:33 wsp171944wss hcid[5812]: HCI dev 0 down
Jul 27 14:52:33 wsp171944wss hcid[5812]: Stoping security manager 0
Jul 27 14:52:33 wsp171944wss hcid[14776]: HCI dev 0 unregistered
Jul 27 14:52:33 wsp171944wss hcid[14483]: HCI dev 0 unregistered
Jul 27 14:52:33 wsp171944wss hcid[5812]: HCI dev 0 unregistered
Jul 27 14:52:34 wsp171944wss kernel: usb 1-1: new full speed USB device
using address 7
Jul 27 14:52:34 wsp171944wss hcid[14776]: HCI dev 0 registered
Jul 27 14:52:34 wsp171944wss hcid[14483]: HCI dev 0 registered
Jul 27 14:52:35 wsp171944wss hcid[5812]: HCI dev 0 registered
Jul 27 14:52:35 wsp171944wss hcid[14776]: HCI dev 0 up
Jul 27 14:52:35 wsp171944wss hcid[14483]: HCI dev 0 up
Jul 27 14:52:35 wsp171944wss hcid[5812]: HCI dev 0 up
Jul 27 14:52:35 wsp171944wss hcid[14776]: Starting security manager 0
Jul 27 14:52:35 wsp171944wss hcid[14483]: Starting security manager 0
Jul 27 14:52:35 wsp171944wss hcid[5812]: Starting security manager 0
Jul 27 15:01:01 wsp171944wss crond(pam_unix)[15071]: session opened for
user root by (uid=0)
Jul 27 15:01:01 wsp171944wss crond(pam_unix)[15071]: session closed for
user root


Lan

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem

[Lan Zhang]

Hi, Marcel:

I forgot the system we had is using vmware system, and that may cause
the HCI to reset. Anyway, I tested all the BT dongle I had here with a
stang along Linux, I attached result below. I htink you may interested. 

Regards,
Lan


EPSON --- WORK
hci0:   Type: USB
        BD Address: 00:03:7A:2A:CD:D8 ACL MTU: 384:8 SCO MTU: 64:8
        HCI 19.2
        Chip version: BlueCore4-External
        Max key size: 56 bit
        SCO mapping:  HCI
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
                <3-slot packets> <5-slot packets> <encryption> <slot
offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
                <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
scheme>
                <power control> <transparent SCO> <broadcast encrypt>
                <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
                <interlaced iscan> <interlaced pscan> <inquiry with
RSSI>
                <extended SCO> <EV4 packets> <EV5 packets> <AFH cap.
slave>
                <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
                <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>
                <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>

Belkin, linksys, D-link --- WORK
hci0:   Type: USB
        BD Address: 00:0A:3A:55:C3:4C ACL MTU: 192:8 SCO MTU: 64:8
        HCI 16.4
        Chip version: BlueCore02-External
        Max key size: 56 bit
        SCO mapping:  HCI
        Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot
offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
                <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
scheme>
                <transparent SCO>


CNet --- WORK
hci0:   Type: USB
        BD Address: 00:11:F6:02:85:C8 ACL MTU: 120:20 SCO MTU: 64:0
        Unsupported manufacturer
        Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot
offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
                <HV3 packets> <u-law log> <A-law log> <CVSD> <power
control>
                <enhanced iscan> <interlaced iscan> <interlaced pscan>
                <AFH cap. slave> <AFH class. slave> <AFH cap. master>
                <AFH class. master>



AmbiCom --- DIDN'T WORK at all, cannot send out inquire. 
hci0:   Type: USB
        BD Address: 00:0E:A1:32:CA:E1 ACL MTU: 377:10 SCO MTU: 16:0
        Firmware 0.105 / 97
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot
offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <RSSI> <channel quality> <SCO link> <HV2 packets>
                <HV3 packets> <u-law log> <A-law log> <CVSD> <power
control>
                <transparent SCO> <enhanced iscan> <interlaced iscan>
                <interlaced pscan> <AFH cap. slave> <AFH cap. master>

Kensington --- DIDN'T WORK at all. 
hci0:   Type: USB
        BD Address: 00:0C:55:F6:6A:01 ACL MTU: 377:10 SCO MTU: 16:0
        Firmware 0.105 / 101
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot
offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <RSSI> <channel quality> <SCO link> <HV2 packets>
                <HV3 packets> <u-law log> <A-law log> <CVSD> <power
control>
                <transparent SCO> <enhanced iscan> <interlaced iscan>
                <interlaced pscan> <AFH cap. slave> <AFH cap. master>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem - Caused by USB Hub

[Andreas Gaufer]

Hi,

further tests proofed that the problem described here are caused by
the USB-hub used. It seems to be unable to handle the load and just
breaks down. The same operations are working on other (higher quality) hubs.

Watch out for lines like

    usb 1-1: USB disconnect, address 29

in syslog and/or dmesg to check if your problem is similar. Make sure
not to mess with real physical disconnects which produce the same log
output.

I guess the HCI_RESET is issued by bluez after the device comes back on.

Greetings

Andy



On Fri, 28 Jul 2006 13:39:33 +0200
Andreas Gaufer <Andreas.Gaufer@bluecellnetworks.com> wrote:

> Hi,
> 
> I have evidence that this may be caused by the usb-part of these devices
> (B-Speech, Model: DataSpeed). Other devices (Level One, MDU-0025USB)
> don't show this problem on first sight. Both use BlueCore04, HCI 19.2.
> 
> The tests where run using USB 2 Hub with 4 bt-devices pumping obex
> traffic at max possible speed and this Host Controller:
> 
> 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1e) (prog-if 00 [UHCI])
>         Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
>         Flags: bus master, medium devsel, latency 32, IRQ 12
>         I/O ports at d400 [size=32]
>         Capabilities: [80] Power Management version 2
> 
> ## dmesg ##
> hub 1-1:1.0: port 2 disabled by hub (EMI?), re-enabling...
> usb 1-1.2: USB disconnect, address 31
> usb 1-1.2: new full speed USB device using address 34
> hub 1-1:1.0: port 3 disabled by hub (EMI?), re-enabling...
> usb 1-1.3: USB disconnect, address 32
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
> hub 1-1:1.0: cannot disable port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: cannot reset port 3 (err = -71)
> hub 1-1:1.0: Cannot enable port 3.  Maybe the USB cable is bad?
> hub 1-1:1.0: cannot disable port 3 (err = -71)
> hub 1-1:1.0: cannot disable port 3 (err = -71)
> hub 1-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
> usb 1-1: USB disconnect, address 29
> usb 1-1.1: USB disconnect, address 30
> usb 1-1.2: USB disconnect, address 34
> usb 1-1.4: USB disconnect, address 33
> usb 1-1: new full speed USB device using address 37
> hub 1-1:1.0: USB hub found
> hub 1-1:1.0: 4 ports detected
> usb 1-1.1: new full speed USB device using address 38
> 
> Do you want one of these for your "nightmare chamber" marcel? ;)
> 
> Lan, can you check your dmesg/syslog for usb related problems please.
> 
> Greetings
> 
> Andy
> 
> On Fri, 28 Jul 2006 12:37:24 +0200
> Andreas Gaufer <Andreas.Gaufer@bluecellnetworks.com> wrote:
> 
> > Hi,
> > 
> > I guess I'm approaching the same or at least a related problem. I don't
> > feel like getting close the root of the problem yet but maybe the
> > attached output helps marcel or someone else to see clearer.
> > 
> > I can't pretend that the reset in the attached log is not beeing sent from a
> > user-application but i felt like the oops is worth posting.
> > 
> > Kernel used is 2.6.8.1 but i know that the thing happens also with 2.6.17.6.
> > 
> > Hardware used:
> > 
> > hci1:   Type: USB
> >         BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8
> >         HCI 19.2
> >         Chip version: BlueCore4-ROM
> >         Max key size: 128 bit
> >         SCO mapping:  HCI
> >         BD Address: 00:02:5B:00:BF:66 ACL MTU: 384:8 SCO MTU: 64:8
> >         Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
> >                 <3-slot packets> <5-slot packets> <encryption> <slot offset> 
> >                 <timing accuracy> <role switch> <hold mode> <sniff mode> 
> >                 <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> 
> >                 <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> 
> >                 <power control> <transparent SCO> <broadcast encrypt> 
> >                 <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> 
> >                 <interlaced iscan> <interlaced pscan> <inquiry with RSSI> 
> >                 <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave> 
> >                 <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL> 
> >                 <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps> 
> >                 <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features> 
> > 
> > I don't expect any feedback on this, I'll post in this thread if I find anything..
> > 
> > Greetings
> > 
> > Andy
> > 
> > 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem - Caused by USB Hub

[Marcel Holtmann]

Hi Andreas,

> further tests proofed that the problem described here are caused by
> the USB-hub used. It seems to be unable to handle the load and just
> breaks down. The same operations are working on other (higher quality) hubs.
> 
> Watch out for lines like
> 
>     usb 1-1: USB disconnect, address 29
> 
> in syslog and/or dmesg to check if your problem is similar. Make sure
> not to mess with real physical disconnects which produce the same log
> output.

does this also happens if you load the hci_usb driver with "isoc=0" to
disable all ISOC transfers.

> I guess the HCI_RESET is issued by bluez after the device comes back on.

This could be the case.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem - Caused by USB Hub

[Andreas Gaufer]

On Mon, 31 Jul 2006 20:19:40 +0200
Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Andreas,
Hi Marcel,

> 
> > further tests proofed that the problem described here are caused by
> > the USB-hub used. It seems to be unable to handle the load and just
> > breaks down. The same operations are working on other (higher quality) hubs.
> > 
> > Watch out for lines like
> > 
> >     usb 1-1: USB disconnect, address 29
> > 
> > in syslog and/or dmesg to check if your problem is similar. Make sure
> > not to mess with real physical disconnects which produce the same log
> > output.
> 
> does this also happens if you load the hci_usb driver with "isoc=0" to
> disable all ISOC transfers.
> 

Confuses me a bit... my kernel (2.6.8.1) says:  kernel: hci_usb: Unknown parameter `isoc'
my modinfo -p hci_usb says: "nothing".

> > I guess the HCI_RESET is issued by bluez after the device comes back on.
> 
> This could be the case.
> 
> Regards
> 
> Marcel
> 
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hci Reset Problem - Caused by USB Hub

[Marcel Holtmann]

Hi Andreas,

> > > further tests proofed that the problem described here are caused by
> > > the USB-hub used. It seems to be unable to handle the load and just
> > > breaks down. The same operations are working on other (higher quality) hubs.
> > > 
> > > Watch out for lines like
> > > 
> > >     usb 1-1: USB disconnect, address 29
> > > 
> > > in syslog and/or dmesg to check if your problem is similar. Make sure
> > > not to mess with real physical disconnects which produce the same log
> > > output.
> > 
> > does this also happens if you load the hci_usb driver with "isoc=0" to
> > disable all ISOC transfers.
> > 
> 
> Confuses me a bit... my kernel (2.6.8.1) says:  kernel: hci_usb: Unknown parameter `isoc'
> my modinfo -p hci_usb says: "nothing".

this is a fairly old kernel. This also means that this can be a bug in
the USB subsystem. Move to the latest 2.6.17 or even 2.6.18-rc3 kernel.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users