Bug 562502
| Summary: | btusb regression | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Carlos Romero <kcrashcore> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, sgruszka | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-27 14:54:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Hi Carlos (In reply to comment #0) > Created an attachment (id=389334) [details] > 2.6.31.12-174.2.3.fc12 and 2.6.32.7-37.fc12 > > Description of problem: bluetooth mouse crashes Xorg Does Xorg really crash because of that? If so, this bug should be against Xorg. > How reproducible: > using a bluetooth mouse I get thousands of these kernel errors - > btusb_bulk_complete: hci0 urb ffff8800b06d70c0 failed to resubmit (1) > btusb_intr_complete: hci0 urb ffff8800b06d7840 failed to resubmit (1) Does this workaround helps: https://bugzilla.redhat.com/show_bug.cgi?id=570291#c13 > The problem mostly manifested in mouse events being trapped in a window or > button not being active in f12 kernel .32* until mouse was switched off. > switching kernel/xorg/firefox to rawhide caused even more pronounced errors > like radeon r600 rendering gliches, stalling, menus locking up firefox, and not > being able to open more windows. Huh, perhaps except autosuspend we have another problem in btusb, that make this gliches. > and this added to compile for kernel-2.6.33-0.27.rc6.git1.fc13.x86_64 > @@ -1068,7 +1067,7 @@ > return 0; > > spin_lock_irq(&data->txlock); > - if (!(interface_to_usbdev(intf)->auto_pm && data->tx_in_flight)) { > + if (!((message.event & PM_EVENT_AUTO) && data->tx_in_flight)) { > set_bit(BTUSB_SUSPENDING, &data->flags); > spin_unlock_irq(&data->txlock); > } else { I'm a bit confusing, this patch is only for fix compilation right? that workaround for the most part works, but every now and then the mouse still goes odd, probably missed a hid packet, and needs to be reset. That patch only got rid of the error messages, but the mouse still went odd alot more often than it is doing now. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 389334 [details] 2.6.31.12-174.2.3.fc12 and 2.6.32.7-37.fc12 Description of problem: bluetooth mouse crashes Xorg Version-Release number of selected component (if applicable): kernel-2.6.32.7-37.fc12.x86_64 - kernel-2.6.33-0.27.rc6.git1.fc13.x86_64 How reproducible: using a bluetooth mouse I get thousands of these kernel errors - btusb_bulk_complete: hci0 urb ffff8800b06d70c0 failed to resubmit (1) btusb_intr_complete: hci0 urb ffff8800b06d7840 failed to resubmit (1) The problem mostly manifested in mouse events being trapped in a window or button not being active in f12 kernel .32* until mouse was switched off. switching kernel/xorg/firefox to rawhide caused even more pronounced errors like radeon r600 rendering gliches, stalling, menus locking up firefox, and not being able to open more windows. Additional info: built just the btusb.c module from kernel-2.6.31.12-174.2.3.fc12 source and used it to replace the ko from the newer kernels and have had none of those xorg glitches or kernel messages. Attached is the diff that causes the errors between kernel-2.6.31.12-174.2.3.fc12 and kernel-2.6.32.7-37.fc12 and this added to compile for kernel-2.6.33-0.27.rc6.git1.fc13.x86_64 @@ -1068,7 +1067,7 @@ return 0; spin_lock_irq(&data->txlock); - if (!(interface_to_usbdev(intf)->auto_pm && data->tx_in_flight)) { + if (!((message.event & PM_EVENT_AUTO) && data->tx_in_flight)) { set_bit(BTUSB_SUSPENDING, &data->flags); spin_unlock_irq(&data->txlock); } else {