| Summary: | sys-kernel/gentoo-sources usb bluetooth dongle spams dmesg to the point of making it useless for debugging other problems (Patch in hand) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ariel Poliak <apoliak> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | hwoarang, luca.santarelli |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://thread.gmane.org/gmane.linux.bluez.devel/15067 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
solution patch - in diff -u format
lsusb -v information about the device causing the problem |
||
|
Description
Ariel Poliak
2007-12-24 00:02:19 UTC
Created attachment 139223 [details, diff]
solution patch - in diff -u format
Are you the author of this patch? I found the information for the fix on a google search. This means other people are also affected. I can't find the original page with the fix info, but the exact same problem is described in Ubuntu's bugtracker (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152689) I manually updated the source file on my system and when it worked, created the patch file. I ran diff -u, so technically I am the author of THIS patch, however it is based on another patch, which I can no longer find. If you are asking if I'm willing to keep the patch working as the kernel is updated and syntaxes change until it is incorporated in the official kernel, the answer is yes... Here's the link to ubuntu's patch. Could not find this on usb-devel list, git repo or lkml or mainline git repo. Not sure why Ubuntu has not submitted this. http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=771d0cc54dc1710c585d3ee29447ddfc92aec440 I emailed the canonical guy at Ubuntu who committed the patch and asked him if he plans on submitting this upstream. Here's his answer, which I think implies that they will not be submitting upstream. ------------------------------------------ Here is the provenance for the fix (which Ossi Berg says he found in the vanilla kernel): https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152689 I have not bothered to check that the patch is already upstream somewhere. rtg ---------------------------------- yes, we should submit this then (with correct author attribution). However, you can't just submit a patch like that, you need a proper description of the issue it solves. So we need Ariel to give us the exact error message first. or at least just to confirm from memory that it looked something like: hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 (In reply to comment #7) > hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 That is in fact the query I put into Google to get to the solution... (In reply to comment #7) > hci_scodata_packet: hci0 SCO packet for unknown connection handle 92 That is in fact the query I put into Google to get to the solution... I no longer have the original error message, as it was logrotated until it got flagged for deletion, and I patched my kernel, so the problem no longer occurs (at least until the next time I emerge gentoo-sources), but I am 100% sure that was the error message that flooded dmesg. submitted upstream no response after 2 weeks: sent again patch added to -mm Please attach the "lsusb -v" output for this device Also please post the output of "hciconfig hci0 version" from when this device is up and running Don't worry about the above info now. someone else provided it and a final patch is going upstream Sorry for dropping off the face of the earth. I just went through three weeks of midterm exams, several homework programming projects, and a catastrophic system failure on one of my other systems. I have not booted Gentoo since I started studying for those midterms (if I did, I would have spent all the time emerging stuff and messing with it, and would not have studied at all -- same reason why I left Portal at home before Finals Week last semester...) Anyway, I'm in Spring Break now, and being I'm under 21 (1 month and change left), there's not a whole lot to do, so I'll do the digging around for that information, even if it is not completely necessary, but at least for archival and completeness-of-information purposes. I'll post that information sometime this week. Once Again, sorry for the delay in replying. Fixed in gentoo-sources-2.6.24-r4 (genpatches-2.6.24-5) Now it hasnt been fixed. I still have the same problem. I ll try to apply the patch *** Bug 230854 has been marked as a duplicate of this bug. *** Nope patch doesnt work I am using 2.6.25-gentoo-r6 kernel Created attachment 159630 [details]
lsusb -v information about the device causing the problem
(In reply to comment #18) > Now it hasnt been fixed. I still have the same problem. I ll try to apply the > patch I second Markos' comment. It (still) doesn't work on 2.6.26-gentoo-r3. Shouldn't this mean a "REOPEN BUG"? As a side note, after I start the service, /etc/init.d/bluetooth reports "crashed" as status and I can't find any device to pair, but adding the term "bluetooth" to a forum search is the same as adding "*" :-( On a dual booting Windows XP the dongle works fine, pairs with devices and transfers files. Where should I search for informations? I'm using bluez* as per x86 tree (so 2.x) From what I understand this is not a Gentoo specific bug but an upstream one. Im not sure about that thought. Look at /var/log/messages for the error output (In reply to comment #23) > From what I understand this is not a Gentoo specific bug but an upstream one. > Im not sure about that thought. Look at /var/log/messages for the error output I've dug a bit and yes, it's an upstream bug. I've fixed it for our dongle (we have the same one), it's a single line of code in drivers/bluetooth/hci_usb.c which needs to be modified. As soon as I understand how to make a proper email to upstream, I'll send it asking for inclusion. Regarding the BlueZ issue, going ~x86 fixed the crash, now bluetooth is working. Could you please post here the changes you made on that file? Thanks :) This bug has to be "fixed" seperately for each broken device that is in existence. We fixed it for Ariel's device but there are probably other (broken devices) like yours in the wild. Please open new bug reports. Also, just because it is an upstream bug doesn't mean you should avoid posting it here. We need to fix our kernel as well as upstream. (In reply to comment #26) > Also, just because it is an upstream bug doesn't mean you should avoid posting > it here. We need to fix our kernel as well as upstream. Daniel, thanks for your kind answer. I have opened a new bug, attaching the patch I made (Markos, you can grab the patch and apply it). It's here: http://bugs.gentoo.org/show_bug.cgi?id=249523 If you're kind enough to point me to the right way to submit a patch upstream, I'll gladly do it myself (first kernel patch in my life, I'm kind of moved). I heard about people who sign your patch, but I don't know much more... |
