Bug 227893
| Summary: | Kernel oops -- Bluetooth subsystem hangs -- backtrace available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Vismor <tvismor> | ||||||
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rawhide | CC: | davej, dwmw2, rh_bugzilla, wtogami | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2007-05-18 15:56:15 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 150226 | ||||||||
| Attachments: |
|
||||||||
|
Description
Tim Vismor
2007-02-08 20:20:19 UTC
One further observation. I have been using this same hardware (Kensington dongle and mouse) on a Thinkpad T43 that has been tracking Rawhide for the last 18 months. This is the first time I've seen this problem (or had any problem with the Bluetooth mouse). A good bug report, but... I'll keep it in NEW state for now. I suspect that the generic HID caused it. Just in case, please attach /proc/bus/usb/devices. I'd like to see it. Created attachment 147912 [details]
/proc/bus/usb/devices before oops occurs
I have attached a copy of /proc/bus/usb/devices immediately after boot up
(before the oops) occurs and will also attach a copy of the file from a couple
of days after the oops. There was no change in hardware attached to the
machine.
Created attachment 147913 [details]
/proc/bus/usb/devices a couple of days after the oops
I actually diff'ed these two files and realized that there is virtually no difference between "before" and "after" instances except for some of the device numbers. To avoid any misunderstanding about this, let me state that the procedure I used to get these files was to print the usb devices from a system with a hung mouse, reboot the system, then print the usb devices from a system with a working Bluetooth mouse. Hence, there was a reboot in the interval between the two usb device snapshots. Marcel, are you interested? Drop off cc: if not. *** Bug 231601 has been marked as a duplicate of this bug. *** *** Bug 229096 has been marked as a duplicate of this bug. *** For now I'm running with this patch to prevent my laptop from constantly
crashing. Why _did_ we enable CONFIG_SYSFS_DEPRECATED anyway? We should have
bugs filed for any userspace which requires it.
--- linux-2.6.20.ppc/drivers/base/class.c~ 2007-03-11 15:35:12.000000000 +0100
+++ linux-2.6.20.ppc/drivers/base/class.c 2007-03-11 16:56:58.000000000 +0100
@@ -379,7 +379,7 @@ static int deprecated_class_uevent(char
struct device *dev = class_dev->dev;
char *path;
- if (!dev)
+ if (1 || !dev)
return 0;
/* add device, backing this class device (deprecated) */
Applied this change to 2.6.20-1.2985.fc7 and it solves the issue described in Bug 229096. But with this change bluetoothd-serv eats more than 90% of CPU and won't come down unless I stop the bluetooth service which is off course not a solution. Also when hidd is started it always spits out "Starting hidd: Can't listen on HID control channel: Address already in use". The mouse does work correctly though. FYI. System has been running for several days now with Bluetooth USB dongle plugged in/Bluetooth mouse active and no oop's. Currently running kernel 2.6.20-1.3045.fc7. Yeah, we have a hack which works around the problem. |