kernel-packages team mailing list archive

[Keng-Yu Lin <keng-yu.lin@xxxxxxxxxxxxx>]

@Po-Hsu, can you try if rmmod dell-laptop.ko can solve the bug?

** Changed in: hwe-next
     Assignee: (unassigned) => Anthony Wong (anthonywong)

** Changed in: hwe-next
   Importance: Undecided => Low

** Changed in: hwe-next
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1495782

Title:
  Suspend / Hibernate will toggle Wifi / BT status on Trusty

Status in HWE Next:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  CID: 201412-16319 Dell Latitude 3150
  CID: 201407-15273 Dell Latitude 3450

  Running hibernate or suspend will trigger a rfkill event on resume and
  toggle both of the Wireless network and Bluetooth, so they will be
  blocked when you suspend it for the first time, and be re-enabled when
  you suspend it again.

  After the first suspend, "rfkill list" shows:
  ubuntu@201412-16319:~$ cat rfkill 
  0: phy0: Wireless LAN
  	Soft blocked: yes
  	Hard blocked: yes
  1: dell-wifi: Wireless LAN
  	Soft blocked: yes
  	Hard blocked: no
  2: dell-bluetooth: Bluetooth
  	Soft blocked: yes
  	Hard blocked: no

  You may unblock then with the wireless hotkey, however, on
  201412-16319, sometime the wireless can't be re-enable with the hotkey
  (fail rate: 3~4 out of 12), I will need to suspend this system again
  to make wireless back to work. (0 out of 12 on 201407-15273)

  I noticed that this issue seems to happen only on the system with an individual wireless key input event:
  $ sudo evtest
  /dev/input/event6:	DELL Wireless hotkeys

  (A 14.04.2 certified Dell Vostro 5470 ,CID: 201307-14037, does not
  have this issue, and it does not have a wireless key input event in
  evtest, the wireless key event is called KEY_WLAN and is integrated in
  Dell WMI hotkeys event)

  If you use evtest to monitor this wireless hotkey event, I can see
  that it will send a rfkill event after resume from suspend:

  ubuntu@201407-15273:~$ sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:	Lid Switch
  /dev/input/event1:	Power Button
  /dev/input/event2:	Sleep Button
  /dev/input/event3:	Power Button
  /dev/input/event4:	AT Translated Set 2 keyboard
  /dev/input/event5:	SynPS/2 Synaptics TouchPad
  /dev/input/event6:	DELL Wireless hotkeys
  /dev/input/event7:	Video Bus
  /dev/input/event8:	HDA Intel PCH Headphone Mic
  /dev/input/event9:	Dell WMI hotkeys
  /dev/input/event10:	HDA Intel HDMI HDMI/DP,pcm=3
  /dev/input/event11:	HDA Intel HDMI HDMI/DP,pcm=7
  /dev/input/event12:	HDA Intel HDMI HDMI/DP,pcm=8
  /dev/input/event13:	Integrated_Webcam_HD
  Select the device event number [0-13]: 6
  Input driver version is 1.0.1
  Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
  Input device name: "DELL Wireless hotkeys"
  Supported events:
    Event type 0 (EV_SYN)
    Event type 1 (EV_KEY)
      Event code 247 (KEY_RFKILL)
  Properties:
  Testing ... (interrupt to exit)
  Event: time 1442315336.476988, -------------- SYN_REPORT ------------
  Event: time 1442315379.463923, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1
  Event: time 1442315379.463923, -------------- SYN_REPORT ------------
  Event: time 1442315379.463927, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0
  Event: time 1442315379.463927, -------------- SYN_REPORT ------------

  (The first SYN_REPORT here is for suspend, as when you press the
  wireless hotkey it will send out the "type 1 (EV_KEY)" information
  first)

  Steps to reproduce:
  1. Install 14.04.2 + update
  2. Suspend it from the system menu
  3. Wake it up.
  4. Suspend it again.
  5. Wake it up

  Expected result:
  * Wireless and Bluetooth should be working all the time.

  Actual result:
  * They got disabled on the first, third, fifth... cycle.

  
  You can verify it here with "sudo pm-hibernate" too, and will get the same result.

  This issue can be reproduced on 3.16 and 3.19 kernel. And some pre-
  installed systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 15 00:17:34 2015
  InstallationDate: Installed on 2015-09-11 (4 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1574 F.... pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c9ac4cb4-606e-492c-a4a0-c511bad7444f
  InstallationDate: Installed on 2015-09-11 (4 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6709 Microdia
   Bus 001 Device 036: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3150
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic root=UUID=f071bd28-7686-4baa-a134-8392289e49d2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware                             1.127.15
  Tags:  trusty
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 021010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA02:bd07/31/2015:svnDellInc.:pnLatitude3150:pvr:rvnDellInc.:rn021010:rvrD02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3150
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1495782/+subscriptions