[Kernel-packages] [Bug 1599071] Re: Add Intel 8265 Bluetooth firmware

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add Intel 8265 Bluetooth firmware

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  Intel 8265 Bluetooth kernel driver support will be added to Xenial and
  it also needs firmware not yet being merged into the package

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1643558] Re: bnx2x driver crash

[Seth Arnold]

Kernel team, is there anything missing?

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

Title:
  bnx2x driver crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On server with two NICs on Broadcom, bnx2x driver is crashes on boot.
  Full crash dump is in attach.

  # lspci | grep BCM57711
  15:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 
10-Gigabit PCIe
  15:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 
10-Gigabit PCIe

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 ноя 21 13:50 seq
   crw-rw 1 root audio 116, 33 ноя 21 13:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Nov 21 16:21:07 2016
  InstallationDate: Installed on 2001-01-01 (5803 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: IBM BladeCenter HS22 -[7870H4G]-
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=8fae9581-bd38-4063-8871-cda77ac6c4ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2012
  dmi.bios.vendor: IBM
  dmi.bios.version: -[P9E156CUS-1.17]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 68Y8071
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 17
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBM:bvr-[P9E156CUS-1.17]-:bd02/03/2012:svnIBM:pnBladeCenterHS22-[7870H4G]-:pvr07:rvnIBM:rn68Y8071:rvr(none):cvnIBM:ct17:cvrnone:
  dmi.product.name: BladeCenter HS22 -[7870H4G]-
  dmi.product.version: 07
  dmi.sys.vendor: IBM

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly

[Guy Paddock]

I just ran into this issue with Bento Box's 64-bit image for 16.04. We
were trying to boot into recovery mode in order to run `zerofree` prior
to packaging up a custom box for internal use (per steps from
https://snippets.khromov.se/shrinking-a-virtualbox-linux-image-with-
zerofree/).

I can confirm this is a systemd-specific issue. We booted normally,
followed instructions under "Permanent switch back to upstart" in
https://wiki.ubuntu.com/SystemdForUpstartUsers, and rebooted, which
successfully removed systemd. We then booted into Recovery Mode and had
no interruptions or strange boot behavior (though there was an error
about not being able to start "User Service" on the boot after
installing Upstart).

Prior to removing systemd, the behavior @b-candler described is exactly
what we were seeing -- after about 1 to 2 mins, it seems like systemd
gets impatient and starts booting the system normally, bringing up
networking, etc, AND THEN starts the recovery menu and recovery shell on
top of an existing session. After another few minutes, you actually get
a third one on top of that. If you can actually brave the storm and get
to a prompt, running `init 1` will cause a system hang.

Looks like Ubuntu is not alone here:
- 
https://www.reddit.com/r/linuxquestions/comments/5dug3e/linux_mint_recovery_mode_crashingtiming_out/
- https://forums.linuxmint.com/viewtopic.php?t=232329

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

Title:
  Recovery mode won't allow recovery after manually installing the OS
  incorrectly

Status in linux package in Ubuntu:
  Opinion

Bug description:
  If one manually installs Ubuntu but doesn't install a boot partition,
  the recovery mode doesn't work.

  The expectation (perhaps naively) is that the recovery mode is
  bootable and allows one to fix the situation.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=a91f753b-69af-4125-a03d-0dcb63d55d38 ro net.ifnames=0
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0054.2016.0503.1546
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-407
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0054.2016.0503.1546:bd05/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-407:cvn:ct3:cvr:

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1512848] Re: Radeon VCE Init Error

[madbiologist]

Does this still occur on an up to date installation of Ubuntu 16.04
"Xenial Xerus"?

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

Title:
  Radeon VCE Init Error

Status in Skylinux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

   dmesg | grep -E 'drm|radeon'
  [2.164605] [drm] Initialized drm 1.1.0 20060810
  [2.192852] [drm] radeon kernel modesetting enabled.
  [2.201268] [drm] Memory usable by graphics device = 2048M
  [2.201274] fb: switching to inteldrmfb from EFI VGA
  [2.201394] [drm] Replacing VGA console driver
  [2.204234] radeon :01:00.0: enabling device ( -> 0003)
  [2.207919] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [2.207921] [drm] Driver supports precise vblank timestamp query.
  [2.242929] fbcon: inteldrmfb (fb0) is primary device
  [3.529125] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
has_drrs (expected 1, found 0)
  [3.529141] WARNING: CPU: 1 PID: 195 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:12700 
intel_modeset_check_state+0x5aa/0x870 [i915]()
  [3.529150] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid 
hid rtsx_usb_sdmmc rtsx_usb amdkfd amd_iommu_v2 i915(+) radeon(+) i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 
ahci drm libahci mii fjes wmi video
  [3.529201]  [] drm_atomic_commit+0x37/0x60 [drm]
  [3.529206]  [] drm_atomic_helper_set_config+0x1bf/0x420 
[drm_kms_helper]
  [3.529212]  [] drm_mode_set_config_internal+0x62/0x100 
[drm]
  [3.529215]  [] restore_fbdev_mode+0xb3/0x110 
[drm_kms_helper]
  [3.529219]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
  [3.529221]  [] drm_fb_helper_set_par+0x2d/0x50 
[drm_kms_helper]
  [3.529253]  [] drm_fb_helper_initial_config+0x250/0x3e0 
[drm_kms_helper]
  [3.535608] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.546293] [drm] Initialized i915 1.6.0 20150731 for :00:02.0 on 
minor 0
  [3.546469] [drm] initializing kernel modesetting (OLAND 0x1002:0x6600 
0x144D:0xC0E6).
  [3.546483] [drm] register mmio base: 0xF7E0
  [3.546484] [drm] register mmio size: 262144
  [3.574408] [drm] GPU not posted. posting now...
  [3.587216] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [3.587218] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [3.587220] [drm] Detected VRAM RAM=1024M, BAR=256M
  [3.587220] [drm] RAM width 128bits DDR
  [3.587314] [drm] radeon: 1024M of VRAM memory ready
  [3.587315] [drm] radeon: 2048M of GTT memory ready.
  [3.587322] [drm] Loading oland Microcode
  [3.587398] [drm] Internal thermal controller without fan control
  [3.587450] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
  [3.593155] [drm] radeon: dpm initialized
  [3.594806] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [3.594811] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [3.595617] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
  [3.595620] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [4.815819] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [4.815912] radeon :01:00.0: WB enabled
  [4.815914] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x880416408c00
  [4.815916] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x880416408c04
  [4.815917] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x880416408c08
  [4.815918] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x880416408c0c
  [4.815919] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x4c10 and cpu addr 0x880416408c10
  [4.816694] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90003035a18
  [4.917369] radeon :01:00.0: VCE init error (-110).
  [4.917391] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.917391] [drm] Driver supports precise vblank timestamp query.
  [4.917393] radeon :01:00.0: radeon: MSI limited to 32-bit
  [4.917461] radeon :01:00.0: radeon: using MSI.
  [4.917484] [drm] radeon: irq initialized.
  [5.062349] [drm] ring test on 0 succeeded in 2 usecs
  [5.062353] [drm] ring test on 1 succeeded 

[Kernel-packages] [Bug 1648034] modoc (ppc64el) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/modoc__4.8.0-31.33__2016-12-08_04-49-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647694] Re: Broadcom 4352 not installing module for Kernel 4.8.0-30

[Jeff]

I have now also attempted to install them by downloading the linux-image
and linux-image-extra and opening them with GDebi, to install them.  The
results were the same.  When rebooting into the 4.8.0-30 kernel, the
wireless device is not installed or recognized.  This prevents me from
accessing the Internet or any networks on this system.  When I have
upgraded the kernels in the 4.4 series, the install goes smoothly and
updates the broadcom module as expected.

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

Title:
  Broadcom 4352 not installing module for Kernel 4.8.0-30

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing Kernel 4.8.0-30, over existing Kernel 4.4.0-51 with a
  Broadcom 4352 wireless device, the kernel install fails to install the
  kernel module, resulting in wireless connectivity being inoperative.

  lscpi-vnvn.log attached.  Version log is not the kernel in question.
  Linux Mint 18 Sarah  RELEASE 18

  Expected the WL driver module to be installed for the 4.8.0-30 kernel and for 
wireless networking to function as a result.   Actual result, error in install, 
prevents kernel module from installing correctly and precludes wireless 
networking functionality.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jag2030 F pulseaudio
   /dev/snd/controlC3:  jag2030 F pulseaudio
   /dev/snd/controlC2:  jag2030 F pulseaudio
   /dev/snd/controlC0:  jag2030 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18
  HibernationDevice: RESUME=UUID=bc762603-aa60-4343-a125-bbda5dcf5340
  InstallationDate: Installed on 2016-07-04 (155 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=a414df14-dae7-4f65-8614-a21b2e4a2061 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  Tags:  sarah
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jag2006 F pulseaudio
   /dev/snd/controlC3:  jag2006 F pulseaudio
   /dev/snd/controlC2:  jag2006 F pulseaudio
   /dev/snd/controlC0:  jag2006 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18
  HibernationDevice: RESUME=UUID=bc762603-aa60-4343-a125-bbda5dcf5340
  InstallationDate: Installed on 2016-07-04 (155 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=a414df14-dae7-4f65-8614-a21b2e4a2061 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  Tags:  sarah
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/27/2015
  

[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

[Phong Nguyen]

Hi Joseph,
This test kernel is also working for me.
I don't see kernel crash when creating 2 RAID volumes consecutively on a single 
boot.

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 

[Kernel-packages] [Bug 1574319] Re: HDMi sound speed reduced : Intel GPU

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HDMi sound speed reduced : Intel GPU

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since 16.04 on my Broadwell Low power Intel Mini PC, the sound ( and
  video) is playing really low speed which change any sound played on
  the PC.

  TO overcome that I need to use the i915.disable_power_well=0 grub
  switch.

  I woud be great to have this work as default.

  the problem reappear after the machine goes out of sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-base 4.0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 17:49:59 2016
  Dependencies:

  InstallationDate: Installed on 2015-11-10 (165 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: linux-base
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1602743] Re: wifi stops working after xenial upgrade - HP Pavilion 13-b208tu w/ Broadcom BCM43142

[Launchpad Bug Tracker]

[Expired for bcmwl (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bcmwl (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  wifi stops working after xenial upgrade - HP Pavilion 13-b208tu w/
  Broadcom BCM43142

Status in bcmwl package in Ubuntu:
  Expired

Bug description:
  wifi no longer works on this laptop after upgrading to Xenial. I don't
  see any error messages. The wifi device is no longer listed in the
  network manager applet or by ifconfig.

  Per Bug #1434136, this laptop is not using the latest bios availble
  for download, as it has never worked with Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stub   2235 F pulseaudio
   /dev/snd/controlC0:  stub   2235 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 22:22:54 2016
  HibernationDevice: RESUME=UUID=85d38fc2-ada5-4f5e-83ec-ca176c194dab
  InstallationDate: Installed on 2015-03-13 (488 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Hewlett-Packard HP Pavilion 13 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-04 (8 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2340
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd11/28/2014:svnHewlett-Packard:pnHPPavilion13NotebookPC:pvr097D12005F0400080:rvnHewlett-Packard:rn2340:rvr07.09:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 13 Notebook PC
  dmi.product.version: 097D12005F0400080
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648034] kernel02 (s390x.zVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-30.32-generic/kernel02__4.8.0-30.32__2016-12-08_04-18-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648034] Re: linux: 4.8.0-31.33 -proposed tracker

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-30.32-generic/s2lp4__4.8.0-30.32__2016-12-08_04-17-00/results-index.html

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 08. December 2016 04:15 UTC

** Description changed:

  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 08. December 2016 04:15 UTC

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648034] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-30.32-generic/s2lp6g002__4.8.0-30.32__2016-12-08_04-17-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

[AceLan Kao]

The 2 i915 patches can't be backported to 3.19 kernel, so I use another way to 
archive the same function.
The test kernel could be found here, I'll try to see if we could find a machine 
here to verify it.

http://people.canonical.com/~acelan/bugs/lp1646537/

** Changed in: linux (Ubuntu Vivid)
   Status: New => In Progress

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

Title:
  Backlight sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in xorg source package in Vivid:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xorg source package in Xenial:
  Invalid

Bug description:
  Back-light sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

  Issue is interment in occurrence. Will be reproducible with the
  command "sudo pm-suspend" & or close/reopen laptop lid for a period of
  time days or hours, then go a period of time, days or hours without
  being able to trigger it again.

  This is irrespective of running "apt-get update && apt-get upgrade -y"
  and has continued to be intermittent on last 3 versions of 3.19
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-74-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  1 10:06:43 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06e5]
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed 
root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.14
  dmi.board.name: 0W7V82
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  1 09:14:43 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648034] Re: linux: 4.8.0-31.33 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-54.75-lowlatency/onza__4.4.0-54.75__2016-12-08_03-33-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647788] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86~14.04.1-generic/onza__3.19.0-78.86~14.04.1__2016-12-08_02-42-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-78.86~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-78.86~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1647787
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647788/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

[bugproxy]

Debian kernel package with genwqe-bad-page.patch applied.

** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/bugs/1559194/+attachment/4788007/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1593943] Re: Touchpad not working in 'ACER ASPIRE ES 15' after fresh install ubuntu 16.04

[BlackDalek]

Also affects Acer Aspire ES 15 / ES1-521-606B

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

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

Title:
  Touchpad not working in 'ACER ASPIRE ES 15' after fresh install ubuntu
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of ubuntu 16.04 I noticed my touchpad is not
  working at all.

  If I plug a mouse I'm enabled to use the pointer.

  Exact model : Aspire ES 15 / ES1-521-63DV

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-25-generic 4.4.0-25.44 [modified: 
boot/vmlinuz-4.4.0-25-generic]
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  patricia   1585 F pulseaudio
   /dev/snd/controlC0:  patricia   1585 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jun 18 11:05:57 2016
  HibernationDevice: RESUME=UUID=5c5afe1d-07d1-4355-ad22-fcdfb1793add
  InstallationDate: Installed on 2016-06-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160616)
  MachineType: Acer Aspire ES1-521
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-25-generic.efi.signed 
root=UUID=4c7679e9-a51d-4829-af5c-0627e4f6a311 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-25-generic N/A
   linux-backports-modules-4.4.0-25-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BELLEMERE_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.name: Aspire ES1-521
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648279] Re: Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

[AceLan Kao]

The patch in linux-next / linux-pm tree fixes this issue

commit 708f5dcc21ae9b35f395865fc154b0105baf4de4
Author: Michael Pobega 
Date:   Fri Nov 11 22:29:14 2016 -0500

ACPI / blacklist: Make Dell Latitude 3350 ethernet work

The Dell Latitude 3350's ethernet card attempts to use a reserved
IRQ (18), resulting in ACPI being unable to enable the ethernet.

Adding it to acpi_rev_dmi_table[] helps to work around this problem.

Signed-off-by: Michael Pobega 
[ rjw: Changelog ]
Signed-off-by: Rafael J. Wysocki 

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

Title:
  Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Steps]
  1. install trusty image
  2. "sudo apt-get update" and install available updates to enable upgrading in 
images
  3. enable Trusty -proposed ppa
  4. "sudo apt-get update"
  5. "sudo apt-get dist-upgrade && sudo apt-get install --install-recommends 
linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial"
  6. Reboot system
  7. Check Ethernet

  [Expected results]
  Ethernet work

  [Actual results]
  Ethernet not work

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648279] [NEW] Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

[AceLan Kao]

Public bug reported:

[Steps]
1. install trusty image
2. "sudo apt-get update" and install available updates to enable upgrading in 
images
3. enable Trusty -proposed ppa
4. "sudo apt-get update"
5. "sudo apt-get dist-upgrade && sudo apt-get install --install-recommends 
linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial"
6. Reboot system
7. Check Ethernet

[Expected results]
Ethernet work

[Actual results]
Ethernet not work

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

Title:
  Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Steps]
  1. install trusty image
  2. "sudo apt-get update" and install available updates to enable upgrading in 
images
  3. enable Trusty -proposed ppa
  4. "sudo apt-get update"
  5. "sudo apt-get dist-upgrade && sudo apt-get install --install-recommends 
linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial"
  6. Reboot system
  7. Check Ethernet

  [Expected results]
  Ethernet work

  [Actual results]
  Ethernet not work

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647605] IwConfig.txt

[asgard2]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1647605/+attachment/4787996/+files/IwConfig.txt

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

Title:
  constantly freezing on high wifi load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My device is constantly freezing on high wifi load.

  I tested multiple distros and linux kernels.
  Such as:
  - xubuntu 16.04
  - xubuntu 16.10 and the current mainline kernel
  - current ubuntu 17.04 daily build
  - manjaro 
  - fedora

  It seems to be a general problem with this hardware.
  Compared to windows 10, it's not freezing.

  Changing /proc/irq/42/smp_affinity to f also did not help.

  Device: HP Notebook – 15-ba029ng(X7F58EA)
  - RTL8723BE PCIe Wireless Network Adapter
  - AMD E2-7110
  Regards
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xubuntu1901 F pulseaudio
   /dev/snd/controlC0:  xubuntu1901 F pulseaudio
  CasperVersion: 1.379
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  LiveMediaBuild: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81F5
  dmi.board.vendor: HP
  dmi.board.version: 66.30
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.17:bd09/02/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F5:rvr66.30:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1547151] Re: 10ec:8168 r8169 won't connect

[AceLan Kao]

** Changed in: linux (Ubuntu)
 Assignee: AceLan Kao (acelankao) => (unassigned)

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

Title:
  10ec:8168 r8169 won't connect

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  At school when I connect with my Ethernet cable to its network it
  doesn't see my cable, like it is disconnected. This occurs with a
  different computer using the same kernel driver with the same LAN
  chip. The realtek r8168 works flawlessly but it disconnects randomly.
  I don't have problems in Windows (speed is 100Mbps), or with other
  computers using the same cable.

  WORKAROUND: ethtool -s enp1s0f1 autoneg off speed 100 duplex full

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  luky   1556 F pulseaudio
   /dev/snd/controlC0:  luky   1556 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-02-12 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire E5-571G
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-29-generic.efi.signed 
root=UUID=211171d7-1b39-4c4b-8078-7ccbdd97ffdc ro quiet acpi_osi= acpi=force 
acpi_enforce_resources=lax i915.enable_rc6=1 i915.enable_fbc=1 
i915.lvds_downclock=1 i915.semaphores=1 drm.vblankoffdelay=1 
acpi_backlight=vendor
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-29-generic N/A
   linux-backports-modules-4.2.0-29-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
  Uname: Linux 4.2.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd08/03/2015:svnAcer:pnAspireE5-571G:pvrV1.31:rvnAcer:rnEA50_HB:rvrV1.31:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.31
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647048] Re: System freezes after login (NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s)

[misko]

Hi,

retried with the kernel-parameter softlockup_panic=1 , to get a stack-strace.
For me, the stacktrace seems to point to the sound-driver:

[  180.226284] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1^AdModules 
linked in:^Ac ccm^Ac rfcomm^Ac vmw_vsock_vmci_transport^Ac vsock^Ac vmw_vmci^Ac 
bnep^Ac acer_wmi^Ac sparse_keymap^A
c snd_hda_codec_hdmi^Ac intel_rapl^Ac x86_pkg_temp_thermal^Ac 
intel_powerclamp^Ac coretemp^Ac kvm_intel^Ac kvm^Ac irqbypass^Ac 
crct10dif_pclmul^Ac crc32_pclmul^Ac ghash_clmulni_intel^Ac aesni_i
ntel^Ac aes_x86_64^Ac lrw^Ac glue_helper^Ac ablk_helper^Ac cryptd^Ac 
intel_cstate^Ac arc4^Ac uvcvideo^Ac intel_rapl_perf^Ac videobuf2_vmalloc^Ac 
videobuf2_memops^Ac videobuf2_v4l2^Ac videobuf2_
core^Ac ath9k^Ac snd_hda_codec_realtek^Ac snd_hda_codec_generic^Ac joydev^Ac 
input_leds^Ac ath9k_common^Ac snd_seq_midi^Ac ath9k_hw^Ac snd_seq_midi_event^Ac 
snd_hda_intel^Ac videodev^Ac serio_r
aw^Ac snd_hda_codec^Ac ath3k^Ac ath^Ac snd_hda_core^Ac btusb^Ac snd_hwdep^Ac 
snd_rawmidi^Ac btrtl^Ac mac80211^Ac snd_pcm^Ac btbcm^Ac media^Ac btintel^Ac 
rtsx_pci_ms^Ac bluetooth^Ac cfg80211^Ac 
snd_seq^Ac snd_seq_device^Ac memstick^Ac lpc_ich^Ac snd_timer^Ac snd^Ac 
soundcore^Ac mei_me^Ac mei^Ac shpchp^Ac 
[  180.238400] CPU: 1 PID: 3175 Comm: alsa-sink-HDMI  Not tainted 
4.9.0-040900rc8-generic #201612051443
[  180.240530] Hardware name: Acer TravelMate 8481TG/BA41_HS, BIOS V1.16 
11/28/2012
[  180.242699]  8be0ffa45b50^Ac ac2177d2^Ac ^Ac 
^Ac
[  180.244882]  8be0ffa45b68^Ac abf46df6^Ac 8be0f5edc000^Ac 
8be0ffa45ba0^Ac
[  180.247056]  abf8fd23^Ac 0001^Ac 8be0ffa4a400^Ac 
8be0f5edc000^Ac
[  180.249166] Call Trace:
[  180.251194][] dump_stack+0x63/0x81
[  180.253168]  [] watchdog_overflow_callback+0xb6/0xe0
[  180.255016]  [] __perf_event_overflow+0x83/0x1b0
[  180.256898]  [] perf_event_overflow+0x14/0x20
[  180.258775]  [] intel_pmu_handle_irq+0x1d5/0x490
[  180.260641]  [] perf_event_nmi_handler+0x2c/0x50
[  180.262476]  [] nmi_handle+0x6a/0x120
[  180.264273]  [] default_do_nmi+0x53/0x110
[  180.266057]  [] do_nmi+0x119/0x180
[  180.267837]  [] end_repeat_nmi+0x1a/0x1e
[  180.269588]  [] ? 
native_queued_spin_lock_slowpath+0x179/0x1a0
[  180.271304]  [] ? 
native_queued_spin_lock_slowpath+0x179/0x1a0
[  180.273036]  [] ? 
native_queued_spin_lock_slowpath+0x179/0x1a0
[  180.274753][] _raw_spin_lock+0x20/0x30
[  180.276479]  [] azx_pcm_trigger+0x171/0x280 [snd_hda_codec]
[  180.278231]  [] snd_pcm_do_stop+0x3e/0x50 [snd_pcm]
[  180.279982]  [] snd_pcm_action_single+0x2f/0x70 [snd_pcm]
[  180.281737]  [] snd_pcm_action+0x103/0x110 [snd_pcm]
[  180.283487]  [] snd_pcm_drop+0x61/0x90 [snd_pcm]
[  180.285238]  [] snd_pcm_common_ioctl1+0x7cf/0xc90 [snd_pcm]
[  180.286912]  [] ? eventfd_ctx_read+0x67/0x210
[  180.288619]  [] ? wake_up_q+0x80/0x80
[  180.290312]  [] snd_pcm_playback_ioctl1+0x139/0x260 
[snd_pcm]
[  180.292008]  [] snd_pcm_playback_ioctl+0x27/0x40 [snd_pcm]
[  180.293682]  [] do_vfs_ioctl+0xa3/0x600
[  180.295356]  [] ? vfs_read+0x11b/0x130
[  180.297019]  [] SyS_ioctl+0x79/0x90
[  180.298679]  [] entry_SYSCALL_64_fastpath+0x1e/0xad


(full log is attached

** Attachment added: "netconsole-mainline5.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647048/+attachment/4788854/+files/netconsole-mainline5.log

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

Title:
  System freezes after login (NMI watchdog: BUG: soft lockup - CPU#0
  stuck for 22s)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since I updated to kubuntu 16.10 I quite often have the situation that
  my laptop completely freezes after login in sddm (that means: while
  KDE is loading).

  During that time:
  - Fans run high
  - laptop is completely unuseable (no mouse or keyboard-input accepted, can't 
switch to other terminal, etc ...) - only a long press to the power-button 
helps .
  - network-connections break (tried to monitor the system remotely, but when 
the error occurs, also the ssh-connection fails)
  - the kern.log stops and contains only a few lines of rubbish:
  Dec  3 11:01:37 orbit kernel: [   18.951805] ACPI: \_SB_.PCI0.PEG0.PEGP: 
failed to evaluate _DSM
  Dec  3 11:01:37 orbit kernel: [   18.951808] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20160422/nsarguments-95)
  Dec  3 11:01:37 orbit kernel: [   18.951891] nouveau :01:00.0: DRM: 
suspending console...
  Dec  3 11:01:37 orbit kernel: [   18.951894] nouveau :01:00.0: DRM: 
suspending display...
  Dec  3 11:01:37 orbit kernel: [   18.951902] nouveau :01:00.0: DRM: 
evicting buffers...
  Dec  3 11:01:37 orbit kernel: [   18.960908] nouveau :01:00.0: DRM: 
waiting for kernel channels to go idle...
  Dec  3 11:01:37 

[Kernel-packages] [Bug 1648259] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1648259

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise
  it probably needs to go to linux-input (where I've seen folks from
  Cirque and Alps post frequently).

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] Re: Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648260/+attachment/4788835/+files/dmesg.log

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] Re: Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648260/+attachment/4788837/+files/lspci-vvnn.log

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] Re: Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

I'm hopeful that with the right initialization sequence it will show up
as a HID trackpad and just report a proper descriptor, but that's
probably wishful thinking :)

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] Re: Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

** Attachment added: "lsinput.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648260/+attachment/4788836/+files/lsinput.log

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] Re: Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648260/+attachment/4788838/+files/uname-a.log

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] JournalErrors.txt

[Steve Kondik]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1648260/+attachment/4788833/+files/JournalErrors.txt

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] ProcEnviron.txt

[Steve Kondik]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1648260/+attachment/4788834/+files/ProcEnviron.txt

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  # Event code 4 ((null))
  # Event code 5 ((null))
  # Event code 6 ((null))
  # Event code 7 ((null))
  # Event code 8 ((null))
  # Event code 9 ((null))
  # Event code 10 ((null))
  # Event code 11 ((null))
  # Event code 12 ((null))
  # Event code 13 ((null))
  # Event code 14 ((null))
  #   Event type 1 (EV_KEY)
  # Event code 272 (BTN_LEFT)
  # Event code 273 (BTN_RIGHT)
  # Event code 274 (BTN_MIDDLE)
  #   Event type 2 (EV_REL)
  # Event code 0 (REL_X)
  # Event code 1 (REL_Y)
  # Event code 8 (REL_WHEEL)
  #   Event type 4 (EV_MSC)
  # Event code 4 (MSC_SCAN)
  #   Event type 20 (EV_REP)
  # Event code 0 (REP_DELAY)
  # Properties:
  N: CRQ1001:00 0488:D020
  I: 0018 0488 d020 0100
  P: 00 00 00 00 00 00 00 00
  B: 00 0b 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 07 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 01 00 00 00 00 00 00 00 00
  B: 02 03 01 00 00 00 00 00 00
  B: 03 00 00 00 00 00 00 00 00
  B: 04 10 00 00 00 00 00 00 00
  B: 05 00 00 00 00 00 00 00 00
  B: 11 00 00 00 00 00 00 00 00
  B: 12 00 00 00 00 00 00 00 00
  B: 14 01 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00
  B: 15 00 00 00 00 00 00 00 00

  
  The Windows driver .inf identifies it as "Glide_RazerFrancine":
  %GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

  Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  yakkety
  Uname: Linux 4.9.0-040900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users 
vboxusers
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648260] [NEW] Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

Public bug reported:

The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
and hasn't seen much Linux activity as of yet. I've worked on several
drivers and improvements already, however the trackpad on this laptop is
not functioning correctly and needs upstream love.

The trackpad appears to be a new Glidepoint model from Cirque, and I am
unable to find any information or even similar models compare with. It
is connected over the Designware I2C bus, and ends up claimed as a mouse
by the hid-generic driver. Simple usage works, but multitouch, gestures,
and other customizations are not possible. I have tried to use the hid-
alps driver with it, but it does not work (after adding the relevant
identifiers). I've also tried a laundry list of hacks and workarounds
found in dubious places of the internet, with no help. Additionally, I
tried Dell's uinput-based Glidepoint driver which of course did not
work. I've not done any protocol sniffing or reverse engineering as of
yet.

I've tested with both the yakkety production kernel and am now on
mainline 4.9-rc8 with the same behavior.

Output from evemu-describe:

# EVEMU 1.2
# Input device name: "CRQ1001:00 0488:D020"
# Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
# Supported events:
#   Event type 0 (EV_SYN)
# Event code 0 (SYN_REPORT)
# Event code 1 (SYN_CONFIG)
# Event code 2 (SYN_MT_REPORT)
# Event code 3 (SYN_DROPPED)
# Event code 4 ((null))
# Event code 5 ((null))
# Event code 6 ((null))
# Event code 7 ((null))
# Event code 8 ((null))
# Event code 9 ((null))
# Event code 10 ((null))
# Event code 11 ((null))
# Event code 12 ((null))
# Event code 13 ((null))
# Event code 14 ((null))
#   Event type 1 (EV_KEY)
# Event code 272 (BTN_LEFT)
# Event code 273 (BTN_RIGHT)
# Event code 274 (BTN_MIDDLE)
#   Event type 2 (EV_REL)
# Event code 0 (REL_X)
# Event code 1 (REL_Y)
# Event code 8 (REL_WHEEL)
#   Event type 4 (EV_MSC)
# Event code 4 (MSC_SCAN)
#   Event type 20 (EV_REP)
# Event code 0 (REP_DELAY)
# Properties:
N: CRQ1001:00 0488:D020
I: 0018 0488 d020 0100
P: 00 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 07 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 03 01 00 00 00 00 00 00
B: 03 00 00 00 00 00 00 00 00
B: 04 10 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 01 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00


The Windows driver .inf identifies it as "Glide_RazerFrancine":
%GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

Filing the bug here in case someone at Canonical can help, otherwise it 
probably needs to go to linux-input (where I've seen folks from Cirque and Alps 
post frequently).
--- 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
Tags:  yakkety
Uname: Linux 4.9.0-040900rc8-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxusers
_MarkForUpload: True

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-collected yakkety

** Tags added: apport-collected yakkety

** Description changed:

  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop is
  not functioning correctly and needs upstream love.
  
  The trackpad appears to be a new Glidepoint model from Cirque, and I am
  unable to find any information or even similar models compare with. It
  is connected over the Designware I2C bus, and ends up claimed as a mouse
  by the hid-generic driver. Simple usage works, but multitouch, gestures,
  and other customizations are not possible. I have tried to use the hid-
  alps driver with it, but it does not work (after adding the relevant
  identifiers). I've also tried a laundry list of hacks and workarounds
  found in dubious places of the internet, with no help. Additionally, I
  tried Dell's uinput-based Glidepoint driver which of course did not
  work. I've not done any protocol sniffing or reverse engineering as of
  yet.
  
  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.
  
  Output from evemu-describe:
  
  # EVEMU 

[Kernel-packages] [Bug 1648259] [NEW] Trackpad on Razer Blade Pro (2016) only functions as mouse

[Steve Kondik]

Public bug reported:

The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
and hasn't seen much Linux activity as of yet. I've worked on several
drivers and improvements already, however the trackpad on this laptop is
not functioning correctly and needs upstream love.

The trackpad appears to be a new Glidepoint model from Cirque, and I am
unable to find any information or even similar models compare with. It
is connected over the Designware I2C bus, and ends up claimed as a mouse
by the hid-generic driver. Simple usage works, but multitouch, gestures,
and other customizations are not possible. I have tried to use the hid-
alps driver with it, but it does not work (after adding the relevant
identifiers). I've also tried a laundry list of hacks and workarounds
found in dubious places of the internet, with no help. Additionally, I
tried Dell's uinput-based Glidepoint driver which of course did not
work. I've not done any protocol sniffing or reverse engineering as of
yet.

I've tested with both the yakkety production kernel and am now on
mainline 4.9-rc8 with the same behavior.

Output from evemu-describe:

# EVEMU 1.2
# Input device name: "CRQ1001:00 0488:D020"
# Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
# Supported events:
#   Event type 0 (EV_SYN)
# Event code 0 (SYN_REPORT)
# Event code 1 (SYN_CONFIG)
# Event code 2 (SYN_MT_REPORT)
# Event code 3 (SYN_DROPPED)
# Event code 4 ((null))
# Event code 5 ((null))
# Event code 6 ((null))
# Event code 7 ((null))
# Event code 8 ((null))
# Event code 9 ((null))
# Event code 10 ((null))
# Event code 11 ((null))
# Event code 12 ((null))
# Event code 13 ((null))
# Event code 14 ((null))
#   Event type 1 (EV_KEY)
# Event code 272 (BTN_LEFT)
# Event code 273 (BTN_RIGHT)
# Event code 274 (BTN_MIDDLE)
#   Event type 2 (EV_REL)
# Event code 0 (REL_X)
# Event code 1 (REL_Y)
# Event code 8 (REL_WHEEL)
#   Event type 4 (EV_MSC)
# Event code 4 (MSC_SCAN)
#   Event type 20 (EV_REP)
# Event code 0 (REP_DELAY)
# Properties:
N: CRQ1001:00 0488:D020
I: 0018 0488 d020 0100
P: 00 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 07 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 03 01 00 00 00 00 00 00
B: 03 00 00 00 00 00 00 00 00
B: 04 10 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 01 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00


The Windows driver .inf identifies it as "Glide_RazerFrancine":
%GlideTpd.Francine%  = Glide_RazerFrancine, HID\CRQ1001

Filing the bug here in case someone at Canonical can help, otherwise it
probably needs to go to linux-input (where I've seen folks from Cirque
and Alps post frequently).

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Trackpad on Razer Blade Pro (2016) only functions as mouse

Status in linux package in Ubuntu:
  New

Bug description:
  The new Razer Blade Pro (2016) is an extremely high-end gaming laptop
  and hasn't seen much Linux activity as of yet. I've worked on several
  drivers and improvements already, however the trackpad on this laptop
  is not functioning correctly and needs upstream love.

  The trackpad appears to be a new Glidepoint model from Cirque, and I
  am unable to find any information or even similar models compare with.
  It is connected over the Designware I2C bus, and ends up claimed as a
  mouse by the hid-generic driver. Simple usage works, but multitouch,
  gestures, and other customizations are not possible. I have tried to
  use the hid-alps driver with it, but it does not work (after adding
  the relevant identifiers). I've also tried a laundry list of hacks and
  workarounds found in dubious places of the internet, with no help.
  Additionally, I tried Dell's uinput-based Glidepoint driver which of
  course did not work. I've not done any protocol sniffing or reverse
  engineering as of yet.

  I've tested with both the yakkety production kernel and am now on
  mainline 4.9-rc8 with the same behavior.

  Output from evemu-describe:

  # EVEMU 1.2
  # Input device name: "CRQ1001:00 0488:D020"
  # Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
  # Supported events:
  #   Event type 0 (EV_SYN)
  # Event code 0 (SYN_REPORT)
  # Event code 1 (SYN_CONFIG)
  # Event code 2 (SYN_MT_REPORT)
  # Event code 3 (SYN_DROPPED)
  #   

[Kernel-packages] [Bug 1647887] Re: NVMe driver accidentally reverted to use GSI instead of MSIX

[Dan Streetman]

Note: this problem isn't in yakkety or zesty, no backporting of these
particular NVMe patches was needed for those kernels, as the commits
were already included in the kernel they are based on.  This is an issue
only in the xenial kernel.  (of course the precise/trusty kernels are
far too old for this problem to be present)

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

Title:
  NVMe driver accidentally reverted to use GSI instead of MSIX

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  These commit ids are in the xenial kernel branch.

  Commit 90c9712fbb388077b5e53069cae43f1acbb0102a ("NVMe: Always use MSI/MSI-x
  interrupts") changed the NVMe driver to always use MSI/MSI-x interrupts.
  However, later commit 30d6592fce71beabe18460252c3823747c4742f6 ("NVMe: Don't
  unmap controller registers on reset") as well as commit
  e9820e415895bdd9cfd21f87e80e3e0a10f131f0 ("UBUNTU: (fix) NVMe: Don't unmap
  controller registers on reset") accidentally reverted part of the original
  commit, which reverted the NVMe   driver to using GSI interrupts instead 
of
  always using MSI/MSI-x interrupts.

  The original commit was added because GSI interrupts do not always
  work for NVMe on all systems, while MSI/MSIX interrupts do work.  The
  accidental reversion of the code to use MSI/MSIX causes the NVMe
  driver to not work on some systems with NVMe drives.

  [Test Case]

  On a system with NVMe drive(s) that do not work (because the NVMe
  driver is using the non-working GSI interrupt, instead of MSI/MSIX
  interrupt), test the current xenial kernel, and some or all of the
  NVMe drives will fail to initialize.  Then test with the fixed kernel,
  and all the NVMe drives will initialize.

  [Regression Potential]

  If MSI/MSIX interrupts do not work with NVMe drives on some systems,
  this change would break those systems.  Those systems would also be
  broken by the upstream kernel, however; additionally, without MSI/MSIX
  support, such NVMe controllers would be significantly slower due to
  reliance on a single GSI for notification of completion of all I/O.
  So it's very unlikely there are any systems with NVMe controllers that
  do not support MSI/MSI-x.

  [Other Info]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648034] Re: linux: 4.8.0-31.33 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Description changed:

  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase-changed:Wednesday, 07. December 2016 10:30 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 07. December 2016 22:45 UTC

** Description changed:

  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 07. December 2016 22:45 UTC
+ phase: Uploaded

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-31.33 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648034/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1639920] modified.conffile..etc.apport.crashdb.conf.txt

[bugproxy]

Default Comment by Bridge

** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/bugs/1639920/+attachment/4788794/+files/modified.conffile..etc.apport.crashdb.conf.txt

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

Title:
  NVMe detection failed during bootup

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've been running an on-off test on a couple of Power8 systems and
  have been getting a failure of detection on the NVMe drives on Ubuntu
  16.04.1 only.  I've ran the same test on RHEL 7.2 and have not
  encountered this proble. Once the problem occurs the OS will stop to
  boot up and a message appears:

  Welcome to emergency mode! After logging in, type "journalctl -xb" to view 
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try 
again to boot into default mode.
  Give root password for maintenance (or press Control-D to continue):

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  CrashReports:
   640:0:116:12295:2016-11-07 11:11:27.995107650 -0800:2016-11-07 
11:31:31.733627559 -0800:/var/crash/_usr_bin_apport-bug.0.crash
   644:0:116:0:2016-11-07 11:11:28.931104586 -0800:2016-11-07 
11:11:28.931104586 -0800:/var/crash/_usr_bin_apport-cli.0.None.hanging
  Date: Mon Nov  7 11:11:28 2016
  ExecutablePath: /usr/bin/apport-bug
  InstallationDate: Installed on 2016-11-05 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el 
(20160719)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.30 0.41 0.19 1/1132 2428
  ProcLocks:
   
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition157914048   0   
-1
  ProcVersion: Linux version 4.4.0-45-generic (buildd@bos01-ppc64el-030) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.2) ) #66-Ubuntu SMP Wed 
Oct 19 14:13:11 UTC 2016
  PythonArgs: ['/usr/bin/ubuntu-bug', '--hanging']
  SourcePackage: apport
  Title: apport-bug crashed with TypeError in run_hang(): int() argument must 
be a string, a bytes-like object or a number, not 'NoneType'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8
  mtime.conffile..etc.apport.crashdb.conf: 2016-11-07T10:38:18.528739

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-54.75-lowlatency/onza__4.4.0-54.75__2016-12-07_22-21-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1639920] Re: NVMe detection failed during bootup

[dexterb]

Hi Dan,

  The test kernel is working.  I'm not seeing the issue anymore.  Here's
what I've tried with our on-off test:

 1.) 1U system with (2x) 2-port NVMe controller with over 500 cycles = no issue
 2.) 1U system with (1x) 4-port NVMe controller with over 300 cycles = no issue
 3.) 2U system with (1x) 4-port NVMe controller with over 250 cycles = no issue

Please let me know if you need any info from me?  
I'd also like to know how or what we need to do in order to proceed and getting 
this fix for GA?

thank you so much!!

regards,
Dexter

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

Title:
  NVMe detection failed during bootup

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've been running an on-off test on a couple of Power8 systems and
  have been getting a failure of detection on the NVMe drives on Ubuntu
  16.04.1 only.  I've ran the same test on RHEL 7.2 and have not
  encountered this proble. Once the problem occurs the OS will stop to
  boot up and a message appears:

  Welcome to emergency mode! After logging in, type "journalctl -xb" to view 
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try 
again to boot into default mode.
  Give root password for maintenance (or press Control-D to continue):

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  CrashReports:
   640:0:116:12295:2016-11-07 11:11:27.995107650 -0800:2016-11-07 
11:31:31.733627559 -0800:/var/crash/_usr_bin_apport-bug.0.crash
   644:0:116:0:2016-11-07 11:11:28.931104586 -0800:2016-11-07 
11:11:28.931104586 -0800:/var/crash/_usr_bin_apport-cli.0.None.hanging
  Date: Mon Nov  7 11:11:28 2016
  ExecutablePath: /usr/bin/apport-bug
  InstallationDate: Installed on 2016-11-05 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el 
(20160719)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.30 0.41 0.19 1/1132 2428
  ProcLocks:
   
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition157914048   0   
-1
  ProcVersion: Linux version 4.4.0-45-generic (buildd@bos01-ppc64el-030) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.2) ) #66-Ubuntu SMP Wed 
Oct 19 14:13:11 UTC 2016
  PythonArgs: ['/usr/bin/ubuntu-bug', '--hanging']
  SourcePackage: apport
  Title: apport-bug crashed with TypeError in run_hang(): int() argument must 
be a string, a bytes-like object or a number, not 'NoneType'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8
  mtime.conffile..etc.apport.crashdb.conf: 2016-11-07T10:38:18.528739

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-54.75-generic/onza__4.4.0-54.75__2016-12-07_21-55-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642739] Re: Kernel panic on shutdown

[Gustav Näslund]

This one is good, it does not have the bug.

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

Title:
  Kernel panic on shutdown

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] modoc (ppc64el) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-54.75-generic/modoc__4.4.0-54.75__2016-12-07_21-35-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-54.75-generic/onza__4.4.0-54.75__2016-12-07_21-28-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] kernel01 (s390x.zVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-53.74-generic/kernel01__4.4.0-53.74__2016-12-07_21-07-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] Re: linux: 4.4.0-54.75 -proposed tracker

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-53.74-generic/s2lp6g001__4.4.0-53.74__2016-12-07_21-05-00/results-index.html

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 07. December 2016 21:03 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 07. December 2016 21:03 UTC
- kernel-stable-phase:Uploaded

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-53.74-generic/s2lp3__4.4.0-53.74__2016-12-07_21-06-00/results-index.html

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1641049] Re: NFSv4 do not invalidate cached information about deleted files

[Joseph Salisbury]

We can perform a "Reverse" bisect to identify the commit that fixes this
in v4.9-rc6.  We first need to identify the last bad kernel version and
the first good one.  Does v4.9-rc5 exhibit the bug?

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

Title:
  NFSv4 do not invalidate cached information about deleted files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using NFSv4 client in Ubuntu 16.04 the the following sequence of
  actions fails.

  You need a NFS server (S) and two clients (A and B).

  Let the NFS share be mounted at /nfsdata

  A: echo test > /nfsdata/file
  B: cat /nfsdata/file ===> test
  A: rm /nfsdata/file
  B: cat /nfsdata/file ===> cat: No such file or directory
  A: echo test > /nfsdata/file
  B: cat /nfsdata/file ===> cat: No such file or directory (!)

  Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible
  on B.

  14.04 works without any problem.

  I have attached log from one of our servers, 4.4.0-47 kernel does not fix 
