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

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not 

[Kernel-packages] [Bug 1649292] CRDA.txt

[Thomas Fili]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1649292/+attachment/4791060/+files/CRDA.txt

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session 

[Kernel-packages] [Bug 1649292] AlsaInfo.txt

[Thomas Fili]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1649292/+attachment/4791059/+files/AlsaInfo.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/1649292

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as 

[Kernel-packages] [Bug 1649292] Lsusb.txt

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session 

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

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

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

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not 

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

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

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

[Thomas Fili]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1649292/+attachment/4791070/+files/WifiSyslog.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+attachment/4790718/+files/AlsaInfo.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/1649292

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 

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

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

[Kernel-packages] [Bug 1649292] Lspci.txt

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session 

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

[Thomas Fili]

apport information

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session 

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

[Thomas Fili]

apport information

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

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

[Kernel-packages] [Bug 1649292] Re: NFS client : permission denied when trying to access subshare, since kernel 4.4.0-31

[Thomas Fili]

Sorry, i forget to trigger the problem before sending apport-collect ...
I will send the right one and delete the old

When i try to login i got :

Could not chdir to home directory /home/VI/staff/fili/linux : Permission denied
...
-bash: /home/VI/staff/fili/linux/.bash_profile: Permisson denied

But when i try to mount the subshare directly in fstab i got :

mount.nfs: access denied by server while mounting ...

** Description changed:

  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.
  
  I tried this under (K)ubuntu Trusty and Xenial and also with the ubuntu
  based Mint Versions 17.3 Rosa an 18 Sarah.
  
  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package
  
  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)
  
  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.
  
  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.
  
  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI
  
  My posix homedirectory path is /home/VI/staff/fili/linux
  
  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the permission
  denied.
  
  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z
  
  I tried also autofs but with the same result.
  
  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
  
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
  
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:
  
  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  
  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  system 1876 F pulseaudio
+  /dev/snd/controlC0:  system 1876 F pulseaudio
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
+ InstallationDate: Installed on 2016-10-17 (56 days ago)
+ InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig:
+  enp7s0no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
+ ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  

[Kernel-packages] [Bug 1647787] onibi (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onibi__3.19.0-78.86__2016-12-13_05-23-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1647787] onibi (amd64) - tests ran: 33, failed: 5

[Brad Figg]

tests ran:  33, failed: 5;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onibi__3.19.0-78.86__2016-12-13_03-37-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1647787] Re: linux: 3.19.0-78.86 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver

[bugproxy]

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

** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4791006/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4791007/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

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

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

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

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

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

[bugproxy]

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

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

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

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

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

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

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

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

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

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

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-13_03-25-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

tests ran:  10, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/s2lp6g002__4.8.0-31.33__2016-12-13_03-49-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1629554] Re: After pressing suspend button, resume never works.

[Launchpad Bug Tracker]

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

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

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

Title:
  After pressing suspend button, resume never works.

Status in linux package in Ubuntu:
  Expired

Bug description:
  Suspending and then resuming by using the keyboard button has worked very 
well on Ubuntu 14 LTS.
  After upgrading to 16.04 LTS it has never worked.

  The computer suspends, but no keyboard press can ever wake it again. As it 
could before.
  Pressing the power on/off button on the computer does not work either. 
Holding it in long enough
  will force a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashReports:
   640:0:116:551826:2016-10-01 15:36:55.950586080 +0200:2016-10-01 
15:36:56.950586080 +0200:/var/crash/susres.2016-10-01_15:36:07.837470.crash
   640:0:116:1686186:2016-09-30 19:18:17.126433916 +0200:2016-09-30 
19:18:17.202434226 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
   600:109:116:0:2016-10-01 15:37:06.852207459 +0200:2016-10-01 
15:37:06.852207459 +0200:/var/crash/susres.2016-10-01_15:36:07.837470.uploaded
   644:0:116:0:2016-10-01 15:37:04.228927639 +0200:2016-10-01 
15:37:04.228927639 +0200:/var/crash/susres.2016-10-01_15:36:07.837470.upload
  CurrentDesktop: Unity
  Date: Sat Oct  1 15:38:35 2016
  InstallationDate: Installed on 2015-03-07 (573 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (40 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  fredrik2248 F pulseaudio
   /dev/snd/controlC0:  fredrik2248 F pulseaudio
   /dev/snd/controlC2:  fredrik2248 F pulseaudio
   /dev/snd/controlC1:  fredrik2248 F pulseaudio
  CRDA:
   country AW: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=da28ba36-6689-4c4b-9fa9-596ec5bfa1c0
  InstallationDate: Installed on 2015-03-07 (573 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Apple Inc. iMac11,3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=191ae4fd-e41c-40d3-a976-216ac6b1367d ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/11
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B01.1112090906
  dmi.board.name: Mac-F2238BAE
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac11,3
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238BAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B01.1112090906:bd12/09/11:svnAppleInc.:pniMac11,3:pvr1.0:rvnAppleInc.:rnMac-F2238BAE:rvriMac11,3:cvnAppleInc.:ct13:cvrMac-F2238BAE:
  dmi.product.name: iMac11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629554/+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 1629917] Re: When using external monitor displays become unstable

[Launchpad Bug Tracker]

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

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

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

Title:
  When using external monitor displays become unstable

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am using a HP Pavilion dv6 with ATI Mobility Radeon HD 5650 Graphics.  
After upgrading to ubuntu 16.04 LTS using Gallium 0.4 on AMD REDWOOD (DRM 
2.43.0, LLVM 3.8.0).  I get an unstable display when I plug in my external 
display through the VGA port.  The system keeps cycling through the display 
options using only one display, then both then extended and then the other 
display.  This happens every 10-15 seconds.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   herman 1805 F...m pulseaudio
   /dev/snd/controlC0:  herman 1805 F pulseaudio
   /dev/snd/controlC1:  herman 1805 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=bf329afe-facd-48b6-8900-b8dac03d336b
  InstallationDate: Installed on 2014-04-25 (901 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=c9235e01-b5fa-4362-bfca-c6763140abba ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (22 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1448
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 65.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr048E10242B102:rvnHewlett-Packard:rn1448:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 048E10242B102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629917/+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 1631565] Re: hibernate does not work

[Launchpad Bug Tracker]

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

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

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

Title:
  hibernate does not work

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have tried many corrections found on the web but the hibernate
  function does not work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seriovento   1739 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct  8 08:28:58 2016
  HibernationDevice: RESUME=UUID=97625b83-52e9-45f2-a9b5-0760feb84ed3
  InstallationDate: Installed on 2016-10-05 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Dell Inc. XPS M1330
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=UUID=25b1036c-861d-4bab-b3b1-325d89cd25d6 ro 
resume=UUID=97625b83-52e9-45f2-a9b5-0760feb84ed3 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0N6705
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd06/19/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0N6705:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1330
  dmi.sys.vendor: Dell Inc.

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

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

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

[bugproxy]

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver

[bugproxy]

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

** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4790602/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4735551/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

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

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

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

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

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

[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect

[Scott Cowles Jacobs]

>4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6

Is "Michael Bock (michi-bock)" referring to a different problem?

I installed the previous version (4.8.0-29.31), which said:
 "* Yakkety update to v4.8.11 stable release (LP: #1645421)"
and it fixed a timer problem ("usb: increase ohci watchdog delay to 275 msec").
It certainly fixed my printing problem (most USB devices failed every time I 
tried to print).

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

Title:
  specific USB devices disconnect and don't reconnect

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

Bug description:
  2 USB ports randomly disconnect and don't reconnect (it's always the
  same two), and in dmesg all I get is

  "
  [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
  [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
  [ 1276.916553] usb 3-1: USB disconnect, device number 2
  [ 1277.017302] usb 3-2: USB disconnect, device number 3
  "
  This only started happening when Yakkety went to the 4.8 branch, with 4.7 
branch this doesn't occur, hence the bug report since it's unlikely that a 
hardware failure will only stick to one OS and one branch of the kernel for 
that OS. (these USB ports don't randomly die on Windows or BSD, I've tested 
that in the past couple of days)

  
  kernel version: 4.8.0.17.27
  Ubuntu version
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  c_smith2213 F pulseaudio
   /dev/snd/controlC0:  c_smith2213 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+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 1647787] onza (amd64) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-13_02-11-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1648034] onibi (i386) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/onibi__4.8.0-31.33__2016-12-13_00-57-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

The lp1649326 version failed to boot for me, but in a different way from
the others on SOME launches -- rather than crashing VirtualBox with a
"guru meditation" dialog box, it displayed the following messages within
the emulated environment:

failed to get file info size
failed to alloc highmem for files

The VM then hung. This occurred when I launched using VirtualBox's
built-in EFI shell or when I launched from rEFInd. When I launched from
an EFI shell that was in turn launched by rEFInd, VirtualBox produced
the same "guru meditation" dialog box followed by a VM crash described
earlier.

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1647787] onza (i386) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-13_00-47-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1647787] onza (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-12_23-11-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1648034] onibi (amd64) - tests ran: 33, failed: 1

[Brad Figg]

tests ran:  33, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/onibi__4.8.0-31.33__2016-12-12_22-24-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[misko]

Further info:
After adding this line to my modprobe-settings:
options snd-hda-intel enable=1,0
(which disables the audio-output on the HDMI-port)
I was not able to reproduce the issue anymore.

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

  During that time:
  - Fans run high
  - laptop is completely unuseable (no mouse or keyboard-input accepted, can't 
switch to other terminal, etc ...) - only a long press to the power-button 
helps .
  - network-connections break (tried to monitor the system remotely, but when 
the error occurs, also the ssh-connection fails)
  - the kern.log stops and contains only a few lines of rubbish:
  Dec  3 11:01:37 orbit kernel: [   18.951805] ACPI: \_SB_.PCI0.PEG0.PEGP: 
failed to evaluate _DSM
  Dec  3 11:01:37 orbit kernel: [   18.951808] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20160422/nsarguments-95)
  Dec  3 11:01:37 orbit kernel: [   18.951891] nouveau :01:00.0: DRM: 
suspending console...
  Dec  3 11:01:37 orbit kernel: [   18.951894] nouveau :01:00.0: DRM: 
suspending display...
  Dec  3 11:01:37 orbit kernel: [   18.951902] nouveau :01:00.0: DRM: 
evicting buffers...
  Dec  3 11:01:37 orbit kernel: [   18.960908] nouveau :01:00.0: DRM: 
waiting for kernel channels to go idle...
  Dec  3 11:01:37 orbit kernel: [   18.960935] nouveau :01:00.0: DRM: 
suspending client object trees...
  Dec  3 11:01:37 orbit kernel: [   18.961192] nouveau :01:00.0: DRM: 
suspending kernel object tree...
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  ...
  - installed and tested kernel-crashdump, but in this situation it is not 
triggered (or fails to write a coredump)
  - (once I tried to leave the machin alone for about 30 min, it does not 
recover...)

  As a last resort, I installed netconsole and captured the kernel.log
  on a remote machine, this revealed, that during the lookup, following
  "soft lockups" occur:

  [  107.926161] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[baloo_file:2491]
  [  107.926172] Modules linked in: vmnet(OE) vmw_vsock_vmci_transport vsock 
vmw_vmci vmmon(OE) ccm rfcomm bnep joydev acer_wmi sparse_keymap 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate arc4 intel_rapl_perf 
ath9k ath9k_common ath9k_hw ath input_leds mac80211 uvcvideo serio_raw 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 ath3k videobuf2_core btusb 
btrtl videodev btbcm rtsx_pci_ms btintel cfg80211 media snd_hda_codec_realtek 
bluetooth snd_hda_codec_generic lpc_ich memstick snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_seq_midi snd_pcm[  135.919531] NMI watchdog: BUG: 
soft lockup - CPU#0 stuck for 22s! [baloo_file:2491]
  [  135.919536] Modules linked in: vmnet(OE) vmw_vsock_vmci_transport vsock 
vmw_vmci vmmon(OE) ccm rfcomm bnep joydev acer_wmi sparse_keymap 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate arc4 intel_rapl_perf 
ath9k ath9k_common ath9k_hw ath input_leds mac80211 uvcvideo serio_raw 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 ath3k videobuf2_core btusb 
btrtl videodev btbcm 

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

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-12_21-49-00/results-index.html

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

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Joseph Salisbury]

I started a kernel bisect between 3.13.0-100 and 3.13.0-101. The kernel
bisect will require testing of about 6 test kernels.

I built the first test kernel, up to the following commit:
b9d249e8599e305f77dfc83c5bd9dadef87d4e23

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

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

Thanks in advance

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Stunts]

Ok, so it turns out I'm still having some issues with this after OTA-14.
I can still pair the phone with the Hands Free System (HFS), but...
I can only do this if I make the phone search for the HFS. If I try the pairing 
by having the HFS search for the phone, I get an error - the PIN (hardcoded to 
) is requested by the HFS, but the phone never displays any requests, and 
the connection fails with an error.
Would a new log file, this time with this very behaviour, be interesting for 
further debugging?

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Joseph Salisbury]

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

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Tags added: performing-bisect

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1648034] onibi (i386) - tests ran: 5, failed: 2

[Brad Figg]

tests ran:   5, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/onibi__4.8.0-31.33__2016-12-12_17-19-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/modoc__4.8.0-31.33__2016-12-12_21-30-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1647787] dwalin (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/dwalin__3.19.0-78.86__2016-12-12_20-53-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1649292] Re: NFS client : permission denied when trying to access subshare, since kernel 4.4.0-31

[Seth Forshee]

There's nothing interesting in the logs.

Can you confirm one thing for me - the error you get is "permission
denied" and not "operation not permitted"? Those represent different
error codes, so I want to be certain which one you're getting. Thanks.

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+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 1648873] Re: Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode, sig: 5 [#1] " (lpfc)

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-December/081398.html

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

Title:
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel
  mode, sig: 5 [#1] " (lpfc)

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in debian-installer source package in Yakkety:
  New
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #33 - Mauricio Faria De Oliveira - 2016-12-09 06:49:57 ==

  Hi Canonical,

  Can you please apply this patch [1] to 16.10 and 16.04.x HWE (4.8) ?
  It's fixes a regression introduced in 4.8.

  As you can see, it's in the SCSI maintainer (James Bottomley)'s
  'fixes' branch, but didn't make 4.9-rc8 (maybe he considered it late
  for this one).

  We have installer, boot, and post-boot problems due to this one.
  It'd be good if the netboot images for 16.04.x HWE kernel can get it too.

  Thank you,

  [1] scsi: lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put() 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=2319f847a8910cff1d46c9b66aa1dd7cc3e836a9

  Historical context:

  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-21 02:39:35 ==
  ---Problem Description---
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode. " 
(kernel: 4.8.0-27)
   
  Machine Type = Power8 baremetal  
   
  ---boot type---
  QEMU direct boot kernel/initrd
   
  ---Kernel cmdline used to launch install---
  On a Power8 server,  Using kernel and initrd images, 

  netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=98:BE:94:00:4C:68 netcfg/get_ipaddress=9.47.67.159/20 
netcfg/get_gateway=9.47.79.254 netcfg/get_nameservers=
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
   
  ---Point of failure---
  Other failure during installation (stage 1)

  == Comment: #1 - HARSHA THYAGARAJA - 2016-11-21 02:41:54 ==
  The netboot install fails and Call traces are seen at the Disk detection step.

  == Comment: #8 - Mauricio Faria De Oliveira - 2016-11-21 15:58:25 ==
  Finally got it.

  The assembly offset/code + the trap signal is due to this BUG_ON(),
  and the second condition triggered the trap.

  Checking why piocb is not NULL but piocb->vport is NULL.
  This might have happened in the lpfc_linkdown_port() path, in the stack trace.

  Would need a more readable console log (ie, dmesg, as requested in
  comments 5, 3) to help understanding it.

  --

  static int
  lpfc_sli_ringtxcmpl_put(struct lpfc_hba *phba, struct lpfc_sli_ring *pring,
  struct lpfc_iocbq *piocb)
  {
  lockdep_assert_held(>hbalock);

  BUG_ON(!piocb || !piocb->vport);
  <...>
  }

  [  226.147886] NIP [db7324c0]
  lpfc_sli_ringtxcmpl_put+0x48/0x120 [lpfc]

  0x2478 + 0x48 = 0x24c0 (tdnei; trap doubleword not equal immediate)

  2478 :
  <...>
  2498:   78 2b bf 7c mr  r31,r5 // r31 is *piocb (r5 is the 
3rd function parameter)
  249c:   78 1b 7d 7c mr  r29,r3
  24a0:   78 23 9e 7c mr  r30,r4
  24a4:   01 00 00 48 bl  24a4  
// probably converted at module load time to the call lockdep_assert_held()
  24a8:   00 00 00 60 nop
  24ac:   00 00 bf 2f cmpdi   cr7,r31,0 // compare piocb with 0. 
checking for NULL.
  24b0:   70 00 9e 41 beq cr7,2520 
 // if equal to zero, branch out. done w/ the  
former part of the OR check.
  24b4:   e8 00 3f e9 ld  r9,232(r31) // an offset of piocb. 
probably piocb->vport in the bug_on
  24b8:   74 00 29 7d cntlzd  r9,r9 // count leading zeroes. if r59 
is null (0), leading zeroes is 64 (binary: 0100_, bit 6 is 1, and 6 LSbs 
[bits 5-0] are 0)
  24bc:   82 d1 29 79 rldicl  r9,r9,58,6 // rotate left 58 (ie, 
those 6 LSbs are now MSbs, and that bit 6 from 64 was rotated in the register 
and is now bit 0, the LSb), now AND the 6 MSbs w/ 0-bits, and the all lower 
bits with 1-bits (ie, save the LSb). 
  24c0:   00 00 09 0b tdnei   r9,0 // trap if not equal to zero. 
(ie, the whole r9 was zero, with 64 leading/consecutive zeroes, then bit 6 is 
1, it becomes bit 0.. 

[Kernel-packages] [Bug 1574758] Re: i915 HDMI display turns off during boot after upgrade to 16.04

[Daniel Drake]

Problem no longer occurs on 4.8.0-30-generic (Ubuntu 16.10)

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

Title:
  i915 HDMI display turns off during boot after upgrade to 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 15.10 was working fine, but on upgrading to 16.04, my HDMI
  display goes into low-power mode once the kernel starts booting.

  Logging in over ssh I can see these errors in the kernel log:

  [1.730599] i915 :00:02.0: No connectors reported connected with modes
  [1.730607] [drm] Cannot find any crtc or sizes - going 1024x768

  System is an Intel NUC DN2820FYK
  00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c)

  Kernel version: linux-image-4.4.0-21-generic

  Workaround: add video=HDMI-A-1:1920x1080@60D to kernel parameters
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsd1696 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e53c2a43-d5d9-4c58-9bae-a6d63b8a4fa1
  InstallationDate: Installed on 2014-08-30 (604 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: � 
�
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=39a14ffe-9286-4cfa-9362-bf5bfef37843 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 
video=HDMI-A-1:1920x1080@60D
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/12/2014
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FYBYT10H.86A.0045.2014.1212.1150
  dmi.board.name: DN2820FYK
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H24582-201
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: �
  dmi.chassis.version: �
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFYBYT10H.86A.0045.2014.1212.1150:bd12/12/2014:svn:pn:pvr:rvnIntelCorporation:rnDN2820FYK:rvrH24582-201:cvn:ct3:cvr:
  dmi.product.name: �
  dmi.product.version: �
  dmi.sys.vendor: �

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574758/+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 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

[Tim Gardner]

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Ubuntu Kernel Team (ubuntu-kernel-team)
   Status: Triaged

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Ubuntu Kernel Team (ubuntu-kernel-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/1215411

Title:
  libcpupower.so is not installed from linux-tools (saucy)

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

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+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 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!

[Cristian Aravena Romero]

Hello:

https://bugzilla.kernel.org/show_bug.cgi?id=111291#c10

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

Title:
  uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not
  initialized!

Status in Skylinux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
  [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was 
not initialized!
  [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-14-generic 4.8.0-14.15
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2032 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2032 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 22 17:20:51 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (424 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-14-generic N/A
   linux-backports-modules-4.8.0-14-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1626731/+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 1649147] Re: package linux-image-4.4.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Justin]

Thanks for that. The first command worked and installed the kernel image update.
"sudo apt-get install -f"

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

Title:
  package linux-image-4.4.0-53-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened whilst allowing software updater to perform an update it
  prompted me about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bussys 9151 F pulseaudio
  Date: Mon Dec 12 10:37:07 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=438d9ec0-a58d-4e8b-8e4a-c40e79548889
  InstallationDate: Installed on 2013-10-13 (1154 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=b25f6afc-81b2-426e-83e6-6370d6d39424 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-53-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-30 (103 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649147/+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 1642228] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From gpicc...@br.ibm.com 2016-12-12 15:54 EDT---
(In reply to comment #9)
> Marking verification-done-yakkety. Spot checking the resulting deb shows
> that at least ohci-platform, cxlflash, ibmpowernv, and powernv_flash are now
> included in the generic package.

We experimented the kernel but some modules aren't included - we might need 
some more.
We're on discussion on which of them are necessary, but as for now, I can say 
at least the modules kvm_hv and kvm_pr are not included and are necessary.

Will update here soon with more news.
Thanks,

Guilherme

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

Title:
  Move some kernel modules to the main kernel package

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

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2016-10-20 
08:51:24 ==
  Hello Canonical,

  There are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  My suggestion is to add these important modules to the main archive,
  so, we do not require the installation of the -extra package.

  We are working on the full list of packages, but I would like to
  anticipate these modules:

  01. lpfc
  02. qla2xxx
  03. be2net
  04. bnx2x
  05. i40e
  06. igb
  07. ixgbe
  08. cxl
  09. cxlflash
  10. jsm
  11. ohci-platform
  12. xhci
  13. aacraid
  14. ipr
  15. megaraid_sas
  16. mpt3sas
  17. powernv-rng
  18. ipmi_powernv
  19. leds-powernv
  20. ibmpowernv
  21. opal-prd
  22. powernv_flash
  23. nx-compress-powernv
  24. vfio (all modules:  vfio.ko, vfio-pci.ko, vfio_iommu_spapr_tce.ko, 
vfio_virqfd.ko, vfio_spapr_eeh.ko)

  
  *Notice*
  The driver "qlge" is presented in the preliminary list but it's not necessary.

  Thanks in advance,

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

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

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

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/modoc__4.8.0-31.33__2016-12-12_20-19-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1467190] Re: No audio over DisplayPort MST

[Ray-Ven]

is kernel bisecting needed?
https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  No audio over DisplayPort MST

Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  I have a Lenovo ThinkPad E540 with an Intel Haswell (4th Gen) HD
  graphics controller connected to a OneLink Pro Dock. The Dock uses
  DisplayPort (DP) 1.2 MST (multi stream transport) to provide both a DP
  and a DVI port. My monitor is connected to the DP.

  When I used kernels <= 3.16 audio worked fine, but the monitor would
  flicker heavily. So I installed linux-lts-vivid (3.19) which fixed the
  graphics problem (now I can see various DP? outputs in xrandr as
  opposed to one before), but there is no DP audio output to chose
  anymore.

  I also tested the latest mainline kernel 4.1-rc8, where this bug still
  exists. To further investigate I got these version's kernel sources,
  applied 4 patches by Dave Airlie from the intel-gfx mailing list [1]
  and tested this build (4.1-rc8+), which fixed the problem! I can play
  sound over DP, the same way I can over HDMI or DP without MST.

  I hope it is possible to backport these changes!

  [1] haswell displayport MST audio support
  http://www.spinics.net/lists/intel-gfx/msg68973.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22~14.04.1-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 21 01:44:30 2015
  InstallationDate: Installed on 2014-01-06 (530 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2014-06-12 (373 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1467190/+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 1467190] Re: No audio over DisplayPort MST

[Ray-Ven]

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.36-trusty/
is the latest working kernel
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.39
for example won't work

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

Title:
  No audio over DisplayPort MST

Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  I have a Lenovo ThinkPad E540 with an Intel Haswell (4th Gen) HD
  graphics controller connected to a OneLink Pro Dock. The Dock uses
  DisplayPort (DP) 1.2 MST (multi stream transport) to provide both a DP
  and a DVI port. My monitor is connected to the DP.

  When I used kernels <= 3.16 audio worked fine, but the monitor would
  flicker heavily. So I installed linux-lts-vivid (3.19) which fixed the
  graphics problem (now I can see various DP? outputs in xrandr as
  opposed to one before), but there is no DP audio output to chose
  anymore.

  I also tested the latest mainline kernel 4.1-rc8, where this bug still
  exists. To further investigate I got these version's kernel sources,
  applied 4 patches by Dave Airlie from the intel-gfx mailing list [1]
  and tested this build (4.1-rc8+), which fixed the problem! I can play
  sound over DP, the same way I can over HDMI or DP without MST.

  I hope it is possible to backport these changes!

  [1] haswell displayport MST audio support
  http://www.spinics.net/lists/intel-gfx/msg68973.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22~14.04.1-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 21 01:44:30 2015
  InstallationDate: Installed on 2014-01-06 (530 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2014-06-12 (373 days ago)

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1649326/+attachment/4790871/+files/CRDA.txt

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1649326/+attachment/4790881/+files/WifiSyslog.txt

** 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/1649326

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

I've tried with 3.13.0-100 and it worked. I tried with 3.13.0-106 and it
failed.

I've attached the requested apport-collect information from a 3.13.0-106
kernel; however, because of the nature of the bug, I had to boot that
kernel via GRUB 2, not via the EFI stub loader. The apport-collect
information was collected inside a VirtualBox VM.

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Rod Smith]

apport information

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

apport information

** Tags added: apport-collected

** Description changed:

  The EFI stub loader produces consistent boot errors when booting Trusty
  starting with version 3.13.0-101-generic. This bug can be reproduced in
  many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach
  is:
  
  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic
  
  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)
  
  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101 kernel.
  See this Kubuntu forum thread for details:
  
  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels
  
  Note that early on, this thread focuses on rEFInd; however, the bug can
  be reproduced with other boot managers, including the EFI shell, as
  described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel,
  and I believe it's this component that's failing. The problem does NOT
  occur when using GRUB to launch the kernel. (GRUB does not rely on the
  EFI stub loader.)
  
- I have NOT encountered the problem with Xenial and its 4.4.0-series
- kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series
- kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty
- with kernels from series beyond 3.13.0.
+ I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
+ CurrentDesktop: LXDE
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
+ InstallationDate: Installed on 2014-04-27 (960 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ IwConfig:
+  eth0  no wireless extensions.
+  
+  lono wireless extensions.
+ Lsusb:
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-106-generic N/A
+  linux-backports-modules-3.13.0-106-generic  N/A
+  linux-firmware  1.127.22
+ RfKill:
+  
+ Tags:  trusty
+ Uname: Linux 3.13.0-106-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/01/2006
+ dmi.bios.vendor: innotek GmbH
+ dmi.bios.version: VirtualBox
+ dmi.board.name: VirtualBox
+ dmi.board.vendor: Oracle Corporation
+ dmi.board.version: 1.2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Oracle Corporation
+ dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
+ dmi.product.name: VirtualBox
+ dmi.product.version: 1.2
+ dmi.sys.vendor: innotek GmbH

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1649326/+attachment/4790869/+files/AlsaInfo.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/1649326

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 

[Kernel-packages] [Bug 1467190] Re: No audio over DisplayPort MST

[Ray-Ven]

Problem persists in yakkety (and all other ubuntu versions with kernels
higher than 3.16)

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

Title:
  No audio over DisplayPort MST

Status in linux-lts-vivid package in Ubuntu:
  Triaged

Bug description:
  I have a Lenovo ThinkPad E540 with an Intel Haswell (4th Gen) HD
  graphics controller connected to a OneLink Pro Dock. The Dock uses
  DisplayPort (DP) 1.2 MST (multi stream transport) to provide both a DP
  and a DVI port. My monitor is connected to the DP.

  When I used kernels <= 3.16 audio worked fine, but the monitor would
  flicker heavily. So I installed linux-lts-vivid (3.19) which fixed the
  graphics problem (now I can see various DP? outputs in xrandr as
  opposed to one before), but there is no DP audio output to chose
  anymore.

  I also tested the latest mainline kernel 4.1-rc8, where this bug still
  exists. To further investigate I got these version's kernel sources,
  applied 4 patches by Dave Airlie from the intel-gfx mailing list [1]
  and tested this build (4.1-rc8+), which fixed the problem! I can play
  sound over DP, the same way I can over HDMI or DP without MST.

  I hope it is possible to backport these changes!

  [1] haswell displayport MST audio support
  http://www.spinics.net/lists/intel-gfx/msg68973.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22~14.04.1-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 21 01:44:30 2015
  InstallationDate: Installed on 2014-01-06 (530 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2014-06-12 (373 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1467190/+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 1642228] Re: Move some kernel modules to the main kernel package

[Tim Gardner]

Marking verification-done-yakkety. Spot checking the resulting deb shows
that at least ohci-platform, cxlflash, ibmpowernv, and powernv_flash are
now included in the generic package.

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

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

Title:
  Move some kernel modules to the main kernel package

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

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2016-10-20 
08:51:24 ==
  Hello Canonical,

  There are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  My suggestion is to add these important modules to the main archive,
  so, we do not require the installation of the -extra package.

  We are working on the full list of packages, but I would like to
  anticipate these modules:

  01. lpfc
  02. qla2xxx
  03. be2net
  04. bnx2x
  05. i40e
  06. igb
  07. ixgbe
  08. cxl
  09. cxlflash
  10. jsm
  11. ohci-platform
  12. xhci
  13. aacraid
  14. ipr
  15. megaraid_sas
  16. mpt3sas
  17. powernv-rng
  18. ipmi_powernv
  19. leds-powernv
  20. ibmpowernv
  21. opal-prd
  22. powernv_flash
  23. nx-compress-powernv
  24. vfio (all modules:  vfio.ko, vfio-pci.ko, vfio_iommu_spapr_tce.ko, 
vfio_virqfd.ko, vfio_spapr_eeh.ko)

  
  *Notice*
  The driver "qlge" is presented in the preliminary list but it's not necessary.

  Thanks in advance,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642228/+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 1647787] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-12_20-13-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[bagl0312]

I am using the newly released 4.9, but the same "feature"was present in
the previous rcX versions:

uname -a
Linux nbbag7 4.9.0-040900-generic #201612111631 SMP Sun Dec 11 21:33:00 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

BTW,I am noticing now that tapping with a single finger on the lower-
right part of the trackpad is equivalent of a right-click.

So it seems that there are some default gestures on the upper/lower-right part 
that are not understood by the current driver and are enabled by default.
I don't know if this can be considered a bug

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1649292] Re: NFS client : permission denied when trying to access subshare, since kernel 4.4.0-31

[Seth Forshee]

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

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

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+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 1647787] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/onza__3.19.0-78.86__2016-12-12_19-50-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/1647787

Title:
  linux: 3.19.0-78.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1647787/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Staffan Persson]

I'm using rc5:
uname -a
Linux se5470 4.9.0-040900rc5-generic #201611131431 SMP Sun Nov 13 19:33:15 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

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

[Brad Figg]

tests ran:  16, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/modoc__4.8.0-31.33__2016-12-12_19-24-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Adam]

@p-staffan Are you also using the 4.9.x kernel (i.e. the one with the
patch so that the touchpad is recognized)?

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1649039] Re: USB 3.1 controller does weird magic: appears after Windows 10, disappears otherwise

[Nazar Mokrynskyi]

No, it didn't start happening after update/upgrade because my PC is few
weeks old and I didn't check 3.1 support ever before.

With mainline kernel 4.9.0-040900-lowlatency behavior is exactly the
same

** Tags added: kernel-bug-exists-upstream

** 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/1649039

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  

[Kernel-packages] [Bug 1637565] Re: nvme: improve performance for virtual Google NVMe devices

[Tim Gardner]

An out of band email response indicated that Yakkety works as expected.
See comment #1

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

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

Title:
  nvme: improve performance for virtual Google NVMe devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  This change provides a mechanism to reduce the number of MMIO doorbell writes 
for the NVMe driver. When running in a virtualized environment like QEMU, the 
cost of an MMIO is quite hefy here. The main idea for the patch is provide the 
device two memory location locations:
   1) to store the doorbell values so they can be lookup without the 
doorbell
  MMIO write
   2) to store an event index.
  I believe the doorbell value is obvious, the event index not so much. Similar 
to the virtio specificaiton, the virtual device can tell the driver (guest OS) 
not to write MMIO unless you are writing past this value.
  
  FYI: doorbell values are written by the nvme driver (guest OS) and the event 
index is written by the virtual device (host OS).
  
  The patch implements a new admin command that will communicate where these 
two memory locations reside. If the command fails, the nvme driver will work as 
before without any optimizations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637565/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Staffan Persson]

yes, I can reproduce it like this:
- open a text doc
- select some text in it
- tap in the top right corner of the touchpad
then the selected text gets pasted for every tap

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/onza__4.8.0-31.33__2016-12-12_18-20-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1649057] Re: Auto Shutdown of system while web-browsing in tabs

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9

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

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

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

Title:
  Auto Shutdown of system while web-browsing in tabs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Laptop shutdowns while web browsing in 6 or 7 sites at a time.

  Gateway NE56R laptop is in power-save mode.

  Instead of allowing shutdowns it should notify to close down some tabs or 
process if it cannot handle many process or heat (ie. when it exceeds allowed 
limits).
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uppili 4023 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a2523c8-4df7-4ab7-85df-e2625f8fdad7
  InstallationDate: Installed on 2013-12-18 (1088 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gateway NE56R
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=d4d1be7d-bc6a-473d-a3c1-a159453959cf ro splash plymouth:debug=1 quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/09/2012
  dmi.bios.vendor: Gateway
  dmi.bios.version: V1.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V1.13
  dmi.modalias: 
dmi:bvnGateway:bvrV1.13:bd10/09/2012:svnGateway:pnNE56R:pvrV1.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV1.13:
  dmi.product.name: NE56R
  dmi.product.version: V1.13
  dmi.sys.vendor: Gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649057/+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 1649039] Re: USB 3.1 controller does weird magic: appears after Windows 10, disappears otherwise

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9

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

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

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte 

[Kernel-packages] [Bug 1649048] Re: "Power off" required for resume from hybrid-sleep on AC power

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9

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

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

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

Title:
  "Power off" required for resume from hybrid-sleep on AC power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Due to issues with "waking from suspend", I have modified a few entries in 
/etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 
'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 
'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my 
laptop lid while it is plugged it and when I return to it later, it does not 
resume on lifting the lid. The disk spins up and the fan runs as if the laptop 
was resuming but I am unable to do anything other than hold the power button 
down until it shuts down - much as I had to when I was having problems with 
suspend. When I hit the power button again and select the entry for Ubuntu in 
grub, the laptop boots to the login screen normally. When I log in, everything 
is just as it was when I originally closed the laptop's lid - basically 
"resuming" the way I had hoped. I do not believe that this is the intended 
behavior as I have had my computer resume from hybrid-sleep without powering it 
off in 16
 .04 and in 16.10 (I have not, that I know of, experienced this problem while 
on battery power). In case it is relevant, the current values of 'Suspend when 
inactive for' and 'When the lid closes' in Settings > Power are "Don't suspend" 
(for battery and plugged in) and "Suspend" (for battery and plugged in), 
respectively.
  I will attach the output from 'cat /proc/version_signature' and 'lspci -vnvn' 
but I would like to add that 'sudo lspci -vnvn' sent 'pcilib: sysfs_read_vpd: 
read failed: Input/output error' to stderr, which was not redirected to the log 
file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steven 4004 F pulseaudio
   /dev/snd/controlC0:  steven 4004 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 10 22:06:19 2016
  HibernationDevice: RESUME=UUID=891e7a47-9f8c-4fc9-9fe3-fe5c88ef2147
  InstallationDate: Installed on 2016-11-23 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20347
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=b40d7383-45c3-4885-a1df-0e534eb44fef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 99CN21WW(V1.04)
  dmi.board.asset.tag: Std
  dmi.board.name: Lenovo Y40-70
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr99CN21WW(V1.04):bd03/24/2014:svnLENOVO:pn20347:pvrLenovoY40-70:rvnLENOVO:rnLenovoY40-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY40-70:
  dmi.product.name: 20347
  dmi.product.version: Lenovo Y40-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649048/+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 1649147] Re: package linux-image-4.4.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-image-4.4.0-53-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened whilst allowing software updater to perform an update it
  prompted me about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bussys 9151 F pulseaudio
  Date: Mon Dec 12 10:37:07 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=438d9ec0-a58d-4e8b-8e4a-c40e79548889
  InstallationDate: Installed on 2013-10-13 (1154 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=b25f6afc-81b2-426e-83e6-6370d6d39424 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-53-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-30 (103 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

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

[Brad Figg]

tests ran:  36, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/modoc__4.8.0-31.33__2016-12-12_17-03-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1649207] Re: mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory

[Joseph Salisbury]

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

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

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

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

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

Title:
  mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot
  allocate memory

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

Bug description:
  Failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate
  memory

  Scenario

  ubuntu@cto-netsim3:~$ sudo ethtool -g ens6f0
  [sudo] password for ubuntu:
  Ring parameters for ens6f0:
  Pre-set maximums:
  RX: 4096
  RX Mini: 0
  RX Jumbo: 0
  TX: 8192
  Current hardware settings:
  RX: 1024
  RX Mini: 0
  RX Jumbo: 0
  TX: 1024

  ubuntu@cto-netsim3:~$ sudo ethtool -G ens6f0 rx 4096
  Cannot set device ring parameters: Cannot allocate memory

  After brinding the interface down with:

  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 down

  I can not bring it back up !!!

  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$

  dmsg:
  [ 774.935067] mlx5_core :81:00.0: swiotlb buffer is full (sz: 8388608 
bytes)
  [ 774.935070] swiotlb: coherent allocation failed for device :81:00.0 
size=8388608
  [ 774.935074] CPU: 38 PID: 6042 Comm: ethtool Not tainted 4.8.0-22-generic #24
  [ 774.935075] Hardware name: Quanta Computer Inc D51B-1U (dual 1G LoM)/S2B-MB 
(dual 1G LoM), BIOS S2B_3A19 05/15/2015
  [ 774.935078] 0286 65a68699 8d946b1db9a0 
8502f5d2
  [ 774.935083]  007f 8d946b1db9e8 
8505a280
  [ 774.935087] 8d946b1dba80 8d94000b 024082c0 
8db471b0e0a0
  [ 774.935091] Call Trace:
  [ 774.935104] [] dump_stack+0x63/0x81
  [ 774.935108] [] swiotlb_alloc_coherent+0x140/0x160
  [ 774.935115] [] x86_swiotlb_alloc_coherent+0x43/0x50
  [ 774.935150] [] mlx5_dma_zalloc_coherent_node+0xa4/0x100 
[mlx5_core]
  [ 774.935164] [] mlx5_buf_alloc_node+0x4d/0xc0 [mlx5_core]
  [ 774.935181] [] mlx5_cqwq_create+0x7e/0x160 [mlx5_core]
  [ 774.935199] [] mlx5e_open_cq+0x9e/0x1f0 [mlx5_core]
  [ 774.935214] [] mlx5e_open_channels+0x715/0xf30 [mlx5_core]
  [ 774.935229] [] mlx5e_open_locked+0xda/0x1e0 [mlx5_core]
  [ 774.935245] [] mlx5e_set_ringparam+0x21e/0x350 [mlx5_core]
  [ 774.935252] [] dev_ethtool+0x59f/0x1fc0
  [ 774.935255] [] ? new_slab+0x300/0x6e0
  [ 774.935259] [] ? __rtnl_unlock+0x2a/0x50
  [ 774.935262] [] ? netdev_run_todo+0x60/0x330
  [ 774.935266] [] ? alloc_set_pte+0x4ec/0x610
  [ 774.935268] [] ? dev_get_by_name_rcu+0x61/0x80
  [ 774.935272] [] dev_ioctl+0x180/0x5a0
  [ 774.935277] [] sock_do_ioctl+0x42/0x50
  [ 774.935280] [] sock_ioctl+0x1d2/0x290
  [ 774.935283] [] do_vfs_ioctl+0xa3/0x610
  [ 774.935287] [] ? __do_page_fault+0x203/0x4d0
  [ 774.935289] [] SyS_ioctl+0x79/0x90
  [ 774.935307] [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [ 774.935312] mlx5_core :81:00.0: :81:00.0:mlx5_cqwq_create:121:(pid 
6042): mlx5_buf_alloc_node() failed, -12
  [ 774.935537] mlx5_core :81:00.0 ens6f0: mlx5e_open_locked: 
mlx5e_open_channels failed, -12

  
  This is the upstream patches that fix this issue 
  ec8b9981ad3f net/mlx5e: Create UMR MKey per RQ
  3608ae77c098 net/mlx5e: Move function mlx5e_create_umr_mkey
  1c1b522808a1 net/mlx5e: Implement Fragmented Work Queue (WQ)


  Thanks, 
  Talat

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[mike]

I can confirm this problem in Kubuntu 14.04 on:
vmlinuz-3.13.0-101-generic.

So, to summarize my tests, in Kubuntu 14.04,
I do NOT have the problem with vmlinuz-3.13.0-100-generic.
I do, however, have the problem with the following three kernels:
vmlinuz-3.13.0-101-generic
vmlinuz-3.13.0-103-generic
vmlinuz-3.13.0-105-generic

(I really don't have the advanced skills it might take to go deeper into
this.  All my basic work is simply done at Konsole in Kubuntu using
efibootmgr -c commands and such.)

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series
  kernels (last tested: 4.4.0-53-generic) or Yakkety and its
  4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet
  tested Trusty with kernels from series beyond 3.13.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[bagl0312]

@pmonas triggered by your comment, I made some further investigation and it 
seems that the middle-click is alway triggered when I click with a single 
finger in the upper-right part of the trackpad
Please check if you find the same

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

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

[Brad Figg]

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

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

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

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

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

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

  From: Long Li 

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

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


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

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

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

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

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

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

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[bagl0312]

@pmonas yes, I think the singe tap is sometime interpreted as a middle-click. I 
can guarantee that I click with a single finger, though ...
Is someone else using the 4.9 kernel on the e7370 observing this ?

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1649207] Re: mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate memory

[Joseph Salisbury]

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

** Tags added: kernel-da-key

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

Title:
  mlx5_core failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot
  allocate memory

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Failed to increase rx ring to 4096 - SIOCSIFFLAGS: Cannot allocate
  memory

  Scenario

  ubuntu@cto-netsim3:~$ sudo ethtool -g ens6f0
  [sudo] password for ubuntu:
  Ring parameters for ens6f0:
  Pre-set maximums:
  RX: 4096
  RX Mini: 0
  RX Jumbo: 0
  TX: 8192
  Current hardware settings:
  RX: 1024
  RX Mini: 0
  RX Jumbo: 0
  TX: 1024

  ubuntu@cto-netsim3:~$ sudo ethtool -G ens6f0 rx 4096
  Cannot set device ring parameters: Cannot allocate memory

  After brinding the interface down with:

  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 down

  I can not bring it back up !!!

  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$
  ubuntu@cto-netsim3:~$ sudo ifconfig ens6f0 up
  SIOCSIFFLAGS: Cannot allocate memory
  ubuntu@cto-netsim3:~$

  dmsg:
  [ 774.935067] mlx5_core :81:00.0: swiotlb buffer is full (sz: 8388608 
bytes)
  [ 774.935070] swiotlb: coherent allocation failed for device :81:00.0 
size=8388608
  [ 774.935074] CPU: 38 PID: 6042 Comm: ethtool Not tainted 4.8.0-22-generic #24
  [ 774.935075] Hardware name: Quanta Computer Inc D51B-1U (dual 1G LoM)/S2B-MB 
(dual 1G LoM), BIOS S2B_3A19 05/15/2015
  [ 774.935078] 0286 65a68699 8d946b1db9a0 
8502f5d2
  [ 774.935083]  007f 8d946b1db9e8 
8505a280
  [ 774.935087] 8d946b1dba80 8d94000b 024082c0 
8db471b0e0a0
  [ 774.935091] Call Trace:
  [ 774.935104] [] dump_stack+0x63/0x81
  [ 774.935108] [] swiotlb_alloc_coherent+0x140/0x160
  [ 774.935115] [] x86_swiotlb_alloc_coherent+0x43/0x50
  [ 774.935150] [] mlx5_dma_zalloc_coherent_node+0xa4/0x100 
[mlx5_core]
  [ 774.935164] [] mlx5_buf_alloc_node+0x4d/0xc0 [mlx5_core]
  [ 774.935181] [] mlx5_cqwq_create+0x7e/0x160 [mlx5_core]
  [ 774.935199] [] mlx5e_open_cq+0x9e/0x1f0 [mlx5_core]
  [ 774.935214] [] mlx5e_open_channels+0x715/0xf30 [mlx5_core]
  [ 774.935229] [] mlx5e_open_locked+0xda/0x1e0 [mlx5_core]
  [ 774.935245] [] mlx5e_set_ringparam+0x21e/0x350 [mlx5_core]
  [ 774.935252] [] dev_ethtool+0x59f/0x1fc0
  [ 774.935255] [] ? new_slab+0x300/0x6e0
  [ 774.935259] [] ? __rtnl_unlock+0x2a/0x50
  [ 774.935262] [] ? netdev_run_todo+0x60/0x330
  [ 774.935266] [] ? alloc_set_pte+0x4ec/0x610
  [ 774.935268] [] ? dev_get_by_name_rcu+0x61/0x80
  [ 774.935272] [] dev_ioctl+0x180/0x5a0
  [ 774.935277] [] sock_do_ioctl+0x42/0x50
  [ 774.935280] [] sock_ioctl+0x1d2/0x290
  [ 774.935283] [] do_vfs_ioctl+0xa3/0x610
  [ 774.935287] [] ? __do_page_fault+0x203/0x4d0
  [ 774.935289] [] SyS_ioctl+0x79/0x90
  [ 774.935307] [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [ 774.935312] mlx5_core :81:00.0: :81:00.0:mlx5_cqwq_create:121:(pid 
6042): mlx5_buf_alloc_node() failed, -12
  [ 774.935537] mlx5_core :81:00.0 ens6f0: mlx5e_open_locked: 
mlx5e_open_channels failed, -12

  
  This is the upstream patches that fix this issue 
  ec8b9981ad3f net/mlx5e: Create UMR MKey per RQ
  3608ae77c098 net/mlx5e: Move function mlx5e_create_umr_mkey
  1c1b522808a1 net/mlx5e: Implement Fragmented Work Queue (WQ)


  Thanks, 
  Talat

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

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

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

[Brad Figg]

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[mike]

I can confirm this problem in Kubuntu 14.04 on two kernels:
vmlinuz-3.13.0-103-generic-efi.signed, in 14.04
vmlinuz-3.13.0-105-generic-efi.signed, in 14.04

(The details of my test are in the thread Rod Smith cited:
https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-kernels=396267=1#post396267
 -- I have no problem booting the kernel vmlinuz-3.13.0-100-generic-efi.signed, 
in 14.04 directly by UEFI using stub loader (on an ASUS H97-PLUS motherboard).)

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series
  kernels (last tested: 4.4.0-53-generic) or Yakkety and its
  4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet
  tested Trusty with kernels from series beyond 3.13.0.

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

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

[Kernel-packages] [Bug 1648034] dwalin (amd64) - tests ran: 36, failed: 1

[Brad Figg]

tests ran:  36, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-31.33-generic/dwalin__4.8.0-31.33__2016-12-12_16-59-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1649292] Re: NFS client : permission denied when trying to access subshare, since kernel 4.4.0-31

[Joseph Salisbury]

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

** Tags added: kernel-da-key

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

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

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+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 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Chris Valean]

Hi Joe,

I did verify this again with the below kernels and results:
- 4.8.0-22 16.10 kernel - kdump through NMI on 4 CPU cores doesn't work - VM 
gets stuck and there is no crash file nor a reboot.
- 4.9.0-040900RC8 kernel from ubuntu mainline - kdump through NMI works fine 
when using single core or SMP *with 4 cores*.
Using 8 cores on this kernel, triggering the crash will result in the same bad 
behavior as from the GA kernel. I don't see any crash messages on the console, 
and the VM will just hang. Will have to do more debugging on this new pattern.

All tests have been done with crashkernel=512M and 2GB RAM for the VM.

4.9 also just got released, as of 11/12.

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

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

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

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

  REPRO STEPS:

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

  2. after configuration reboot the VM

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

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

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

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

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

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

[Kernel-packages] [Bug 1604396] Re: Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

[Joseph Salisbury]

** Tags removed: needs-bisect
** Tags added: performing-bisect

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

Title:
  Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

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

Bug description:
  Since apt-upgrading my Ubuntu 16.04 PC to kernel 4.4.0-31 I can't cd
  into NFS4 subvolumes any more:

  zierke@rzpc100$ uname -a
  Linux rzpc100 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  zierke@rzpc100$ kinit
  Password for zie...@informatik.uni-hamburg.de:
  zierke@rzpc100$ cd /informatik2
  zierke@rzpc100$ cd rz
  -bash: cd: /informatik2/rz: Operation not permitted

  When I reboot my PC with the previous kernel 4.4.0-28 this works fine.

  This problem has also been mentioned in
  
https://www.kubuntuforums.net/showthread.php?70499-Latest-16-04-bug-NFS-problem-no-access-unless-I-use-root-first-strange
  https://ubuntuforums.org/showthread.php?t=2331137

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

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

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

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-30.32-generic/s2lp6g002__4.8.0-30.32__2016-12-12_18-06-00/results-index.html

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

Title:
  linux: 4.8.0-31.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1649318] Re: ASUS R751 L CLickpad not detected after installing Ubuntu

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer to 
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 
kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9


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

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

Title:
  ASUS R751 L  CLickpad not detected after installing Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the installation of Ubuntu 16.04 on to my ASUS R 751L Model
  (from Windows 10) the Clickpad is not detected or does not work at
  all. I could not find a Ubuntu installation for the ASUS Smart gesture
  online. A mouse works.

  The terminal input " cat /proc/bus/input/devices" gives back:

  
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:07/LNXVIDEO:00/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=1532 Product=001c Version=0111
  N: Name="Razer  Razer Abyssus"
  P: Phys=usb-:00:1d.0-1.4/input0
  S: 
Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:1532:001C.0001/input/input6
  U: Uniq=
  H: Handlers=mouse0 event6 
  B: PROP=0
  B: EV=17
  B: KEY=7f 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input7
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input8
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input10
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel HDMI HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=04f2 Product=b3d8 Version=6953
  N: Name="USB2.0 HD UVC WebCam"
  P: Phys=usb-:00:1d.0-1.6/button
  S: 
Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input12
  U: Uniq=
  H: Handlers=kbd event12 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Toshiba WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input13
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=1

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: 

[Kernel-packages] [Bug 1649342] Re: md5sum fails with message "Invalid argument" on 4, 294, 967, 295-byte files in FAT32 - tracked down to Ubuntu incompatible change to kernel's fread and stdio stream

[Joseph Salisbury]

The changes mentioned in the bug description were made by the following
commit in mainline:

commit c2a9737f45e27d8263ff9643f994bda9bac0b944
Author: Wei Fang 
Date:   Fri Oct 7 17:01:52 2016 -0700

vfs,mm: fix a dead loop in truncate_inode_pages_range()


That commit was added to mainline as of 4.9-rc1.  Ubuntu 16.10 received this 
changes via stable updates from upstream.  This commit came in with the 4.8.4 
upstream stable updates(Commit 3d549dc in 4.8.4).

Can you test the upstream 4.8.4 upstream stable kernel and see if it also 
exhibits this bug?  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.4/


It might also be worthwhile to test the current 4.9 mainline kernel to see if 
the bug is fixed or still exists in mainline.  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/


** Tags added: yakkety

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

Title:
  md5sum fails with message "Invalid argument" on 4,294,967,295-byte
  files in FAT32 - tracked down to Ubuntu incompatible change to
  kernel's fread and stdio stream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Bug discovered in the threads at http://lists.gnu.org/archive/html
  /bug-coreutils/2016-12/msg8.html and
  https://bugzilla.kernel.org/show_bug.cgi?id=189981 partially quoted
  below (with the permission of the persons involved).

  
  === Message 1 ===

  --- Bug ---
  In a FAT32 file system, if one runs md5sum on a 4,294,967,294-byte file (one 
byte less than the maximum file size) it succeeds, but if one runs md5sum on a 
4,294,967,295-byte file (the maximum file size) it fails with error message 
"Invalid argument".

  --- How to reproduce the bug ---
  Create a FAT32 file system in a file "tmp.fs":
 truncate -s 9G tmp.fs
 mkfs.vfat -F 32 tmp.fs
  Mount at "/tmp/mounted_tmp/" the file system in file "tmp.fs":
 sudo mkdir /tmp/mounted_tmp/
 sudo mount -o loop,rw,uid=1000,gid=1000 tmp.fs /tmp/mounted_tmp/
  Create two files in "/tmp/mounted_tmp/", file "file_1" with 4,294,967,294 
bytes and file "file_2" with 4,294,967,295 bytes:
 cd /tmp/mounted_tmp/
 truncate -s 4294967294 file_1
 truncate -s 4294967295 file_2
  Run md5sum on the two files "file_1" and "file_2":
 md5sum file_1
 md5sum file_2
  The outputs should be respectively (notice that the second output is an error 
message):
 541249e3205af07b4a03f891185f64a0  file_1
 md5sum: file_2: Invalid argument
  Unmount the file system at "/tmp/mounted_tmp/":
 cd ..
 sudo umount /tmp/mounted_tmp/
 sudo rmdir /tmp/mounted_tmp/
  Remove the file "tmp.fs".

  --- Notes ---
  Tested with md5sum 8.25 running on an updated Ubuntu 16.10 with kernel 
4.8.0-30-generic.
  The same bug affects sha1sum, sha224sum, sha256sum, sha384sum, and sha512sum, 
but not crc32.

  
  === Message 2 ===

  ...
  > --- How to reproduce the bug ---
  ...

  I can't repro this with any md5sum version on 4.2.5-300.fc23.x86_64
  So I'm guessing a kernel regression.
  Can you strace -o /tmp/md5sum.strace md5sum file_2,
  and look towards the end of the strace file to identify the syscall returning 
EINVAL?
  In any case I'd direct the issue towards the kernel folks.
  ...

  
  === Message 3 ===

  > Can you strace -o /tmp/md5sum.strace md5sum file_2,
  > and look towards the end of the strace file to identify the syscall
  > returning EINVAL?

  It is the seventh and eighth lines below:

...
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32768
 read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 
32767
 read(3, 0x25c12b0, 8192)= -1 EINVAL (Invalid argument)
 read(3, 0x25c12b0, 8192)= -1 EINVAL (Invalid argument)
 write(2, "md5sum: ", 8) = 8
 write(2, "file_2", 6)   = 6
 open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 4
 fstat(4, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
 read(4, "# Locale name alias data base.\n#"..., 4096) = 2995
 read(4, "", 4096)   = 0
 close(4)= 0
 open("/usr/share/locale/en_GB/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT 
(No such file or directory)
 open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No 
such file or directory)
 open("/usr/share/locale-langpack/en_GB/LC_MESSAGES/libc.mo", O_RDONLY) = 4
 fstat(4, 

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Joseph Salisbury]

Can you see if this bug still exists in the 3.13.0-106 kernel?  It can be 
downloaded from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11527714

If it does, can you see if this bug happens with the 3.13.0-100 kernel?  It can 
be downloaded from:
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/11039050

Both these kernel required installing both the linux-image and linux-
image-extra .deb packages.

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

** Tags added: kernel-da-key

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series
  kernels (last tested: 4.4.0-53-generic) or Yakkety and its
  4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet
  tested Trusty with kernels from series beyond 3.13.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1649358] Re: linux: 4.8.0-32.34 -proposed tracker

[Brad Figg]

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-hwe-edge (16.04.1) - bug 1649361

** 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 4.8.0-32.34 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Monday, 12. December 2016 18:19 UTC

** Description changed:

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

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

Title:
  linux: 4.8.0-32.34 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 12. December 2016 18:19 UTC

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1649358/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Adam]

@bagl0312: both of those are what you'd expect from a "middle-click".
This seems somehow like a different bug (or perhaps you're inadvertently
tapping with two or three fingers and your system is set up to interpret
that as a middle-click)

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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