Bug 968041

Summary: Both wifi and bluetooth radios get disabled during kernel 3.9.4 boot up
Product: [Fedora] Fedora Reporter: Damian Wrobel <dwrobel>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 02:28:20 UTC Type: Bug
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 Flags
dmesg from 3.9.4-100
none
dmesg from 3.8.13-100 none

Description Damian Wrobel 2013-05-28 20:30:25 UTC
Description of problem:
Both wifi and bluetooth radios get disabled during kernel boot up.

Version-Release number of selected component (if applicable):
kernel-3.9.4-100.fc17.src.rpm

How reproducible:
100%

Steps to Reproduce:
1. Boot the machine using the 3.9.4-100.fc17.i686.PAE kernel

Actual results:
Both wifi and bluetooth are disabled:

rfkill from the kernel 3.9.4-100.fc17.i686.PAE:
0: hp-wifi: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
1: hp-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: no
3: hp-gps: GPS
        Soft blocked: yes
        Hard blocked: yes
4: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

Expected results:
Both wifi and bluetooth should be enabled.

Additional info:

It works without any problems while booting using the 3.8.13-100 kernel.

rfkill from the kernel 3.8.13-100.fc17.i686.PAE boot-up:

0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: hp-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Comment 1 Damian Wrobel 2013-05-28 20:32:16 UTC
Created attachment 754083 [details]
dmesg from 3.9.4-100

Comment 2 Damian Wrobel 2013-05-28 20:32:59 UTC
Created attachment 754084 [details]
dmesg from 3.8.13-100

Comment 3 Damian Wrobel 2013-05-28 20:41:36 UTC
Manually enabling wireless in KDE causes the oops as reported in the bug #968024.

Enabling bluetooth with 'rfkill unblock 1' works without any problem.

[ 2059.778359] Bluetooth: RFCOMM TTY layer initialized
[ 2059.778380] Bluetooth: RFCOMM socket layer initialized
[ 2059.778384] Bluetooth: RFCOMM ver 1.11
[ 2060.340749] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 2060.340765] Bluetooth: HIDP socket layer initialized
[ 2196.661295] hid-generic 0005:046D:B008.0004: unknown main item tag 0x0
[ 2196.661617] input: Bluetooth Laser Travel Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input10
[ 2196.664728] hid-generic 0005:046D:B008.0004: input,hidraw3: BLUETOOTH HID v3.14 Mouse [Bluetooth Laser Travel Mouse] on 00:1e:37:b4:04:99


Once enabled both interfaces works correctly.

Comment 4 Fedora End Of Life 2013-07-03 23:37:44 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 5 Fedora End Of Life 2013-08-01 02:28:25 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.