Wireless HW killswitch doesn't work on HP Elitebook Folio 1040 G1

Bug #1303420 reported by Jonathan Davies on 2014-04-06
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

The hardware wifi killswitch doesn't work on a HP Elitebook Folio 1040 G1.

The sound mute button next to it does though.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic]
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jpds 3933 F.... pulseaudio
 /dev/snd/controlC0: jpds 3933 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Apr 6 18:37:24 2014
HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89
InstallationDate: Installed on 2014-04-06 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/09/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L83 Ver. 01.05
dmi.board.name: 213E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 24.2A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook Folio 1040 G1
dmi.product.version: A3009DD18303
dmi.sys.vendor: Hewlett-Packard

Jonathan Davies (jpds) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Jonathan Davies (jpds) wrote :

Running:

$ sudo showkey -s

...and pressing the wifi key shows no output.

Joseph Salisbury (jsalisbury) wrote :

id this issue occur in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 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.14-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Jonathan Davies (jpds) wrote :

Confirmed working using linux-image-3.14.0-031400-generic_3.14.0-031400.201403310035_amd64.deb.

tags: added: kernel-fixed-upstream
Joseph Salisbury (jsalisbury) wrote :

Do you happen to know if this bug always existed in Trusty? Has it also happened in prior releases?

Jonathan Davies (jpds) wrote :

No idea, I got this laptop this weekend.

Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.

Can you test the following kernels and report back? We are looking for the earliest kernel version that doesn't have this bug:

v3.13-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty

If v3.13-rc3 exhibits the bug then test v3.13-rc6:
v3.13-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty

If v3.13-rc3 does not exhibit the bug then test v3.13-rc2:
v3.13-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty

You don't have to test every kernel, just up until the first kernel that does not have this bug.

Thanks in advance!

tags: added: performing-bisect
Joseph Salisbury (jsalisbury) wrote :

Sorry, the links should all point to the 3.14 release candidates and not 3.13.

Can you test the following kernels and report back? We are looking for the earliest kernel version that doesn't have this bug:

v3.14-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty

If v3.14-rc4 exhibits the bug then test v3.14-rc6:
v3.14-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc6-trusty

If v3.14-rc3 does not exhibit the bug then test v3.14-rc2:
v3.14-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc2-trusty

Jonathan Davies (jpds) wrote :

v3.14-rc4 doesn't have the problem.

Jonathan Davies (jpds) wrote :

-rc{4,2,1} - all good.

Joseph Salisbury (jsalisbury) wrote :

I started a "Reverse" bisect between v3.13 final and v3.14-rc1.

The first test kernel is built up to commit:
365c483f190fea03971b3eca8d68406f425777b5

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1303420/

Can you test this kernel and post back if it has the bug or not? I'll build the next test kernel based on your result.

Joseph Salisbury (jsalisbury) wrote :

I re-uploaded the test kernel, and it should now be available at:

http://kernel.ubuntu.com/~jsalisbury/lp1303420/

Jonathan Davies (jpds) wrote :

This kernel (linux-image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201404091235_amd64.deb) has the bug.

Joseph Salisbury (jsalisbury) wrote :

Sorry for the delay, Jonathan. I'm having some issues building kernels during the bisect due to another bug that happens while building. I'll investigate that further and should have another test kernel shortly.

tags: added: latest-bios-01.05
Joseph Salisbury (jsalisbury) wrote :

Can you see if this bug still exists in the latest upstream 3.13 kernel, which can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.2-trusty/

Steffen (steffen-weber) wrote :

Kernel parameter to workaround this bug on an HP EliteBook 840 G1: acpi_osi='!Windows 2012'

Related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313196

Steffen (steffen-weber) wrote :

Alternative solution that worked for me on Linux 3.14.4, too: CONFIG_HP_WIRELESS=y

Joseph Salisbury (jsalisbury) wrote :

I believe this bug will be fixed by commit 15d75fcebdf78d316a980487eddcac8e4f1574c8, which is in Trusty as of Ubuntu-3.13.0-28.51. This commit is a cherry pick of upstream 54290fa6.

Can you test the 3.13.0-28.51 kernel and confirm if it fixes this bug or not? It can be downloaded from:
https://launchpad.net/~canonical-kernel-team/+archive/ppa/+files/linux-image-3.13.0-28-generic_3.13.0-28.51_amd64.deb

The following bugs are probably duplicates:

bug 1118689
bug 1313196
bug 1303737

Changed in linux (Ubuntu):
status: Confirmed → Fix Committed
Jonathan Davies (jpds) wrote :

OK, the above kernel works, but kern.log still complains about a "atkbd: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0)".

Jonathan Davies (jpds) wrote :

(For other testers, you also need to download linux-image-extra-3.13.0-28-generic_3.13.0-28.51_amd64.deb).

Matt Alexander (lowbassman) wrote :

What's the current status of this bug? I have the Folio 1040 and can't turn on wireless.

$ uname -r
3.13.0-32-generic

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers