date:20170525

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+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 1693673] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883840/+files/CurrentDmesg.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted

apport information

** Tags added: apport-collected xenial

** Description changed:

  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 May 26 12:21 seq
+  crw-rw 1 root audio 116, 33 May 26 12:21 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.6
+ Architecture: arm64
+ 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=f8faea1d-17bf-4c48-9b44-ca04875978b9
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb:
+  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: AppliedMicro X-Gene Mustang Board
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=vt220
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.8.0-53-generic N/A
+  linux-backports-modules-4.8.0-53-generic  N/A
+  linux-firmware1.157.10
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial
+ Uname: Linux 4.8.0-53-generic aarch64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: Feb 28 2017
+ dmi.bios.vendor: AppliedMicro
+ dmi.bios.version: 3.07.09
+ dmi.board.asset.tag: Not Specified
+ dmi.board.name: X-Gene Mustang Board
+ dmi.board.vendor: AppliedMicro
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: Not Specified
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: AppliedMicro
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
+ dmi.product.name: X-Gene Mustang Board
+ dmi.product.version: 1.0
+ dmi.sys.vendor: AppliedMicro

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1693673/+attachment/4883839/+files/CRDA.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

[Kernel-packages] [Bug 1693673] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883844/+files/ProcCpuinfoMinimal.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883845/+files/ProcInterrupts.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883843/+files/ProcCpuinfo.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1693673/+attachment/4883847/+files/UdevDb.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883841/+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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883848/+files/WifiSyslog.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1693673/+attachment/4883842/+files/Lspci.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883846/+files/ProcModules.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  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=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693677] Re: Bluetooth and wifi not working

Maybe this?
$ sudo modprobe wl

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

Title:
  Bluetooth and wifi not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Am unable to connect my laptop with any other devices using bluetooth
  and wifi. It does not show any device list eventhough it is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siddharth   1573 F pulseaudio
   /dev/snd/controlC0:  siddharth   1573 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 26 10:13:59 2017
  InstallationDate: Installed on 2017-04-12 (43 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
   
   ppp0  no wireless extensions.
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=718e2720-e3ad-4111-9b51-861762095f1c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 04XW3R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn04XW3R:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693677/+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 1686268] Re: Backlight brightness level not restored after reboot

It can't be reproduced once you changed the brightness via slider in
BIOS.

It should be reproduceable if the brightness was *never* touched in
BIOS.

Once the brightness is changed in BIOS, the issue can no longer be
reproduced regardless the brightness value.

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

Title:
  Backlight brightness level not restored after reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to report this, so feel free
  to move it elsewhere.

  It looks like the systemd-backlight service (/lib/systemd/system
  /systemd-backlight@.service) does not restore the brightness level
  (although it saves it before shut-down).

  However the following command does restore the saved brightness:

  sudo /lib/systemd/systemd-backlight load backlight:intel_backlight

  As a temporary solution to automate it at boot I am using the
  following line added to the root cron:

  @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight

  - Ubuntu 4.10.0-20.22-generic 4.10.8
  - Gnome 3.24

  Please, let me know if you need more info. Thanks.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 1540 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-04-12 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs

This patch solves the kernel panic issue and make rtl8723bs working:
https://www.spinics.net/lists/linux-wireless/msg162060.html

Let's just wait Linux kernel in Artful switch to 4.12.

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

Title:
  024C:B723 Need support for Realtek Wifi card rtl8723bs

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

