[Kernel-packages] [Bug 1554613] Re: screen flickering on XPS13 9350

[Moondog]

While I noticed the screen-flicker doesn't show while compiling a linux
kernel, I am guessing the problem might be related to c-states. After
adding "intel_idle.max_cstate=0" to the kernel command-line the screen-
flicker hasn't shown anymore.

While disabling c-states is not acceptable as a workaround, it might
help to find the root-cause of the problem for the (Intel) developers.
Can anyone confirm the c-state relation?

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

Title:
  screen flickering on XPS13 9350

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1554613/+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 1355562] PulseList.txt

[Po-Hsu Lin]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640447/+files/PulseList.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] Card0.Codecs.codec.3.txt

[Po-Hsu Lin]

apport information

** Attachment added: "Card0.Codecs.codec.3.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640438/+files/Card0.Codecs.codec.3.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] BootDmesg.txt

[Po-Hsu Lin]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640435/+files/BootDmesg.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] Card0.Amixer.values.txt

[Po-Hsu Lin]

apport information

** Attachment added: "Card0.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640436/+files/Card0.Amixer.values.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] Lspci.txt

[Po-Hsu Lin]

apport information

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

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] ProcCpuinfo.txt

[Po-Hsu Lin]

apport information

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

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] RfKill.txt

[Po-Hsu Lin]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1355562/+attachment/4640448/+files/RfKill.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] UdevLog.txt

[Po-Hsu Lin]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640450/+files/UdevLog.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] ProcInterrupts.txt

[Po-Hsu Lin]

apport information

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

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] PciMultimedia.txt

[Po-Hsu Lin]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640443/+files/PciMultimedia.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] WifiSyslog.gz

[Po-Hsu Lin]

apport information

** Attachment added: "WifiSyslog.gz"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640451/+files/WifiSyslog.gz

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] Card0.Codecs.codec.0.txt

[Po-Hsu Lin]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640437/+files/Card0.Codecs.codec.0.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] UdevDb.txt

[Po-Hsu Lin]

apport information

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

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] CurrentDmesg.txt

[Po-Hsu Lin]

apport information

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

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] Lsusb.txt

[Po-Hsu Lin]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1355562/+attachment/4640442/+files/Lsusb.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] AlsaDevices.txt

[Po-Hsu Lin]

apport information

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640433/+files/AlsaDevices.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1355562] Re: An "Unknown" display appears with no external display connected on 12.04.5

[Po-Hsu Lin]

apport information

** Tags added: apport-collected staging

** Description changed:

  CID: 201202-10511 Dell Inspiron 5420
  
  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5
  
  The problem with this issue is that you will be able to move the cursor
  out of your screen, even open an application on the extended display.
  
  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display
  
  Expected result:
  * There should be only a "Laptop" display
  
  Actual result:
  * An "Unknown" display available
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
+ ApportVersion: 2.0.1-0ubuntu17.13
+ Architecture: amd64
+ ArecordDevices:
+   List of CAPTURE Hardware Devices 
+  card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
+Subdevices: 1/1
+Subdevice #0: subdevice #0
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
+ CRDA:
+  country TW:
+   (2402 - 2472 @ 40), (3, 27)
+   (5270 - 5330 @ 40), (3, 17), DFS
+   (5735 - 5815 @ 40), (3, 30)
+ Card0.Amixer.info:
+  Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
+Mixer name : 'Intel PantherPoint HDMI'
+Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
+Controls  : 27
+Simple ctrls  : 10
+ DistroRelease: Ubuntu 12.04
+ HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
+ InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
+ MachineType: Dell Inc. Inspiron 5420
+ MarkForUpload: True
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  0 inteldrmfb
+  1 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-85-generic N/A
+  linux-backports-modules-3.13.0-85-generic  N/A
+  linux-firmware 1.79.18
+ StagingDrivers: rts5139
+ Tags:  precise running-unity staging
+ Uname: Linux 3.13.0-85-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ dmi.bios.date: 07/24/2012
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: X58
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: 0.1
+ dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
+ dmi.product.name: Inspiron 5420
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AcpiTables.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640432/+files/AcpiTables.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  

[Kernel-packages] [Bug 1355562] AplayDevices.txt

[Po-Hsu Lin]

apport information

** Attachment added: "AplayDevices.txt"
   
https://bugs.launchpad.net/bugs/1355562/+attachment/4640434/+files/AplayDevices.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/1355562

Title:
  An "Unknown" display appears with no external display connected on
  12.04.5

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201202-10511 Dell Inspiron 5420

  After boot to desktop, there will be an "Unknown" display work as an
  extended display on this system with 12.04.5

  The problem with this issue is that you will be able to move the
  cursor out of your screen, even open an application on the extended
  display.

  Steps:
  1. Install 12.04.5, boot to desktop with no external monitor connected
  2. Open the "Display" utility, check whether there is an "Unknown" display

  Expected result:
  * There should be only a "Laptop" display

  Actual result:
  * An "Unknown" display available

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 22:36:12 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-85-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1930 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1a1 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:14f1506e,1028055e,0012 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=0cbc4d1f-a6f7-4398-a928-15aee8a03533
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5420
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=34d03260-41c4-47df-b29f-e585414ee516 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-85.129~precise1-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.79.18
  StagingDrivers: rts5139
  Tags:  precise running-unity staging
  Uname: Linux 3.13.0-85-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X58
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrX58:bd07/24/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 5420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1355562/+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 1378727] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] No audio output on HDMI / DP port with nvidia-331

[Po-Hsu Lin]

This can't be verified without the nvidia driver, Xorg will crash when
connecting an external HDMI monitor.

I checked with the Power-saving profile with nvidia driver installed,
external monitor does not work (no signal, and it's not detected in the
Display utility).

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

Title:
  nVidia GK106GLM [Quadro K2100M] [10de:11fc] No audio output on HDMI /
  DP port with nvidia-331

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201305-13527 Dell Precision M4800

  There is no HDMI / DP audio output availlable with nvidia-331 driver.

  Steps:
  1. Installl 14.04.1 + nvidia-331, reboot
  2. Connect to a DP / HDMI monitor, try to change the output to it.

  Expected result:
  * After connect to a HDMI / DP monitor, there should be an extra audio output 
available.

  Actual result:
  * No extra audio output available.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 4041 F pulseaudio
   /dev/snd/controlC0:  ubuntu 4041 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Oct  8 05:38:15 2014
  HibernationDevice: RESUME=UUID=46ed949d-eff8-48e9-b337-6425f480cf12
  InstallationDate: Installed on 2014-10-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision M4800
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=e7f55d08-44a4-447e-8fc6-563864d60df4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FVDR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1378727/+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 1539863] Re: linux-image-extra-4.4.0-2-generic_4.4.0-2.16_amd64.deb Module snd-ice1712.ko is missing!

[Launchpad Bug Tracker]

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

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

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

Title:
  linux-image-extra-4.4.0-2-generic_4.4.0-2.16_amd64.deb Module snd-
  ice1712.ko is missing!

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

Bug description:
  M-Audio Delta 1010LT doesn't work at all.

  #modprobe snd-ice1712
  modprobe: FATAL: Module snd-ice1712 not found.

  #ls /lib/modules/4.4.0-2-generic/kernel/sound/pci/ice1712
  snd-ice1724.ko  snd-ice17xx-ak4xxx.ko
  Same problem with  4.4.0-0-generic

  This problem also detected in 4.5.0-040500rc1-generic. (kernel ppa
  mainline)

  I guess that an error in the source code. I have not found my sound
  card in the list, when configuring the kernel, before building from
  source. (make menuconfig)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.4
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Sat Jan 30 10:04:29 2016
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539863/+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 1572258] Re: linux-lts-vivid: 3.19.0-59.65~14.04.1 -proposed tracker

[Brad Figg]

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1572258/+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 1109029] Re: Depend on linux-initramfs-tool

[Unit 193]

This bug was fixed in the package kbd - 1.15.5-1ubuntu3

---
kbd (1.15.5-1ubuntu3) wily; urgency=medium

  * Drop initramfs-tools dependency. It causes other providers of
linux-initramfs-tool (like dracut) to become uninstallable, and is an
ancient Ubuntu-ism which has never been forwarded, nor is it kbd's place
to dictate whether or not you should have an initramfs.

 -- Martin Pitt   Tue, 08 Sep 2015 12:50:53
+0200

** Changed in: kbd (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Depend on linux-initramfs-tool

Status in apparmor package in Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Invalid
Status in multipath-tools package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Confirmed
Status in watershed package in Ubuntu:
  Confirmed

Bug description:
  Many core packages depend on initramfs-tools when they should actually
  depend on linux-initramfs-tool (virtual package provided by initramfs-
  tools and dracut).

  Debian seems to be using "Depends: initramfs-tools | linux-initramfs-
  tool" for almost every relevant package.

  See also bug #1108987, which is about the fact that dracut shouldn't
  conflict with initramfs-tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1109029/+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 1109029] Re: Depend on linux-initramfs-tool

[Unit 193]

This bug was fixed in the package plymouth - 0.9.2-3ubuntu1

---
plymouth (0.9.2-3ubuntu1) xenial; urgency=medium

  * Merged from debian unstable (first time ever…) Remaining changes:
- include ubuntu theme logos:
  themes/ubuntu-logo/*, debian/source/include-binaries.
- debian/libplymouth4.apport: add Apport hook.
- Ship ubuntu-logo instead of debian-logo (debian/rules and
  debian/local/plymouth.hook).
- Ship debian/source_plymouth.apport apport hook (debian/rules).
- Add plymouth-label as a separate package and makes themes depending on
  it (debian/control, debian/plymouth-label.install,
  debian/plymouth-themes.install).
- As log-viewer is disabled by default upstream and now in debian, don't
  ship its man page (debian/plymouth.links).
- Ship plymouth-theme-ubuntu-logo and plymouth-theme-ubuntu-text specific
  themes (debian/plymouth-theme-ubuntu-* and debian/control) and add
  Recommends on it | plymouth-theme to accommodate flavors.
- Remove debian/patches/0003-default-theme.patch as we handle our defaults
  via alternatives. (and refresh debian/patches/0008-show-delay.patch)
- debian/patches/misc-changes.patch: old undocumented inline changes.
  export a new symbol added in debian/libplymouth4.symbols.
- debian/patches/avoid-sigpipe.patch:
  Use first a socket connection before fallbacking to regular write()
- debian:patches/details-short-prompt.patch: When we display bullets in the
  ubuntu details theme, shorten the prompt.
- debian/patches/details-remove-separator.patch: Removed explicit printing
  of ':'.
- debian/patches/details-update-status.patch: Implement update status (U)
  splash plugin function for details plugin, imply display those updates
  as text messages.
- debian/patches/initramfsless-boot.patch: support intramfsless boot.
- debian/patches/fix-split-writes.patch: fix split writes for long server
  responses.
- debian/patches/ubuntu-add-splash-option.patch: add "splash" option as a
  condition to trigger plymouth.
- debian/rules:
  - disable optimization is noopt found in $DEB_BUILD_OPTION
  - enable -Werror
  - use ubuntu-themes background color
- debian/local/: export OPTION=FRAMEBUFFER for user's
  command line argument explicitly disabling framebuffer.
- We use alternatives instead of plymouth-set-default-theme tool:
  + debian/plymouth-themes.{prerm,postinst}: ensure we select one default
   plymouth logo and text themes through alternatives even when we remove
   ubuntu-base ones.
  + debian/rules, debian/plymouth.{install,links), don't ship non
non alternative-based theme policy files and tools.
  + update plymouth.README.Debian to tell to use update-alternative
instead of set-default-theme
  + change debian/local/plymouth.hook to use update-alternative to get
default theme instead of set-default-theme. Also, don't copy
deleted files to initramfs.
- Add Breaks: against older themes versions as they are shipping in /lib
  instead of /usr/share.
  * Noticeable changes from previous ubuntu version:
- Follow debian in moving all renderers from /lib to /usr/lib 
- Follow debian as well in moving all themes from /lib to /usr/share
  and handle transition removing older /lib/plymouth/theme generated files.
- Renamed all ubuntu_logo* to ubuntu-logo* to follow debian naming. Do
  something comparable with all our assets and adapt scripts to it.
- Renamed debian/libplymouth4.apport to debian/source_plymouth.apport
  as we install it under this name.
- Cleaning up deprecated transitions in maintainer scripts and package
  metadata.
- Log viewer has been disabled in upstream build for quite a while and
  is now not built either in debian. Follow this changes. We can re-enable
  it if there is a need but systemd logs should be generally enough.
- Update ubuntu specific package description to match debian's one.
- Following debian change, we disable plymouth splash with !nosplash as
  a kernel command parameter.
- All patches needed some adapation as upstream changed its identation from
  2 to 8 space characters.
- debian/plymouth-theme-ubuntu-text.postrm: clean up generated postinst
  ubuntu-text plymouth metafile.
- we do select one default theme when no ubuntu related themes are
  installed from the default plymouth theme package (spinner theme). If
  you don't want to install an ubuntu plymouth theme and select another
  one from the default set manually, update the alternative.
- add missing lsb-release dep on plymouth-theme-ubuntu-text
  * ubuntu old changelog containing debian-like packaging version has been
copied to debian/changelog.ubuntu.old in the source package.

 -- Didier Roche   Wed, 02 Dec 2015 09:41:06 +0100

** Changed 

[Kernel-packages] [Bug 1109029] Re: Depend on linux-initramfs-tool

[Unit 193]

This bug was fixed in the package console-setup - 1.108ubuntu6

---
console-setup (1.108ubuntu6) wily; urgency=medium

  * debian/control: allow dracut to be installable by adding an alternate
depends on linux-initramfs-tool for console-setup.

 -- Mathieu Trudel-Lapierre   Tue, 08 Sep 2015
22:36:52 -0400

** Changed in: console-setup (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Depend on linux-initramfs-tool

Status in apparmor package in Ubuntu:
  Fix Released
Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Invalid
Status in multipath-tools package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Confirmed
Status in watershed package in Ubuntu:
  Confirmed

Bug description:
  Many core packages depend on initramfs-tools when they should actually
  depend on linux-initramfs-tool (virtual package provided by initramfs-
  tools and dracut).

  Debian seems to be using "Depends: initramfs-tools | linux-initramfs-
  tool" for almost every relevant package.

  See also bug #1108987, which is about the fact that dracut shouldn't
  conflict with initramfs-tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1109029/+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 1568599] Re: Screen flickering with 16.04 on Dell XPS13 9350

[Nhellwege]

@ Richard Platt
Are you still without flicker? If so, what Kernel are you on? (uname -a)

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

Title:
  Screen flickering with 16.04 on Dell XPS13 9350

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 16.04 on my XPS13 9350 and I am experiencing
  and intermittent screen flickering. The screen goes black for a brief
  moment and constantly does this. While I have been typing it has done
  it 20-30  times.

  plattr@beatrice:~$ uname -a
  Linux beatrice 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  
  plattr@beatrice:~$ sudo dmidecode | grep -A3 '^System Information'
  [sudo] password for plattr: 
  System Information
Manufacturer: Dell Inc.
Product Name: XPS 13 9350
Version: Not Specified

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  plattr 1194 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 10 21:07:48 2016
  HibernationDevice: RESUME=UUID=84cb2e32-5b42-44ab-be61-5906241daa1e
  InstallationDate: Installed on 2016-03-28 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=ddbb6ae6-9a35-4877-beba-6edd31e0ab97 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568599/+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 1572261] Re: linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-86.130~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1572261/+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 1572347] Missing required logs.

[Brad Figg]

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

apport-collect 1572347

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1572347] Re: problems with network speed reporting in sysfs on s390

[Jeff Lane]

Whoops, set it to New, not Confirmed, that triggered your bot again.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1572347

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1572347] WifiSyslog.txt

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1572347] ProcModules.txt

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1572347] Re: problems with network speed reporting in sysfs on s390

[Jeff Lane]

Looks to me like apport-collect just submitted the exact same logs as
ubuntu-bug did.  Your bot may be broken...

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
 

[Kernel-packages] [Bug 1572347] ProcCpuinfo.txt

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1572347] Re: problems with network speed reporting in sysfs on s390

[Jeff Lane]

I don't understand... why am I having to run apport-collect? Why didnt
ubuntu-bug submit all the logs?

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

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: 

[Kernel-packages] [Bug 1572347] UdevDb.txt

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably 

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

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1572347] CurrentDmesg.txt

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1572347] Re: problems with network speed reporting in sysfs on s390

[Jeff Lane]

apport information

** Tags added: apport-collected

** Description changed:

  On an amd64 system with a 1Gb NIC, I can examine /sys/class/net/
  for various bits of data.  In this case, we need link speed.
  
  For example:
  
  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000
  
  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10
  
  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported maximum
  speed.
  
  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:
  
  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument
  
  So on zKVM even root is not able to view the current link speed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: s390x
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ 

[Kernel-packages] [Bug 1572347] ProcInterrupts.txt

[Jeff Lane]

apport information

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log 

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

[Brad Figg]

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

apport-collect 1572347

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

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
  1000

  However, on my z/VM instance of Xenial on s390, the reported speed is WAY 
below what it actually is:
  hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
  10

  iperf confirms that this virtual device is actually functioning at 1Gb
  speeds.  This is causing failures in the cert networking tests that
  probe for reported link speed and then compare that to reported
  maximum speed.

  On a zKVM instance of Xenial, this is even worse as I am completely
  unable to examine /sys/class/net//speed at all:

  hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
  cat: /sys/class/net/eth0/speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ ll
  total 0
  drwxr-xr-x 5 root root0 Apr 19 20:02 ./
  drwxr-xr-x 3 root root0 Apr 19 20:02 ../
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
  -r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 address
  -r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
  -r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
  lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
  -r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
  -r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
  -r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
  -r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
  -r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
  -r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
  -r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
  drwxr-xr-x 2 root root0 Apr 19 20:02 power/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
  drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
  -r--r--r-- 1 root root 4096 Apr 19 20:02 speed
  drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
  lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
  -r--r--r-- 1 root root 4096 Apr 19 20:02 type
  -rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
  cat: speed: Invalid argument
  hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
  root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
  cat: speed: Invalid argument

  So on zKVM even root is not able to view the current link speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 19 22:58:52 2016
  HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc

[Ryan]

Noticing everyone in this bug report has Intel + Radeon graphics, I
tried disabling the Radeon.  Simply running 'sudo rmmod radeon' after
the laptop boots up with the stock 4.4 kernel allows it to properly
sleep.  Removing the kernel module causes kernel oops, but otherwise
everything seems fine after unloading it.  I've attached a dmesg showing
the kernel module removal with the oops, and the successful sleep/wake
that follows it.  I've tried it several times and sleep/wake is working
every time after removing radeon, and fails every time while radeon is
loaded.

** Attachment added: "dmesg after removing radeon module"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566828/+attachment/4640297/+files/dmesg.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/1566828

Title:
  Suspension does not work, freezes the pc

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have this notebook
  HP 15 ac 191 nl

  Intel® Core™ i5-5200U with integrated Intel HD 5500
  RAM 8 gb
  DEdicated GPU AMD Radeon R5 M330

  I am running kubuntu 16.04 beta2.

  When i suspend the pc, gettin down the screen or givin the command in the 
menù, the screen goes black but the fan keeps running. So you can hear the fan 
working..and the pc got hot.
  It is also impossible to wake up the pc, it stays freezed in this condition, 
i have to force the shutdown with the power button pressing it for 3 sec. 

  The problem is present every time i try to suspend the pc.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: HP
  dmi.board.version: 96.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1572347] [NEW] problems with network speed reporting in sysfs on s390

[Jeff Lane]

Public bug reported:

On an amd64 system with a 1Gb NIC, I can examine /sys/class/net/
for various bits of data.  In this case, we need link speed.

For example:

bladernr@galactica:~/Datacenters/Home$ cat /sys/class/net/enp2s0/speed 
1000

However, on my z/VM instance of Xenial on s390, the reported speed is WAY below 
what it actually is:
hwe@hwe-zvm1:/sys/class/net/enc600$ cat speed
10

iperf confirms that this virtual device is actually functioning at 1Gb
speeds.  This is causing failures in the cert networking tests that
probe for reported link speed and then compare that to reported maximum
speed.

On a zKVM instance of Xenial, this is even worse as I am completely
unable to examine /sys/class/net//speed at all:

hwe@s1lp9g003:~$ cat /sys/class/net/eth0/speed 
cat: /sys/class/net/eth0/speed: Invalid argument
hwe@s1lp9g003:/sys/class/net/eth0$ ll
total 0
drwxr-xr-x 5 root root0 Apr 19 20:02 ./
drwxr-xr-x 3 root root0 Apr 19 20:02 ../
-r--r--r-- 1 root root 4096 Apr 19 20:02 addr_assign_type
-r--r--r-- 1 root root 4096 Apr 19 20:02 addr_len
-r--r--r-- 1 root root 4096 Apr 19 20:02 address
-r--r--r-- 1 root root 4096 Apr 19 20:02 broadcast
-rw-r--r-- 1 root root 4096 Apr 19 20:02 carrier
-r--r--r-- 1 root root 4096 Apr 19 20:02 carrier_changes
-r--r--r-- 1 root root 4096 Apr 19 20:02 dev_id
-r--r--r-- 1 root root 4096 Apr 19 20:02 dev_port
lrwxrwxrwx 1 root root0 Apr 19 20:02 device -> ../../../virtio1/
-r--r--r-- 1 root root 4096 Apr 19 20:02 dormant
-r--r--r-- 1 root root 4096 Apr 19 20:02 duplex
-rw-r--r-- 1 root root 4096 Apr 19 20:02 flags
-rw-r--r-- 1 root root 4096 Apr 19 20:02 gro_flush_timeout
-rw-r--r-- 1 root root 4096 Apr 19 20:02 ifalias
-r--r--r-- 1 root root 4096 Apr 19 20:02 ifindex
-r--r--r-- 1 root root 4096 Apr 19 20:02 iflink
-r--r--r-- 1 root root 4096 Apr 19 20:02 link_mode
-rw-r--r-- 1 root root 4096 Apr 19 20:02 mtu
-r--r--r-- 1 root root 4096 Apr 19 20:02 name_assign_type
-rw-r--r-- 1 root root 4096 Apr 19 20:02 netdev_group
-r--r--r-- 1 root root 4096 Apr 19 20:02 operstate
-r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_id
-r--r--r-- 1 root root 4096 Apr 19 20:02 phys_port_name
-r--r--r-- 1 root root 4096 Apr 19 20:02 phys_switch_id
drwxr-xr-x 2 root root0 Apr 19 20:02 power/
-rw-r--r-- 1 root root 4096 Apr 19 20:02 proto_down
drwxr-xr-x 4 root root0 Apr 19 20:02 queues/
-r--r--r-- 1 root root 4096 Apr 19 20:02 speed
drwxr-xr-x 2 root root0 Apr 19 20:02 statistics/
lrwxrwxrwx 1 root root0 Apr 19 20:02 subsystem -> 
../../../../../../../class/net/
-rw-r--r-- 1 root root 4096 Apr 19 20:02 tx_queue_len
-r--r--r-- 1 root root 4096 Apr 19 20:02 type
-rw-r--r-- 1 root root 4096 Apr 19 20:02 uevent
hwe@s1lp9g003:/sys/class/net/eth0$ sudo cat speed
cat: speed: Invalid argument
hwe@s1lp9g003:/sys/class/net/eth0$ sudo su
root@s1lp9g003:/sys/devices/css0/0.0.0001/0.0.0001/virtio1/net/eth0# cat speed
cat: speed: Invalid argument

So on zKVM even root is not able to view the current link speed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-18-generic 4.4.0-18.34
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic s390x
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Tue Apr 19 22:58:52 2016
HibernationDevice: RESUME=UUID=7ddabd20-1d15-492c-bcd5-ec2dbb16b777
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b732515f-dacf-4007-85af-a27b5bf48fdf 
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-18-generic N/A
 linux-backports-modules-4.4.0-18-generic  N/A
 linux-firmware1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug s390x 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/1572347

Title:
  problems with network speed reporting in sysfs on s390

Status in linux package in Ubuntu:
  New

Bug description:
  On an amd64 system with a 1Gb NIC, I can examine
  /sys/class/net/ for various bits of data.  In this case, we
  need link speed.

  For example:

  

[Kernel-packages] [Bug 1510196] Re: OOM killer causes complete system freezes

[Noah Meyerhans]

The fixes for this bug do not appear to have made it to the trusty
kernel repos despite this bug's "Fix Released" status. I can confirm
that the symptoms are still present with currently released ubuntu
packages and the master-next branch is still lacking the upstream fixes.

I'm working on backporting the upstream fixes to the current trusty
kernels for my own testing, but it'd be good to see an official update
containing the fix as well.

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

Title:
  OOM killer causes complete system freezes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  A race condition in the Linux kernel randomly causes complete system
  freezes when the system or a cgroup runs out of memory and the OOM
  killer is invoked. I ran into this issue twice during the last 2 weeks
  (Ubuntu 14.04.3 LTS, kernel version 3.13.0-65.106), in my case it was
  an LXC cgroup running out of memory and not the system itself. The
  system log files did not show any errors, but there were repeating
  error messages on the system console (see attached screenshot).

  When searching for these error messages I found the following website
  that provides more information about the cause and a possible solution
  to fix it: https://community.nitrous.io/posts/stability-and-a-linux-
  oom-killer-bug

  I did not see any OOM killer related messages in the system logs at
  the time the freeze happened, but one of the LXC containers running on
  that server went out of memory exactly at that time, so I guess this
  must be related.

  I was not able to reproduce the error in a testing environment as it
  seems to be a race condition between several processes that does not
  occur every time. However, I have applied the 3 suggested commits for
  mm/oom_kill.c
  
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=0c740d0afc3bff0a097ad03a1c8df92757516f5c...4d4048be8a93769350efa31d2482a038b7de73d0)
  from kernel 3.14 to the current trusty kernel, built the patched
  kernel and it seems to work. Could this bugfix for the OOM killer be
  backported to the official trusty kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-66-generic 3.13.0-66.108
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 23 09:12 seq
   crw-rw 1 root audio 116, 33 Oct 23 09:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Oct 26 12:19:55 2015
  HibernationDevice: RESUME=UUID=728105e7-2f6b-46fd-bf56-1bf67239adea
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Supermicro H8DGT
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=08db4f0e-59c5-4ffd-a34c-866e3fe126c5 ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-66-generic N/A
   linux-backports-modules-3.13.0-66-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: H8DGT-HF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.21A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: SGI.COM
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd05/07/2013:svnSupermicro:pnH8DGT:pvr1234567890:rvnSupermicro:rnH8DGT-HF:rvr1.21A:cvnSGI.COM:ct17:cvr1234567890:
  dmi.product.name: H8DGT
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510196/+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 1566828] Re: Suspension does not work, freezes the pc

[hesediel84]

So i made all day of tests with the 4.6 rc4 kernel:

- difference to 4.4 kernel, suspending does not freeze totally the pc,
some times the screen stays black sometimes it show the wallpaper. It's
blocked but pressing the power button couple of times the pc returns
withiut forcing a shutdown.

-Confirm that kernel 4.4 freezes the pc

-The suspend system works some times, rarely, but some time works. I
wasnt unable to recognize a causing factor like battery or not, wifi on
or off...dont know.

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

Title:
  Suspension does not work, freezes the pc

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have this notebook
  HP 15 ac 191 nl

  Intel® Core™ i5-5200U with integrated Intel HD 5500
  RAM 8 gb
  DEdicated GPU AMD Radeon R5 M330

  I am running kubuntu 16.04 beta2.

  When i suspend the pc, gettin down the screen or givin the command in the 
menù, the screen goes black but the fan keeps running. So you can hear the fan 
working..and the pc got hot.
  It is also impossible to wake up the pc, it stays freezed in this condition, 
i have to force the shutdown with the power button pressing it for 3 sec. 

  The problem is present every time i try to suspend the pc.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: HP
  dmi.board.version: 96.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home 

[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc

[hesediel84]

** Tags removed: kernel-fixed-upstream xenial
** Tags added: kernel-bug-exists-upstream

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

Title:
  Suspension does not work, freezes the pc

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have this notebook
  HP 15 ac 191 nl

  Intel® Core™ i5-5200U with integrated Intel HD 5500
  RAM 8 gb
  DEdicated GPU AMD Radeon R5 M330

  I am running kubuntu 16.04 beta2.

  When i suspend the pc, gettin down the screen or givin the command in the 
menù, the screen goes black but the fan keeps running. So you can hear the fan 
working..and the pc got hot.
  It is also impossible to wake up the pc, it stays freezed in this condition, 
i have to force the shutdown with the power button pressing it for 3 sec. 

  The problem is present every time i try to suspend the pc.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: HP
  dmi.board.version: 96.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

[Paolo Sabatino]

This is GREAT news! We have a hint to start with.

i8042.c linux kernel source code defines more module parameters. The module 
parameter "direct" disables the scan code translation, but the module parameter 
"dumbkbd" completely disables the write capability of the kernel module to the 
i8042 controller and this actually makes the problem totally disappear!
The only side effect I noticed by now is that the keyboard leds don't react 
anymore to the lock status (ie: the Caps Lock led won't turn on).

I think there is some configuration/setting keyboard controller doesn't
like and makes it misbehaving, thus disabling completely the write
capability solves the problem.

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ 

[Kernel-packages] [Bug 1562618] Re: whole OS freezes seemingly randomly

[Vincent Gerris]

the saga continues. I am on this now:
Linux vincent-Lenovo-Yoga-2-11 4.2.0-040200-generic #201510260713 SMP Mon Oct 
26 11:14:43 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

The bcmwl driver did not work, so I had to use this solution to make it work as 
a workaround:
https://github.com/longsleep/bcmwl-ubuntu/issues/10

Before that I watched video and did some downloads, without issues.

I saw this in dmesg which worried me a bit, but I have no freezes so
far:

[48898.144263] ata1.00: exception Emask 0x10 SAct 0x40 SErr 0x40c action 
0xe frozen
[48898.144276] ata1.00: irq_stat 0x0040, connection status changed
[48898.144285] ata1: SError: { CommWake 10B8B DevExch }
[48898.144293] ata1.00: failed command: READ FPDMA QUEUED
[48898.144308] ata1.00: cmd 60/08:30:38:5b:57/00:00:01:00:00/40 tag 6 ncq 4096 
in
res 40/00:34:38:5b:57/00:00:01:00:00/40 Emask 0x10 (ATA 
bus error)
[48898.144316] ata1.00: status: { DRDY }
[48898.144328] ata1: hard resetting link
[48898.868269] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[48898.949146] ata1.00: configured for UDMA/133
[48898.949224] ata1: EH complete

could that be something that later kernels choke on?
It is still to early to be further conclusive so I'll keep on testing.

Please let me know if there is anything I can do to speed this up.
Thank you

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

Title:
  whole OS freezes seemingly randomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I had some random freezes of the whole operating system.
  No caps lock response or terminal switching, nothng.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent1714 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 27 23:46:02 2016
  HibernationDevice: RESUME=UUID=8180a7b6-a1c0-494a-9f65-99a7b54f6deb
  InstallationDate: Installed on 2015-11-01 (147 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20332
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=44fb018f-3dbd-4eb6-ab9a-6668de8d13d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (2 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562618/+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 1572316] Re: oops when propagating mounts into containers

[Seth Forshee]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Also affects: linux (Ubuntu Xenial)
   Importance: High
 Assignee: Seth Forshee (sforshee)
   Status: 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/1572316

Title:
  oops when propagating mounts into containers

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

Bug description:
  If I use LXD on xenial with a configuration that does something like:
  (/nfs in my case is an nfs mount, but based on the kernel code in
  question anything is probably okay):

  devices:
bind:
  type: disk
  source: /nfs
  path: /nfs
  recursive: "true"

  and then start the container and on the host, do a new mount:

  sudo mount $ipaddr:/some/nfs/path /nfs/newpath

  You get the following kernel oops:

  Apr 11 21:59:36 stock2 kernel: [ 1648.993034] Oops:  [#1] SMP 
  Apr 11 21:59:36 stock2 kernel: [ 1648.993415] Modules linked in: binfmt_misc 
veth rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache xt_CHECKSUM 
iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) ppdev kvm_intel parport_pc joydev kvm input_leds mac_hid 
irqbypass parport i2c_piix4 8250_fintek serio_raw ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
psmouse fb_sys_fops floppy drm pata_acpi
  Apr 11 21:59:36 stock2 kernel: [ 1649.002015] CPU: 2 PID: 9449 Comm: 
mount.nfs Tainted: P   O4.4.0-18-generic #34+tych0201604111025
  Apr 11 21:59:36 stock2 kernel: [ 1649.003037] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
  Apr 11 21:59:36 stock2 kernel: [ 1649.004042] task: 880074c1a580 ti: 
880067d3 task.ti: 880067d3
  Apr 11 21:59:36 stock2 kernel: [ 1649.004810] RIP: 0010:[]  
[] propagate_one+0xbe/0x1c0
  Apr 11 21:59:36 stock2 kernel: [ 1649.005654] RSP: 0018:880067d33d68  
EFLAGS: 00010297
  Apr 11 21:59:36 stock2 kernel: [ 1649.006211] RAX: 88003bb4ca80 RBX: 
880074ad8300 RCX: 880074503500
  Apr 11 21:59:36 stock2 kernel: [ 1649.006934] RDX:  RSI: 
019c RDI: 
  Apr 11 21:59:36 stock2 kernel: [ 1649.007656] RBP: 880067d33d78 R08: 
8800363bad80 R09: 813eac5c
  Apr 11 21:59:36 stock2 kernel: [ 1649.008390] R10: ea2b5800 R11: 
00018711 R12: 8800363ba600
  Apr 11 21:59:36 stock2 kernel: [ 1649.009111] R13: 880067d33dc0 R14: 
880074ad8300 R15: 
  Apr 11 21:59:36 stock2 kernel: [ 1649.009835] FS:  7f653eac4880() 
GS:88007cd0() knlGS:
  Apr 11 21:59:36 stock2 kernel: [ 1649.010642] CS:  0010 DS:  ES:  
CR0: 8005003b
  Apr 11 21:59:36 stock2 kernel: [ 1649.011237] CR2: 0010 CR3: 
77a4e000 CR4: 06e0
  Apr 11 21:59:36 stock2 kernel: [ 1649.011984] Stack:
  Apr 11 21:59:36 stock2 kernel: [ 1649.012255]  880074ad8300 
8800363ba600 880067d33db0 8123d060
  Apr 11 21:59:36 stock2 kernel: [ 1649.013070]  88003bb4ca80 
8800363ba600 88000c211980 
  Apr 11 21:59:36 stock2 kernel: [ 1649.013892]  880067d33e98 
880067d33df8 8122dd97 88003bb4c900
  Apr 11 21:59:36 stock2 kernel: [ 1649.014751] Call Trace:
  Apr 11 21:59:36 stock2 kernel: [ 1649.015053]  [] 
propagate_mnt+0x120/0x150
  Apr 11 21:59:36 stock2 kernel: [ 1649.015643]  [] 
attach_recursive_mnt+0x147/0x230
  Apr 11 21:59:36 stock2 kernel: [ 1649.016286]  [] 
graft_tree+0x58/0x90
  Apr 11 21:59:36 stock2 kernel: [ 1649.016809]  [] 
do_add_mount+0x8e/0xd0
  Apr 11 21:59:36 stock2 kernel: [ 1649.017342]  [] 
do_mount+0x2c0/0xe00
  Apr 11 21:59:36 stock2 kernel: [ 1649.017863]  [] ? 
copy_mount_options+0xb4/0x220
  Apr 11 21:59:36 stock2 kernel: [ 1649.018466]  [] 
SyS_mount+0x9f/0x100
  Apr 11 21:59:36 stock2 kernel: [ 1649.018996]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Apr 11 21:59:36 stock2 kernel: [ 1649.019631] Code: 39 90 d8 00 00 00 75 ec 
8b b0 10 01 00 00 48 89 3d 80 e1 f8 00 48 89 05 81 e1 f8 00 39 b1 10 01 00 00 
74 19 48 8b bf d8 00 00 00 <48> 8b 47 10 48 89 3d 5f e1 f8 00 48 89 05 60 e1 f8 
00 8b 43 30 
  Apr 11 21:59:36 stock2 kernel: [ 1649.022395] RIP  [] 

[Kernel-packages] [Bug 1572316] [NEW] oops when propagating mounts into containers

[Tycho Andersen]

Public bug reported:

If I use LXD on xenial with a configuration that does something like:
(/nfs in my case is an nfs mount, but based on the kernel code in
question anything is probably okay):

devices:
  bind:
type: disk
source: /nfs
path: /nfs
recursive: "true"

and then start the container and on the host, do a new mount:

sudo mount $ipaddr:/some/nfs/path /nfs/newpath

You get the following kernel oops:

Apr 11 21:59:36 stock2 kernel: [ 1648.993034] Oops:  [#1] SMP 
Apr 11 21:59:36 stock2 kernel: [ 1648.993415] Modules linked in: binfmt_misc 
veth rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache xt_CHECKSUM 
iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) ppdev kvm_intel parport_pc joydev kvm input_leds mac_hid 
irqbypass parport i2c_piix4 8250_fintek serio_raw ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
psmouse fb_sys_fops floppy drm pata_acpi
Apr 11 21:59:36 stock2 kernel: [ 1649.002015] CPU: 2 PID: 9449 Comm: mount.nfs 
Tainted: P   O4.4.0-18-generic #34+tych0201604111025
Apr 11 21:59:36 stock2 kernel: [ 1649.003037] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
Apr 11 21:59:36 stock2 kernel: [ 1649.004042] task: 880074c1a580 ti: 
880067d3 task.ti: 880067d3
Apr 11 21:59:36 stock2 kernel: [ 1649.004810] RIP: 0010:[]  
[] propagate_one+0xbe/0x1c0
Apr 11 21:59:36 stock2 kernel: [ 1649.005654] RSP: 0018:880067d33d68  
EFLAGS: 00010297
Apr 11 21:59:36 stock2 kernel: [ 1649.006211] RAX: 88003bb4ca80 RBX: 
880074ad8300 RCX: 880074503500
Apr 11 21:59:36 stock2 kernel: [ 1649.006934] RDX:  RSI: 
019c RDI: 
Apr 11 21:59:36 stock2 kernel: [ 1649.007656] RBP: 880067d33d78 R08: 
8800363bad80 R09: 813eac5c
Apr 11 21:59:36 stock2 kernel: [ 1649.008390] R10: ea2b5800 R11: 
00018711 R12: 8800363ba600
Apr 11 21:59:36 stock2 kernel: [ 1649.009111] R13: 880067d33dc0 R14: 
880074ad8300 R15: 
Apr 11 21:59:36 stock2 kernel: [ 1649.009835] FS:  7f653eac4880() 
GS:88007cd0() knlGS:
Apr 11 21:59:36 stock2 kernel: [ 1649.010642] CS:  0010 DS:  ES:  CR0: 
8005003b
Apr 11 21:59:36 stock2 kernel: [ 1649.011237] CR2: 0010 CR3: 
77a4e000 CR4: 06e0
Apr 11 21:59:36 stock2 kernel: [ 1649.011984] Stack:
Apr 11 21:59:36 stock2 kernel: [ 1649.012255]  880074ad8300 
8800363ba600 880067d33db0 8123d060
Apr 11 21:59:36 stock2 kernel: [ 1649.013070]  88003bb4ca80 
8800363ba600 88000c211980 
Apr 11 21:59:36 stock2 kernel: [ 1649.013892]  880067d33e98 
880067d33df8 8122dd97 88003bb4c900
Apr 11 21:59:36 stock2 kernel: [ 1649.014751] Call Trace:
Apr 11 21:59:36 stock2 kernel: [ 1649.015053]  [] 
propagate_mnt+0x120/0x150
Apr 11 21:59:36 stock2 kernel: [ 1649.015643]  [] 
attach_recursive_mnt+0x147/0x230
Apr 11 21:59:36 stock2 kernel: [ 1649.016286]  [] 
graft_tree+0x58/0x90
Apr 11 21:59:36 stock2 kernel: [ 1649.016809]  [] 
do_add_mount+0x8e/0xd0
Apr 11 21:59:36 stock2 kernel: [ 1649.017342]  [] 
do_mount+0x2c0/0xe00
Apr 11 21:59:36 stock2 kernel: [ 1649.017863]  [] ? 
copy_mount_options+0xb4/0x220
Apr 11 21:59:36 stock2 kernel: [ 1649.018466]  [] 
SyS_mount+0x9f/0x100
Apr 11 21:59:36 stock2 kernel: [ 1649.018996]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
Apr 11 21:59:36 stock2 kernel: [ 1649.019631] Code: 39 90 d8 00 00 00 75 ec 8b 
b0 10 01 00 00 48 89 3d 80 e1 f8 00 48 89 05 81 e1 f8 00 39 b1 10 01 00 00 74 
19 48 8b bf d8 00 00 00 <48> 8b 47 10 48 89 3d 5f e1 f8 00 48 89 05 60 e1 f8 00 
8b 43 30 
Apr 11 21:59:36 stock2 kernel: [ 1649.022395] RIP  [] 
propagate_one+0xbe/0x1c0
Apr 11 21:59:36 stock2 kernel: [ 1649.022990]  RSP 
Apr 11 21:59:36 stock2 kernel: [ 1649.023362] CR2: 0010
Apr 11 21:59:36 stock2 kernel: [ 1649.027053] ---[ end trace 46ce79a38cba28a5 
]---

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: Confirmed

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: 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/1572316

Title:
  oops when propagating mounts into containers

Status in linux package in Ubuntu:
  Confirmed
Status in linux 

[Kernel-packages] [Bug 1555344] Re: s390/cpumf: Fix lpp detection

[dann frazier]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  s390/cpumf: Fix lpp detection

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-03-09 10:54:54 ==
  Please backport 

  
http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=fixes=7a76aa95f6f6682db5629449d763251d1c9f8c4e

  The patch is currently in the s390 tree queued for the next merge
  window.  I will attach a patch for convenience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1555344/+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 1572291] Re: s390/pci: add extra padding to function measurement block

[dann frazier]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => In Progress

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  s390/pci: add extra padding to function measurement block

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Please backport upstream commit:

  commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa
  Author: Sebastian Ott 
  Date:   Thu Mar 31 11:48:31 2016 +0200

  s390/pci: add extra padding to function measurement block
  
  Newer machines might use a different (larger) format for function
  measurement blocks. To ensure that we comply with the alignment
  requirement on these machines and prevent memory corruption (when
  firmware writes more data than we expect) add 16 padding bytes
  at the end of the fmb.
  
  Cc: sta...@vger.kernel.org # v4.1+
  Signed-off-by: Sebastian Ott 
  Signed-off-by: Martin Schwidefsky 

   arch/s390/include/asm/pci.h | 3 ++-
   1 file changed, 2 insertions(+), 1 deletion(-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1572291/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Rubens]

Hi Vittorio, the touchpad is working, but not the gestures. Thanks anyways
:-).
El 19 abr. 2016 9:01 p. m., "vittorio" 
escribió:

> hi rubens, for your touchpad issue: what kernel have you? ('uname -a'
> comand in terminal). Some have resolved by updating the kernel to
> xenial-release one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1563110
>
> Title:
>   No sound on Asus e200ha, intel sst with cx2072x codec
>
> Status in ALSA driver:
>   Unknown
> Status in alsa-driver package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I've recently bought an Asus e200ha.
>   Sound in this laptop doesn't work.
>   The sound card is an intel sst with codec conexant cx2072x
>
>   aplay -l:
>   aplay: device_list:268: no soundcard found...
>   in the sound setting there is a "Dummy output"
>   ---
>   ApportVersion: 2.14.1-0ubuntu3.19
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: XFCE
>   DistroRelease: Ubuntu 14.04
>   HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
>   InstallationDate: Installed on 2016-03-28 (0 days ago)
>   InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
>   Lsusb:
>Bus 002 Device 002: ID 0781:5583 SanDisk Corp.
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 13d3:3496 IMC Networks
>Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. E200HA
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic
> root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
>   RelatedPackageVersions:
>linux-restricted-modules-3.19.0-32-generic N/A
>linux-backports-modules-3.19.0-32-generic  N/A
>linux-firmware 1.127.16
>   Tags:  rosa
>   Uname: Linux 3.19.0-32-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 11/26/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: E200HA.203
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: E200HA
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: ATN12345678901234567
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.name: E200HA
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Rubens]

Hi Vittorio, the touchpad is working, but not the gestures. Sorry for
the misunderstanding :-).

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1571791] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 13, failed: 4

[Brad Figg]

tests ran:  13, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-21.37/ms10-35-mcdivittB0-kernel__4.4.0-21.37__2016-04-19_18-41-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/1571791

Title:
  linux: 4.4.0-21.37 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 18. April 2016 18:15 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1571791/+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 1572291] Re: s390/pci: add extra padding to function measurement block

[Tim Gardner]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: New

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Tim Gardner 
(timg-tpi)

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

Title:
  s390/pci: add extra padding to function measurement block

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

Bug description:
  Please backport upstream commit:

  commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa
  Author: Sebastian Ott 
  Date:   Thu Mar 31 11:48:31 2016 +0200

  s390/pci: add extra padding to function measurement block
  
  Newer machines might use a different (larger) format for function
  measurement blocks. To ensure that we comply with the alignment
  requirement on these machines and prevent memory corruption (when
  firmware writes more data than we expect) add 16 padding bytes
  at the end of the fmb.
  
  Cc: sta...@vger.kernel.org # v4.1+
  Signed-off-by: Sebastian Ott 
  Signed-off-by: Martin Schwidefsky 

   arch/s390/include/asm/pci.h | 3 ++-
   1 file changed, 2 insertions(+), 1 deletion(-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572291/+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 1572258] Re: linux-lts-vivid: 3.19.0-59.65~14.04.1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Description changed:

  This bug is for tracking the 3.19.0-59.65~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
- kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase-changed:Tuesday, 19. April 2016 20:00 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.19.0-59.65~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
  -- swm properties --
- phase: Packaging
- kernel-stable-phase-changed:Tuesday, 19. April 2016 20:00 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1572258/+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 1572261] Re: linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Description changed:

  This bug is for tracking the 3.13.0-86.130~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
- kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase-changed:Tuesday, 19. April 2016 20:00 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.13.0-86.130~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
  -- swm properties --
- phase: Packaging
- kernel-stable-phase-changed:Tuesday, 19. April 2016 20:00 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-86.130~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1572261/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[vittorio]

hi rubens, for your touchpad issue: what kernel have you? ('uname -a'
comand in terminal). Some have resolved by updating the kernel to
xenial-release one.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1558847] Re: CVE-2016-3156

[Steve Beattie]

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3156

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in 

[Kernel-packages] [Bug 1556878] Re: CVE-2016-3137

[Steve Beattie]

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3137

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in 

[Kernel-packages] [Bug 1556888] Re: CVE-2016-3140

[Steve Beattie]

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3140

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in 

[Kernel-packages] [Bug 1561388] Re: CVE-2016-3157

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3157

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package 

[Kernel-packages] [Bug 1556880] Re: CVE-2016-3138

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3138

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package 

[Kernel-packages] [Bug 1556877] Re: CVE-2016-3136

[Steve Beattie]

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3136

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in 

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joseph Salisbury]

Thanks for the suggestions @faulpeltz and @Emsi.  I was using the
Windows Server Backup GUI, which allowed me a maximum of 30 minutes
backup intervals.

I now have a Powershell script to kick of one backup after another:

$i=1
while($true)
{
"###"
"Starting backup $i"
"###"
wbadmin start backup -quiet -backupTarget:"\\?\Volume{VOLUME_INFO}" 
-hyperv:"VM_NAME"
"###"
"Finished backup $i"
"###"
$i++
}


I'm re-running the test that took 35 hours to reproduce the bug(Commit
da1674843 as tip of tree).  I hope it causes the bug to trigger much
faster.  If it does, I'll use this method for testing.

If it still takes a considerable amount of time to reproduce, I'll
investigate the snapeshot only method as suggested by @Emsi.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

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

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption

[Steve Beattie]

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  Linux netfilter IPT_SO_SET_REPLACE memory corruption

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-keystone source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-keystone source package in Trusty:
  Fix Released
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-keystone source package in Wily:
  Invalid
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  

[Kernel-packages] [Bug 1572291] Re: s390/pci: add extra padding to function measurement block

[Luciano Chavez]

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  s390/pci: add extra padding to function measurement block

Status in linux package in Ubuntu:
  New

Bug description:
  Please backport upstream commit:

  commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa
  Author: Sebastian Ott 
  Date:   Thu Mar 31 11:48:31 2016 +0200

  s390/pci: add extra padding to function measurement block
  
  Newer machines might use a different (larger) format for function
  measurement blocks. To ensure that we comply with the alignment
  requirement on these machines and prevent memory corruption (when
  firmware writes more data than we expect) add 16 padding bytes
  at the end of the fmb.
  
  Cc: sta...@vger.kernel.org # v4.1+
  Signed-off-by: Sebastian Ott 
  Signed-off-by: Martin Schwidefsky 

   arch/s390/include/asm/pci.h | 3 ++-
   1 file changed, 2 insertions(+), 1 deletion(-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572291/+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 1561414] Re: CVE-2016-2188

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2188

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package 

[Kernel-packages] [Bug 1554260] Re: CVE-2016-2847

[Steve Beattie]

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2847

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Released
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  Fix Released
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-armadaxp 

[Kernel-packages] [Bug 1572291] [NEW] s390/pci: add extra padding to function measurement block

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Please backport upstream commit:

commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa
Author: Sebastian Ott 
Date:   Thu Mar 31 11:48:31 2016 +0200

s390/pci: add extra padding to function measurement block

Newer machines might use a different (larger) format for function
measurement blocks. To ensure that we comply with the alignment
requirement on these machines and prevent memory corruption (when
firmware writes more data than we expect) add 16 padding bytes
at the end of the fmb.

Cc: sta...@vger.kernel.org # v4.1+
Signed-off-by: Sebastian Ott 
Signed-off-by: Martin Schwidefsky 

 arch/s390/include/asm/pci.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-140474 severity-high 
targetmilestone-inin1604
-- 
s390/pci: add extra padding to function measurement block
https://bugs.launchpad.net/bugs/1572291
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1561411] Re: CVE-2016-2186

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2186

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package 

[Kernel-packages] [Bug 1572261] Re: linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 3.13.0-86.130~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 19. April 2016 18:11 UTC
+ kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.13.0-86.130~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
  kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-86.130~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:11 UTC
  kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1572261/+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 1572258] Re: linux-lts-vivid: 3.19.0-59.65~14.04.1 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-59.65~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 19. April 2016 18:00 UTC
+ kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.19.0-59.65~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
  kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. April 2016 18:00 UTC
  kernel-stable-phase-changed:Tuesday, 19. April 2016 19:00 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1572258/+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 1566828] Re: Suspension does not work, freezes the pc

[hesediel84]

@update

I reinstalled the 16.04 from zero and i downloaded 
The image, the header and headers_all
in installed them with the command:  
sudo dpkg -i linux*.deb
 
and now...the new kernels 4.5.1 and also 4.6rc4 does NOT solve the problem. 
Still present.

I dont know..

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

Title:
  Suspension does not work, freezes the pc

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have this notebook
  HP 15 ac 191 nl

  Intel® Core™ i5-5200U with integrated Intel HD 5500
  RAM 8 gb
  DEdicated GPU AMD Radeon R5 M330

  I am running kubuntu 16.04 beta2.

  When i suspend the pc, gettin down the screen or givin the command in the 
menù, the screen goes black but the fan keeps running. So you can hear the fan 
working..and the pc got hot.
  It is also impossible to wake up the pc, it stays freezed in this condition, 
i have to force the shutdown with the power button pressing it for 3 sec. 

  The problem is present every time i try to suspend the pc.
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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-16-generic N/A
   linux-backports-modules-4.4.0-16-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: HP
  dmi.board.version: 96.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1315 F pulseaudio
   /dev/snd/pcmC1D0c:   ale1315 F...m pulseaudio
   /dev/snd/pcmC1D0p:   ale1315 F...m pulseaudio
   /dev/snd/controlC1:  ale1315 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
  InstallationDate: Installed on 2016-03-31 (5 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed 
root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  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-16-generic N/A
   

[Kernel-packages] [Bug 1538428] Re: CVE-2016-2053

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Fix Committed

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

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

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

** Description changed:

  [Denial of service with specially crafted key file]
  
- Break-Fix: 3d167d68e3805ee45ed2e8412fc03ed919c54c24 -
+ Break-Fix: 3d167d68e3805ee45ed2e8412fc03ed919c54c24
+ 0d62e9dd6da45bbf0f33a8617afc5fe774c8f45f

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

Title:
  CVE-2016-2053

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in 

[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2184

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package 

[Kernel-packages] [Bug 1561410] Re: CVE-2016-2185

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2185

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package 

[Kernel-packages] [Bug 1561389] Re: CVE-2016-0821

[Steve Beattie]

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-0821

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  

[Kernel-packages] [Bug 1555765] Re: Backport upstream bugfixes to ubuntu-16.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  Backport upstream bugfixes to ubuntu-16.04

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

Bug description:
  Backport the below upstream "powernv-cpufreq" bug fixes to ubuntu
  16.04:

  The below listed patchset is accepted upstream and is in linux-next.

  1) 86622cb8c57abb05fe95bea3a068949c0ca79fc3 cpufreq: powernv: Free 'chips' on 
module exit
  2) 6d167a44e6c8da3316e037b788585fcf96112bea  cpufreq: powernv: Hot-plug safe 
the kworker thread
  3) 96c4726f01cdbf53acf74cf2394e287d74bf40a3 cpufreq: powernv: Remove 
cpu_to_chip_id() from hot-path
  4) 0306e481d479a58eff17c27adf213fbb5822946b cpufreq: powernv/tracing: Add 
powernv_throttle tracepoint
  5)c89f2682a39192433c296bf97b834fd2815a758b cpufreq: powernv: Replace pr_info 
with trace print for throttle event

  Two more patches that are posted upstream:
  6) http://marc.info/?l=linuxppc-embedded=145648325218686=2
  7) http://marc.info/?l=linux-pm=145648316718658=2

  1) Fixes a memory leak
  2) Makes the worker thread hot-plug safe which is scheduled on an OCC event.
  3) Fixes the below 

[Kernel-packages] [Bug 1549494] Re: arm64: guest hangs when ntpd is running

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  arm64: guest hangs when ntpd is running

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

Bug description:
  SRU Justification:

  Impact: KVM guests hang on arm64 host running ntpd

  Fix: From linux-next:
  commit 1c5631c73fc2261a5df64a72c155cb53dcdc0c45
  Author: Marc Zyngier 
  Date:   Wed Apr 6 09:37:22 2016 +0100

  KVM: arm/arm64: Handle forward time correction gracefully
  
  BugLink: http://bugs.launchpad.net/bugs/1549494
  
  On a host that runs NTP, corrections can have a direct impact on
  the background timer that we program on the behalf of a vcpu.
  
  In particular, NTP performing a forward correction will result in
  a timer expiring sooner than expected from a guest point of view.
  Not a big deal, we kick the vcpu anyway.
  
  But on wake-up, the vcpu thread is going to perform a check to
  find out whether or not it should block. And at that point, the
  timer check is going to say "timer has not expired yet, go back
  to sleep". This results 

[Kernel-packages] [Bug 1567091] Re: fixes for thunderx nic in multiqueue mode

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  fixes for thunderx nic in multiqueue mode

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

Bug description:
  There are a number of bug fixes in the thunderx nic driver for multi-
  queue support that have landed upstream since 4.4:

  commit 4fbe366ce304d836d53685c1dd26865dc1fea66c
  Merge: 1eea84b ad2eceb
  Author: David S. Miller 
  Date:   Wed Feb 17 22:24:57 2016 -0500

  Merge branch 'thunderx-fixes'
  
  Sunil Goutham says:
  
  
  net: thunderx: Miscellaneous fixes
  
  This patch series fixes couple of issues w.r.t multiqset mode
  and receive packet statastics.
  
  
  Signed-off-by: David S. Miller 

  commit ad2ecebd67d8a80fe5412d11df375a5ed2db7cd1
  Author: Sunil Goutham 
  Date:   Tue Feb 16 16:29:51 2016 +0530

  net: thunderx: Fix receive packet stats
  
  Counting rx packets for every CQE_RX in CQ irq handler is incorrect.
  Synchronization is missing when 

[Kernel-packages] [Bug 1554260] Re: CVE-2016-2847

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2016-2847

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring 

[Kernel-packages] [Bug 1554003] Re: xenial kernel crash on HP BL460c G7 (qla24xx problem?)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  xenial kernel crash on HP BL460c G7 (qla24xx problem?)

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

Bug description:
  Dear Members,

  Latest Xenial kernel (linux-image-generic-4.4.0-8-generic) is crash on
  booting. Same problem with 4.4.0-9 and 4.4.0-10.

  
  [1.654419] qla2xxx [:06:00.1]-0034:3: MSI-X: Unsupported ISP 
  2432 SSVID/SSDID (0x103C,0x1705).
  [1.685273] hid-generic 0003:03F0:7029.0001: in
  [1.685273] hid-generic 0003:03F0:7029.0001: input,hidraw0: USB HID 
  v1.01 Keyboard [HP  Virtual Keyboard ] on usb-:01:00.4-1/input0
  [1.685455] input: HP  Virtual Keyboard  as 
  
/devices/pci:00/:00:1c.4/:01:00.4/usb6/6-1/6-1:1.1/0003:03F0:7029.0002/input/inpu
 
  1048576 bytes) :0
  1:00.4/usb6/6-1/6-1:1.1/0003:03F0:7029.0002/input/inpu
  [2.001109] CR2: 0050
  [2.001170] ---
  [ end trace 20a247b9d60f8e00 ]---
  [2.001232] Kernel panic - not syncing: Fatal exception in interrup
  [2.001232] Kernel panic - not syncing: Fatal exception in interrupt
  [

[Kernel-packages] [Bug 1555344] Re: s390/cpumf: Fix lpp detection

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  s390/cpumf: Fix lpp detection

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-03-09 10:54:54 ==
  Please backport 

  
http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=fixes=7a76aa95f6f6682db5629449d763251d1c9f8c4e

  The patch is currently in the s390 tree queued for the next merge
  window.  I will attach a patch for convenience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1555344/+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 1536245] Re: s390x kernel image needs weightwatchers

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  s390x kernel image needs weightwatchers

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

Bug description:
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/cdrom/vmlinuz

  is 6.6M

  http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-
  s390x/current/images/generic/kernel.debian

  is 12M

  Yet, s390x has much less drivers. I would have expected it to be
  slimmer than amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536245/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  Kernel Panic in Ubuntu 16.04 netboot installer

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

Bug description:
  Hello,

  we are working with the Ubuntu 16.04 developer preview. Yesterday we
  observed a kernel panic of the installer kernel on one of our machines.
  The machine is of type

  Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015

  We are installing the machine via PXEboot with the netboot installer
  system using the following kernel/initrd:

  
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz
  
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux

  When using this version the kernel crashes (see attached log file). We
  have also tried the version 447 instead of 446. This version shows
  the same effect.

  Some time ago we worked with the installer version 441. This release
  worked as expected.

  Someone out there knows what has changed? It seems that the kernel has a
  problem with the harddisk IO system. In our machine 

[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  linux: MokSBState is ignored

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

Bug description:
  Ubuntu-4.4.0-20.36 was released with signed module enforcement
  enabled, but contained no way of disabling secure boot for DKMS.
  Without these kernel patches it is possible to get your machine in an
  unbootable state, especially if you don't have a fallback kernel.

  This patch set implements the ability to disable secure boot on demand
  from user space (with some password shennaigans). If one boots in
  secure boot mode and then installs a third party module (such as
  DKMS), then a dialog is displayed giving the user an option to disable
  secure boot, thereby also disabling module signature verification.
  Patch 1/2 is a scaffold patch of which only the GUID macros are
  actually used. The rest of the code is fenced by
  CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series.
  Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3
  simply prints a bit more informative state information.

  Information regarding 

[Kernel-packages] [Bug 1567581] Re: Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after upgrading to Ubuntu 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
  upgrading to Ubuntu 16.04

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

Bug description:
  Not seeing sgX device for LUNs after upgrading to Ubuntu 16.04 -17
  kernel

  This is probably caused by the following patch added on Ubuntu kernel
  4.4.0-17:

  - SAUCE: (noup) powerpc/pci: Assign fixed PHB number based on device-tree
  properties".

  That said, i would like to ask Canonical to revert the SAUCE patch
  42a1e725ec14f0ce4d5e5b0fcf6d23260d0dcc08. It has a bad side effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567581/+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 1571018] Re: CVE-2015-8845

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Fix Committed

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Fix Committed

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

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

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

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2015-8845

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp 

[Kernel-packages] [Bug 1566468] Re: systemd-modules-load.service: Failing due to missing module 'ib_iser'

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  systemd-modules-load.service: Failing due to missing module 'ib_iser'

Status in linux package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in open-iscsi source package in Xenial:
  Invalid

Bug description:
  On a number of VMs using Xenial daily builds 20160330 and 20160403,
  out of the box (just after booting for the first time), the following
  appears in dmesg at boot time:

  systemd[1]: systemd-modules-load.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: Failed to start Load Kernel Modules.
  systemd[1]: systemd-modules-load.service: Unit entered failed state.
  systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

  The following related complaint appears in /var/log/syslog:

  ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp'
  ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser'

  It looks like 'ib_iser' is some Mellanox-related module, which I don't
  *think* is something that a stock cloudimg install should attempt to
  

[Kernel-packages] [Bug 1571069] Re: linux: 4.4.0-20.36 -proposed tracker

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1571791 ***
https://bugs.launchpad.net/bugs/1571791

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  linux: 4.4.0-20.36 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

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

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

[Kernel-packages] [Bug 1571791] Re: linux: 4.4.0-21.37 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  linux: 4.4.0-21.37 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 18. April 2016 18:15 UTC
  -- swm properties --
  phase: Promoted 

[Kernel-packages] [Bug 1570348] Re: linux: 4.4.0-19.35 -proposed tracker

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1571791 ***
https://bugs.launchpad.net/bugs/1571791

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  linux: 4.4.0-19.35 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

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

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

[Kernel-packages] [Bug 1563916] Re: CVE-2016-0774

[Steve Beattie]

** Description changed:

  pipe buffer state corruption after unsuccessful atomic read from pipe
+ 
+ Break-Fix: local-2016-0774-break local-2016-0774-fix

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

Title:
  CVE-2016-0774

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-armadaxp source package in Xenial:
  

[Kernel-packages] [Bug 1567093] Re: thunderx nic performance improvements

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  thunderx nic performance improvements

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

Bug description:
  Two patches have landed upstream that improve thunderx nic
  performance:

  commit b6e4038262bc933f2ef5427b6bcd2607d02ba4bb
  Merge: 9bd160b 1d36879
  Author: David S. Miller 
  Date:   Mon Mar 14 12:33:37 2016 -0400

  Merge branch 'thunderx-perf'
  
  Sunil Goutham says:
  
  
  net: thunderx: Performance enhancement changes
  
  Below patches attempts to improve performance by reducing
  no of atomic operations while allocating new receive buffers
  and reducing cache misses by adjusting nicvf structure elements.
  
  Changes from v1:
   No changes, resubmitting a fresh as per David's suggestion.
  
  
  Signed-off-by: David S. Miller 

  commit 1d368790bc2d4111feae6fcc0b3b68d6ae92ff0f
  Author: Sunil Goutham 
  Date:   Mon Mar 14 16:36:15 2016 +0530

  net: thunderx: 

[Kernel-packages] [Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  [regression]: Failed to call clock_adjtime(): Invalid argument

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

Bug description:
  Steps to reproduce:

  1) Force a time delta
  date -s "now - 1 hour"
  2) Restart systemd-timesyncd to have it fix the time
  systemctl restart systemd-timesyncd

  Expected behavior:

  The clock should be back in sync.

  Actual (problematic) behavior:

  The clock stays out of sync because the call to clock_adjtime()
  failed.

  # systemctl status systemd-timesyncd.service 
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: active (running) since Tue 2016-04-05 14:26:25 EDT; 1s ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 11567 (systemd-timesyn)
 Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 512)
 Memory: 

[Kernel-packages] [Bug 1566221] Re: linux: Enforce signed module loading when UEFI secure boot

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  linux: Enforce signed module loading when UEFI secure boot

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

Bug description:
  Add code to implement secure boot checks. Unsigned or incorrectly
  signed modules will continue to install while tainting the kernel
  _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566221/+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 1564901] Re: xpad rumble causes full system hang

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  xpad rumble causes full system hang

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux-lts-vivid package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  To reproduce:

  1. Have a wired xbox controller.
  2. Modify the SDL2 testrumble.c so it runs forever. (attached)
  3. Build and run it.
  4. Kill it with sigkill from another terminal.

  Expected result: The program should stop running.

  Actual result: Entire computer freezes. Soundcard continuously plays
  the last second of audio. No response from any input devices or the
  network.

  The bug can also be reproduced by playing the game Borderlands 2 while
  having a wired xbox controller connected. The system will randomly
  freeze in the exact same way.

  The bug has existed since at least 14.04.

  The last thing the kernel prints is this:

  Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 

[Kernel-packages] [Bug 1570906] Re: sysfs mount failure during stateful lxd snapshots

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-21.37

---
linux (4.4.0-21.37) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571791

  * linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
- SAUCE: (noup) efi: Disable secure boot if shim is in insecure mode
- SAUCE: (noup) Display MOKSBState when disabled

linux (4.4.0-20.36) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1571069

  * sysfs mount failure during stateful lxd snapshots (LP: #1570906)
- SAUCE: kernfs: Do not match superblock in another user namespace when
  mounting

  * Kernel Panic in Ubuntu 16.04 netboot installer (LP: #1570441)
- x86/topology: Fix logical package mapping
- x86/topology: Fix Intel HT disable
- x86/topology: Use total_cpus not nr_cpu_ids for logical packages
- xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
- x86/topology: Fix AMD core count

  * [regression]: Failed to call clock_adjtime(): Invalid argument
(LP: #1566465)
- ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO

linux (4.4.0-19.35) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1570348

  * CVE-2016-2847 (LP: #1554260)
- pipe: limit the per-user amount of pages allocated in pipes

  * xenial kernel crash on HP BL460c G7 (qla24xx problem?) (LP: #1554003)
- SAUCE: (noup) qla2xxx: Add irq affinity notification V2

  * arm64: guest hangs when ntpd is running (LP: #1549494)
- SAUCE: (noup) KVM: arm/arm64: Handle forward time correction gracefully

  * linux: Enforce signed module loading when UEFI secure boot (LP: #1566221)
- [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y

  * s390/cpumf: Fix lpp detection (LP: #1555344)
- s390/facilities: use stfl mnemonic instead of insn magic
- s390/facilities: always use lowcore's stfle field for storing facility 
bits
- s390/cpumf: Fix lpp detection

  * s390x kernel image needs weightwatchers (LP: #1536245)
- [Config] s390x: Use compressed kernel bzImage

  * Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after
upgrading to Ubuntu 16.04 (LP: #1567581)
- Revert "UBUNTU: SAUCE: (noup) powerpc/pci: Assign fixed PHB number based 
on
  device-tree properties"

  * Backport upstream bugfixes to ubuntu-16.04 (LP: #1555765)
- cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path
- Revert "cpufreq: postfix policy directory with the first CPU in 
related_cpus"
- cpufreq: powernv: Add sysfs attributes to show throttle stats

  * systemd-modules-load.service: Failing due to missing module 'ib_iser' (LP: 
#1566468)
- [Config] Add ib_iser to generic inclusion list

  * thunderx nic performance improvements (LP: #1567093)
- net: thunderx: Set recevie buffer page usage count in bulk
- net: thunderx: Adjust nicvf structure to reduce cache misses

  * fixes for thunderx nic in multiqueue mode (LP: #1567091)
- net: thunderx: Fix for multiqset not configured upon interface toggle
- net: thunderx: Fix for HW TSO not enabled for secondary qsets
- net: thunderx: Fix receive packet stats

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs after CONFIG_DRM_I915_BPO_PRELIMINARY_HW_SUPPORT=n

  * Miscellaneous upstream changes (LP: #1564901)
- Input: xpad - correctly handle concurrent LED and FF requests

 -- Tim Gardner   Mon, 18 Apr 2016 07:00:22
-0600

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2847

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

Title:
  sysfs mount failure during stateful lxd snapshots

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

Bug description:
  SRU Justification:

  Impact: Stateful lxd container snapshotting fails due to a failure to
  mount the container's sysfs in the host's user namespace. This is a
  regression.

  Fix: Force kernfs to use a new super block for mounts in different
  user namespaces.

  Test Case: "lxc snapshot --stateful " fails in the current
  xenial kernel without the fix. It succeeds with the fix applied.

  ---

  During a stateful lxd snapshot criu tries to mount sysfs for the
  container's network namespace from a different user namespace. This
  fails in xenial because sget() won't allow mounting the same super
  block in different user namespaces.

  With sysfs there's no reason that this needs to use the same super
  block, so kernfs can be updated so that a super block with the same ns
  tag but in a different userns is not matched. The only other kernfs-
  based filesystem mountable from non-init user namespaces is cgroupfs,
  and 

[Kernel-packages] [Bug 1571013] Re: CVE-2015-8844

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Fix Committed

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Fix Committed

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

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

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

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2015-8844

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp