Bug 783715
| Summary: | Running bluetooth.service makes soft blocked wifi be hard blocked after resume from suspend | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aleksandra Fedorova <alpha> | ||||||||||||||||
| Component: | pm-utils | Assignee: | Jaroslav Škarvada <jskarvad> | ||||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 16 | CC: | extras-orphan, hughsient, jskarvad, notting, pknirsch | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2013-02-14 01:23:40 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: |
|
||||||||||||||||||
|
Description
Aleksandra Fedorova
2012-01-21 23:54:31 UTC
Created attachment 556725 [details]
dmesg
Created attachment 556726 [details]
lsmod
Created attachment 556727 [details]
lspci -k
How the bluetooth dependency was found: as a workaround I tried the following: # echo "SUSPEND_MODULES=rfkill" >> /etc/pm/config.d/rfkill but then /var/log/pm-suspend.log showed that rfkill depends on bnep module, which cannot be unloaded: Unloading kernel module rfkill...FATAL: Module bnep is in use. /usr/lib64/pm-utils/functions: line 89: log: command not found FATAL: Module bnep is in use. /usr/lib64/pm-utils/functions: line 89: log: command not found Failed. Then, while I was looking for the way how to unload bnep module, I disabled bluetooth.service, and everything started to work _without_ "SUSPEND_MODULES=rfkill" config option. Created attachment 556728 [details]
pm-suspend.log - bluetooth is running, default pm options
Softblocked wifi becomes hardblocked
Created attachment 556730 [details]
pm-suspend.log - bluetooth is stopped, default pm options
This suspend is made directly after previous broken one but with bluetooth stopped. As a result: Wifi is unblocked, and everything works.
P.S. And sorry for flooding the bug with comments. I am not sure which info might be useful here.
Could you resolve your issue by disabling the bluetooth pm-utils hook? i.e.: # echo 'HOOK_BLACKLIST="49bluetooth"' > /etc/pm/config.d/bluetooth.conf If it doesn't help, re-enable the hook by: # rm /etc/pm/config.d/bluetooth.conf Sorru it took so long to answer. It seems I was wrong with my initial assumption about bluetooth involved. I participated in Power Management testday and retested the problem with current Fedora Beta 17 rc3 image. The reproducible sequence is as follows: 1) boot - wireless device is enabled and recognizes several wifi networks 2) switch wireless of using the switch in NetworkManager interface in gnome-shell 3) suspend 4) resume 5) try to switch the wireless device on in NM interface. The switch changes to "hardware disabled" label 6) suspend 7) resume 8) and wireless device is working again and shows the wireless networks. Thus, if wireless device was switched off before suspend it can not be switched on after resume. You have to switch it on and then perform additional suspend/resume step to make it work. Tested with pm-utils-1.4.1-18.fc17.x86_64 Smolt: http://www.smolts.org/client/show/pub_7008de12-54c3-4060-a250-6d62023a83f9 Created attachment 575505 [details]
pm-test-day-bugreport
Output of pm bugreport tool after the suspend/resume with wireless switched off.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |