kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Furkan, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags removed: bios-outdated-f12
** Tags added: latest-bios-f12

** Changed in: linux (Ubuntu)
   Importance: Low => Medium

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Tags added: regression-release

-- 
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/1554371

Title:
  [Regression] Volume keys not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Microsoft Sculpt Ergonomic Desktop (keyboard/mouse combo). It
  was working great with Ubuntu 15.10. After upgrading to 16.04, the
  media keys stop working after suspending and resuming. This seems to
  be the relevant error from Xorg.log:

  [   176.121] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0:
  Unable to open evdev device "/dev/input/event6".

  The USB receiver creates 5 devices:

  lrwxrwxrwx 1 root root   9 Mar  7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd -> ../event4
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-event-mouse -> ../event5
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-mouse -> ../mouse1
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-event-kbd -> ../event6
  lrwxrwxrwx 1 root root   6 Mar  7 20:17 usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-kbd -> ../js0

  After suspending and resuming, the last 2 devices (event6 and js0)
  disappear.

  I have tried booting up into the Vivid and Trusty kernels, and the
  problem persists, so at first glance it doesn't seem to be an issue
  with the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-4-generic 4.4.0-4.19
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  furkan     2733 F.... pulseaudio
   /dev/snd/controlC1:  furkan     2733 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  7 20:17:56 2016
  HibernationDevice: RESUME=UUID=a8eb7091-e848-4e63-82a1-8fa9562a3a61
  InstallationDate: Installed on 2014-06-06 (640 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-4-generic N/A
   linux-backports-modules-4.4.0-4-generic  N/A
   linux-firmware                           1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-01-04 (63 days ago)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554371/+subscriptions