Bug description:
  This device is appearing in some OEM machines.

  WORKAROUND: sudo apt-get install build-essential linux-headers-generic git
  git clone https://github.com/hadess/rtl8723as.git
  cd rtl8723as
  make
  sudo make install
  sudo depmod -a
  sudo modprobe r8723bs

  cat /sys/bus/sdio/devices/mmc1:0001:1/*
  0x07
  0xb723
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory
  sdio:c07v024CdB723
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory
  SDIO_CLASS=07
  SDIO_ID=024C:B723
  MODALIAS=sdio:c07v024CdB723
  0x024c

  WORKAROUND 2: Install this DKMS driver package:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files
  /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963
  InstallationDate: Installed on 2016-05-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc.
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer One S1002
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  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:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.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: 10/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.name: Popcorn
  dmi.board.vendor: Acer
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: One S1002
  dmi.product.version: 1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1581711/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

2017-05-25 Thread flux242

> If verification is not done by 5 working days from today, this fix
will be dropped from the source code, and this bug will be closed.

never go full retard, dude

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe-edge source package in Zesty:
  Fix Committed

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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

Re: [Kernel-packages] [Bug 1686268] Re: Backlight brightness level not restored after reboot

2017-05-25 Thread Domizio Demichelis

Mine was about half in the battery slider and 0 in the AC slider.

On Fri, May 26, 2017, 12:11 PM Mario Limonciello 
wrote:

> That sounds a little crazy that it can't reproduce in my opinion. When it
> "did" reproduce was the brightness at one of the extremes? Eg full high on
> shutdown or full low on shutdown?
>
> On Thu, May 25, 2017, 03:21 Kai-Heng Feng 
> wrote:
>
> > Mario, can you take a look?
> >
> > A quick summary:
> > 1. Boot the system.
> > 2. The value systemd-backlight read from intel backlight is 0.
> > 3. systemd-backlight restore the value it from
> /var/lib/systemd/backlight.
> > 4. Brightness value being overwritten to maximum value, 1500.
> >
> > After I changed the brightness slider in BIOS:
> > 1. Boot the system.
> > 2. The value systemd-backlight read from intel backlight is a sane value,
> > not 0 anymore.
> > 3. systemd-backlight restore the value it from
> /var/lib/systemd/backlight.
> > 4. profit.
> >
> > Restore defaults in BIOS cannot revert the behavior back to the bad one.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1686268
> >
> > Title:
> >   Backlight brightness level not restored after reboot
> >
> > To manage notifications about this bug go to:
> >
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686268
>
> Title:
>   Backlight brightness level not restored after reboot
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I am not sure if this is the right place to report this, so feel free
>   to move it elsewhere.
>
>   It looks like the systemd-backlight service (/lib/systemd/system
>   /systemd-backlight@.service) does not restore the brightness level
>   (although it saves it before shut-down).
>
>   However the following command does restore the saved brightness:
>
>   sudo /lib/systemd/systemd-backlight load backlight:intel_backlight
>
>   As a temporary solution to automate it at boot I am using the
>   following line added to the root cron:
>
>   @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight
>
>   - Ubuntu 4.10.0-20.22-generic 4.10.8
>   - Gnome 3.24
>
>   Please, let me know if you need more info. Thanks.
>   ---
>   ApportVersion: 2.20.4-0ubuntu4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  dd 1540 F pulseaudio
>   CurrentDesktop: GNOME
>   DistroRelease: Ubuntu 17.04
>   InstallationDate: Installed on 2017-04-12 (13 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170411)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 002: ID 8087:0a2b Intel Corp.
>Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Precision 5520
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed
> root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash
> vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-20-generic N/A
>linux-backports-modules-4.10.0-20-generic  N/A
>linux-firmware 1.164
>   Tags:  zesty
>   Uname: Linux 4.10.0-20-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 03/29/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.2.4
>   dmi.board.name: 06X96V
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.name: Precision 5520
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+subscriptions
>

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

Title:
  Backlight brightness level not restored after reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to report this, so feel free
  to move it elsewhere.

  It looks like the systemd-backlight service (/lib/systemd/system
  /systemd-backlight@.service) does not restore the brightness level
  (although it saves it before shut-down).

  However the following

Re: [Kernel-packages] [Bug 1686268] Re: Backlight brightness level not restored after reboot

2017-05-25 Thread Mario Limonciello

That sounds a little crazy that it can't reproduce in my opinion. When it
"did" reproduce was the brightness at one of the extremes? Eg full high on
shutdown or full low on shutdown?

On Thu, May 25, 2017, 03:21 Kai-Heng Feng 
wrote:

> Mario, can you take a look?
>
> A quick summary:
> 1. Boot the system.
> 2. The value systemd-backlight read from intel backlight is 0.
> 3. systemd-backlight restore the value it from /var/lib/systemd/backlight.
> 4. Brightness value being overwritten to maximum value, 1500.
>
> After I changed the brightness slider in BIOS:
> 1. Boot the system.
> 2. The value systemd-backlight read from intel backlight is a sane value,
> not 0 anymore.
> 3. systemd-backlight restore the value it from /var/lib/systemd/backlight.
> 4. profit.
>
> Restore defaults in BIOS cannot revert the behavior back to the bad one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686268
>
> Title:
>   Backlight brightness level not restored after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+subscriptions
>

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

Title:
  Backlight brightness level not restored after reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to report this, so feel free
  to move it elsewhere.

  It looks like the systemd-backlight service (/lib/systemd/system
  /systemd-backlight@.service) does not restore the brightness level
  (although it saves it before shut-down).

  However the following command does restore the saved brightness:

  sudo /lib/systemd/systemd-backlight load backlight:intel_backlight

  As a temporary solution to automate it at boot I am using the
  following line added to the root cron:

  @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight

  - Ubuntu 4.10.0-20.22-generic 4.10.8
  - Gnome 3.24

  Please, let me know if you need more info. Thanks.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 1540 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-04-12 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1693677] Status changed to Confirmed

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

Title:
  Bluetooth and wifi not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Am unable to connect my laptop with any other devices using bluetooth
  and wifi. It does not show any device list eventhough it is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siddharth   1573 F pulseaudio
   /dev/snd/controlC0:  siddharth   1573 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 26 10:13:59 2017
  InstallationDate: Installed on 2017-04-12 (43 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
   
   ppp0  no wireless extensions.
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=718e2720-e3ad-4111-9b51-861762095f1c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 04XW3R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn04XW3R:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693677/+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 1693677] [NEW] Bluetooth and wifi not working

2017-05-25 Thread Siddharth

Public bug reported:

Am unable to connect my laptop with any other devices using bluetooth
and wifi. It does not show any device list eventhough it is turned on.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  siddharth   1573 F pulseaudio
 /dev/snd/controlC0:  siddharth   1573 F pulseaudio
CurrentDesktop: Unity
Date: Fri May 26 10:13:59 2017
InstallationDate: Installed on 2017-04-12 (43 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp7s0no wireless extensions.
 
 lono wireless extensions.
 
 ppp0  no wireless extensions.
MachineType: Dell Inc. Inspiron 3543
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=718e2720-e3ad-4111-9b51-861762095f1c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-78-generic N/A
 linux-backports-modules-4.4.0-78-generic  N/A
 linux-firmware1.157.10
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 04XW3R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn04XW3R:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3543
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bluetooth and wifi not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Am unable to connect my laptop with any other devices using bluetooth
  and wifi. It does not show any device list eventhough it is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siddharth   1573 F pulseaudio
   /dev/snd/controlC0:  siddharth   1573 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 26 10:13:59 2017
  InstallationDate: Installed on 2017-04-12 (43 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
   
   ppp0  no wireless extensions.
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=718e2720-e3ad-4111-9b51-861762095f1c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 04XW3R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn04XW3R:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693677/+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 1693673] Missing required logs.

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

apport-collect 1693673

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

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted

** Attachment added: "Bootlog for Ubuntu Zesty"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+attachment/4883802/+files/Mustang_Ubuntu_Zesty.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  New

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted

The issue can be fixed by applying below patch:
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/ethernet/apm?id=8aba8474181070a30f56ffd19359f5d80665175e

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

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  New

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted

** Attachment added: "Bootlog for Ubuntu Yakkety"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+attachment/4883801/+files/Mustang_Ubuntu_Yakkety.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  New

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693673] [NEW] Ubuntu 16.04 IOB Error when the Mustang board rebooted

Public bug reported:

When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
[   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction error
[   38.199164] xgene-edac 7880.edac: IOB BA write response error
[   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
[   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.

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

** Attachment added: "Bootlog for Ubuntu Xenial"
   
https://bugs.launchpad.net/bugs/1693673/+attachment/4883800/+files/Mustang_Ubuntu_Xenial.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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

Status in linux package in Ubuntu:
  New

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+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 1693345] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]

2017-05-25 Thread Nabeel Omer

The upstream fixed this problem, but now I'm seeing another suspicious entry in 
the dmesg log:
[ 1923.628750] [ cut here ]
[ 1923.628837] WARNING: CPU: 0 PID: 0 at 
/home/kernel/COD/linux/net/mac80211/rx.c:630 ieee80211_rx_napi+0x905/0xa20 
[mac80211]
[ 1923.628842] Modules linked in: rtsx_usb_ms memstick rtsx_usb_sdmmc rtsx_usb 
ccm rfcomm bnep nls_iso8859_1 hid_rmi cmdlinepart rmi_core joydev 
intel_spi_platform intel_spi spi_nor intel_rapl mtd x86_pkg_temp_thermal 
intel_powerclamp kvm_intel dell_wmi sparse_keymap kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel arc4 pcbc dell_laptop 
dell_smbios ath9k dcdbas ath9k_common dell_smm_hwmon snd_hda_codec_hdmi 
snd_hda_codec_realtek aesni_intel snd_soc_rt5640 snd_hda_codec_generic 
aes_x86_64 snd_soc_rl6231 crypto_simd glue_helper ath9k_hw snd_hda_intel 
snd_soc_core uvcvideo snd_hda_codec cryptd ath snd_hda_core intel_cstate 
videobuf2_vmalloc snd_hwdep videobuf2_memops videobuf2_v4l2 snd_compress 
intel_rapl_perf ac97_bus snd_seq_midi mac80211 videobuf2_core snd_pcm_dmaengine 
snd_seq_midi_event
[ 1923.628944]  snd_rawmidi input_leds videodev ath3k hid_multitouch serio_raw 
cfg80211 btusb snd_pcm media snd_seq btrtl btbcm btintel snd_seq_device 
elan_i2c bluetooth snd_timer snd ecdh_generic soundcore mei_me shpchp lpc_ich 
mei snd_soc_sst_acpi i2c_designware_platform dw_dmac snd_soc_sst_match 
i2c_designware_core dw_dmac_core spi_pxa2xx_platform 8250_dw dell_rbtn mac_hid 
ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG 
xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp coretemp nf_conntrack parport_pc libcrc32c 
ppdev iptable_filter lp parport ip_tables x_tables autofs4
[ 1923.629067]  usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 ahci drm libahci mii wmi video sdhci_acpi sdhci 
i2c_hid hid
[ 1923.629108] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW   
4.12.0-041200rc2-generic #201705212331
[ 1923.629113] Hardware name: Dell Inc. Inspiron 3542/0KHNVP, BIOS A03 
05/27/2014
[ 1923.629119] task: 8c2104c0 task.stack: 8c20
[ 1923.629179] RIP: 0010:ieee80211_rx_napi+0x905/0xa20 [mac80211]
[ 1923.629185] RSP: 0018:97eddfa03d18 EFLAGS: 00010246
[ 1923.629196] RAX: 0001 RBX: 97edd4876a00 RCX: 97edd03fc1a8
[ 1923.629201] RDX: 0004 RSI: c09c8000 RDI: 97edcfac0780
[ 1923.629206] RBP: 97eddfa03de8 R08:  R09: 97eddfda5000
[ 1923.629211] R10:  R11:  R12: 
[ 1923.629216] R13:  R14: 97edd12cd9b8 R15: 97edcfac0780
[ 1923.629223] FS:  () GS:97eddfa0() 
knlGS:
[ 1923.629229] CS:  0010 DS:  ES:  CR0: 80050033
[ 1923.629234] CR2: 7ff82a858000 CR3: 0001b6a09000 CR4: 001406f0
[ 1923.629240] Call Trace:
[ 1923.629246]  
[ 1923.629263]  ? map_single+0x32/0x80
[ 1923.629272]  ? __netdev_alloc_skb+0xc8/0x120
[ 1923.629284]  ? ath9k_cmn_rx_skb_postprocess+0x4c/0x130 [ath9k_common]
[ 1923.629293]  ? swiotlb_tbl_unmap_single+0xf4/0x120
[ 1923.629311]  ath_rx_tasklet+0xacc/0xff0 [ath9k]
[ 1923.629331]  ath9k_tasklet+0x1e4/0x250 [ath9k]
[ 1923.629348]  tasklet_action+0x5e/0x110
[ 1923.629357]  __do_softirq+0x104/0x28f
[ 1923.629368]  irq_exit+0xb6/0xc0
[ 1923.629376]  do_IRQ+0x4f/0xd0
[ 1923.629384]  common_interrupt+0x89/0x89
[ 1923.629394] RIP: 0010:cpuidle_enter_state+0x121/0x2c0
[ 1923.629400] RSP: 0018:8c203dd0 EFLAGS: 0246 ORIG_RAX: 
ff5e
[ 1923.629407] RAX:  RBX: 0004 RCX: 001f
[ 1923.629412] RDX: 01bfe1340439 RSI: 97eddfa19718 RDI: 
[ 1923.629418] RBP: 8c203e08 R08: 0337 R09: 0018
[ 1923.629423] R10: 8c203da0 R11: 00fa R12: 97eddfa24900
[ 1923.629429] R13: 8c387a98 R14: 01bfe1340439 R15: 8c387a80
[ 1923.629434]  
[ 1923.629449]  cpuidle_enter+0x17/0x20
[ 1923.629458]  call_cpuidle+0x23/0x40
[ 1923.629467]  do_idle+0x194/0x200
[ 1923.629476]  cpu_startup_entry+0x71/0x80
[ 1923.629484]  rest_init+0x77/0x80
[ 1923.629493]  start_kernel+0x44b/0x46c
[ 1923.629502]  ? early_idt_handler_array+0x120/0x120
[ 1923.629509]  x86_64_start_reservations+0x29/0x2b
[ 1923.629517]  x86_64_start_kernel+0x154/0x177
[ 1923.629527]  secondary_startup_64+0x9f/0x9f
[ 1923.629534] Code: ff 48 8b 95 70 ff ff ff 4c 8b ab d8 00 00 00 4c 8b b2 d8 
00 00 00 e9 8c f9 ff ff 48 89 de 4c 89 ff e8 50 1d fe ff e9 d0 f9 ff ff <0f> ff 
48 89 df e8 71 2f 45 cb e9 d5 f7 ff ff 0f ff e9 c6 f7 ff 
[ 1923.629657] ---[ end trace affb4b11847df853 ]---

Should I file a new bug report for this?


**

[Kernel-packages] [Bug 1693229] starmie-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.11.0-4.9-generic/starmie-kernel__4.11.0-4.9__2017-05-26_03-57-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/1693229

Title:
  linux: 4.11.0-4.9 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.11.0-4.9 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
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1693229/+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 1664312] Re: Update ENA driver to 1.1.2 from net-next

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  Update ENA driver to 1.1.2 from net-next

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  "net/ena 1.1.2 changeset" recently merged into linux/net-next:
  http://marc.info/?l=linux-netdev=148664692122357=2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664312/+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 1686519] Re: POWER9: CAPI2 enablement

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  POWER9: CAPI2 enablement

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2017-04-26 
15:08:18 ==
  Hello,

  We would like to include CAPI2  support on the CXL device driver on
  Zesty kernel.

   The coherent accelerator interface is designed to allow the coherent
  connection of accelerators (FPGAs and other devices) to a  POWER
  system. These devices need to adhere to the Coherent Accelerator
  Interface Architecture (CAIA).

  
This PSL Version 9 provides new features such as:
  * Interaction with the nest MMU on the P9 chip.
  * Native DMA support.
  * Supports sending ASB_Notify messages for host thread wakeup.
  * Supports Atomic operations.

  == Comment: #3 - Breno Henrique Leitao  - 2017-04-26 
15:21:25 ==
  These are the patches we need:

  f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code
  d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush 
during device shutdown
  abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls
  64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific 
functions
  bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service 
layer
  6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct 
associated with a context
  66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in 
bare-metal environment.
  aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image
  39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1686519/+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 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+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 1580272] Re: i915-bpo crashes on external hdmi input

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  i915-bpo crashes on external hdmi input

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  This issue happens when plugging in an external HDMI projector in
  mirrored mode.

  To reproduce this issue:
  1) Plug in external HDMI monitor
  2) Set mirrored displays
  3) Unplug HDMI
  4) check dmesg for warnings

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mark   4296 F pulseaudio
  Date: Tue May 10 10:25:07 2016
  InstallationDate: Installed on 2016-05-02 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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 0a5c:6410 Broadcom Corp.
   Bus 001 Device 004: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580272/+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 1677319] Re: Support low-pin-count devices on Hisilicon SoCs

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  Support low-pin-count devices on Hisilicon SoCs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The HiSilicon Hip06/Hip07 SoCs include a low-pin-count (LPC) host controller. 
The Linux kernel needs support for this interface to use attached devices, such 
as a UART and the IPMI system interface.

  [Test Case]
  Boot up a HiSilicon D05 system, confirm that the following command returns 
w/o error:

  $ sudo ipmitool lan print

  [Regression Risk]
  The proposed patchset only enables LIBIO for arm64, so the greatest 
regression risk is to other arm64 systems. We have mitigated that by testing on 
a wide range of hardware (all certified arm64 servers + some in-devel systems). 
There remains some arch-independent changes to the generic PCI code. The patch 
"PCI: Restore codepath for !CONFIG_LIBIO" was added to mitigate the risk to 
other architectures by restoring the previous code for those architectures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677319/+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 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  [Zesty] d-i: replace msm_emac with qcom_emac

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 
drivers/net/ethernet/qualcomm/emac/

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+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 1686061] Re: Precision Rack failed to resume from S4

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Precision Rack failed to resume from S4

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

Bug description:
  On a Precision Rack with two CPUs, it failed to resume from S4 at ~70%
  rate.

  These two commits can fix the issue:

  commit 406f992e4a372dafbe3c2cff7efbb2002a5c8ebd
  Author: Rafael J. Wysocki 
  Date:   Thu Jul 14 03:55:23 2016 +0200

  x86 / hibernate: Use hlt_play_dead() when resuming from
  hibernation

  
  commit e4630fdd47637168927905983205d7b7c5c08c09
  Author: Rafael J. Wysocki 
  Date:   Mon Aug 8 15:31:31 2016 +0200

  x86/power/64: Always create temporary identity mapping correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1686061/+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 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev=149200746116365
  2: http://marc.info/?l=linux-netdev=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe-edge source package in Zesty:
  Fix Committed

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1689856] Re: perf: qcom: Add L3 cache PMU driver

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  perf: qcom: Add L3 cache PMU driver

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Without this driver, users of Qualcomm QDF2400 servers will be unable to 
profile L3 cache events.

  [Test case]
  ubuntu@ubuntu:~$ sudo perf list | grep l3cache | wc -l
  84

  Without this driver, there are 0.

  [Regression Risk]
  This is a new driver that is only used on these servers, so the regression 
risk is pretty isolated to this platform. To mitigate the risk there, I ran 
perf_fuzzer on that system and verified that it survived. Note: I did this 
testing w/ a workaround for LP: #1689855 applied, to avoid hangs caused by a 
hardware issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689856/+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 1689818] Re: tty: pl011: fix earlycon work-around for QDF2400 erratum 44

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-zesty

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

Title:
tty: pl011: fix earlycon work-around for QDF2400 erratum 44

Status in linux package in Ubuntu:
Incomplete

Bug description:
[Impact]
The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44
sets the qdf2400_e44_present" global variable if the work-around is needed.
However, this check does not happen until after earlycon is initialized, which
means the work-around is not used, and the console hangs as soon as it displays
one character.

[Test Case]
Enable earlycon and boot the kernel. Please see comments below for detailed
test results on QDF2400 system.

[Regression Potential]
This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

[Fix]

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
=tty-testing=5a0722b898f851b9ef108ea7babc529e4efc773d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689818/+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 1687512] Re: Kernel panics on Xenial when using cgroups and strict CFS limits

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Kernel panics on Xenial when using cgroups and strict CFS limits

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

Bug description:
  SRU Justification
  -

  [Impact]
  Apache Mesos and Kubernetes workloads on Xenial cause a panic
  (NULL pointer dereference) in the completely fair scheduler.

  These panics are in pick_next_entity and include pick_next_task_fair
  in the call stack.

  [Fix]
  Cherry-picking both
  754bd598be9bbc953bc709a9e8ed7f3188bfb9d7
  (http://lkml.kernel.org/r/146608183552.21905.15924473394414832071.stgit@buzz)
  and
  094f469172e00d6ab0a3130b0e01c83b3cf3a98d
  (http://lkml.kernel.org/r/146608182119.21870.8439834428248129633.stgit@buzz)
  fix the crash.
  They appear to be intended as a series - they were posted to LKML at
  the same time.

  [Testcase]
  The fix has been validated by the user who reported the bug

  Bug description
  ---

  We see a number of kernel panics on servers running Apache Mesos using
  cgroups with small (0.1-0.2) cpu limits.

  These all appear as NULL pointer dereferences in and around
  pick_next_entity and pick_next_task_fair, for example:

  [24334.493331] BUG: unable to handle kernel NULL pointer dereference at 
0050
  [24334.501611] IP: [] pick_next_entity+0x7f/0x160
  [24334.507868] PGD 3eacfa067 PUD 3eacfb067 PMD 0
  [24334.512806] Oops:  [#1] SMP
  [24334.516420] Modules linked in: ipvlan xt_nat xt_tcpudp veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs tcp_diag 
inet_diag nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache dm_crypt 
ppdev input_leds mac_hid i2c_piix4 8250_fintek parport_pc pvpanic parport 
serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi
  [24334.576359] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.0-66-generic 
#87~14.04.1-Ubuntu
  [24334.584748] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [24334.594188] task: 8803ee671c00 ti: 8803ee67c000 task.ti: 
8803ee67c000
  [24334.601799] RIP: 0010:[] [] 
pick_next_entity+0x7f/0x160
  [24334.610490] RSP: 0018:8803ee67fdd8 EFLAGS: 00010086
  [24334.615924] RAX: 8803ebed4c00 RBX: 880036529800 RCX: 

  [24334.623190] RDX: 0225341f RSI:  RDI: 

  [24334.630479] RBP: 8803ee67fe00 R08: 0004 R09: 

  [24334.637758] R10: 8803e7ed7600 R11: 0001 R12: 

  [24334.645153] R13:  R14: 0009067729c4 R15: 
8803ee672178
  [24334.652512] FS: () GS:8803ffd0() 
knlGS:
  [24334.660721] CS: 0010 DS:  ES:  CR0: 80050033
  [24334.666587] CR2: 0050 CR3: 0003eacf9000 CR4: 
001406e0
  [24334.673851] Stack:
  [24334.675980] 8803ffd16e00 8803ffd16e00 8803e855a200 
880036529800
  [24334.683995] 0002 8803ee67fe68 810b98a6 
8803ffd16e70
  [24334.692024] 00016e00 8803e7ed7600 8803ee671c00 

  [24334.700172] Call Trace:
  [24334.702750] [] pick_next_task_fair+0x66/0x4b0
  [24334.708886] [] __schedule+0x7f4/0x980
  [24334.714349] [] schedule+0x35/0x80
  [24334.719445] [] schedule_preempt_disabled+0xe/0x10
  [24334.725962] [] cpu_startup_entry+0x18a/0x350
  [24334.732012] [] start_secondary+0x149/0x170
  [24334.737895] Code: 8b 70 50 4d 2b 74 24 50 4d 85 f6 7e 59 4c 89 e7 e8 67 ff 
ff ff 49 39 c6 7f 04 4c 8b 6b 48 48 8b 43 40 48 85 c0 74 1f 4c 8b 70 50 <4d> 2b 
74 24 50 4d 85 f6 7e 2c 4c 89 e7 e8 3f ff ff ff 49 39 c6
  [24334.765124] RIP [] pick_next_entity+0x7f/0x160
  [24334.771473] RSP 
  [24334.775077] CR2: 0050
  [24334.779121] ---[ end trace 05d941efb97b7bae ]---

  and

  [155852.028575] BUG: unable to handle kernel NULL pointer dereference at

[Kernel-packages] [Bug 1689661] Re: No PMU support for ACPI-based arm64 systems

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  No PMU support for ACPI-based arm64 systems

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  ACPI-based arm64 systems, such as the Qualcomm QDF2400 and the Hisilicon D05, 
do not currently have PMU support. This means that tools like perf are unable 
to use the built-in hardware event counters.

  [Test Case]
  On an ACPI-based arm64 system, run the following commands:

  sudo perf list pmu
  sudo perf list hw

  Without ACPI PMU support, these will be empty.

  [Regression Risk]
  The changes are restricted to ARM-specific code, other than an added enum 
value in linux/cpuhotplug.h. This reduces the non-negligible regression risk to 
the ARM architecture.

  For ACPI-based ARM platforms, regression risk is limited because they
  did not have PMU support previously. However, if this code is buggy,
  previously working commands that just made use of non-PMU events (e.g.
  perf top) might start causing problems. To mitigate this, I did a
  perf_fuzzer run on a QDF2400 (ACPI-based) and confirmed it survived
  (Note: this included a workaround for LP: #1689855, which will need to
  be fixed separately once upstreamed).

  For non-ACPI-based (i.e. devicetree) ARM platforms, there is a chance
  that the changes have broken PMU support. To mitigate that, I also did
  a perf_fuzzer run on a Cavium ThunderX system booted in DT mode, which
  it survived.

  Finally, the non-perf related changes in this series are restricted to
  a change in arch/arm64/kernel/smp.c that saves off pointers to each
  CPU's MADT GICC tables. The code is populating a static array with
  existing data - so pretty low risk (no pointer dereferences, etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689661/+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 1689886] Re: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  $ sudo ipmitool fru print 0
   Chassis Type : Rack Mount Chassis
   Chassis Part Number : 
   Chassis Serial : 
   Board Mfg Date : Wed Jan 4 14:18:00 2017
   Board Mfg : WIWYNN
   Board Product : REP Board
   Board Serial : 12345
   Board Part Number : 
   Product Manufacturer : WIWYNN
   Product Name : REP
   Product Part Number : ..
   Product Version : EVT
   Product Serial : 
   Product Asset Tag :
  ubuntu@ubuntu:~/FRU$

  ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin
  Fru Size : 1024 bytes
  Size to Write : 256 bytes
  [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual 
address 0025
  [ 1815.419668] pgd = 219ca2168000
  [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, 
*pmd=
  [ 1815.431225] Internal error: Oops: 9604 [#1] SMP
  [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat 
aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce 
sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs 
autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci 
xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci 
usb_common pinctrl_qdf2xxx
  [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic 
#5~pdaw1.0+bandera.9-Ubuntu
  [ 1815.480789] Hardware name: Default string Default string/Default string, 
BIOS 5.12 12/12/2012
  [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: 
edf1a782
  [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif]
  [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif]
  [ 1815.508046] pc : [] lr : [] pstate: 
00400145
  [ 1815.515424] sp : edf1a7823de0
  [ 1815.518723] x29: edf1a7823de0 x28: 
  [ 1815.524018] x27:  x26: 
  [ 1815.529313] x25:  x24: 
  [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000
  [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00
  [ 1815.545198] x19: edeeb9dbb800 x18: 0014
  [ 1815.550494] x17:  x16: 
  [ 1815.555789] x15:  x14: 
  [ 1815.561084] x13:  x12: 071c71c71c71c71c
  [ 1815.566379] x11: 00ba x10: 0960
  [ 1815.571674] x9 : 0040 x8 : edf1ad28
  [ 1815.576969] x7 :  x6 : edf1aa9f9600
  [ 1815.582264] x5 : edf1ad00 x4 : 
  [ 1815.587560] x3 : 0026 x2 : 0025
  [ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00
  [ 1815.598150]
  [ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020)
  [ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000)
  [ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 
219ca20cdfa8
  [ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 
edeeb9dbb800
  [ 1815.627925] 3e20:  219ca11c4f10 219ca122ca30 
edf1ab9d5800
  [ 1815.635737] 3e40:    

  [ 1815.643550] 3e60:  219ca12399a8 edeeb9dbb800 
edf1
  [ 1815.651363] 3e80:  edf1a7823e88 edf1a7823e88 

  [ 1815.659175] 3ea0:  edf1a7823ea8 edf1a7823ea8 
cb88537fdc8ba500
  [ 1815.666987] 3ec0:    

  [ 1815.674800] 3ee0:    

  [ 1815.682612] 3f00:    

  [ 1815.690425] 3f20:    

  [ 1815.698237] 3f40:    

  [ 1815.706050] 3f60:

[Kernel-packages] [Bug 1687877] Re: bonding - mlx5 - speed changed to 0 after changing ring size

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  bonding - mlx5 - speed changed to 0 after changing ring size

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  The problem happens when changing the ring size of a mlx5_core interface that 
is part of a LACP bond.

  [268312.721076] mlx5_core :42:00.1 enp66s0f1: mlx5e_update_carrier:143: 
Link up
  [268312.721940] mlx5_core :42:00.1 enp66s0f1: speed changed to 0 for port 
enp66s0f1
  [268312.732089] bond0: link status up again after 0 ms for interface enp66s0f1

  
  the upstream commit "bonding: allow notifications for 
bond_set_slave_link_state " fix the issue, will cherry-pick and send to xenial 
git tree.

  
  Thanks,
  Talat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687877/+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 1688114] Re: arm64/ACPI support for SBSA watchdog

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  arm64/ACPI support for SBSA watchdog

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  On arm64/ACPI-based servers, such as the QDT2400 and HiSilicon D05, there is 
a watchdog feature based on the architected timer that is not usable in Ubuntu. 
This prevents these systems from using this facility to automatically recover 
from a hard lockup.

  [Test Case]
  sudo modprobe sbsa-gwdt
  ls -l /dev/watchdog*

  [Regression Risk]
  The changes required are to the ARM architected timer driver and some new 
code to parse the configuration data from the ACPI GTDT table. These changes 
only apply to ARM-specific code, so the risk is limited to those platforms.

  This has been tested on the QDT2400 and HiSilicon D05, and regression
  tested on an non-ACPI (devicetree) HP m400 and Cavium ThunderX
  systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688114/+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 1688259] Re: kernel-wedge fails in artful due to leftover squashfs-modules d-i files

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  kernel-wedge fails in artful due to leftover squashfs-modules d-i
  files

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  We no longer produce a squashfs-modules udeb, but some of the d-i
  files remain in the tree, all of which include another file which has
  been removed. kernel-wedge in artful is choking on these files. Since
  we don't use them anymore they should be removed.

  We also need to tell consumers of squashfs-modules that this is
  provided by the kernel so they do not have to remove their
  dependencies on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688259/+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 1688132] Re: Support IPMI system interface on Cavium ThunderX

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  Support IPMI system interface on Cavium ThunderX

Status in linux package in Ubuntu:
  Fix Committed
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:
  Fix Committed

Bug description:
  [Impact]
  The IPMI system interface (/dev/ipmi0) is unavailable on Cavium 
ThunderX-based systems. This prevents various in-band management tasks, 
including auto-enlistment using MAAS.

  [Test Case]
  sudo modprobe ipmi_ssif
  sudo modprobe ipmi_devintf

  Do you have a working /dev/ipmi0?
  sudo ipmitool lan print

  [Regression Risk]
  For hwe-z, this is a small fix to a driver that is only used on 
ThunderX-based systems, and is currently not usable w/o magic manual steps.

  For hwe-x and hwe-y, this also impacts the i2c-octeon driver. After
  hwe-y, upstream split that driver into 2 pieces to factor out code
  that could be shared with i2c-thunderx, and then i2c-thunderx was
  added. i2c-octeon is a driver for Cavium OCTEON systems, which are
  MIPS64 - an architecture unsupported by Ubuntu, so regression risk is
  negligible. i2c-thunderx is a new driver that is only loaded on
  ThunderX-based systems, so the testing we've performed on ThunderX
  should mitigate that regression risk.

  Note: there are issues with older firmware (version varies depending
  on platform) where the IPMI device can vanish between reboots,
  requiring a BMC reset to recover. This doesn't cause any other problem
  - drivers don't load, and it's as if this driver was never added.
  However, it is worth noting here in case people google it. Please
  upgrade your firmware if you run into this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688132/+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 1688164] Re: arm64: Add CNTFRQ_EL0 handler

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  arm64: Add CNTFRQ_EL0 handler

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Userspace reads of CNTVCT_EL0 are broken on HiSilicon D05 systems, which 
breaks some applications such as OpenMPI.

  [Test Case]
  #include 
  #include 

  int main(int argc, char *argv[])
  {
     unsigned int freq;
     __asm__ __volatile__ ("mrs %0, CNTFRQ_EL0" : "=r" (freq));
     printf("freq %d\n",freq);
  return (int)freq;
  }

  ==
  gcc test.c test
  ./test

  This will report an illegal instruction, but should print a frequency
  value.

  [Regression Risk]
  The best way we can minimize risk is to verify on both a system that has an 
errata handler for the timer (D05) and a system that doesn't. We should then be 
exercising both code paths.

  I have regression tested this, using the above test case, on the HP
  m400, the QDT Centriq 2400, and a Cavium ThunderX CRB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688164/+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 1688579] Re: linux-aws/linux-gke incorrectly producing and using linux--tools-common/linux--cloud-tools-common

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  linux-aws/linux-gke incorrectly producing and using linux-*-tools-
  common/linux-*-cloud-tools-common

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-gke package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed

Bug description:
  Both linux-aws and linux-gke are producing linux-*-tools-common and
  linux-*-cloud-tools-common.  By shipping common files in this way we
  create conflicting packages:

  $ sudo apt-get install linux-tools-generic
  [...]
  $ sudo apt-get install linux-tools-gke  
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.4.0-45 linux-headers-4.4.0-45-generic 
linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic linux-headers-4.8.0-27
linux-headers-4.8.0-27-generic linux-image-4.4.0-45-generic 
linux-image-4.4.0-75-generic linux-image-4.8.0-27-generic
linux-image-extra-4.4.0-45-generic linux-image-extra-4.4.0-75-generic 
linux-image-extra-4.8.0-27-generic linux-signed-image-4.4.0-45-generic
linux-signed-image-4.4.0-75-generic snap-confine ubuntu-core-launcher
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
linux-gke-tools-4.4.0-1012 linux-gke-tools-common linux-tools-4.4.0-1012-gke
  The following NEW packages will be installed
linux-gke-tools-4.4.0-1012 linux-gke-tools-common 
linux-tools-4.4.0-1012-gke linux-tools-gke
  0 to upgrade, 4 to newly install, 0 to remove and 0 not to upgrade.
  Need to get 0 B/804 kB of archives.
  After this operation, 2,344 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  (Reading database ... 427294 files and directories currently installed.)
  Preparing to unpack .../linux-gke-tools-common_4.4.0-1012.12_all.deb ...
  Unpacking linux-gke-tools-common (4.4.0-1012.12) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-gke-tools-common_4.4.0-1012.12_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man8/x86_energy_perf_policy.8.gz', which 
is also in package linux-tools-common 4.4.0-77.98
  Selecting previously unselected package linux-gke-tools-4.4.0-1012.
  Preparing to unpack .../linux-gke-tools-4.4.0-1012_4.4.0-1012.12_amd64.deb ...
  Unpacking linux-gke-tools-4.4.0-1012 (4.4.0-1012.12) ...
  Selecting previously unselected package linux-tools-4.4.0-1012-gke.
  Preparing to unpack .../linux-tools-4.4.0-1012-gke_4.4.0-1012.12_amd64.deb ...
  Unpacking linux-tools-4.4.0-1012-gke (4.4.0-1012.12) ...
  Selecting previously unselected package linux-tools-gke.
  Preparing to unpack .../linux-tools-gke_4.4.0.1012.14_amd64.deb ...
  Unpacking linux-tools-gke (4.4.0.1012.14) ...
  Processing triggers for man-db (2.7.5-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-gke-tools-common_4.4.0-1012.12_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688579/+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 1690155] Re: Fix NVLINK2 TCE route

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

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

Title:
  Fix NVLINK2 TCE route

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == Comment: #0 - Breno Henrique Leitao  -
  2017-05-11 09:14:17 ==

  Commit 616badd2fb49 ("powerpc/powernv: Use OPAL call for TCE kill on
  NVLink2") forced all TCE kills to go via the OPAL call for
  NVLink2. However the PHB3 implementation of TCE kill was still being
  called directly from some functions which in some circumstances caused
  a machine check

  The following commit was added into zesty using LP#1667081

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690155/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

2017-05-25 Thread Daniel van Vugt

There are multiple variables here you need to consider...

The headset socket is 4-contact to support headphones with built-in
microphone. So if you plug in a 4-contact jack then you are more likely
(not guaranteed) to get a clean connection (4 contacts touching 4
separate contacts).

However a "clean" connection is not helpful if you've plugged in the
wrong type of headset. See there are different types (too many):

  
https://technosyndicate.files.wordpress.com/2012/12/122312_0549_common35mm11.png
  http://www.cablechick.com.au/blog/understanding-trrs-and-audio-jacks/

So an imperfect connection is pretty common. And an imperfect connection
might touch the laptop's mic contact to something else. In fact if you
get a pair of Bose Quiet Comfort QC25 then you have a choice between
buying one with Apple support or Samsung/Android support (although some
stores will only stock Apple). One doesn't work in the other but they
both appear to be identical 4-contact 3.5mm jacks.

Yes indeed this can be fixed in software to silence or reduce noise from
the mic line. But remember it's a hardware problem as well as a software
problem. You should try both hardware and software solutions.

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

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1693647] Status changed to Confirmed