kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #08784
[Bug 1214059] Re: Wifi and bluetooth disabled at boot and hard to re-enable
3.11.0-* (starting from 3.11.0-0) -> not ok, see bug description
3.10.0-* -> ok but wifi is *sometime* turned off at boot (I have to check "Enable Wifi network" in NM)
In this case I see a "RF_KILL bit toggled to disable radio" in dmesg with no visible error.
The fact that this is random is quite strange.
3.9.0-* -> work perfectly (Wifi already connected when lightdm appears
on screen)
So the big thing seems to be with 3.11 (at least >= rc4, which is 3.11.0-0 AFAIK).
Now trying to narrow the scope with mainline kernels:
v3.11-rc1-saucy -> It works!
v3.11-rc2-saucy -> It works!
v3.11-rc3-saucy -> It works!
v3.11-rc4-saucy -> FAIL
So the problem is between rc3 and rc4.
Now it's going to be more complicated because this laptop is not suited for building kernels. It will take forever.
(I have a more powerful desktop, but it's not running Saucy)
Could someone help me find a potential faulty commit in order to speed up the bisecting process?
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1214059
Title:
Wifi and bluetooth disabled at boot and hard to re-enable
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Network Manager says either "Device not ready" or "wireless is disabled by hardware switch" (it depends).
Enabling Bluetooth in the control-center just enable it for like half a second and then it's switched off again.
I have a combined hardware button for both Wifi and Bluetooth, it's red when it's disabled and blue when enabled.
In this case it stays red even when I repeatedly press it (though the Bluetooth setting panel reliably indicate when it is hardware disabled, so I guess the color is only related to software lock).
I manage to make it work again after playing with "rfkill
[block|unblock] all" and messing around with network manager
(disabling network and then re-enabling it...). I usually need around
5 minutes to make it work.
I did not have this problem on Raring. I had it on saucy with the 3.10
kernel but it seems to be worse with 3.11 (I need to mess around for
more time in order to make it work again).
Feel free to ask if you need any additional test.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: nicolas 1670 F.... pulseaudio
/dev/snd/controlC0: nicolas 1670 F.... pulseaudio
Date: Mon Aug 19 19:20:56 2013
HibernationDevice: RESUME=UUID=7e493485-d08d-4944-8362-444f69fd1e08
InstallationDate: Installed on 2013-07-10 (39 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130710)
MachineType: Hewlett-Packard HP EliteBook 8530p
MarkForUpload: True
PccardctlStatus:
Socket 0:
3.3V
16-bit
PC Card
Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=821ce4aa-35e4-436c-93cc-c8c2d9aba532 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-2-generic N/A
linux-backports-modules-3.11.0-2-generic N/A
linux-firmware 1.113
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.11
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.26
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530p:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530p
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214059/+subscriptions
References