Bug 102061
Summary: | 4.1 panics intermittently if BT mouse is connected via intel 7260 Wifi/BT combo and then disconnected | ||
---|---|---|---|
Product: | Drivers | Reporter: | Anton Gubarkov (anton.gubarkov) |
Component: | Bluetooth | Assignee: | linux-bluetooth (linux-bluetooth) |
Status: | ASSIGNED --- | ||
Severity: | high | CC: | aaron.lu |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
URL: | https://bugs.gentoo.org/show_bug.cgi?id=552920 | ||
Kernel Version: | 4.1 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
Anton Gubarkov
2015-07-27 21:18:29 UTC
As it is a regression, v4.0.6 works ok, v4.1 doesn't, I tried a bisect between them. The problem is masked by another regression fixed with 1f5014d6a77513fa7cefe30eb7791d5856c04384. A lot of my tests ended with non-funcioning bt mouse. So I attempted a second bisect between v4.0.6 and 1f5014d6a77513fa7cefe30eb7791d5856c04384. This time I landed on 297d716f6260cc9421d971b124ca196b957ee458. My bt mouse works fine before this commit and my system is stable. When I apply this commit, I get a panic within 30 minutes of the 1st disconnect of my bt mouse, either because it goes standby to save its battery or if I switch it off by a hardware switch. I have no kernel devel experience so I couldn't even dare to look for a possible reason myself, the commit is 10500 lines. Here is my bisect log: r9-008cln linux-stable # git bisect log git bisect start # bad: [5939d9dfe4406a49d8688eb827d88abcaf233c42] power: twl4030_madc_battery: Add missing MODULE_ALIAS git bisect bad 5939d9dfe4406a49d8688eb827d88abcaf233c42 # good: [a0ce889438e8204b87d1f30f941646636e26837e] Linux 4.0.6 git bisect good a0ce889438e8204b87d1f30f941646636e26837e # good: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1 git bisect good c517d838eb7d07bbe9507871fab3931deccff539 # good: [0595439a0a8740f776a0ae367a4c7f243add24ec] power: generic-adc-battery: Fix power_supply_property returned value git bisect good 0595439a0a8740f776a0ae367a4c7f243add24ec # bad: [ed6dad52298152a5c493223234e431f206c5a46b] x86/olpc/xo1/sci: Use newly added power_supply_put API git bisect bad ed6dad52298152a5c493223234e431f206c5a46b # good: [15077fc1f78488169ee5b87f553d17c1afcb1255] power_supply: ab8500: Use power_supply_*() API for accessing function attrs git bisect good 15077fc1f78488169ee5b87f553d17c1afcb1255 # good: [b70229bca127283c3d30e5f471d30b1acccd7096] power_supply: charger-manager: Use power_supply_*() API for accessing function attrs git bisect good b70229bca127283c3d30e5f471d30b1acccd7096 # bad: [1a352462b5377ac68f5955d674b3460c7bac52a3] power_supply: Add power_supply_put for decrementing device reference counter git bisect bad 1a352462b5377ac68f5955d674b3460c7bac52a3 # bad: [297d716f6260cc9421d971b124ca196b957ee458] power_supply: Change ownership from driver to core git bisect bad 297d716f6260cc9421d971b124ca196b957ee458 # first bad commit: [297d716f6260cc9421d971b124ca196b957ee458] power_supply: Change ownership from driver to core Drivers/bluetooth seems to be a better place for this bug. It seems that 4.2 works ok. I continue testing this newest kernel will report back. |