Created attachment 709219 [details] Crash log Description of problem: When the bluetooth mouse that comes with the laptop is turned off for five seconds then turned back on, the kernel panics and leaves the syste is a mostly hung state. I am running xfce. This also happens at random times. I suspect it's when the bluetooth link fails for some reason and reconnects. Version-Release number of selected component (if applicable): This has been happening on all the kernels I've tried for the last few months. The current kernel version is 3.8.2-206.fc18.x86_64 #1 SMP. How reproducible: Always. Steps to Reproduce: 1. Turn off bluetooth mouse (that was already on and connected). 2. Wait 5 seconds 3. Turn mouse back on 4. Wait a few seconds for the panic Actual results: Kernel panic Expected results: The mouse should reconnect and the computer should not crash. Additional info: The relevant portion of my /var/log/messages file is attached.
Still a problem with kernel 3.8.4-202.fc18.x86_64 #1 SMP.
Hm. For some reason, the device isn't fully being cleaned up when it's disconnected, and it doesn't remove some sysfs entries. Are you still seeing this with 3.9.6 or newer?
It's still there in 3.9.9.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.