this issue. 
  Syslog contains rpcdebug -m nfs -s all output for the scenario (with 
different filenames).
  I can do full packet capture of NFS traffic if you want.
  Mounting nfs with lookupcache=positive do not fix this issue.

  NFSv4 server is CentOS 6.7 in our case.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:13 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Nov 11 17:06:51 2016
  HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1
  InstallationDate: Installed on 2016-11-07 (3 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp.
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  PciMultimedia:

  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.1
  dmi.board.name: 02C2CP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R630
  dmi.sys.vendor: Dell Inc.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:13 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1
  InstallationDate: Installed on 2016-11-07 (3 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI 

[Kernel-packages] [Bug 1647937] Re: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Joseph Salisbury]

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

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

Title:
  package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Invalid

Bug description:
  update software haftway freezed, forced shutdown computer then unable
  to boot.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  daniel 1645 F pulseaudio
   /dev/snd/controlC0:  daniel 1645 F pulseaudio
  Date: Wed Dec  7 13:52:36 2016
  Df:
   Filesystem 1K-blocksUsed Available Use% Mounted on
   /dev/sdb3   50821796 5914916  42302236  13% /
   udev 5067924   0   5067924   0% /dev
   tmpfs10165129920   1006592   1% /run
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=993d82eb-8ad2-4d23-90cb-f5dd2c2c6363
  InstallationDate: Installed on 2016-12-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 8740w (QR933US#AB4)
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=93b795f6-e46a-4246-9cd1-c72e162a4fee ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: linux
  Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.60
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.32
  dmi.chassis.asset.tag: CNF3454B7N
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.60:bd11/10/2015:svnHewlett-Packard:pnHPEliteBook8740w(QR933US#AB4):pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w (QR933US#AB4)
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1646298] Re: Boot failed after kernel upgrade to 4.4.0-51.72

[Joseph Salisbury]

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

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

Title:
  Boot failed after kernel upgrade to 4.4.0-51.72

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After kernel upgrade system could not detect boot device anymore.

  Right after BIOS the following was prompted:
  Reboot and select proper Boot device
  or Insert Boot Media in Selected Boot device and press a key

  Problem was resolved (thanks to Eric^^ support at #ubuntu irc) by
  reinstall of grub.

  Before grub reinstall:
  ubuntu@ubuntu:~$ sudo efibootmgr -v
  BootCurrent: 0005
  Timeout: 1 seconds
  BootOrder: ,0001,0005
  Boot* Hard Drive  BBS(HD,,0x0)
  Boot0001* CD/DVD DriveBBS(CDROM,,0x0)
  Boot0005* UEFI: USB USB Hard Drive
PciRoot(0x0)/Pci(0x1a,0x0)/USB(1,0)/USB(2,0)/HD(1,MBR,0x4294967192,0x800,0x3ba7800)

  After grub reinstall:
  BootCurrent: 0002
  Timeout: 1 seconds
  BootOrder: 0003,,0001,0002
  Boot* Hard Drive  BBS(HD,,0x0)
  Boot0001* CD/DVD DriveBBS(CDROM,,0x0)
  Boot0002* UEFI: USB USB Hard Drive
PciRoot(0x0)/Pci(0x1a,0x0)/USB(1,0)/USB(2,0)/HD(1,MBR,0x4294967236,0x3e,0x78621e)
  Boot0003* ubuntu  
HD(1,GPT,7a7fae49-8b01-4c04-9dc3-2ce2a7988451,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1719 F pulseaudio
   /dev/snd/controlC0:  alexei 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec  1 02:11:16 2016
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (329 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (280 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1491494] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cdead...@us.ibm.com 2016-12-07 15:36 EDT---

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

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR24:  c000f53cbc00 0001  
  

[Kernel-packages] [Bug 1644823] Re: Bluetooth not working

[Mohamed Fawzy]

I had googled this issue a lot and downloaded the attached BCM.hcd file which 
make it works.
however the bluetooth devices get connected, but sometimes the sound is not 
heard properly.

** Attachment added: "BCM.hcd"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644823/+attachment/4788759/+files/BCM.hcd

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

Title:
  Bluetooth not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Lenovo thinkpad E531 laptop.
  The built-in bluetooth not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mfawzy 1927 F pulseaudio
  CRDA:
   country EG: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (N/A, 20), (N/A)
(5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Nov 25 14:40:57 2016
  HibernationDevice: RESUME=UUID=3d81c46b-d5d8-4809-8b2c-45998d99d0e7
  InstallationDate: Installed on 2016-11-15 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 6885DZG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=5348a48b-8050-4470-98f1-f6b758b76ce1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HEET44WW (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 6885DZG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrHEET44WW(1.25):bd05/30/2014:svnLENOVO:pn6885DZG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6885DZG
  dmi.product.version: ThinkPad Edge E531
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648203] Re: Backlight Bug

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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/v4.9-rc8


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

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

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

Title:
  Backlight Bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work and there are no entries in
  /sys/class/backlight

  On other linux distributions backlight control works fine and there is
  an entry in /sys/class/backlight

  I attach the files with debugging information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zulu   1367 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Dec  7 20:03:48 2016
  HibernationDevice: RESUME=UUID=471f1492-ab85-4809-b043-1b95ab3d8e28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=20bcbace-4432-45d8-bff1-cf7b1b4b7aa3 ro nomodeset quiet splash 
vt.handoff=7 video.use_bios_initial_backlight=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build

[Ubuntu Foundations Team Bug Bot]

The attachment "debdiff containing the fix" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Unable to analyse vmcore/dump via crash due to bad kernel debug info
  build

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - NAVEED A. UPPINANGADY SALIH  - 2016-07-01 02:41:07 ==
  ---Problem Description---
  Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel 
with ddeb kernel debuginfo available in 
http://ddebs.ubuntu.com/pool/main/l/linux/

  
http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29-generic-dbgsym_4.4.0-29.48_ppc64el.ddeb
   
  ---uname output---
   4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = model   : 8247-22L machine : PowerNV 8247-22L 
   
  ---Steps to Reproduce---
   # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic 
/var/crash/201606300840/dump.201606300840  
  crash 7.0.3
  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and 
/var/crash/201606300840/dump.201606300840 do not match!

  Userspace rpm: linux-image-4.4.0-29-generic-
  dbgsym_4.4.0-29.48_ppc64el.ddeb

  == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 ==

  The Latest kernel I am having is as follows

  root@ltcalpine-lp6:~# uname -a
  Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 
01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root@ltcalpine-lp6:~# 

  >>> the issue same as posted originally.

  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and 
/var/crash/201607270248/dump.201607270248 do not match!

  
  == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 ==
  The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled
  from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc
  version 5.3.1 which is the source of the issue.

   Resolved this by pulling the kernel debug symbols package from:

deb http://ddebs.ubuntu.com/ -updates  main

  which indeed has the vmlinux compiled with gcc version 4.8.4.
  But I got this error:

crash: invalid structure member offset: module_num_symtab
   FILE: kernel.c  LINE: 3049  FUNCTION: module_init()

  after the update owning to couple of missing patches listed below:

  
commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
Author: Dave Anderson 
Date:   Wed Jan 20 09:56:36 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 7523e4dc5057e157212b4741abd6256e03404cf1
module: use a structure to encapsulate layout.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_init_text_size".
  (seb...@linux.vnet.ibm.com)

  
commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
Author: Dave Anderson 
Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  

[Kernel-packages] [Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Joseph Salisbury]

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

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/v4.9-rc8

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

[Joseph Salisbury]

Does this bug sill happen with the latest Xenial updates?

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

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Incomplete

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

[Joseph Salisbury]

I compiled a test kernel for ppc66el.  It is available from:
http://kernel.ubuntu.com/~jsalisbury/lp1581326/ppc64el

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No 

[Kernel-packages] [Bug 1646068] Re: bonding: don't use stale speed and duplex information

[Joseph Salisbury]

There is now a Trusty test kernel available as well.  It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1646068/trusty

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

Title:
  bonding: don't use stale speed and duplex information

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  This upstream patch is missing (needed for all kernel between 3.9 and
  4.4 (both included)):

  266b495f11d6 bonding: don't use stale speed and duplex information
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=266b495f11d6

  Without this patch, reported speeds can be wrong.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work

[Joseph Salisbury]

It looks like commit 14de6c44d is in the Ubuntu 4.4 based kernel(It was
added to resolve bug 1542939).  However, the commit was never applied to
upstream 4.4.  That would explain why the bug does not exist in upstream
4.4, but it does in 4.4 based Xenial.

Can you see if this bug also exists in the 4.8 based Yakkety kernel?  If
it does, we may just have to revert 14de6c44d in Xenial.

The Yakkety kernel is available from:
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/11288461

If the bug does exist in Yakkety, we could also see if this bug still exists in 
current mainline:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8

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

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error

[Thomas Copeland]

Looks like this got punted to 3.13.0-106, which I installed it from the
canonical-kernel-team ppa. This bug appears to be solved in -106.

thomasco@dev:~$ uname -a
Linux dev 3.13.0-106-generic #153-Ubuntu SMP Tue Dec 6 15:44:32 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
thomasco@dev:~$ sudo sysctl -w net.ipv4.neigh.default.gc_thresh3=4096
net.ipv4.neigh.default.gc_thresh3 = 4096
thomasco@dev:~$ cat /proc/sys/net/ipv4/neigh/default/gc_thresh3
4096
thomasco@dev:~$

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

Title:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or
  later causes 'invalid argument' error

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic
  kernel and below worked fine using the following:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  128

  As of 3.13.0-97-generic, though, it no longer works as expected:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1"

  There are two potentially related revisions in the -97 release -
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty=563cf19389d8e999e69d6c94995966aeaf7c3a08 and
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty=7b82096b0ebc9bf487b390fe970d66ffa5a5774e.

  The expected behavior is that changing neighbor table settings works
  using 'sysctl -w' with the same values as before the -97 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1
  ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-98-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [4.586115] NET: Registered protocol family 40
  Date: Wed Oct 19 06:13:36 2016
  HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg 
noprompt quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-98-generic N/A
   linux-backports-modules-3.13.0-98-generic  N/A
   linux-firmware 1.79.16
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648017] Re: linux: 4.4.0-54.75 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647036] Re: Client does not ACK auth/assoc responses from Cisco AP3800

[Tim Gardner]

** Also affects: bcmwl (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: bcmwl (Ubuntu Zesty)
   Importance: High
 Assignee: Alberto Milone (albertomilone)
   Status: In Progress

** Changed in: bcmwl (Ubuntu Trusty)
   Status: Triaged => In Progress

** Changed in: bcmwl (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: bcmwl (Ubuntu Yakkety)
   Status: New => In Progress

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

Title:
  Client does not ACK auth/assoc responses from Cisco AP3800

Status in bcmwl package in Ubuntu:
  In Progress
Status in bcmwl source package in Trusty:
  In Progress
Status in bcmwl source package in Xenial:
  In Progress
Status in bcmwl source package in Yakkety:
  In Progress
Status in bcmwl source package in Zesty:
  In Progress

Bug description:
  This client does not ACK Assoc Responses from a Cisco 3800.  Traces
  attached.

  - Model:Dell XPS13 9343
  - OS Version:Ubuntu 14.04.5 LTS
  - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248
  - SSID:user.wifi (WPA2/dot1x )
  - MAC address:c4:8e:8f:f5:4a:7f
  -Cisco AP : 3800 (wave 2)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648203] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Backlight Bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight control does not work and there are no entries in
  /sys/class/backlight

  On other linux distributions backlight control works fine and there is
  an entry in /sys/class/backlight

  I attach the files with debugging information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zulu   1367 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Dec  7 20:03:48 2016
  HibernationDevice: RESUME=UUID=471f1492-ab85-4809-b043-1b95ab3d8e28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=20bcbace-4432-45d8-bff1-cf7b1b4b7aa3 ro nomodeset quiet splash 
vt.handoff=7 video.use_bios_initial_backlight=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648203] [NEW] Backlight Bug

[Juanito de los palotes]

Public bug reported:

Backlight control does not work and there are no entries in
/sys/class/backlight

On other linux distributions backlight control works fine and there is
an entry in /sys/class/backlight

I attach the files with debugging information.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-51-generic 4.4.0-51.72
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  zulu   1367 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Dec  7 20:03:48 2016
HibernationDevice: RESUME=UUID=471f1492-ab85-4809-b043-1b95ab3d8e28
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=20bcbace-4432-45d8-bff1-cf7b1b4b7aa3 ro nomodeset quiet splash 
vt.handoff=7 video.use_bios_initial_backlight=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-51-generic N/A
 linux-backports-modules-4.4.0-51-generic  N/A
 linux-firmware1.157.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "backlight_bug_report_files.tar.gz"
   
https://bugs.launchpad.net/bugs/1648203/+attachment/4788716/+files/backlight_bug_report_files.tar.gz

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

Title:
  Backlight Bug

Status in linux package in Ubuntu:
  New

Bug description:
  Backlight control does not work and there are no entries in
  /sys/class/backlight

  On other linux distributions backlight control works fine and there is
  an entry in /sys/class/backlight

  I attach the files with debugging information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zulu   1367 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Dec  7 20:03:48 2016
  HibernationDevice: RESUME=UUID=471f1492-ab85-4809-b043-1b95ab3d8e28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=20bcbace-4432-45d8-bff1-cf7b1b4b7aa3 ro nomodeset quiet splash 
vt.handoff=7 video.use_bios_initial_backlight=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

[Phong Nguyen]

Hi Joseph,
I would like to test this patch this on IBM Power8 system
Can you build a test kernel for ppc64le?

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No 

[Kernel-packages] [Bug 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Joseph Salisbury]

The patch is in fact in -proposed.  The bug bot should come along and
asked to test -proposed once we are in the SRU verification phase.

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build

[Robert Hooker]

crash (7.0.3-3ubuntu4.5) trusty; urgency=medium

  * Fix for: Unable to analyse vmcore/dump via crash due to bad kernel
debug info build (LP: #1607894).

 -- Robert Hooker   Thu, 01 Dec 2016 12:03:17 -0500


** Patch added: "debdiff containing the fix"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1607894/+attachment/4788691/+files/crash_7.0.3-3ubuntu4.5.debdiff

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

Title:
  Unable to analyse vmcore/dump via crash due to bad kernel debug info
  build

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - NAVEED A. UPPINANGADY SALIH  - 2016-07-01 02:41:07 ==
  ---Problem Description---
  Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel 
with ddeb kernel debuginfo available in 
http://ddebs.ubuntu.com/pool/main/l/linux/

  
http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29-generic-dbgsym_4.4.0-29.48_ppc64el.ddeb
   
  ---uname output---
   4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = model   : 8247-22L machine : PowerNV 8247-22L 
   
  ---Steps to Reproduce---
   # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic 
/var/crash/201606300840/dump.201606300840  
  crash 7.0.3
  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and 
/var/crash/201606300840/dump.201606300840 do not match!

  Userspace rpm: linux-image-4.4.0-29-generic-
  dbgsym_4.4.0-29.48_ppc64el.ddeb

  == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 ==

  The Latest kernel I am having is as follows

  root@ltcalpine-lp6:~# uname -a
  Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 
01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root@ltcalpine-lp6:~# 

  >>> the issue same as posted originally.

  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and 
/var/crash/201607270248/dump.201607270248 do not match!

  
  == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 ==
  The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled
  from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc
  version 5.3.1 which is the source of the issue.

   Resolved this by pulling the kernel debug symbols package from:

deb http://ddebs.ubuntu.com/ -updates  main

  which indeed has the vmlinux compiled with gcc version 4.8.4.
  But I got this error:

crash: invalid structure member offset: module_num_symtab
   FILE: kernel.c  LINE: 3049  FUNCTION: module_init()

  after the update owning to couple of missing patches listed below:

  
commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
Author: Dave Anderson 
Date:   Wed Jan 20 09:56:36 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 7523e4dc5057e157212b4741abd6256e03404cf1
module: use a structure to encapsulate layout.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_init_text_size".
  (seb...@linux.vnet.ibm.com)

  
commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
Author: Dave Anderson 
Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Applying the above patches on top of crash tool version 7.0.3-3ubuntu4.4,
  was able to analyze the dump. 

[Kernel-packages] [Bug 1643978] Re: hv_set_ifconfig creates corrupt file for multiple interfaces

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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/v4.9-rc8

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

Title:
  hv_set_ifconfig creates corrupt file for multiple interfaces

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  hv_set_ifconfig will create multiple GATEWAY entries in the interfaces
  file if there are multiple ethernet interfaces. This causes subsequent
  calls to ifup for the primary interface to fail with "RTNETLINK
  answers: File exists".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-virtual-lts-xenial 4.4.0.47.50
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov 22 20:16 seq
   crw-rw+ 1 root audio 116, 33 Nov 22 20:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Nov 22 20:26:27 2016
  HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916
  InstallationDate: Installed on 2016-11-22 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=31af956a-1342-4e8d-9c74-af0308e00111 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Joshua R. Poulson]

The test kernels were okay, should we be testing -proposed?

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642739] Re: Kernel panic on shutdown

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
e0a1e44ce0d8ea736d110b7115c5d31b0b5414c8

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

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Kernel panic on shutdown

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  Since I have updated to Ubuntu 16.10 (from 16.04) I have this problem
  where the shutdown takes a long time (~30s) and ends with a (at least
  I think it is) kernel panic with blinking harddrive- and battery
  status LEDs. Nothing is visible on the screen.

  This didnt happen on Ubuntu 16.04 so I tried installing a 4.4 kernel
  and the problem disappeared.

  I have then tested with various kernels from http://kernel.ubuntu.com
  /~kernel-ppa/mainline/ and I have found that the last good kernel is
  4.7.10 and the first bad kernel is 4.8-rc1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gustav 1998 F pulseaudio
   /dev/snd/controlC1:  gustav 1998 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Nov 17 22:01:52 2016
  HibernationDevice: RESUME=UUID=d7a5213f-0285-4708-9e97-2486aec53935
  InstallationDate: Installed on 2016-09-15 (63 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 004: ID 1bcf:28ae Sunplus Innovation Technology Inc. Laptop 
Integrated Webcam HD
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=15f681e4-0a4a-4613-8810-ba7535bfa0a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (22 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading

[Brad Figg]

** No longer affects: linux (Ubuntu Precise)

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

Title:
  [Hyper-V] netvsc: fix incorrect receive checksum offloading

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  The Hyper-V netvsc driver was looking at the incorrect status bits
  in the checksum info. It was setting the receive checksum unnecessary
  flag based on the IP header checksum being correct. The checksum
  flag is skb is about TCP and UDP checksum status. Because of this
  bug, any packet received with bad TCP checksum would be passed
  up the stack and to the application causing data corruption.
  The problem is reproducible via netcat and netem.

  This had a side effect of not doing receive checksum offload
  on IPv6. The driver was also also always doing checksum offload
  independent of the checksum setting done via ethtool.

  Signed-off-by: Stephen Hemminger 

  https://patchwork.ozlabs.org/patch/685660/

  When this patch is committed I will include the commit ID in this bug.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1618550] Re: [HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

[Arto Makkonen]

Still there in upstream 4.9-rc8

** Tags removed: kernel-bug-exists-upstream-4.9-rc3
** Tags added: kernel-bug-exists-upstream-4.9-rc8

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

Title:
  [HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My HP notebook won't wake from suspend with 16.04 LTS, waited for the
  latest 4.4.0-36 kernel update before reporting this bug. Computer goes
  to suspend, but attempts to wake it up just start the fan (and HDD)
  while the display remains black.

  Also tested this with the mainline upstream kernel
  4.8.0-040800rc3-generic. With this version there was different
  behaviour but still a bug: the display woke up but Ubuntu was very
  unstable, did not connect to Wifi and the GUI froze very soon after
  resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   3449 F pulseaudio
   /dev/snd/controlC1:  arto   3449 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 30 19:42:38 2016
  HibernationDevice: RESUME=UUID=8b70a4a1-df29-4f51-9b65-c2a17b4361a2
  InstallationDate: Installed on 2015-09-18 (347 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=c1e1c032-887a-44c8-b4d2-0850b57082e8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-15 (15 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097610405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

[David Jordan]

Just tested 1.161.1 in yakkety-proposed and can confirm it fixes the
issue.

** Tags added: verification-done

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

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1643341] Re: Unexpected shutdown

[Sam_]

Still no luck with recent updated 
Linux version 4.4.0-53-generic (buildd@lcy01-28) (gcc version 5.4.0 20160609 
(Ubuntu 5.4.0-6ubuntu1~16.04.4))

** Attachment added: "kernlog-53"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643341/+attachment/4788676/+files/kernlog-53

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

Title:
  Unexpected shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens twice in between a short time, 2-5 minutes, after the computer 
was turned on and Ubuntu desktop has started.
  It never happens a third time.
  From Ubuntu desktop, the cooler starts to run, a shutdown dialog with four 
options appears and computer turns off.
  I turn it on again and watch the same procedure happen again.
  I turn it on the third time, all is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68 and 4.4.0-49.70
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zootie 1897 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov 20 17:19:01 2016
  HibernationDevice: RESUME=UUID=6a848b08-24f4-499b-8281-8ba10097226d
  InstallationDate: Installed on 2016-11-02 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160823)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 5986:055c Acer, Inc
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=31f6cc2f-d9df-473c-be2d-fd1abf719500 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RB
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/16/2015:svnNotebook:pnW65_W67RB:pvrNotApplicable:rvnNotebook:rnW65_W67RB:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65_W67RB
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647937] Re: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Daniel Lee]

Thanks for the reply. 
Problem fixed by using USB stick & run boot-repair.

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

Title:
  package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  update software haftway freezed, forced shutdown computer then unable
  to boot.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  daniel 1645 F pulseaudio
   /dev/snd/controlC0:  daniel 1645 F pulseaudio
  Date: Wed Dec  7 13:52:36 2016
  Df:
   Filesystem 1K-blocksUsed Available Use% Mounted on
   /dev/sdb3   50821796 5914916  42302236  13% /
   udev 5067924   0   5067924   0% /dev
   tmpfs10165129920   1006592   1% /run
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=993d82eb-8ad2-4d23-90cb-f5dd2c2c6363
  InstallationDate: Installed on 2016-12-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 8740w (QR933US#AB4)
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=93b795f6-e46a-4246-9cd1-c72e162a4fee ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: linux
  Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.60
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.32
  dmi.chassis.asset.tag: CNF3454B7N
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.60:bd11/10/2015:svnHewlett-Packard:pnHPEliteBook8740w(QR933US#AB4):pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w (QR933US#AB4)
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642709] Re: Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

[Justin King-Lacroix]

** Tags added: verification-done

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

Title:
  Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1630970] Re: crypto/vmx/p8_ghash memory corruption

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  crypto/vmx/p8_ghash memory corruption

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  That bug was reported on the linux-crypto mailing list by Jan Stancek.
  The bug is not easily reproduced on Xenial because the crypto API test
  manager is not enabled and the hash test that exorcises this bug is
  not present on the Xenial kernel.

  ---
  Hi,

  I'm chasing a memory corruption with 4.8-rc7 as I'm observing random Oopses
  on ppc BE/LE systems (lpars, KVM guests). About 30% of issues is that
  module list gets corrupted, and "cat /proc/modules" or "lsmod" triggers
  an Oops, for example:

  [   88.486041] Unable to handle kernel paging request for data at address 
0x0020
  ...
  [   88.487658] NIP [c020f820] m_show+0xa0/0x240
  [   88.487689] LR [c020f834] m_show+0xb4/0x240
  [   88.487719] Call Trace:
  [   88.487736] [c004b605bbb0] [c020f834] m_show+0xb4/0x240 
(unreliable)
  [   88.487796] [c004b605bc50] [c045e73c] seq_read+0x36c/0x520
  [   88.487843] [c004b605bcf0] [c04e1014] proc_reg_read+0x84/0x120
  [   88.487889] [c004b605bd30] [c040df88] vfs_read+0xf8/0x380
  [   88.487934] [c004b605bde0] [c040fd40] SyS_read+0x60/0x110
  [   88.487981] [c004b605be30] [c0009590] system_call+0x38/0xec

  0x20 offset is module_use->source, module_use is NULL because 
module.source_list
  gets corrupted.

  The source of corruption appears to originate from a 'ahash' test for
  p8_ghash:

  cryptomgr_test
   alg_test
alg_test_hash
 test_hash
  __test_hash
   ahash_partial_update
shash_async_export
 memcpy

  With some extra traces [1], I'm seeing that ahash_partial_update() allocates 
56 bytes
  for 'state', and then crypto_ahash_export() writes 76 bytes into it:

  [5.970887] __test_hash alg name p8_ghash, result: c4333ac0, key: 
c004b860a500, req: c004b860a380
  [5.970963] state: c4333f00, statesize: 56
  [5.970995] shash_default_export memcpy c4333f00 c004b860a3e0, 
len: 76

  This seems to directly correspond with:
p8_ghash_alg.descsize = sizeof(struct p8_ghash_desc_ctx) == 56
shash_tfm->descsize = sizeof(struct p8_ghash_desc_ctx) + 
crypto_shash_descsize(fallback) == 56 + 20
  where 20 is presumably coming from "ghash_alg.descsize".

  My gut feeling was that these 2 should match, but I'd love to hear
  what crypto people think.

  Thank you,
  Jan
  ---

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642709] Re: Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

[Justin King-Lacroix]

s/appropriate/requested/

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

Title:
  Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642709] Re: Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

[Justin King-Lacroix]

I can confirm that this contains the appropriate firmware file.

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

Title:
  Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1646547] Re: nvidia-367.57 with kernel 4.4.0-51-generic won't boot

[Brendan]

** Description changed:

  Pretty much identical to bug 1642400 and bug 1638990 except that this
  behavior also happens with the most recent Xenial kernel,
  4.4.0-51-generic.
  
  If I boot into recovery mode on 4.4.0-51-generic, mount the filesystem as 
read/write, start networking, the resume normal boot, I can finally get into my 
window manager. But if I reboot and let
  GRUB handle boot normally, it doesn't even let me enter my encryption 
passphrase. Just sits at a blinking cursor.
  
  Switching back to nouveau works, but after reinstalling 367.57, the
  behavior returns and the aforementioned steps have to be followed.
  
+ Holding shift doesn't affect the outcome.
+ 
  Ubuntu 4.4.0-51.72-generic 4.4.30
  
  :~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  :~$ apt-cache policy linux-image-4.4.0-51-generic
  linux-image-4.4.0-51-generic:
-   Installed: 4.4.0-51.72
-   Candidate: 4.4.0-51.72
-   Version table:
-  *** 4.4.0-51.72 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
+   Installed: 4.4.0-51.72
+   Candidate: 4.4.0-51.72
+   Version table:
+  *** 4.4.0-51.72 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  
  I expect that I should be able to boot normally with nvidia drivers,
  without any special steps to boot. But instead, I just get a blinking
  cursor before I can even unlock my encrypted drive.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  lost   4789 F pulseaudio
-  /dev/snd/controlC0:  lost   4789 F pulseaudio
-  /dev/snd/controlC2:  lost   4789 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  lost   4789 F pulseaudio
+  /dev/snd/controlC0:  lost   4789 F pulseaudio
+  /dev/snd/controlC2:  lost   4789 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec  1 10:48:04 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (29 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic 
root=/dev/mapper/xubuntu--vg-root ro recovery nomodeset
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-51-generic N/A
-  linux-backports-modules-4.4.0-51-generic  N/A
-  linux-firmware1.157.5
+  linux-restricted-modules-4.4.0-51-generic N/A
+  linux-backports-modules-4.4.0-51-generic  N/A
+  linux-firmware1.157.5
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

Title:
  nvidia-367.57 with kernel 4.4.0-51-generic won't boot

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Pretty much identical to bug 1642400 and bug 1638990 except that this
  behavior also happens with the most recent Xenial kernel,
  4.4.0-51-generic.

  If I boot into recovery mode on 4.4.0-51-generic, mount the filesystem as 
read/write, start networking, the resume normal boot, I can finally get into my 
window manager. But if I reboot and let
  GRUB handle boot normally, it doesn't even let me enter my encryption 
passphrase. Just sits at a blinking cursor.

  Switching back to nouveau works, but after reinstalling 367.57, the
  behavior returns and the aforementioned 

[Kernel-packages] [Bug 1648017] Re: linux: 4.4.0-54.75 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Description changed:

  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase-changed:Wednesday, 07. December 2016 10:02 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 07. December 2016 16:33 UTC

** Description changed:

  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 07. December 2016 16:33 UTC
+ phase: Uploaded

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

Title:
  linux: 4.4.0-54.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-54.75 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648017/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648142] [NEW] nvidia-367.57 with kernel 4.4.0-53-generic won't boot

[Brendan]

Public bug reported:

Pretty much identical to bug 1642400, bug 1638990, and bug 1646547
except that this behavior also happens with the most recent Xenial
kernel, 4.4.0-53-generic.

If I boot into recovery mode on 4.4.0-53-generic, mount the filesystem as 
read/write, start networking, the resume normal boot, I can finally get into my 
window manager. But if I reboot and let
GRUB handle boot normally, it doesn't even let me enter my encryption 
passphrase. Just sits at a blinking cursor.

Switching back to nouveau works, but after reinstalling 367.57, the
behavior returns and the aforementioned steps have to be followed.

Holding shift doesn't affect the outcome.

Ubuntu 4.4.0-53.74-generic 4.4.30

~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

~$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 4.4.0.53.56
  Candidate: 4.4.0.53.56
  Version table:
 *** 4.4.0.53.56 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 4.4.0.21.22 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

I expect that I should be able to boot normally with nvidia drivers,
without any special steps to boot. But instead, I just get a blinking
cursor before I can even unlock my encrypted drive.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.53.56
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  lost   4106 F pulseaudio
 /dev/snd/pcmC1D0p:   lost   4106 F...m pulseaudio
 /dev/snd/controlC1:  lost   4106 F pulseaudio
 /dev/snd/controlC0:  lost   4106 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Dec  7 10:19:46 2016
HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
InstallationDate: Installed on 2016-11-01 (35 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 11361Q0
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 
root=/dev/mapper/xubuntu--vg-root ro recovery nomodeset
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-53-generic N/A
 linux-backports-modules-4.4.0-53-generic  N/A
 linux-firmware1.157.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: A3KT57AUS
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: 573921
dmi.chassis.type: 7
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
dmi.product.name: 11361Q0
dmi.product.version: ThinkStation C30
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: nvidia-graphics-drivers-367 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug boot encryption lvm nvidia xenial

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1648142/+attachment/4788626/+files/lspci-vnvn.log

** Also affects: nvidia-graphics-drivers-367 (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Pretty much identical to bug 1642400, bug 1638990, and bug 1646547
  except that this behavior also happens with the most recent Xenial
  kernel, 4.4.0-53-generic.
  
  If I boot into recovery mode on 4.4.0-53-generic, mount the filesystem as 
read/write, start networking, the resume normal boot, I can finally get into my 
window manager. But if I reboot and let
  GRUB handle boot normally, it doesn't even let me enter my encryption 
passphrase. Just sits at a blinking cursor.
  
  Switching back to nouveau works, but after reinstalling 367.57, the
  behavior returns and the aforementioned steps have to be followed.
  
+ Holding shift doesn't affect the outcome.
+ 
  Ubuntu 4.4.0-53.74-generic 4.4.30
  
  ~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  ~$ apt-cache policy linux-image-generic
  linux-image-generic:
-   Installed: 4.4.0.53.56
-   Candidate: 4.4.0.53.56
-   Version table:
-  *** 4.4.0.53.56 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  4.4.0.21.22 500
- 

[Kernel-packages] [Bug 1648142] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  nvidia-367.57 with kernel 4.4.0-53-generic won't boot

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New

Bug description:
  Pretty much identical to bug 1642400, bug 1638990, and bug 1646547
  except that this behavior also happens with the most recent Xenial
  kernel, 4.4.0-53-generic.

  If I boot into recovery mode on 4.4.0-53-generic, mount the filesystem as 
read/write, start networking, the resume normal boot, I can finally get into my 
window manager. But if I reboot and let
  GRUB handle boot normally, it doesn't even let me enter my encryption 
passphrase. Just sits at a blinking cursor.

  Switching back to nouveau works, but after reinstalling 367.57, the
  behavior returns and the aforementioned steps have to be followed.

  Holding shift doesn't affect the outcome.

  Ubuntu 4.4.0-53.74-generic 4.4.30

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ~$ apt-cache policy linux-image-generic
  linux-image-generic:
    Installed: 4.4.0.53.56
    Candidate: 4.4.0.53.56
    Version table:
   *** 4.4.0.53.56 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.4.0.21.22 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I expect that I should be able to boot normally with nvidia drivers,
  without any special steps to boot. But instead, I just get a blinking
  cursor before I can even unlock my encrypted drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.53.56
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   4106 F pulseaudio
   /dev/snd/pcmC1D0p:   lost   4106 F...m pulseaudio
   /dev/snd/controlC1:  lost   4106 F pulseaudio
   /dev/snd/controlC0:  lost   4106 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Dec  7 10:19:46 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (35 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 
root=/dev/mapper/xubuntu--vg-root ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log

[Manisha Luthra]

facing same issue with
Linux kernel 4.8.10-040810-generic on Lenovo carbon x1 + one link dock
also system freezes after sometime, from this only a restart helps

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

Title:
  cdc_ether fills kernel log

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X1 4th gen with a dock attached:

  [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped
  [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped

  
  The USB Ethernet device would warn occasionally under the 4.4 kernel. Under 
the 4.8 kernel, it spams my kernel log so much that I don't get anything else.

  $ uname -a
  Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  joel@aurora ~ 
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1646868] Re: Installing Kernel 3.13.0-85 (and further versions) distorts video on Intel Corporation Xeon E3-1200

[Joseph Salisbury]

Thanks for testing!  This bug should be resolved by applying the latest
updates.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  Installing Kernel 3.13.0-85 (and further versions) distorts video on
  Intel Corporation Xeon E3-1200

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  The installation of linux-image-3.13.0-85 messed up my video. The
  upper left corner of the screen works fine, but as you get to the
  right, the images wobble and renders out of sync. Running an old
  version of the kernel solved the issue, that is why I think this image
  is the culprit.

  I am running Ubuntu 14.04. The computer has an intel card:

  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200
  v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

  This is a video of the situation:

  https://www.youtube.com/watch?v=k6vF7iRcg6w

  
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gavox  2153 F pulseaudio
   /dev/snd/controlC1:  gavox  2153 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-01-24 (1043 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020 AIO
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-88-generic 
root=UUID=769b2ef2-08f8-4ea5-9848-1c970b3d62cd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-88-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-08-05 (849 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0V8DVD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/13/2013:svnDellInc.:pnOptiPlex9020AIO:pvr01:rvnDellInc.:rn0V8DVD:rvrA01:cvnDellInc.:ct13:cvr:
  dmi.product.name: OptiPlex 9020 AIO
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gavox  2153 F pulseaudio
   /dev/snd/controlC1:  gavox  2153 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-01-24 (1043 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020 AIO
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-88-generic 
root=UUID=769b2ef2-08f8-4ea5-9848-1c970b3d62cd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-88-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-08-05 (849 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0V8DVD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/13/2013:svnDellInc.:pnOptiPlex9020AIO:pvr01:rvnDellInc.:rn0V8DVD:rvrA01:cvnDellInc.:ct13:cvr:
  dmi.product.name: OptiPlex 9020 AIO
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1647802] Re: mpt3sas "Fix secure erase premature termination"

[Joseph Salisbury]

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

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Triaged

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

** Tags added: yakkety

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

Title:
  mpt3sas "Fix secure erase premature termination"

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  mpt3sas (and earlier mptsas/mpt2sas) as shipped doesn't support ata
  secure erase:

  /dev/disk/by-id/scsi-SATA_ST2000DL003-9VT1_XXX:
   Issuing SECURITY_ERASE command, password="Eins", user=user
  The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device.
  SECURITY_ERASE: Invalid argument

  
  This already appears to be fixed upstream: https://lkml.org/lkml/2016/12/1/47

  can we get it pulled into Ubuntu asap?

  Thanks

  
  $ lsb_release -rd
  Description:Ubuntu 16.10
  Release:16.10

  # uname -a
  Linux Riffraff 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647812] Re: HP EliteBook 725 G3 docked see only one DisplayPort attached

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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/v4.9-rc8

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

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

Title:
  HP EliteBook 725 G3 docked see only one DisplayPort attached

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  In that system only one display port is attached as seen by driver/X,
  but the image is displayed on both screen, but mirrored, when I switch
  to resolution 3840x1080 the image is stretched on both full hd
  displays. The drawback of this situation is when I want to stretch to
  fullscreen it stretches on both screens treated as one. This is not
  the case under Windows.

  Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 16384 x 16384
  eDP connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 
277mm x 156mm
 1366x768  60.06*+  40.04  
 1280x720  59.86  
 1152x768  59.78  
 1024x768  59.92  
 800x600   59.86  
 848x480   59.66  
 720x480   59.71  
 640x480   59.38  
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected 1920x1080+1366+0 (normal left inverted right x axis y 
axis) 509mm x 286mm
 1920x1080 60.00*+
 3840x1080 60.00  
 2560x1024 60.00  
 1680x1050 59.95  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x720  60.00  
 1024x768  60.00  
 800x600   60.32  
 640x480   59.94  
 720x400   70.08

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-signed-image-generic 4.8.0.22.31
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  6 19:19:26 2016
  MachineType: HP HP EliteBook 725 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N73 Ver. 01.12
  dmi.board.name: 8084
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 75.48
  dmi.chassis.asset.tag: 5CG6255NMM
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN73Ver.01.12:bd04/29/2016:svnHP:pnHPEliteBook725G3:pvr:rvnHP:rn8084:rvrKBCVersion75.48:cvnHP:ct10:cvr:
  dmi.product.name: HP EliteBook 725 G3
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647793] Re: Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

[Joseph Salisbury]

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

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Triaged

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

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

Title:
  Yakkety: arm64: CONFIG_ARM64_ERRATUM_845719 isn't enabled

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  CONFIG_ARM64_ERRATUM_845719 should have been enabled in Yakkety, but
  it isn't actually.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647887] Re: NVMe driver accidentally reverted to use GSI instead of MSIX

[Joseph Salisbury]

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

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

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

Title:
  NVMe driver accidentally reverted to use GSI instead of MSIX

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  These commit ids are in the xenial kernel branch.

  Commit 90c9712fbb388077b5e53069cae43f1acbb0102a ("NVMe: Always use MSI/MSI-x
  interrupts") changed the NVMe driver to always use MSI/MSI-x interrupts.
  However, later commit 30d6592fce71beabe18460252c3823747c4742f6 ("NVMe: Don't
  unmap controller registers on reset") as well as commit
  e9820e415895bdd9cfd21f87e80e3e0a10f131f0 ("UBUNTU: (fix) NVMe: Don't unmap
  controller registers on reset") accidentally reverted part of the original
  commit, which reverted the NVMe   driver to using GSI interrupts instead 
of
  always using MSI/MSI-x interrupts.

  The original commit was added because GSI interrupts do not always
  work for NVMe on all systems, while MSI/MSIX interrupts do work.  The
  accidental reversion of the code to use MSI/MSIX causes the NVMe
  driver to not work on some systems with NVMe drives.

  [Test Case]

  On a system with NVMe drive(s) that do not work (because the NVMe
  driver is using the non-working GSI interrupt, instead of MSI/MSIX
  interrupt), test the current xenial kernel, and some or all of the
  NVMe drives will fail to initialize.  Then test with the fixed kernel,
  and all the NVMe drives will initialize.

  [Regression Potential]

  If MSI/MSIX interrupts do not work with NVMe drives on some systems,
  this change would break those systems.  Those systems would also be
  broken by the upstream kernel, however; additionally, without MSI/MSIX
  support, such NVMe controllers would be significantly slower due to
  reliance on a single GSI for notification of completion of all I/O.
  So it's very unlikely there are any systems with NVMe controllers that
  do not support MSI/MSI-x.

  [Other Info]

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647937] Re: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Joseph Salisbury]

Can you boot by selecting the previous kernel from the GRUB menu?

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

** Tags added: kernel-da-key

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

Title:
  package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  update software haftway freezed, forced shutdown computer then unable
  to boot.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  daniel 1645 F pulseaudio
   /dev/snd/controlC0:  daniel 1645 F pulseaudio
  Date: Wed Dec  7 13:52:36 2016
  Df:
   Filesystem 1K-blocksUsed Available Use% Mounted on
   /dev/sdb3   50821796 5914916  42302236  13% /
   udev 5067924   0   5067924   0% /dev
   tmpfs10165129920   1006592   1% /run
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=993d82eb-8ad2-4d23-90cb-f5dd2c2c6363
  InstallationDate: Installed on 2016-12-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 8740w (QR933US#AB4)
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=93b795f6-e46a-4246-9cd1-c72e162a4fee ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: linux
  Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.60
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.32
  dmi.chassis.asset.tag: CNF3454B7N
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.60:bd11/10/2015:svnHewlett-Packard:pnHPEliteBook8740w(QR933US#AB4):pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w (QR933US#AB4)
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648090] Re: BT driver notworking

[Joseph Salisbury]

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

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/v4.9-rc8

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

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

Title:
  BT driver notworking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have recently installed Ubuntu 16.10,and now I am facing some issues
  with it.Ubuntu is getting frozen in between use and it's very slow
  now.Bluetooth is not working. I have tried restarting it updating it
  but no use.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-done-yakkety

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

Title:
  kdump-tools: Fails to load kdump kernel when /proc/cmdline contains
  double quotes

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Yakkety:
  Fix Committed

Bug description:
  [SRU justification]
  This fix is needed to avoid failure to load kdump-tools when one kernel boot 
parameter has double-quotes.

  [Impact]
  kdump functionality becomes unusable

  [Fix]
  Modify kdump-config to handle the presence of double-quotes in the cmdline

  [Test Case]
  Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT :

  \"acpi_osi=!Windows 2012\"
  $ sudo update-grub
  $ sudo reboot

  kdump-config will show the following error upon reboot :

  [   11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service': No s
  uch file or directory 
 
  [   11.602563] kdump-tools[1710]:  * failed to load kdump kernel  
 

  With this fix, the kdump-config command will run successfully

  [Regression]
  None expected. Fix is already in Zesty & Debian. Only one line added to the 
sed statement.

  [Original description of the problem]
  kdump-tools fails to load if one of the kernel parameter has double-quotes

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642709] Please test proposed package

[Adam Conrad]

Hello Justin, or anyone else affected,

Accepted linux-firmware into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.127.23 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Add i915/skl_guc_ver6.bin to linux-firmware in Trusty

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed

Bug description:
  Linux-firmware is missing the following i915 firmware files, required
  by the i915 driver in 4.4.0-47-generic:

  $ update-initramfs -k 4.4.0-47-generic -c
  W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module 
i915_bpo
  W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module 
i915_bpo

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1646197] Please test proposed package

[Adam Conrad]

Hello Seth, or anyone else affected,

Accepted linux-firmware into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.161.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Precise:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Released

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647048] Re: System freezes after login (NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s)

[misko]

What can I else do to find out what the kernel is doing while my computer does 
not respond? (can I turn the kernel or at least some of its modules to more 
verbose logging?)
btw: what does the "rubbish" in the kern.log mean? Does it indicate an error in 
the filesystem or SSD driver?  (or does it just mean that the meachine got 
unresponsive in the middle of writing to the disk?)

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

Title:
  System freezes after login (NMI watchdog: BUG: soft lockup - CPU#0
  stuck for 22s)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since I updated to kubuntu 16.10 I quite often have the situation that
  my laptop completely freezes after login in sddm (that means: while
  KDE is loading).

  During that time:
  - Fans run high
  - laptop is completely unuseable (no mouse or keyboard-input accepted, can't 
switch to other terminal, etc ...) - only a long press to the power-button 
helps .
  - network-connections break (tried to monitor the system remotely, but when 
the error occurs, also the ssh-connection fails)
  - the kern.log stops and contains only a few lines of rubbish:
  Dec  3 11:01:37 orbit kernel: [   18.951805] ACPI: \_SB_.PCI0.PEG0.PEGP: 
failed to evaluate _DSM
  Dec  3 11:01:37 orbit kernel: [   18.951808] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20160422/nsarguments-95)
  Dec  3 11:01:37 orbit kernel: [   18.951891] nouveau :01:00.0: DRM: 
suspending console...
  Dec  3 11:01:37 orbit kernel: [   18.951894] nouveau :01:00.0: DRM: 
suspending display...
  Dec  3 11:01:37 orbit kernel: [   18.951902] nouveau :01:00.0: DRM: 
evicting buffers...
  Dec  3 11:01:37 orbit kernel: [   18.960908] nouveau :01:00.0: DRM: 
waiting for kernel channels to go idle...
  Dec  3 11:01:37 orbit kernel: [   18.960935] nouveau :01:00.0: DRM: 
suspending client object trees...
  Dec  3 11:01:37 orbit kernel: [   18.961192] nouveau :01:00.0: DRM: 
suspending kernel object tree...
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  ...
  - installed and tested kernel-crashdump, but in this situation it is not 
triggered (or fails to write a coredump)
  - (once I tried to leave the machin alone for about 30 min, it does not 
recover...)

  As a last resort, I installed netconsole and captured the kernel.log
  on a remote machine, this revealed, that during the lookup, following
  "soft lockups" occur:

  [  107.926161] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[baloo_file:2491]
  [  107.926172] Modules linked in: vmnet(OE) vmw_vsock_vmci_transport vsock 
vmw_vmci vmmon(OE) ccm rfcomm bnep joydev acer_wmi sparse_keymap 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate arc4 intel_rapl_perf 
ath9k ath9k_common ath9k_hw ath input_leds mac80211 uvcvideo serio_raw 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 ath3k videobuf2_core btusb 
btrtl videodev btbcm rtsx_pci_ms btintel cfg80211 media snd_hda_codec_realtek 
bluetooth snd_hda_codec_generic lpc_ich memstick snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_seq_midi snd_pcm[  135.919531] NMI watchdog: BUG: 
soft lockup - CPU#0 stuck for 22s! [baloo_file:2491]
  [  135.919536] Modules linked in: vmnet(OE) vmw_vsock_vmci_transport vsock 
vmw_vmci vmmon(OE) ccm rfcomm bnep joydev acer_wmi sparse_keymap 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate arc4 

[Kernel-packages] [Bug 1646197] Please test proposed package

[Adam Conrad]

Hello Seth, or anyone else affected,

Accepted linux-firmware into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.127.23 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Precise:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Released

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1647826] Please test proposed package

[Adam Conrad]

Hello David, or anyone else affected,

Accepted linux-firmware into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.161.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Tim Gardner]

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Craig Magina (craig.magina)
   Status: In Progress

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648088] [NEW] linux - Memory Bandwidth Monitoring regression

[Tim Gardner]

Public bug reported:

Hi team,,

I have a customer, who tried to install Xenial or upgrade to 4.4 kernel with 
Trusty on our cloud platform(qemu 1.5.3), reports a defect. he complains that 
only  one cpu is successfully detected, other cpus is disabled if
he used 4.4 kernel. I tried to bisect Xenial kernel tree, and found that this 
bug was introduced by the following commit.

commit 31c2013e4ea2e594522980acc3d20e88664b19f1
Author: Thomas Gleixner 
Date:   Mon Feb 22 22:19:15 2016 +

x86/topology: Create logical package id

BugLink: http://bugs.launchpad.net/bugs/1397880

For per package oriented services we must be able to rely on the number of 
CPU
packages to be within bounds. Create a tracking facility, which

- calculates the number of possible packages depending on nr_cpu_ids
after boot

- makes sure that the package id is within the number of possible packages. 
If
  the apic id is outside we map it to a logical package id if there is 
enough
  space available.

Provide interfaces for drivers to query the mapping and do translations from
physcial to logical ids.

and then I backported 7b0501b1e7cddd32b265178e32d332bdfbb532d4 from
Linus tree to Xenial kernel, the issue goes away, so could we consider
to backport it to xenial kernel tree to solve this issue in next
release?

>From 7b0501b1e7cddd32b265178e32d332bdfbb532d4 Mon Sep 17 00:00:00 2001
From: Jiri Olsa 
Date: Mon, 15 Aug 2016 12:17:00 +0200
Subject: [PATCH] x86/smp: Fix __max_logical_packages value setup

Frank reported kernel panic when he disabled several cores in BIOS
via following option:

Thanks
Wei

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  linux - Memory Bandwidth Monitoring regression

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hi team,,

  I have a customer, who tried to install Xenial or upgrade to 4.4 kernel with 
Trusty on our cloud platform(qemu 1.5.3), reports a defect. he complains that 
only  one cpu is successfully detected, other cpus is disabled if
  he used 4.4 kernel. I tried to bisect Xenial kernel tree, and found that this 
bug was introduced by the following commit.

  commit 31c2013e4ea2e594522980acc3d20e88664b19f1
  Author: Thomas Gleixner 
  Date:   Mon Feb 22 22:19:15 2016 +

  x86/topology: Create logical package id

  BugLink: http://bugs.launchpad.net/bugs/1397880

  For per package oriented services we must be able to rely on the number 
of CPU
  packages to be within bounds. Create a tracking facility, which

  - calculates the number of possible packages depending on
  nr_cpu_ids after boot

  - makes sure that the package id is within the number of possible 
packages. If
the apic id is outside we map it to a logical package id if there is 
enough
space available.

  Provide interfaces for drivers to query the mapping and do translations 
from
  physcial to logical ids.

  and then I backported 7b0501b1e7cddd32b265178e32d332bdfbb532d4 from
  Linus tree to Xenial kernel, the issue goes away, so could we consider
  to backport it to xenial kernel tree to solve this issue in next
  release?

  From 7b0501b1e7cddd32b265178e32d332bdfbb532d4 Mon Sep 17 00:00:00 2001
  From: Jiri Olsa 
  Date: Mon, 15 Aug 2016 12:17:00 +0200
  Subject: [PATCH] x86/smp: Fix __max_logical_packages value setup

  Frank reported kernel panic when he disabled several cores in BIOS
  via following option:

  Thanks
  Wei

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1648090] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1648090

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  BT driver notworking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have recently installed Ubuntu 16.10,and now I am facing some issues
  with it.Ubuntu is getting frozen in between use and it's very slow
  now.Bluetooth is not working. I have tried restarting it updating it
  but no use.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp