From: nirav rabara <niravrabara@gmail.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Kernel panic when SCO connection
Date: Wed, 3 Feb 2010 10:21:13 +0530 [thread overview]
Message-ID: <912bb79a1002022051o1faf229en95605084fa0e380b@mail.gmail.com> (raw)
In-Reply-To: <20100202171612.GA7034@vigoh>
- Show quoted text -
On Tue, Feb 2, 2010 at 10:46 PM, Gustavo F. Padovan
<padovan@profusion.mobi> wrote:
> Hi Nirav,
>
> * nirav rabara <niravrabara@gmail.com> [2010-02-02 22:28:53 +0530]:
>
>> Hi,
>> When I try to connect SCO socket, Kernel getting crash.
>> Linux kernel - 2.6.22
>> Bluez - 4.58
>
> Please try a 2.6.33 kernel and tell us if the bug still happens.
>
>>
>> error message,
>> __tx_submit:hci0 tx submit failed urb c0552c14 type 3 err -19
>>
>> sometimes in connection is showing error while connection as below,
>> hci_acldata_packet:hci0 ACL packet data for unknown connection handler 2
>>
>> It would be really appreciable if somebody put some on light on this
>> issue, OR suggest me any patch or documentation.
>>
>> --
>> With Regards,
>> Nirav Rabara
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> Gustavo F. Padovan
> http://padovan.org
>
> ProFUSION embedded systems - http://profusion.mobi
>
Hi Gustavo,
Thanks for your suggestion, but I am using bluez 4.58 on ATMEL
AT91SAM9263, no patch available for the newer kernel 2.6.33 . Patches
related to my board only available up to 2.6.30.
It would be a great help if suggest me any alternet for this issue. OR
any patches for the same problem as i mentioned for 2.6.22.
--
With Regards,
Nirav Rabara
next prev parent reply other threads:[~2010-02-03 4:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 16:58 Kernel panic when SCO connection nirav rabara
2010-02-02 17:16 ` Gustavo F. Padovan
2010-02-02 22:01 ` Ahmed Ragab
2010-02-04 5:56 ` nirav rabara
2010-02-04 15:26 ` Ahmed Ragab
2010-02-03 4:51 ` nirav rabara [this message]
2010-02-04 11:36 ` SINGH DEVENDRA-DHGW76
2010-02-04 14:11 ` Marcel Holtmann
2010-02-05 13:51 ` SINGH DEVENDRA-DHGW76
2010-02-05 14:57 ` Marcel Holtmann
2010-02-04 20:06 ` Ahmed Ragab
2010-02-05 4:31 ` SINGH DEVENDRA-DHGW76
[not found] ` <f97b2b971002042037j5397ef4j7ceb0521ef12e082@mail.gmail.com>
2010-02-05 4:41 ` Ahmed Ragab
2010-02-05 13:45 ` SINGH DEVENDRA-DHGW76
2010-02-08 17:23 ` nirav rabara
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=912bb79a1002022051o1faf229en95605084fa0e380b@mail.gmail.com \
--to=niravrabara@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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;
as well as URLs for NNTP newsgroup(s).