[Dell Precision M4300] Bluetooth LED permanently on

[Cas]

When switching off bluetooth the LED used to also turn off, I re-tested quickly with Natty to confirm this, but for at least the last two releases the LED is stubbornly staying on all the time.

I have identified the commit specific to Dell laptops that broke this and quite coincidentally this same commit was just reverted on the next branch only a few days ago. It's not all good however as the companion commits replace a laptop blacklist with a whitelist meaning it currently only works with Latitude models so I have to see if I can get Precision models also included.

The commit that resulted in this issue was introduced in 3.5 kernel as "dell-laptop: Remove rfkill code"[1]

I have built and tested the linux next branch code with the revert commit [2] and then modify the "Latitude" product string commit [3] to "Precision" and the bluetooth LED is now switching off as it should do.

[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=a6c2390cd6d2083d27a2359658e08f2d3df375ac
[2 ]https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4cc8a57425c623753b10b77b15392e5b83baa5a3
[3] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=2a92551845bbbc8421ba908cd14bbdf065e0f454

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: calum 1528 F.... pulseaudio
CheckboxSubmission: beb20350994a383f56f97def0e07bae1
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Fri Nov 22 19:08:54 2013
HibernationDevice: RESUME=UUID=3f279429-3482-4734-86b6-cc41fa7ce020
InstallationDate: Installed on 2012-02-23 (637 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120223.1)
MachineType: Dell Inc. Precision M4300
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=64e61881-95ee-4b3c-8714-c08c940f4966 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-09-06 (77 days ago)
dmi.bios.date: 06/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0UY141
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M4300
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

[penalvch (penalvch)]

Cas, the next step is to fully commit bisect from Natty to Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Cas (calumlind)]

I have identified the commit specific to Dell laptops that broke this and quite coincidentally this same commit was just reverted on the next branch only a few days ago. It's not all good however as the companion commits replace a laptop blacklist with a whitelist meaning it currently only works with Latitude models so I have to see if I can get Precision models also included.

The commit that resulted in this issue was introduced in 3.5 kernel as "dell-laptop: Remove rfkill code"[1]

I have built and tested the linux next branch code with the revert commit [2] and then modify the "Latitude" product string commit [3] to "Precision" and the bluetooth LED is now switching off as it should do.

[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=a6c2390cd6d2083d27a2359658e08f2d3df375ac
[2 ]https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4cc8a57425c623753b10b77b15392e5b83baa5a3
[3] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=2a92551845bbbc8421ba908cd14bbdf065e0f454

[penalvch (penalvch)]

Cas, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Please provide a direct URL to your post once you have made it so that it may be tracked.

BTW, nicely done investigating the upstream commits and the WORKAROUND.

Thank you for your understanding.