Re: Any update on software caused connection abort issue??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Any update on software caused connection abort issue
>
>
>
>>On Wed, Jun 23, 2010 at 12:48 AM, john michelle <jhnmichelle@xxxxxxxxx> wrote:
>> Dear Bluetooth community,
>>
>> You are committing version after version and have time to add new
>> Features and the core stack have a major bug (software Caused
>> connection abort) that i
>> Have reported on the 7th of may the problem seems to be either in the
>> usb part of the
>> Kernel or the bluez stack, i am no kernel engineer so i came directly
>> to you for reporting
>> This problem and my requests to look into this problem are just
>> ignored. this is a blocker
>> Issue that would prevent and discourage any one from developing
>> application that rely on
>> Bluez sco capabilities, since during transmission the above mentioned
>> error just occurs.
>> I hope that my voice is heared and i would get a reply from the bluez community.
>>
>> John
>>
>>
>>
>> On Wed, Jun 16, 2010 at 3:11 PM, john michelle <jhnmichelle@xxxxxxxxx> wrote:
>>> On Sun, May 30, 2010 at 1:12 PM, john michelle <jhnmichelle@xxxxxxxxx> wrote:
>>>> Hi Gustavo,
>>>>
>>>>>> Please post the output of hcidump when the connection abort happens.
>>>>>>
>>>>
>>>> Below is the output of hcidump the moments the software caused connection abort
>>>>
>>>> Dongle 1:
>>>>> HCI Event: Number of Completed Packets (0x13) plen 5
>>>>  . * . . .
>>>> < HCI Command: Reset (0x03|0x0003) plen 0
>>>> device: disconnected
>>>>
>>>> Dongle 2:
>>>>> HCI Event: Number of Completed Packets (0x13) plen 5
>>>>  . * . . .
>>>> < HCI Command: Reset (0x03|0x0003) plen 0
>>>> device: disconnected
>>>>
>>>>
>>>> I think something triggers hci reset which causes this problem, but what exactly
>>>> Triggers it i don't know.
>>>>
>>>>
>>>> John
>>>>
>>>>
>>>
>>>
>>> Hi all,
>>>
>>> Is anyone going to give this problem a try, it has been like a month now
>>> This is a real problem in the bluez stack and someone have to look in this
>>> Issue.
>>>
>>> John
>>>
>>>> On Mon, May 17, 2010 at 5:21 PM, john michelle <jhnmichelle@xxxxxxxxx> wrote:
>>>>>> Hi Jonh,
>>>>>>
>>>>>> First of all, don't do top posting in this mailing list. ;)
>>>>>>
>>>>>
>>>>> Thanks for the advise , will keep that in mind for future posts.
>>>>>
>>>>>> In which bluez/kernel version the problem started? Any hardware update
>>>>>> during this time? The problem happens when you are already tranfering
>>>>>> SCO data?
>>>>>>
>>>>>
>>>>> I tried bluez versions 3.XX  and kernel 2.6.26(I think) the problem
>>>>> occurs and the kernel panics with no core dumps.then i tried with
>>>>> bluez 4.53-4.62 with
>>>>> Kernel 2.6.31 and 2.6.32. the connection abort problem occurs but the
>>>>> kernel doesn't
>>>>> Panic. regarding the hardware update you mean the dongle or the box.Anyway
>>>>> i changed both and tried different box's, this even happens on a box
>>>>> with 2 giga ram
>>>>> And core2 processor . as for the dongles i am using trust
>>>>>
>>>>> http://www.twenga.co.uk/prices-Bluetooth-2-USB-Adapter-10m-BT-2250p-TRUST-Wireless-network-card-adapter-176178-0
>>>>>
>>>>>  and also using no name dongles all the same problem.
>>>>>
>>>>>> Please post the output of hcidump when the connection abort happens.
>>>>>>
>>>>>
>>>>> well that is going to be a hard one since i have more than one dongle in place
>>>>> And very hard to predict which one will crash.i will work on this and update
>>>>> You as soon as i have the hcidump log.
>>>>>
>>>>>
>>>>>
>>>>>> I tried reproduce this issue in L2CAP but it is a bit hard, lets
>>>>>> say it happen once in a thousand, so it's not easy to track it. I have
>>>>>> to try reproduce that using the SCO, but I'm not used to that layer yet.
>>>>>> ;)
>>>>>
>>>>> I hoped that it happens 1 in 1000 in SCO , but it actually happens 1 in 15
>>>>>
>>>>>
>>>>> John
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On Fri, May 7, 2010 at 3:53 PM, Gustavo F. Padovan <gustavo@xxxxxxxxxxx> wrote:
>>>>>>> > * john michelle <jhnmichelle@xxxxxxxxx> [2010-05-07 15:49:05 -0400]:
>>>>>>> >
>>>>>>> >> Hi Bluetooth hackers,
>>>>>>> >>
>>>>>>> >> i am having this consistent problem with bluez , from time to time i
>>>>>>> >> get the error Software caused connection abort (103 )
>>>>>>> >> And the bluetooth stick seems to disconnect and reconnects. this
>>>>>>> >> happens during an sco connection and it occurs even
>>>>>>> >> More when i am having the voice stream comming through the internet
>>>>>>> >> rather than the lan.i don't know what exact
>>>>>>> >> Details you need to solve this problem please tell me and i will give
>>>>>>> >> you an immediate reply . i have linux kernel 2.6.33 and bluez 4.62
>>>>>>> >
>>>>>>> > I get the same problem sometimes when testing ERTM with l2test. So the
>>>>>>> > problem is on l2cap too. I didn't have time to debug this yet. Now that
>>>>>>> > someone else have confirmed it too, I'll to take a look at the problem.
>>>>>>> >
>>>>>>> >>
>>>>>>
>>>>>> --
>>>>>> Gustavo F. Padovan
>>>>>> http://padovan.org
>>>>>>
>>>>>
>>>>
>>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux