date:20171110

[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/1716213

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  cannot

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  Date: Sun Sep 10 09:48:45 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8m4Snl/77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=5dfe327d-30d2-4c3f-b8c5-844b8424c47e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: ACER
  dmi.product.version: Rev 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716213/+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 1716368] Re: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:10:3467]

[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/1716368

Title:
  NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
  [kworker/2:10:3467]

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 4.12.0-12.13-generic 4.12.8

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13 [modified: 
boot/vmlinuz-4.12.0-12-generic]
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  david  1293 F pulseaudio
   /dev/snd/controlC0:  david  1293 F pulseaudio
   /dev/snd/controlC1:  david  1293 F pulseaudio
  Date: Mon Sep 11 11:30:46 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170904)
  IwConfig:
   eno1  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=b66faf19-2c41-4a84-bd17-864f9f1a5db1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! 
[kworker/2:10:3467]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2906:bd02/24/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97-PRO:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716368/+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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

2017-11-10 Thread Brendan D.

Hello again, I spoke too soon. Problem went away immediately after
installing `intel-microcode` but returned after suspend and resume.

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  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
  
  backports: 1731266
  derivatives:
  kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.4.0-101.124 -proposed tracker

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

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

  backports: 1731266
  derivatives:
  kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

2017-11-10 Thread André

I can confirm that the this last kernel does not work
(lp1722478-bisect-1), while the previous did (fastreconnect)

On a Thinkpad T440s

ps. modprobe workaround also works, while installing intel-microcode
does not (had it previously)

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+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 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU

2017-11-10 Thread Patrick Mackinlay

I can confirm that 4.8.0-040800-generic works fine.

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

Title:
  kernel 4.10 fails to boot on AMD E-350D APU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8
  motherboard). This has always worked fine until the kernel was
  upgraded to 4.10 as part of the regular system upgrades. Since then
  the machine wont boot, there are no errors, the screen just stays
  blank. If I boot using a previous kernel (such as 4.8.0-58-generic)
  then it all works fine.

  As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have
  tried have failed, currently this includes:

  linux-image-4.10.0-30-generic
  linux-image-4.10.0-32-generic
  linux-image-4.10.0-33-generic
  linux-image-4.10.0-38-generic
  linux-image-4.13.0-16-generic

  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pim1369 F pulseaudio
   /dev/snd/controlC0:  pim1369 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
  InstallationDate: Installed on 2017-03-11 (238 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed 
root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-58-generic N/A
   linux-backports-modules-4.8.0-58-generic  N/A
   linux-firmware1.157.13
  RfKill:

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

  _MarkForUpload: True
  dmi.bios.date: 01/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E350N WIN8
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730069/+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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

2017-11-10 Thread Brendan D.

Hi, I am running Ubuntu 17.10 GNOME with Wayland using a Thinkpad T440
as well. Installing `intel-microcode` fixed the issue immediately. I'm
assuming this is proprietary code :\

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+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 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Given that, I'm marking the kernel tasks as invalid as this appears to
be stress-ng being over aggressive.

MAAS deployments (and I presume server installs in general) only provide
about 4 - 8GB swap max in a swap file created in the root filesystem (no
swap partition anymore).

It is not reasonable to create, IMO, 100GB swap files just to be sure we
don't accidentally trip the OOMKiller when running memory tests.

Also, the ratio seems to be variable. On my amd64 system, the swap
consumed was 5x the amount of installed RAM.  On the ppc64le system, the
amount was just shy of 2x the amount of physical RAM (this is also a
NUMA capable system, so maybe that's a contributing factor, beyond the
differences in how each arch handles memory, which I freely admit to not
understanding well.

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

Title:
  stress-ng triggering oomkiller running brk and stack stressors on all
  arches.

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Invalid

Bug description:
  During regression testing on a z/VM instance, I noticed call traces
  being dumped to dmesg that seem to be related to stress-ng.

  The stress-ng invocation we're using is:
  stress-ng --aggressive --verify --timeout $runtime \
   --metrics-brief --tz --times \
   --af-alg 0 --bsearch 0 --context 0 --cpu 0 \
   --crypt 0 --hsearch 0 --longjmp 0 --lsearch 
0 \
   --matrix 0 --qsort 0 --str 0 --stream 0 \
   --tsearch 0 --vecmath 0 --wcs 0

  as executed by the cpu_stress script from the cpu/cpu_stress_ng test
  in the certification suite.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Nov  3 11:12:04 2017
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  artful
  Uname: Linux 4.13.0-16-generic s390x
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1729878/+subscriptions

-- 
Mailing list:

[Kernel-packages] [Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Also retried on amd64 and the effect was the same:

ubuntu@xwing:~$ free -lm
  totalusedfree  shared  buff/cache   available
Mem:   3838 1203601   0 1153510
Low:   3838 2363601
High: 0   0   0
Swap: 97695  61   97633

no OOMKiller messages appeared in dmesg

Test passed according to test output

and the low/high usage is within what is available:

0  0 62   3605  111100   320  1231  252  511  0  0 97  3  0
1  9  19429 86  11090   5825 60607 2863 2301  0  3 11 85  0


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

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

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

Title:
  stress-ng triggering oomkiller running brk and stack stressors on all
  arches.

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Invalid

Bug description:
  During regression testing on a z/VM instance, I noticed call traces
  being dumped to dmesg that seem to be related to stress-ng.

  The stress-ng invocation we're using is:
  stress-ng --aggressive --verify --timeout $runtime \
   --metrics-brief --tz --times \
   --af-alg 0 --bsearch 0 --context 0 --cpu 0 \
   --crypt 0 --hsearch 0 --longjmp 0 --lsearch 
0 \
   --matrix 0 --qsort 0 --str 0 --stream 0 \
   --tsearch 0 --vecmath 0 --wcs 0

  as executed by the cpu_stress script from the cpu/cpu_stress_ng test
  in the certification suite.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Nov  3 11:12:04 2017
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  artful
  Uname: Linux 4.13.0-16-generic s390x
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1729878/+subscriptions

-- 
Mailing

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

2017-11-10 Thread Robin H. Johnson

TL;DR: pass '-vga none' with -nographic, or redirect the screen
somewhere!

I ended up digging into this after it was mentioned by smoser. The bug
is invalid because of a bad assumption in the QEMU inputs. smoser's
workaround of usb=off removes USB as a workaround.

The kernel, OpenFirmware, and QEMU are behaving correctly, but the
original command-line hides the screen output.

If you have both a supported* keyboard AND screen, then OpenFirmware/SLOF sets 
OF stdout to be the screen.
This causes the OF output of 'No console specified using screen & keyboard'

If you are missing either a keyboard OR screen, then OF sets stdout to be 
hvterm (serial).
This causes the OF output of 'No console specified using hvterm'

https://git.qemu.org/?p=SLOF.git;a=blob;f=board-
qemu/slof/OF.fs;h=4e04b840d5e6ff6c39191939e1a4f70f3d169d5d;hb=HEAD#l215

Which devices are available depends on the QEMU commandline...
Base QEMU defaults to '-vga std'.
QEMU '-machine pseries' defaults to enabling USB.


Re supported keyboards: The OpenFirmware/SLOF only seems to support USB 
keyboards at this time (virtio keyboard not supported).

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

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX

[Kernel-packages] [Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

So I did this on 4.4 on ppc64le with 32GB RAM and 96GB Swap:
ubuntu@entei:~$ free -lm
  totalusedfree  shared  buff/cache   available
Mem:  32565 656   30603   21304   30503
Low:  325651961   30603
High: 0   0   0
Swap: 97695 342   97353

And this time OOMKiller was not hit.

ubuntu@entei:~$ ./memory_stress_ng 
Total memory is 32 GiB
Constant run time is 300 seconds per stressor
Variable run time is 620 seconds per stressor
Estimated total run time is 20 minutes

Running stress-ng stack stressor for 300 seconds
stress-ng: info:  [15395] dispatching hogs: 128 stack
stress-ng: info:  [15395] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [15395] cache allocate: default cache size: 2048K
stress-ng: info:  [15395] successful run completed in 317.89s (5 mins, 17.89 
secs)
return_code is 0
Running stress-ng numa stressor for 300 seconds
stress-ng: info:  [15663] dispatching hogs: 128 numa
stress-ng: info:  [15663] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [15663] cache allocate: default cache size: 2048K
stress-ng: info:  [15664] stress-ng-numa: system has 1 of a maximum 256 memory 
NUMA nodes
stress-ng: info:  [15663] successful run completed in 300.08s (5 mins, 0.08 
secs)
return_code is 0
Running stress-ng brk stressor for 620 seconds
stress-ng: info:  [15800] dispatching hogs: 128 brk
stress-ng: info:  [15800] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [15800] cache allocate: default cache size: 2048K
stress-ng: info:  [15800] successful run completed in 666.16s (11 mins, 6.16 
secs)
return_code is 0
***
** stress-ng memory test passed!
***

The only message that appeared in dmesg during this test run is one warning: (I 
cleared the ring buffer with dmesg -C before running the test).
ubuntu@entei:~$ dmesg
[ 7390.968438] stress-ng[15584]: bad frame in setup_rt_frame: 3fffdd0e1040 
nip 

And from looking at vmstat, this is the lowest and highest consumption observed:
 0  0340  30582 14   129900 3   385   27   25  3  3 75 19  0
 0 260  58068196 12   13232   76  2571 78490 3295 5493  0  0 25 74  0

So at the least, only 340MB swap consumed and a full 30GB ram free, and
at the most, 58GB swap consumed and only 196MB free.

So there DOES seem to be a limit to what these tests are consuming.

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

Title:
  stress-ng triggering oomkiller running brk and stack stressors on all
  arches.

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  During regression testing on a z/VM instance, I noticed call traces
  being dumped to dmesg that seem to be related to stress-ng.

  The stress-ng invocation we're using is:
  stress-ng --aggressive --verify --timeout $runtime \
   --metrics-brief --tz --times \
   --af-alg 0 --bsearch 0 --context 0 --cpu 0 \
   --crypt 0 --hsearch 0 --longjmp 0 --lsearch 
0 \
   --matrix 0 --qsort 0 --str 0 --stream 0 \
   --tsearch 0 --vecmath 0 --wcs 0

  as executed by the cpu_stress script from the cpu/cpu_stress_ng test
  in the certification suite.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Nov  3 11:12:04 2017
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0

[Kernel-packages] [Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

2017-11-10 Thread Rainer Rohde

This bug still exists on Dell XPS 15 running Ubuntu 17.10, kernel
4.13.0-17-generic

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

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561474/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-11-10 Thread Dmitrii Shcherbakov

There is a scenario where a real rootfs is located on a bcache device,
however, for that we need to register a bcache device at the initrd
stage which already happens now. Then we'd locate a file system on it
and do pivot_root and so on.

The bcache naming, I believe, is not guaranteed at this point unless
we have a rule that says so.

Side-tracking to our field use-cases, we need persistence in
/dev/bcache names based on superblock UUIDs. So, I expect
/dev/bcache/ names to be persisted by UUID on first discovery (which
corresponds to MAAS deploy stage, not commissioning as in case of disk
serial numbers).

However, we also expect bcache names to match names in MAAS which may
not happen in this scenario because  : bcache
mapping is not enforced.

Going back to https://bugs.launchpad.net/curtin/+bug/1728742, I think we
can break it down into two problems:

1. bcache device numbers are not static across reboots and we need a
static mapping of superblock UUID to bcache for a given device. This
requires CACHED_UUID to be present in uevent environment which is only
possible during a successful registration where this code path is
triggered. As a result of rootfs on bcache requirement, this makes sense
to do at the initrd stage before we have to do pivot_root to the real
rootfs.

Doing something like that when systemd is running post pivot_root and
/dev devtmpfs transfer to the real rootfs doesn't sound right to me as
we have this problem with double registration. In summary, I think
/dev/bcache/by-uuid/ symlinks for bcache devices that exist on initial
boot should be created via udev rules in initrd.

This is what this bug is about.

2. bcache device names may not match the ones in MAAS. This has
implications for our use of Juju Storage functionality when we need
device special files with static names without file systems or partition
tables present. After commissioning in MAAS there's already metadata
present about a given machine - disk serial numbers are gathered (if
present, this is not guaranteed and block driver-specific AFAIK but a
sane assumption to make) and device names that were assigned during
ephemeral image boot are presented and stored in a database with
associated serial numbers available for querying to set up dname
symlinks on deployment.

In order to make  : bcache mapping static we need
to essentially have a mapping of disk serial numbers to bcache
superblock UUIDs which are in turn mapped to bcache names.

I would say that https://bugs.launchpad.net/curtin/+bug/1728742 is about
p.2.



The rationale for p. 1 is that the init script sets up devtmpfs
initially which then gets moved over to the real rootfs (init-bottom
script) before pivot_root is performed. systemd then runs its mount
point set up code which checks if a given entry in its hard-coded table
of mount points is already a mount point and skips its setup if this is
the case. So anything set up during initrd stage will stay there after
systemd runs as devtmpfs is moved and reused.

https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/tree/src/core/mount-setup.c?h=applied/ubuntu/xenial-updates#n77
  { "devtmpfs", "/dev", "devtmpfs", "mode=755", MS_NOSUID|MS_STRICTATIME,

path_is_mount_point -> fd_is_mount_point
https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/tree/src/core/mount-setup.c?h=applied/ubuntu/xenial-updates#n161

static int mount_one(const MountPoint *p, bool relabel) {
...
r = path_is_mount_point(p->where, AT_SYMLINK_FOLLOW);
if (r < 0 && r != -ENOENT) {
log_full_errno((p->mode & MNT_FATAL) ? LOG_ERR : LOG_DEBUG, r, 
"Failed to determine whether %s is a mount point: %m", p->where);
return (p->mode & MNT_FATAL) ? r : 0;
}
if (r > 0)
return 0;


init script:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/init?h=applied/ubuntu/xenial-updates
[ -d /dev ] || mkdir -m 0755 /dev
...

# Note that this only becomes /dev on the real filesystem if udev's scripts
# are used; which they will be, but it's worth pointing out
if ! mount -t devtmpfs -o nosuid,mode=0755 udev /dev; then
 echo "W: devtmpfs not available, falling back to tmpfs for /dev"
 mount -t tmpfs -o nosuid,mode=0755 udev /dev
 [ -e /dev/console ] || mknod -m 0600 /dev/console c 5 1
 [ -e /dev/null ] || mknod /dev/null c 1 3
fi
...


init-bottom:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/tree/debian/extra/initramfs-tools/scripts/init-bottom/udev?h=applied/ubuntu/xenial-updates

...
# move the /dev tmpfs to the rootfs
mount -n -o move /dev ${rootmnt}/dev

# create a temporary symlink to the final /dev for other initramfs scripts
if command -v nuke >/dev/null; then
  nuke /dev
else
  rm -rf /dev
fi
ln -s ${rootmnt}/dev /dev

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

[Kernel-packages] [Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Ok, I've narrowed it down to the brk and stack stressors in stress-ng.
I've recreated this on amd64, ppc64el and s390x across 4.4, 4.10 and
4.13 kernels.

Stress-NG reports the tests as successful so I guess now the only thing
remaining is to confirm that hitting OOM killer is expected behaviour
when running these stressors.

I've tried setting up swap space that is three times the amount of
physical RAM and this is still invoking the OOMkiller.

ubuntu@xwing:~$ free -lm
  totalusedfree  shared  buff/cache   available
Mem:   3838 1053598   0 1333517
Low:   3838 2393598
High: 0   0   0
Swap: 11514  68   11446

And from looking at vmstat while it's running:
procs ---memory-- ---swap-- -io -system-- --cpu-
 r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa st
 0  0 37   3618  51380226  2880  154  138  0  1 60 39  0
 0  9257 82  11140   22   183 23495 1284  907  0  3 61 36  0
 0  9891 84  01100   63 9 65792 3266 1865  0  2  6 92  0
 0 10   1601 87  01080   71 1 73444 3466 1682  0  3  6 92  0
 1  8   2300 83  01080   70 6 72316 3494 1673  0  3  6 91  0
 0 10   2926 82  11060   63   165 64884 2940 1593  0  2  8 90  0
 0  9   3592 95  01060   6769 68825 2987 1672  0  3  8 90  0
 0  9   4326 82  01040   7316 76003 3376 1645  0  3  5 92  0
 0  9   4910 81  01030   58   177 60429 2713 1596  0  2  8 90  0
 0 10   5581 81  01040   67   122 69519 2680 1581  0  2 13 85  0
 0 10   6317 89  01050   7413 76143 3389 1613  0  3  5 92  0
 0  9   6972 83  11040   66   103 67807 2964 1711  0  3  7 90  0
 0  9   7591103  11050   6239 64041 2918 1530  0  3  8 89  0
 0  9   8248 84  11050   6617 68101 3208 1573  0  3  6 91  0
 0 10   8946 82  11050   70 0 72289 2934 1615  0  3  7 90  0
 0  9   9586 82  11040   6460 66192 2953 1725  0  3  6 90  0
 0  9  10276100  11040   69 3 71434 2986 1694  0  3  9 88  0
 0 10  10958 82  11030   6811 70660 3365 1704  0  4  8 88  0
 0  9  11455 82  11020   5053 51572 2269 1533  0  2 15 82  0
 0 11  10249 87  01060   26   783 27601 1323 1721  0  2 16 82  0
 0 10  10407 82  01050   16 6 16883 1487 1438  0  1 39 60  0
procs ---memory-- ---swap-- -io -system-- --cpu-
 r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa st
 0 11  10543 82  01090   14   558 14774 1523 2202  0  1 31 68  0
 0 12  10672 82  11130   13   598 13945 1552 2592  0  1 17 82  0
 1  8  10844 84  11150   17   499 18516 1434 1921  0  1 22 77  0
 0  9  11080 81  11130   24 0 25004 1782 1547  0  2 32 67  0
 0  9  11338 82  11130   26 2 27162 1874 1606  0  2 25 73  0
 0 13   9950 82  01050   25   636 26475 1672 1657  0  2 21 77  0
 0 10  10167 81  01050   22   111 23060 1956 1766  0  1 26 73  0
 0  9  10368 81  01060   2062 21257 1687 1470  0  1 30 68  0
 1  8  10559 81  11060   1992 20380 1660 1542  0  1 30 68  0
 0  9  10815 81  11060   26 0 26964 1960 1523  0  2 30 68  0
 0  9237 95  11160   34   714 35614 2065 2124  0  5 32 63  0
 0  9851 84  11150   6131 63467 3612 2607  0  2  4 94  0
 0 10   1468 82  11150   62   130 63985 3167 2316  0  2  5 92  0
 0  9   2156 83  11150   6912 71113 3476 2294  0  3  4 93  0
 0  9   2837 88  11150   6833 70577 3007 2155  0  3  5 92  0
 0 10   3501 82  11100   6610 68809 3015 2202  0  2  8 90  0
 0  9   4194 82  11090   6937 71556 3648 2597  0  3  5 92  0
 7  1   4901 82  11090   71 3 73264 3368 2087  0  3  8 90  0
 0 10   5551 82  01050   65   183 67353 3121 2189  0  3  9 88  0
 0 10   6241 82  01050   6979 71325 3448 2414  0  3  7 90  0
 0  9   6901 86  11050   6658 68414 3055 2254  0  3  6 91  0
procs ---memory-- ---swap-- -io -system-- --cpu-
 r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa st
 0 10   7619 93  11050   7212 74423 3439 2329  0  3  7 89  0
 0  9   8338 96  11050   7210 74165 3498 2213  0  4  7 90  0
 0 10   8851 82  11040   51   201 53453 3791 2960  0  3  5 92  0
 0  9   9406 88  11050   55   113

[Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

2017-11-10 Thread martin

Is anyone actively looking at this? I uploaded a patch, it just needs to
be tested and merged.

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729051/+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 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

** Summary changed:

- stress-ng triggering call-traces on s390x z/VM instances
+ stress-ng triggering oomkiller running brk and stack stressors on all arches.

** Also affects: stress-ng
   Importance: Undecided
   Status: New

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

Title:
  stress-ng triggering oomkiller running brk and stack stressors on all
  arches.

Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  During regression testing on a z/VM instance, I noticed call traces
  being dumped to dmesg that seem to be related to stress-ng.

  The stress-ng invocation we're using is:
  stress-ng --aggressive --verify --timeout $runtime \
   --metrics-brief --tz --times \
   --af-alg 0 --bsearch 0 --context 0 --cpu 0 \
   --crypt 0 --hsearch 0 --longjmp 0 --lsearch 
0 \
   --matrix 0 --qsort 0 --str 0 --stream 0 \
   --tsearch 0 --vecmath 0 --wcs 0

  as executed by the cpu_stress script from the cpu/cpu_stress_ng test
  in the certification suite.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Nov  3 11:12:04 2017
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M 
BOOT_IMAGE=0
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  artful
  Uname: Linux 4.13.0-16-generic s390x
  UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1729878/+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 1717224] New sosreport captured Aug 23

Default Comment by Bridge

** Attachment added: "New sosreport captured Aug 23"
   
https://bugs.launchpad.net/bugs/1717224/+attachment/5007096/+files/sosreport-sgreenlese.157241-20170823133130.tar.bz2

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in kvm source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in kvm source package in Zesty:
  New
Status in linux source package in Zesty:
  In Progress
Status in procps source package in Zesty:
  New
Status in kvm source package in Artful:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf

[Kernel-packages] [Bug 1717224] New syslog captured Aug 23

Default Comment by Bridge

** Attachment added: "New syslog captured Aug 23"
   
https://bugs.launchpad.net/bugs/1717224/+attachment/5007097/+files/syslog_082317

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in kvm source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in kvm source package in Zesty:
  New
Status in linux source package in Zesty:
  In Progress
Status in procps source package in Zesty:
  New
Status in kvm source package in Artful:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536

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

--- Comment From swgre...@us.ibm.com 2017-11-10 14:39 EDT---
(In reply to comment #31)
> Hi Scott,
> the howto is mixed for Desktop users, Server users and selective upgrades.
> For your case you only need the most simple case which would be:
>
> Essentially you want to:
>
> # Check - all other updates done (to clear the view)
> $ apt list --upgradable
> Listing... Done
>
> # Enable proposed for z on Server
> $ echo "deb http://ports.ubuntu.com/ubuntu-ports/ xenial-proposed main
> restricted universe multiverse" | sudo tee
> /etc/apt/sources.list.d/enable-proposed.list
> $ sudo apt update
> $ apt list --upgradable
> [...]
> linux-headers-generic/xenial-proposed 4.4.0.100.105 s390x [upgradable from:
> 4.4.0.98.103]
> linux-headers-virtual/xenial-proposed 4.4.0.100.105 s390x [upgradable from:
> 4.4.0.98.103]
> linux-image-virtual/xenial-proposed 4.4.0.100.105 s390x [upgradable from:
> 4.4.0.98.103]
>
> # Install just the kernels from proposed
> $ sudo apt install linux-generic
>
> No need to set apt prefs if you only do a selective install.
> If you'd do a global "sudo apt upgrade" you'd get all, but that is likely
> not what you want in your case. After you have done so you can just
> enable/disable the line in /etc/apt/sources.list.d/enable-proposed.list as
> needed.
>
> Hope that helps

Yes, your instructions were immensely useful, thanks for the
explanation.

With the proposed fix applied, I am now able to start over 100 virtual
guests, even with aio-max-nr set to 64K:

root@zm93k8:~# cat /proc/sys/fs/aio-max-nr
65535

root@zm93k8:/tmp# virsh list |grep running
86zs93kag70041   running
87zs93kag70042   running
88zs93kag70055   running
89zs93kag70056   running
90zs93kag70057   running
91zs93kag70058   running
92zs93kag70059   running
93zs93kag70060   running
94zs93kag70061   running
95zs93kag70062   running
96zs93kag70063   running
97zs93kag70064   running
98zs93kag70065   running
99zs93kag70066   running
100   zs93kag70067   running
101   zs93kag70068   running
102   zs93kag70069   running
103   zs93kag70070   running
104   zs93kag70071   running
105   zs93kag70072   running
106   zs93kag70073   running
107   zs93kag70074   running
108   zs93kag70075   running
109   zs93kag70077   running
110   zs93kag70078   running
111   zs93kag70079   running
112   zs93kag70080   running
113   zs93kag70081   running
114   zs93kag70082   running
115   zs93kag70083   running
116   zs93kag70084   running
117   zs93kag70085   running
118   zs93kag70086   running
119   zs93kag70087   running
120   zs93kag70088   running
121   zs93kag70089   running
122   zs93kag70090   running
123   zs93kag70091   running
124   zs93kag70092   running
125   zs93kag70093   running
126   zs93kag70094   running
127   zs93kag70095   running
128   zs93kag70096   running
129   zs93kag70097   running
130   zs93kag70098   running
131   zs93kag70099   running
132   zs93kag70100   running
133   zs93kag70101   running
134   zs93kag70102   running
135   zs93kag70103   running
136   zs93kag70104   running
137   zs93kag70105   running
138   zs93kag70106   running
139   zs93kag70107   running
140   zs93kag70108   running
141   zs93kag70109   running
142   zs93kag70110   running
143   zs93kag70111   running
144   zs93kag70112   running
145   zs93kag70113   running
146   zs93kag70114   running
147   zs93kag70115   running
148   zs93kag70116   running
149   zs93kag70117   running
150   zs93kag70118   running
151   zs93kag70119   running
152   zs93kag70120   running
153   zs93kag70121   running
154   zs93kag70122   running
155   zs93kag70123   running
156   zs93kag70124   running
157   zs93kag70125   running
158   zs93kag70126   running
159   zs93kag70127   running
160   zs93kag70128   running
161   zs93kag70129

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2017-11-10 Thread Occams Beard

Package C7 is the best I can achive as well with the patched r8169
driver & all tunables set to GOOD. But the fan issue seems to be solved
for me with it. The fan rarely even comes on, when it does, it shuts
off a few seconds later, as expected.

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

Title:
Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
Incomplete

Bug description:
Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
be an issue with the fan control. When I first boot up the machine the
fans are off. However, after the laptop warms up under normal usage,
the fans kick on and then never shut off again. Even when the CPU
cools down to below 35c, the fans will continue to run.

If I suspend the the laptop, and then immediately wake it up again
then fans are once again off, until it warms up again. So
essentially, once the fans start they don't seem to ever shut off.

Fans seem to work normally under Windows 10. They turn on as needed,
and then turn off once the laptop cools down.

I've tried the various BIOS updates that Dell has released, without
success. I am currently running Dell's latest BIOS for this laptop
(v1.1.8)

Below is the output of lm-sensors showing the fans running when the
CPU is at a cool 35c

dell_smm-virtual-0
Adapter: Virtual device
Processor Fan: 1925 RPM
Processor Fan: 2143 RPM
CPU:+35.0°C
GPU: +1.0°C
SODIMM: +49.0°C

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob1709 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 13 19:18:45 2016
HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
InstallationDate: Installed on 2016-07-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Inspiron 7559
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.8
dmi.board.name: 0H0CC0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7559
dmi.product.version: 1.1.8
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

2017-11-10 Thread mihai

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

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

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282/+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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => 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/1731264

Title:
  linux: 4.4.0-101.124 -proposed tracker

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

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

  backports: 1731266
  derivatives:
  kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2017-11-10 Thread Julo Petko

@Kai-Heng Feng (kaihengfeng): tried your kernel and no change, even with
all tunables set to good I got only PCakage C7 state. This machine seems
to be enchanted or something.

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2017-11-10 Thread Christopher M. Penalver

** Description changed:

What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the
following three things happen ~50% of the time when I come back to unlock it:
* Most of the time the computer is found shut down.
* Sometimes the notebook screen flickers weirdly and one of the two external
monitors show pixelation.
* The notebook screen shows the lock screen but is completely frozen.
Occasionally unlocking works.

I have two external monitors attached to the docking station.

When I dock my laptop, the battery indicator does recognize its
charging.

I've not seen this issue when:
1) With the laptop in the dock, while actively using the laptop.
2) With the laptop out of the dock and no external monitors present.

This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

Using or not using the following kernel parameter didn't change anything:
i915.enable_rc6=0

+ Updated docking station firmware to latest 2.33.00.
+
PC temperatures are normal as per lm-sensors.
+
+ 20171109 - Not reproducible testing drm-tip for 1.5 days.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: akops 3337 F pulseaudio
/dev/snd/controlC0: akops 3337 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:44:11 2017
HibernationDevice: RESUME=/dev/mapper/system-swap_1
MachineType: LENOVO 20BWS2YL00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0
crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.13.0-16-lowlatency N/A
linux-backports-modules-4.13.0-16-lowlatency N/A
linux-firmware1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
dmi.bios.date: 07/08/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET51WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS2YL00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BWS2YL00
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO

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

Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
FIFO underrun

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

Bug description:
What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the
following three things happen ~50% of the time when I come back to unlock it:
* Most of the time the computer is found shut down.
* Sometimes the notebook screen flickers weirdly and one of the two external
monitors show pixelation.
* The notebook screen shows the lock screen but is completely frozen.
Occasionally unlocking works.

I have two external monitors attached to the docking station.

When I dock my laptop, the battery indicator does recognize its
charging.

I've not seen this issue when:
1) With the laptop in the dock, while actively using the laptop.
2) With the laptop out of the dock and no external monitors present.

This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

Using or not using the following kernel parameter didn't change anything:
i915.enable_rc6=0

Updated docking station firmware to latest 2.33.00.

PC temperatures are normal as per lm-sensors.

20171109 - Not reproducible testing drm-tip for 1.5 days.

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

This change was made by a bot.

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

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

Title:
  Elantech touchpad never work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu 17.10, the touchpad has never worked.

  I read a lot in forums, but no one found a solution.

  Please, solve my problem

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lorenzo1135 F pulseaudio
   /dev/snd/controlC0:  lorenzo1135 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 19:11:04 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 80XV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=02baf904-cbdf-4796-a6f8-f8290963b313 ro i8042.kbdreset=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN17WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN17WW:bd07/13/2017:svnLENOVO:pn80XV:pvrLenovoideapad320-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15AST:
  dmi.product.family: ideapad 320-15AST
  dmi.product.name: 80XV
  dmi.product.version: Lenovo ideapad 320-15AST
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731527/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-11-10 Thread Rafael David Tinoco

Hello Amanda,

I'm actively working into this, will provide better feedback soon. The
script is just a workaround for now, so people can shut down properly,
if they are facing this.

Despite what userland does, the kernel will always potentially hang with
iscsi sessions left opened during shutdown. If, after following the
setup steps, you still faced the issue, its possible that your shutdown
systemd unit ordering is wrong (your mount points are being unmounted
before they are released). I'm working in the kernel issue, so, it shall
cover all the userland-created situations.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+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 1731527] [NEW] Elantech touchpad never work

2017-11-10 Thread Lorenzo Romanella

Public bug reported:

Since I installed Ubuntu 17.10, the touchpad has never worked.

I read a lot in forums, but no one found a solution.

Please, solve my problem

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lorenzo1135 F pulseaudio
 /dev/snd/controlC0:  lorenzo1135 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 10 19:11:04 2017
InstallationDate: Installed on 2017-11-10 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 80XV
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=02baf904-cbdf-4796-a6f8-f8290963b313 ro i8042.kbdreset=1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 5PCN17WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15AST
dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN17WW:bd07/13/2017:svnLENOVO:pn80XV:pvrLenovoideapad320-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15AST:
dmi.product.family: ideapad 320-15AST
dmi.product.name: 80XV
dmi.product.version: Lenovo ideapad 320-15AST
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Elantech touchpad never work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu 17.10, the touchpad has never worked.

  I read a lot in forums, but no one found a solution.

  Please, solve my problem

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lorenzo1135 F pulseaudio
   /dev/snd/controlC0:  lorenzo1135 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 19:11:04 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 80XV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=02baf904-cbdf-4796-a6f8-f8290963b313 ro i8042.kbdreset=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN17WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN17WW:bd07/13/2017:svnLENOVO:pn80XV:pvrLenovoideapad320-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15AST:
  dmi.product.family: ideapad 320-15AST
  dmi.product.name: 80XV
  dmi.product.version: Lenovo ideapad 320-15AST
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731527/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-11-10 Thread Amanda Gartner

I followed all of the setup steps, but was still encountering the ping
timeout issue at reboot. I then ran the script
http://pastebin.ubuntu.com/25894592/ you provided and am no longer
hitting the issue. Was the script supposed to fix the issue? Please let
me know. Thank you!

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+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 1710019] Re: support GICv3 ITS save/restore & migration

2017-11-10 Thread dann frazier

I have a staging PPA that I'm using for testing at ppa:dannf/lp1710019.
The QEMU there is the attached debdiff (trivially) forward-ported to the
latest qemu in updates, and the kernel has the patches I plan to submit
to the kernel team. I've verified that this all works together on a
zesty system.

I also took a look at LP: #1731051 to see if we should include that fix
in this backport as well. I don't think we need to - the reboot command
in question doesn't work at all in zesty (w/ or w/o these patches. I
assume that was a feature added to QEMU post-2.8.

So yeah, from point-of-view this is all good to go. I'll proceed with
submitting the kernel-side backport.

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

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

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

--- Comment From mdr...@us.ibm.com 2017-11-10 12:18 EDT---
So far I've only been able to reproduce this 2 ways:
a) booting up a Debian Jessie guest (kernel 3.16). generally the crash
happens some time after boot, but on some situations it needs some
"help", like running "useradd ".
b) bootup up an Ubuntu 16.04 guest, which doesn't seem to ever trigger
the issue itself, but then chrooting into that same Debian Jessie
image (attaching as a 2nd virtio disk), and then running that same
"useradd ".

Using these test cases, the crash appears to be during the first
instance of compound_head(page) within mm/gup.c:gup_pte_range()

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/mm/gup.c?h=v4.13#n1312

The compound_head(page) call results in a pointer dereference of a
struct *page, via page->compound_page, and that generates a page
fault which leads to the crash. The address of *page in one instance
of the crash was 0xf783af20:

[95667.639406] Unable to handle kernel paging request for data at address 
0xf783af20
[95667.639518] Faulting instruction address: 0xc0309714
90:mon> t
[c01e3c4db900] c030a3d0 get_user_pages_fast+0x110/0x160
[c01e3c4db950] d000181be21c kvmppc_book3s_hv_page_fault+0x384/0xc60 
[kvm_hv]
[c01e3c4dba40] d000181ba94c kvmppc_vcpu_run_hv+0x314/0x790 [kvm_hv]
[c01e3c4dbb10] d000181059ec kvmppc_vcpu_run+0x34/0x48 [kvm]
[c01e3c4dbb30] d00018101aa0 kvm_arch_vcpu_ioctl_run+0x108/0x320 [kvm]
[c01e3c4dbbd0] d000180f5018 kvm_vcpu_ioctl+0x400/0x7c8 [kvm]
[c01e3c4dbd40] c03bd6e4 do_vfs_ioctl+0xd4/0xa00
[c01e3c4dbde0] c03be0d4 SyS_ioctl+0xc4/0x130
[c01e3c4dbe30] c000b184 system_call+0x58/0x6c
--- Exception: c01 (System Call) at 79d53a595550
SP (79d5354ede40) is in userspace

The 0xf address corresponds to the vmemmap area, where page structs are
allocated sequentially for all PFNs in the system, so it isn't obviously
a bad address. Some of our kernel folks took a look at this and worked out
that that with a 64 byte sizeof(struct page), 0xf783af20
corresponds to 0x783af20 / 64 = 1969852th PFN. For a 64K page size this
corresponds to 1969852*64K, an address somewhere at around 120GB, which
is in the range of physical memory on the system (0-128GB in this case)

Since the *page address appeared valid, it was suggested that the issue
was with the vmemmap area being "unbolted" by KVM, leading to a page
fault for an address that should always be pinned/bolted within the
host, and the following fix was suggested:

commit 67f8a8c1151c9ef3d1285905d1e66ebb769ecdf7
Author: Paul Mackerras 
Date:   Tue Sep 12 13:47:23 2017 +1000
KVM: PPC: Book3S HV: Fix bug causing host SLB to be restored incorrectly

I've tested this patch against kernel 4.13.0-16-generic, and at least for
test cases a) and b) above, this does appear to resolve the issue.

So it looks like we need kernel commit 67f8a8c115 pulled into 17.10 to resolve
this 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/1725350

Title:
  KVM on 17.10 crashes the machine

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  When you start qemu on a 17.10 machine, the whole machine goes down
  and crashes:

  [   90.689627] Unable to handle kernel paging request for data at address 
0xf2d3bda0
  [   90.689705] Faulting instruction address: 0xc0361224
  [   90.689840] Oops: Kernel access of bad area, sig: 11 [#1]
  [   90.689911] SMP NR_CPUS=2048 
  [   90.689912] NUMA 
  [   90.690053] PowerNV
  [   90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs 
joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd 
at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq 
vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables
  [   90.690724]  autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 
raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit 
crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm tg3 ahci libahci
  [

[Kernel-packages] [Bug 1726159] Re: PCIe BUS Error causing really slow laptop performance

2017-11-10 Thread George Mathioudakis

Very Important Info: I inserted my Samsung 850 EVO 250GB SSD on my
laptop's HDD slot and on battery power, with TLP off, it runs on normal
speed 550MB/S Read/Write! My primary M.2 SSD "Micron 1100 250GB" is
still running on 32MB/S Read/Write. That means Micron SSD is checking
for battery/ac mode.

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

Title:
  PCIe BUS Error causing really slow laptop performance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought the following laptop:
  Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)

  It came pre-installed with Win10 and I did a fresh install of Ubuntu
  16.04 LTS. The screen was flickering for some reason and installing
  Ubuntu 17.04 fixed the issue.

  The real problem is that when I'm booting the laptop, the following
  error is being shown on my screen:

  [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
  [   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
  [   12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  [   12.898491] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=2041/2000
  [   12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First)
  [   12.898493] pcieport :00:1c.5:[ 6] Bad TLP

  I know that this error can be hid with one of the following kernel boot 
arguments:
  pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.

  The weird thing is that the above output is only being shown when the
  laptop is on AC Power (charging). When the laptop is not connected to
  AC (battery-mode), it has performance issues (slow boot and slow
  application launching). I was trying all day long to fix the problem.
  I removed everything that had to do with power-saving, reinstalled,
  re-tweaked for performance, tried different kernels but had no luck.
  While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that
  my laptop had. The results are:

  * On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
  * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)

  This explains everyting. That's why I'm having a slow boot and slow
  application launching!

  Commands "lspci" and "dmesg" say that the error comes from the following 
device:
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)

  I will attach lspci and dmesg output on a tar.gz file.

  --
  UPDATE: When the laptop is fully charged and still on AC (but not charging 
since it is 100% charged), the errors appear again but the SSD speed is normal 
(~500 Read/Write).
  --
  UPDATE: I installed 'tlp' Advanced Power Management package and when using 
the command 'tlp ac', the SSD speed gets back to normal! The option does not 
persist across reboots.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  georgem2557 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Oct 22 23:17:57 2017
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X542UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2017-11-10 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => Incomplete

** Changed in: linux
   Importance: Unknown => High

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  PC temperatures are normal as per lm-sensors.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727662/+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 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=103643
   Importance: Unknown
   Status: Unknown

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  PC temperatures are normal as per lm-sensors.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1727662/+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 1726626] Re: No matter the interface Ubuntu 17.10 freezes

Can you enable persistent systemd-journald log?

After the freeze happens, use `journalctl -k -b -1` to collect last
kernel message.

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

Title:
  No matter the interface Ubuntu 17.10 freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No matter the interface I choose Ubuntu 17.10 freezes/ crashes. Unity,
  Ubuntu (Gnome), Ubuntu (Gnome) with Xorg, Kodi, and SteamOS. I looked
  it up, and everybody has had this issue in the beta constantly. There
  was no fix, and it only seems to get worse. Most of the time it
  freezes after 20 minutes of running Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrewbean90   2064 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 18:42:46 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=1891cc5f-0530-483f-bf74-a740e46e7af5
  InstallationDate: Installed on 2016-12-29 (298 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 1545
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

> On 9 Nov 2017, at 11:19 PM, Menachem Shapiro  
> wrote:
> 
> I just updated to Lubuntu 17.10 and experienced this issue. I have a
> Qualcomm Atheros QCA9377 card, and kernel version 4.13.0-16-generic had
> this same issue. I reverted back to 4.10.0-38-generic and the problem
> went away.
> 
> I'm waiting for the next kernel release to see if that solves the
> problem.

The Linux kernel in -proposed should fix the issue.

> 
> See also this thread: https://askubuntu.com/questions/965856/kworker-
> blocked-for-more-than-120-seconds-ubuntu-17-10/967440
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1724317
> 
> Title:
>  Shutdown hangs / no standby - possible Wifi-bug in the kernel
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  The Shutdown-process hangs. After about two minutes the following
>  message is displayed:
> 
>  Oct 17 18:47:06 Kahlan kernel: [  363.170588] INFO: task kworker/u8:2:186 
> blocked for more than 120 seconds.
>  Oct 17 18:47:06 Kahlan kernel: [  363.170592]   Tainted: P   OE  
>  4.13.0-12-generic #13-Ubuntu
>  Oct 17 18:47:06 Kahlan kernel: [  363.170593] "echo 0 > 
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> 
>  Two Minutes later this message is displayed:
>  Oct 17 18:49:07 Kahlan kernel: [  484.008650] INFO: task kworker/u8:2:186 
> blocked for more than 120 seconds.
>  Oct 17 18:49:07 Kahlan kernel: [  484.008659]   Tainted: P   OE  
>  4.13.0-12-generic #13-Ubuntu
>  Oct 17 18:49:07 Kahlan kernel: [  484.008662] "echo 0 > 
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> 
>  This message repeates itself. If I am lucky, my laptop shuts down
>  after some time.
> 
>  Also standby does not work. I think my wifi-adapter causes this
>  problem.
> 
>  With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I
>  found a bug report in the Arch Bug System
>  (https://bugs.archlinux.org/task/55872
> 
>  In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the
>  linuxkernel has a bug?
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: xorg 1:7.7+19ubuntu3
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  Uname: Linux 4.13.0-16-generic x86_64
>  ApportVersion: 2.20.7-0ubuntu3
>  Architecture: amd64
>  CompositorRunning: None
>  CurrentDesktop: KDE
>  Date: Tue Oct 17 19:08:32 2017
>  DistUpgraded: Fresh install
>  DistroCodename: artful
>  DistroVariant: kubuntu
>  DkmsStatus:
>   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
>   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
>   nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed
>   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
>  ExtraDebuggingInterest: No
>  GraphicsCard:
>   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
> controller])
> Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962]
>  InstallationDate: Installed on 2017-10-07 (10 days ago)
>  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
>  MachineType: Acer Aspire VN7-571G
>  ProcEnviron:
>   LANGUAGE=de
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=de_DE.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
> root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7
>  SourcePackage: xorg
>  Symptom: display
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 01/08/2015
>  dmi.bios.vendor: Insyde Corp.
>  dmi.bios.version: V1.14
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: Aspire VN7-571G
>  dmi.board.vendor: Acer
>  dmi.board.version: V1.14
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Acer
>  dmi.chassis.version: V1.14
>  dmi.modalias: 
> dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
>  dmi.product.family: Broadwell System
>  dmi.product.name: Aspire VN7-571G
>  dmi.product.version: V1.14
>  dmi.sys.vendor: Acer
>  version.compiz: compiz N/A
>  version.libdrm2: libdrm2 2.4.83-1
>  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
>  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
>  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
>  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
>  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20170309-0ubuntu1
>  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+subscriptions

-- 
You received this bug notification because you are a member of Kernel
Packages, which is

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

--- Comment From cha...@us.ibm.com 2017-11-10 09:03 EDT---
(In reply to comment #11)
> IBM, Could you please test the kernel mentioned in comment #3 ?

Hi Manoj,

Test team is trying to find an available system to recreate with but it
may take a while as they have most of their machines tied up with
ongoing tests. We appreciate your patience.

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

Title:
  Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-30 09:44:23 ==
  Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress 
test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running 
few hours of regression test it dropped at xmon.

  Console logs :
  
  root@guskvm:~# virsh console gusg8 --force
  Connected to domain gusg8
  Escape character is ^]

  
  1:mon> r
  R00 = d288edf4   R16 = 024200ca
  R01 = c000378cb1f0   R17 = 
  R02 = d2936080   R18 = 0020
  R03 = 0001   R19 = c002734d1800
  R04 = c000378cb190   R20 = 
  R05 =    R21 = 
  R06 = 3c00d03fe056   R22 = c0027e26ccf0
  R07 =    R23 = 
  R08 = c48492d0   R24 = 
  R09 = 3c00d03fe056   R25 = 
  R10 = 3c00d03fe062   R26 = 00024df4cd49
  R11 = d28fa360   R27 = 
  R12 =    R28 = d28ac7b0
  R13 = cfb80900   R29 = c4849000
  R14 =    R30 = 
  R15 = c137ad08   R31 = 
  pc  = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs]
  cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440
  lr  = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs]
  msr = 80010280b033   cr  = 82428424
  ctr = c05e4950   xer = 2000   trap =  300
  dar = 3c00d03fe062   dsisr = 4000
  1:mon> t
  [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs]
  [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs]
  [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120
  [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0
  [c000378cb430] c0276db8 shrink_node+0x158/0x3f0
  [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460
  [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280
  [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30
  [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360
  [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0
  [c000378cb920] c02a0770 do_wp_page+0x210/0xb20
  [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0
  [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0
  [c000378cbb10] c0008948 handle_page_fault+0x10/0x30
  --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0
  [c000378cbe30] c0009844 ret_from_fork+0x4/0x54
  --- Exception: c00 (System Call) at 3fffa2b5bf44
  1:mon> d
      ||
  1:mon> c
  cpus stopped: 0x0-0x3
  1:mon>

  Kernel host build
  =
  root@guskvm:~# uname -r
  4.10.0-13-generic
  root@guskvm:~#

  
  == Comment: #1 - Luciano Chavez  - 2017-03-30 10:42:15 ==
  At first glance, based on the following assembly from around the failure 
point:

  d288edd4  38c1  li  r6,1
  d288edd8  7f8802a6  mflrr28
  d288eddc  78a70020  clrldi  r7,r5,32
  d288ede0  7c7d1b78  mr  r29,r3
  d288ede4  7c852378  mr  r5,r4
  d288ede8  386302c8  addir3,r3,712
  d288edec  38810020  addir4,r1,32
  d288edf0  4806b571  bl  d28fa360# 
exit_xfs_fs+0x180c/0xfd44 [xfs]
  d288edf4  e8410018  ld  r2,24(r1)
  d288edf8  2f83  cmpwi   cr7,r3,0
  d288edfc  409d0104  ble cr7,d288ef00# 
xfs_perag_get_tag+0x160/0x170 [xfs]
  d288ee00  7c0004ac  sync
  d288ee04  e9210020  ld  r9,32(r1)
  d288ee08  3949000c  addir10,r9,12
  d288ee0c  7fc05028  lwarx   r30,0,r10
  d288ee10  33de0001  addic   r30,r30,1
  d288ee14  7fc0512d  stwcx.  r30,0,r10

  I believe the crash in fs_perag_get_tag() is after we come back from
  the radix_tree_gang_lookup_tag() call and are attempting the
  atomic_inc_return() and struct xfs_perag*pag is R09 =
  3c00d03fe056

Re: [Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-11-10 Thread Marcos Alano

I entered on BIOS and set the option "Fastboot" to "through". I would
like people check what value is selected for this option and change to
check if error persists. Some people could help me on that?

On Fri, Nov 10, 2017 at 10:37 AM, Sasha Stadnik
<1521...@bugs.launchpad.net> wrote:
> I had the same problem on Linux Lubuntu 17.10 (4.13.0-16-generic)
> Asus X550VXK Intel i7, Nvidia Geforce GTX 950M
>
> First at all i had black screen, temporary added "nomodeset" to grub
> menu solved it.
>
> pci=noaer helped me to get rid of "PCIe Bus Error: severity=Corrected,
> type=Physical Layer"
>
> After that i had wifi problems (often loses connections etc), posts below 
> helped me to fix wifi
> https://forum.manjaro.org/t/wifi-fails-time-to-time-rtl8821ae/28914/9
> the same in 
> https://medium.com/@elmaxx/rtl8821ae-wifi-drivers-in-ubuntu-16-04-4c1286524afa
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1521173
>
> Title:
>   AER: Corrected error received: id=00e0
>
> Status in Linux:
>   Unknown
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux source package in Xenial:
>   Triaged
>
> Bug description:
>   Note: Current workaround is to add pci=noaer to your kernel command
>   line:
>
>   1) edit /etc/default/grub and and add pci=noaer to the line starting with 
> GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
>   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
>   2) run "sudo update-grub"
>   3) reboot
>
>   
>
>   My dmesg gets completely spammed with the following messages appearing
>   over and over again. It stops after one s3 cycle; it only happens
>   after reboot.
>
>   [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
>   [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
> type=Physical Layer, id=00e0(Receiver ID)
>   [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
> status/mask=0001/2000
>   [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
>   [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
> type=Physical Layer, id=00e0(Receiver ID)
>   [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
> status/mask=0001/2000
>   [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
>   [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
> type=Physical Layer, id=00e0(Receiver ID)
>   [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
> status/mask=0001/2000
>   [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
> boot/vmlinuz-4.2.0-19-generic]
>   ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
>   Uname: Linux 4.2.0-19-generic x86_64
>   ApportVersion: 2.19.2-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
>/dev/snd/controlC0:  david  1502 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Mon Nov 30 13:19:00 2015
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
>   InstallationDate: Installed on 2015-11-28 (2 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
>   MachineType: Dell Inc. Inspiron 13-7359
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
> root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
> splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.2.0-19-generic N/A
>linux-backports-modules-4.2.0-19-generic  N/A
>linux-firmware1.153
>   SourcePackage: linux
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/07/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.00.00
>   dmi.board.name: 0NT3WX
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: 
> dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 13-7359
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions


-- 
Marcos H. Alano
Linux System Administrator
marcoshal...@gmail.com

-- 
You

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  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
  
  backports: 1731270
  derivatives:
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 09. November 2017 15:01 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 10. November 2017 13:31 UTC

** Description changed:

  This bug is for tracking the  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
  
  backports: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 10. November 2017 13:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.10.0-40.44 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Confirmed
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 Zesty:
  Confirmed

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

  backports: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: 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/1731269/+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 1723449] Re: swapon: swapfile has holes

2017-11-10 Thread Cristian Aravena Romero

Hello,

https://btrfs.wiki.kernel.org/index.php/Project_ideas#Swap_file_support

Regards,
--
Cristian

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

Title:
  swapon: swapfile has holes

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  dmesg:
  [3.782191] swapon: swapfile has holes

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3697 F pulseaudio
   /dev/snd/pcmC1D0p:   caravena   3697 F...m pulseaudio
   /dev/snd/controlC1:  caravena   3697 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 13 11:41:46 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-37-generic 
root=UUID=ac00c389-d88f-4234-b2d9-12cc018f9f13 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  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/ubuntu/+source/linux/+bug/1723449/+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 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2017-11-10 Thread Alexander Kops

So I was just able to reproduce the shut-down issue with the kernel 
4.14.0-041400rc8-generic and the debugging flags enabled.
I submitted a kern.log to the upstream bug report.

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Triaged

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  PC temperatures are normal as per lm-sensors.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+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 1521173] Re: AER: Corrected error received: id=00e0

2017-11-10 Thread Sasha Stadnik

I had the same problem on Linux Lubuntu 17.10 (4.13.0-16-generic)
Asus X550VXK Intel i7, Nvidia Geforce GTX 950M

First at all i had black screen, temporary added "nomodeset" to grub
menu solved it.

pci=noaer helped me to get rid of "PCIe Bus Error: severity=Corrected,
type=Physical Layer"

After that i had wifi problems (often loses connections etc), posts below 
helped me to fix wifi
https://forum.manjaro.org/t/wifi-fails-time-to-time-rtl8821ae/28914/9
the same in 
https://medium.com/@elmaxx/rtl8821ae-wifi-drivers-in-ubuntu-16-04-4c1286524afa

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1521173/+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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => 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/1731264

Title:
  linux: 4.4.0-101.124 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

  backports: 1731266
  derivatives:
  kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+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 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

2017-11-10 Thread Konrad Zapałowicz

** Description changed:

  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.
  
  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.
  
+ [Impact]
+ 
+ Not possible to pair BLE remote devices such as sensors and such with
+ Ubuntu when the host system uses BT+WiFi combo SoC. The connection
+ attempt is disturbed with a timeout.
+ 
+ [Fix]
+ 
+ It has been fixed by increasing the timeout value from 2 seconds to
+ 4 seconds. It is enough for the events to reach the stack (measured
+ that it takes between 3 and 3.5 seconds).
+ 
+ [Testcase]
+ 
+ Tested with the device that failed to connect to Ubuntu Core gateway.
+ It fails w/o the patch, it connects just fine with the patch applied.
+ 
+ [Regression Potential]
+ 
+ Very small. The increased timeout is taken into consideration only for
+ new and scan report triggered connections. It will not make any already
+ working device to fail to pair.
+ 
+ [Other Info]
+ 
  The bug has been discussed and fixed here:
  
  https://marc.info/?l=linux-bluetooth=150824844606937=2
  
  [Patch]
  
  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571
  
- [Impact]
- 
- Fixing this bug will enable xenial based Ubuntu core devices such as
- gateways connect to various BLE sensors.
- 
- [Regression Potential]
- 
- Although the timeout has been increased the value is still very low
- (4 seconds) therefore should not have a negative impact. It is
- taken into consideration only during pairing and for connections that
- are triggered by the scan report.
- 
- [Other Info]
-  
  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+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 1731467] [NEW] Cannot pair BLE remote devices when using combo BT SoC

2017-11-10 Thread Konrad Zapałowicz

Public bug reported:

It has been observed that sometimes it is not possible to pair with
BLE remote devices when the host system is using combo (WiFi + BT)
chip.

The root cause of the disconnection has been identified as coming from
the internal to bluez timeout. If bluez does not hear any reply from for
two seconds the link is automagically disconnected. The reason fro the
silence is not however a failure of the remote device but quite often a
delay in the WiFi/BT combo driver that causes the packages not to reach
the bluez stack.

[Impact]

Not possible to pair BLE remote devices such as sensors and such with
Ubuntu when the host system uses BT+WiFi combo SoC. The connection
attempt is disturbed with a timeout.

[Fix]

It has been fixed by increasing the timeout value from 2 seconds to
4 seconds. It is enough for the events to reach the stack (measured
that it takes between 3 and 3.5 seconds).

[Testcase]

Tested with the device that failed to connect to Ubuntu Core gateway.
It fails w/o the patch, it connects just fine with the patch applied.

[Regression Potential]

Very small. The increased timeout is taken into consideration only for
new and scan report triggered connections. It will not make any already
working device to fail to pair.

[Other Info]

The bug has been discussed and fixed here:

https://marc.info/?l=linux-bluetooth=150824844606937=2

[Patch]

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

The patch has been accepted by the upstream and will be a part of the next
kernel release. Currently in the bluetooth-next tree.

** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Konrad Zapałowicz (kzapalowicz)
Status: In Progress

** Attachment added:
"0001-bluetooth-increase-timeout-for-le-auto-connections.patch"

https://bugs.launchpad.net/bugs/1731467/+attachment/5006899/+files/0001-bluetooth-increase-timeout-for-le-auto-connections.patch

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

** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

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

Title:
Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
In Progress

Bug description:
It has been observed that sometimes it is not possible to pair with
BLE remote devices when the host system is using combo (WiFi + BT)
chip.

[Impact]

Not possible to pair BLE remote devices such as sensors and such with
Ubuntu when the host system uses BT+WiFi combo SoC. The connection
attempt is disturbed with a timeout.

[Fix]

It has been fixed by increasing the timeout value from 2 seconds to
4 seconds. It is enough for the events to reach the stack (measured
that it takes between 3 and 3.5 seconds).

[Testcase]

Tested with the device that failed to connect to Ubuntu Core gateway.
It fails w/o the patch, it connects just fine with the patch applied.

[Regression Potential]

Very small. The increased timeout is taken into consideration only for
new and scan report triggered connections. It will not make any already
working device to fail to pair.

[Other Info]

The bug has been discussed and fixed here:

https://marc.info/?l=linux-bluetooth=150824844606937=2

[Patch]

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

The patch has been accepted by the upstream and will be a part of the next
kernel release. Currently in the bluetooth-next tree.

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

[Kernel-packages] [Bug 1730374] Re: NULL pointer dereference during writeback

2017-11-10 Thread Metta Crawler

Eventually I'll have time to test the upstream kernel.

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

Title:
  NULL pointer dereference during writeback

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened during dd of 40GB LV:

  $ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo

  I also used SIGUSR1 on the dd to monitor it occasionally.  There was
  other activity at the time as well.

  It appears that an attempt was made to fix this in 4.10
  https://patchwork.kernel.org/patch/9614353/
  but it is still happening in 4.13

  Nov 06 04:19:13 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
  Nov 06 04:19:13 lakshmi kernel: IP: 
locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:13 lakshmi kernel: PGD 0
  Nov 06 04:19:14 lakshmi kernel: P4D 0
  Nov 06 04:19:14 lakshmi kernel:
  Nov 06 04:19:14 lakshmi kernel: Oops:  [#1] SMP
  Nov 06 04:19:14 lakshmi kernel: Modules linked in: xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_
  Nov 06 04:19:14 lakshmi kernel:  async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 hid_g
  Nov 06 04:19:14 lakshmi kernel: CPU: 0 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
  Nov 06 04:19:14 lakshmi kernel: Hardware name: System manufacturer System 
Product Name/M4A89GTD-PRO/USB3, BIOS 302907/05/2012
  Nov 06 04:19:14 lakshmi kernel: task: 93db5adc8000 task.stack: 
b03b01d94000
  Nov 06 04:19:14 lakshmi kernel: RIP: 
0010:locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:14 lakshmi kernel: RSP: 0018:b03b01d97bc8 EFLAGS: 00010292
  Nov 06 04:19:14 lakshmi kernel: RAX:  RBX:  
RCX: 93d9758dfe28
  Nov 06 04:19:14 lakshmi kernel: RDX: 0001 RSI: 05080020 
RDI: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: RBP: b03b01d97bf0 R08:  
R09: 93d9cd655468
  Nov 06 04:19:14 lakshmi kernel: R10: 0228 R11:  
R12: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: R13: 93d9758deae0 R14:  
R15: 0059
  Nov 06 04:19:14 lakshmi kernel: FS:  () 
GS:93db77c0() knlGS:
  Nov 06 04:19:14 lakshmi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 06 04:19:14 lakshmi kernel: CR2:  CR3: 0001d7e08000 
CR4: 06f0
  Nov 06 04:19:14 lakshmi kernel: Call Trace:
  Nov 06 04:19:14 lakshmi kernel:  inode_io_list_del+0x23/0x50
  Nov 06 04:19:14 lakshmi kernel:  evict+0x55/0x1a0
  Nov 06 04:19:14 lakshmi kernel:  dispose_list+0x39/0x50
  Nov 06 04:19:14 lakshmi kernel:  prune_icache_sb+0x5a/0x80
  Nov 06 04:19:14 lakshmi kernel:  super_cache_scan+0x134/0x1b0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab.part.48+0x1d6/0x3d0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab+0x1b/0x30
  Nov 06 04:19:14 lakshmi kernel:  shrink_node+0x11e/0x300
  Nov 06 04:19:14 lakshmi kernel:  kswapd+0x2cc/0x750
  Nov 06 04:19:14 lakshmi kernel:  kthread+0x125/0x140
  Nov 06 04:19:14 lakshmi kernel:  ? mem_cgroup_shrink_node+0x180/0x180
  Nov 06 04:19:14 lakshmi kernel:  ? kthread_create_on_node+0x70/0x70
  Nov 06 04:19:14 lakshmi kernel:  ret_from_fork+0x25/0x30
  Nov 06 04:19:14 lakshmi kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 
e5 41 56 41 55 41 54 53 4c 8d af 88 00 00 00 49 89 fc
  Nov 06 04:19:14 lakshmi kernel: RIP: 
locked_inode_to_wb_and_lock_list+0x26/0x110 RSP: b03b01d97bc8
  Nov 06 04:19:14 lakshmi kernel: CR2: 
  Nov 06 04:19:14 lakshmi kernel: ---[ end trace 5aa11bcf674e53cc ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ksta   3322 F pulseaudio
   /dev/snd/controlC0:  ksta   3322 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 06:59:50 2017
  HibernationDevice: RESUME=/dev/mapper/vg1-swap
  InstallationDate: Installed on 2017-11-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:

  SourcePackage: linux

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

This change was made by a bot.

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

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

Title:
  amdgpu system sometimes takes an extremely long time to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this problem after I corrected the system clock from another
  OS (fixing the time on any of my OSs causes the others to display an
  incorrect time...). Ordinarily Ubuntu 16.04 starts in about 30 seconds
  on my system and displays the splash screen during early
  initialization. When the system clock is wrong, the splash screen is
  not displayed and the system takes about 5 minutes to start.

  Additionally, when the screen saver is on, it takes about 5 minutes
  from moving the mouse for the screens to turn on (there are two, if
  that matters)

  I think this is related to libdrm-amdgpu1 because dmesg gives me
  hundreds of messages looking like:

  [  308.832210] Failed to send Message.
  [  309.230389] Failed to send Previous Message.

  These messages originate from a drm source file:
  
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/powerplay/smumgr/tonga_smumgr.c
  (There's another amdgpu file with the same messages but my GPU is tonga 
architecture)

  I'm not entirely sure that the system clock is responsible but this
  seems to be an intermittent problem and I haven't noticed any other
  contributing factors.

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy libdrm-amdgpu1
  libdrm-amdgpu1:
    Installed: 2.4.67-1
    Candidate: 2.4.67-1
    Version table:
   *** 2.4.67-1 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdrm-amdgpu1 2.4.67-1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 12 11:33:56 2016
  Dependencies:
   gcc-6-base 6-20160405-0ubuntu2
   libc6 2.23-0ubuntu2
   libdrm2 2.4.67-1
   libgcc1 1:6-20160405-0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Tonga PRO [Radeon R9 285/380] 
[1458:229d]
  InstallationDate: Installed on 2016-03-21 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD5
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=b3ebe998-0b62-447a-9406-abf7f5e1f94c ro quiet splash vt.handoff=7
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: X58A-UD5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd02/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD5
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 12 11:21:51 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1028456] Re: unity_support_t: segfault error in libdrm_nouveau.so.1.0

kernel bug which probably is fixed by now, closing

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

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

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

Title:
  unity_support_t: segfault error in libdrm_nouveau.so.1.0

Status in linux package in Ubuntu:
  Invalid

Bug description:
  unity_support_t shows segfault in dmesg during login to unity-2d
  session:

  [ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on vga encoder (output 0)
  [ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on TV encoder (output 1)
  [ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Setting dpms mode 0 
on vga encoder (output 0)
  [ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Output VGA-1 is 
running on CRTC 0 using output A
  [ti heinä 24 16:56:29 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on TV encoder (output 1)
  [ti heinä 24 16:56:29 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on TV encoder (output 1)
  [ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on vga encoder (output 0)
  [ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on TV encoder (output 1)
  [ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 0 
on vga encoder (output 0)
  [ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Output VGA-1 is 
running on CRTC 0 using output A
  [ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 
on TV encoder (output 1)
  [ti heinä 24 16:56:41 2012] unity_support_t[15035]: segfault at 2c ip 
008395fe sp bf9ef590 error 4 in libdrm_nouveau.so.1.0.0[836000+5000]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
  Uname: Linux 3.2.0-27-generic-pae i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,grid,regex,vpswitch,commands,resize,place,mousepoll,thumbnail,session,animation,wall,wobbly,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  Date: Tue Jul 24 17:01:16 2012
  DistUpgraded: 2012-07-07 20:09:36,310 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. AGP-V7100 Pro [1043:4015]
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  MachineType: Hewlett-Packard HP Vectra
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae 
root=UUID=81d95253-df01-40c2-b006-3a74d4d4a245 ro nopat quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to precise on 2012-07-07 (16 days ago)
  dmi.bios.date: 07/19/2001
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JA.01.07US
  dmi.board.name: HP System Board
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: A06
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Version 1.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJA.01.07US:bd07/19/2001:svnHewlett-Packard:pnHPVectra:pvrVL420:rvnHewlett-Packard:rnHPSystemBoard:rvrA06:cvnHewlett-Packard:ct3:cvrVersion1.00:
  dmi.product.name: HP Vectra
  dmi.product.version: VL420
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
8.0.2-0ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1028456/+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 1499884] Re: [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue

enough idling, closing

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

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

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

Title:
  [drm] GPU HANG: ecode 6:-1:0x, reason: Kicking stuck semaphore
  on render ring, action: continue

Status in Nouveau Xorg driver:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  dmesg:
  [ 4917.268485] [drm] GPU HANG: ecode 6:-1:0x, reason: Kicking stuck 
semaphore on render ring, action: continue
  [ 4917.268489] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [ 4917.268491] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [ 4917.268493] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [ 4917.268494] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [ 4917.268496] [drm] GPU crash dump saved to /sys/class/drm/card0/error

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libdrm-intel1 2.4.64-1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Sep 25 17:41:24 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0d7]
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: libdrm
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  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.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Sep 25 11:03:07 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1499884/+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 1594011] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1594011

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

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

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

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

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

Title:
  Radeon GPU driver crashes while playing games

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This happens every time i play Team Fortress 2. Sometimes the game
  freezes completely and after 10-20 seconds it recovers itself. Looking
  at dmesg output seems like the GPU driver crashes and restarts. I'm
  using the open drivers with a Radeon R9 270.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdrm-radeon1 2.4.67-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 20:13:23 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libdrm2 2.4.67-1ubuntu0.16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-04-22 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594011/+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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

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

** Description changed:

  This bug is for tracking the  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
  
  backports: 1731266
  derivatives:
+ kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  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
  
  backports: 1731266
  derivatives:
  kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.4.0-101.124 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

  backports: 1731266
  derivatives:
  kernel-stable-phase-changed:Friday, 10. November 2017 11:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+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 1730374] Re: NULL pointer dereference during writeback

2017-11-10 Thread Metta Crawler

I'd love to have time to work on this kernel bug but I have fires all
over the place with 17.10.

I have a dual-boot setup between 16.04 and 17.10.  The 17.10 took over
nine minutes to boot originally. After finding out about
Debian_bug_867368 I got it to boot in over three minutes.  It still gets
stuck booting and shutting down in other areas.

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

Title:
  NULL pointer dereference during writeback

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened during dd of 40GB LV:

  $ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo

  I also used SIGUSR1 on the dd to monitor it occasionally.  There was
  other activity at the time as well.

  It appears that an attempt was made to fix this in 4.10
  https://patchwork.kernel.org/patch/9614353/
  but it is still happening in 4.13

  Nov 06 04:19:13 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
  Nov 06 04:19:13 lakshmi kernel: IP: 
locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:13 lakshmi kernel: PGD 0
  Nov 06 04:19:14 lakshmi kernel: P4D 0
  Nov 06 04:19:14 lakshmi kernel:
  Nov 06 04:19:14 lakshmi kernel: Oops:  [#1] SMP
  Nov 06 04:19:14 lakshmi kernel: Modules linked in: xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_
  Nov 06 04:19:14 lakshmi kernel:  async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 hid_g
  Nov 06 04:19:14 lakshmi kernel: CPU: 0 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
  Nov 06 04:19:14 lakshmi kernel: Hardware name: System manufacturer System 
Product Name/M4A89GTD-PRO/USB3, BIOS 302907/05/2012
  Nov 06 04:19:14 lakshmi kernel: task: 93db5adc8000 task.stack: 
b03b01d94000
  Nov 06 04:19:14 lakshmi kernel: RIP: 
0010:locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:14 lakshmi kernel: RSP: 0018:b03b01d97bc8 EFLAGS: 00010292
  Nov 06 04:19:14 lakshmi kernel: RAX:  RBX:  
RCX: 93d9758dfe28
  Nov 06 04:19:14 lakshmi kernel: RDX: 0001 RSI: 05080020 
RDI: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: RBP: b03b01d97bf0 R08:  
R09: 93d9cd655468
  Nov 06 04:19:14 lakshmi kernel: R10: 0228 R11:  
R12: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: R13: 93d9758deae0 R14:  
R15: 0059
  Nov 06 04:19:14 lakshmi kernel: FS:  () 
GS:93db77c0() knlGS:
  Nov 06 04:19:14 lakshmi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 06 04:19:14 lakshmi kernel: CR2:  CR3: 0001d7e08000 
CR4: 06f0
  Nov 06 04:19:14 lakshmi kernel: Call Trace:
  Nov 06 04:19:14 lakshmi kernel:  inode_io_list_del+0x23/0x50
  Nov 06 04:19:14 lakshmi kernel:  evict+0x55/0x1a0
  Nov 06 04:19:14 lakshmi kernel:  dispose_list+0x39/0x50
  Nov 06 04:19:14 lakshmi kernel:  prune_icache_sb+0x5a/0x80
  Nov 06 04:19:14 lakshmi kernel:  super_cache_scan+0x134/0x1b0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab.part.48+0x1d6/0x3d0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab+0x1b/0x30
  Nov 06 04:19:14 lakshmi kernel:  shrink_node+0x11e/0x300
  Nov 06 04:19:14 lakshmi kernel:  kswapd+0x2cc/0x750
  Nov 06 04:19:14 lakshmi kernel:  kthread+0x125/0x140
  Nov 06 04:19:14 lakshmi kernel:  ? mem_cgroup_shrink_node+0x180/0x180
  Nov 06 04:19:14 lakshmi kernel:  ? kthread_create_on_node+0x70/0x70
  Nov 06 04:19:14 lakshmi kernel:  ret_from_fork+0x25/0x30
  Nov 06 04:19:14 lakshmi kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 
e5 41 56 41 55 41 54 53 4c 8d af 88 00 00 00 49 89 fc
  Nov 06 04:19:14 lakshmi kernel: RIP: 
locked_inode_to_wb_and_lock_list+0x26/0x110 RSP: b03b01d97bc8
  Nov 06 04:19:14 lakshmi kernel: CR2: 
  Nov 06 04:19:14 lakshmi kernel: ---[ end trace 5aa11bcf674e53cc ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ksta   3322 F pulseaudio
   /dev/snd/controlC0:  ksta   3322 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 06:59:50 2017
  HibernationDevice: RESUME=/dev/mapper/vg1-swap
  InstallationDate: Installed on 2017-11-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb

[Kernel-packages] [Bug 1594011] Re: Radeon GPU driver crashes while playing games

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

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

Title:
  Radeon GPU driver crashes while playing games

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This happens every time i play Team Fortress 2. Sometimes the game
  freezes completely and after 10-20 seconds it recovers itself. Looking
  at dmesg output seems like the GPU driver crashes and restarts. I'm
  using the open drivers with a Radeon R9 270.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdrm-radeon1 2.4.67-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 20:13:23 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libdrm2 2.4.67-1ubuntu0.16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-04-22 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594011/+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 1569436] Re: amdgpu system sometimes takes an extremely long time to boot

the source is the kernel

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

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

Title:
  amdgpu system sometimes takes an extremely long time to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this problem after I corrected the system clock from another
  OS (fixing the time on any of my OSs causes the others to display an
  incorrect time...). Ordinarily Ubuntu 16.04 starts in about 30 seconds
  on my system and displays the splash screen during early
  initialization. When the system clock is wrong, the splash screen is
  not displayed and the system takes about 5 minutes to start.

  Additionally, when the screen saver is on, it takes about 5 minutes
  from moving the mouse for the screens to turn on (there are two, if
  that matters)

  I think this is related to libdrm-amdgpu1 because dmesg gives me
  hundreds of messages looking like:

  [  308.832210] Failed to send Message.
  [  309.230389] Failed to send Previous Message.

  These messages originate from a drm source file:
  
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/powerplay/smumgr/tonga_smumgr.c
  (There's another amdgpu file with the same messages but my GPU is tonga 
architecture)

  I'm not entirely sure that the system clock is responsible but this
  seems to be an intermittent problem and I haven't noticed any other
  contributing factors.

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy libdrm-amdgpu1
  libdrm-amdgpu1:
    Installed: 2.4.67-1
    Candidate: 2.4.67-1
    Version table:
   *** 2.4.67-1 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdrm-amdgpu1 2.4.67-1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 12 11:33:56 2016
  Dependencies:
   gcc-6-base 6-20160405-0ubuntu2
   libc6 2.23-0ubuntu2
   libdrm2 2.4.67-1
   libgcc1 1:6-20160405-0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Tonga PRO [Radeon R9 285/380] 
[1458:229d]
  InstallationDate: Installed on 2016-03-21 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD5
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=b3ebe998-0b62-447a-9406-abf7f5e1f94c ro quiet splash vt.handoff=7
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: X58A-UD5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd02/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD5
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 12 11:21:51 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1028456] [NEW] unity_support_t: segfault error in libdrm_nouveau.so.1.0

You have been subscribed to a public bug:

unity_support_t shows segfault in dmesg during login to unity-2d
session:

[ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
vga encoder (output 0)
[ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
TV encoder (output 1)
[ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Setting dpms mode 0 on 
vga encoder (output 0)
[ti heinä 24 16:56:28 2012] [drm] nouveau :01:00.0: Output VGA-1 is running 
on CRTC 0 using output A
[ti heinä 24 16:56:29 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
TV encoder (output 1)
[ti heinä 24 16:56:29 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
TV encoder (output 1)
[ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
vga encoder (output 0)
[ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
TV encoder (output 1)
[ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 0 on 
vga encoder (output 0)
[ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Output VGA-1 is running 
on CRTC 0 using output A
[ti heinä 24 16:56:31 2012] [drm] nouveau :01:00.0: Setting dpms mode 3 on 
TV encoder (output 1)
[ti heinä 24 16:56:41 2012] unity_support_t[15035]: segfault at 2c ip 008395fe 
sp bf9ef590 error 4 in libdrm_nouveau.so.1.0.0[836000+5000]

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
Uname: Linux 3.2.0-27-generic-pae i686
.tmp.unity.support.test.1:
 
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,grid,regex,vpswitch,commands,resize,place,mousepoll,thumbnail,session,animation,wall,wobbly,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell]
CompositorRunning: None
Date: Tue Jul 24 17:01:16 2012
DistUpgraded: 2012-07-07 20:09:36,310 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. AGP-V7100 Pro [1043:4015]
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: Hewlett-Packard HP Vectra
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae 
root=UUID=81d95253-df01-40c2-b006-3a74d4d4a245 ro nopat quiet splash 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to precise on 2012-07-07 (16 days ago)
dmi.bios.date: 07/19/2001
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: JA.01.07US
dmi.board.name: HP System Board
dmi.board.vendor: Hewlett-Packard
dmi.board.version: A06
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Version 1.00
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJA.01.07US:bd07/19/2001:svnHewlett-Packard:pnHPVectra:pvrVL420:rvnHewlett-Packard:rnHPSystemBoard:rvrA06:cvnHewlett-Packard:ct3:cvrVersion1.00:
dmi.product.name: HP Vectra
dmi.product.version: VL420
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
8.0.2-0ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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


** Tags: apport-bug i386 possible-manual-nvidia-install precise ubuntu
-- 
unity_support_t: segfault error in libdrm_nouveau.so.1.0
https://bugs.launchpad.net/bugs/1028456
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1499884] [NEW] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue

You have been subscribed to a public bug:

dmesg:
[ 4917.268485] [drm] GPU HANG: ecode 6:-1:0x, reason: Kicking stuck 
semaphore on render ring, action: continue
[ 4917.268489] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[ 4917.268491] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[ 4917.268493] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[ 4917.268494] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[ 4917.268496] [drm] GPU crash dump saved to /sys/class/drm/card0/error

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libdrm-intel1 2.4.64-1
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Sep 25 17:41:24 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0d7]
InstallationDate: Installed on 2015-07-26 (61 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: libdrm
UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev'
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.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Fri Sep 25 11:03:07 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu7

** Affects: nouveau
 Importance: Medium
 Status: Invalid

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


** Tags: amd64 apport-bug ubuntu wily
-- 
[drm] GPU HANG: ecode 6:-1:0x, reason: Kicking stuck semaphore on 
render ring, action: continue
https://bugs.launchpad.net/bugs/1499884
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

Re: [Kernel-packages] [Bug 1726159] Re: PCIe BUS Error causing really slow laptop performance

2017-11-10 Thread George Mathioudakis

I attached the output of ssd's hdparm results.

2017-11-10 11:17 GMT+02:00 Kai-Heng Feng :

> Can you attach the output of `hdparm -I /dev/sda`? Assume /dev/sda is
> the SSD.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1726159
>
> Title:
>   PCIe BUS Error causing really slow laptop performance
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I recently bought the following laptop:
>   Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)
>
>   It came pre-installed with Win10 and I did a fresh install of Ubuntu
>   16.04 LTS. The screen was flickering for some reason and installing
>   Ubuntu 17.04 fixed the issue.
>
>   The real problem is that when I'm booting the laptop, the following
>   error is being shown on my screen:
>
>   [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
>   [   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error
> received: id=00e5
>   [   12.898488] pcieport :00:1c.5: PCIe Bus Error:
> severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
>   [   12.898491] pcieport :00:1c.5:   device [8086:9d15] error
> status/mask=2041/2000
>   [   12.898492] pcieport :00:1c.5:[ 0] Receiver Error
>  (First)
>   [   12.898493] pcieport :00:1c.5:[ 6] Bad TLP
>
>   I know that this error can be hid with one of the following kernel boot
> arguments:
>   pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.
>
>   The weird thing is that the above output is only being shown when the
>   laptop is on AC Power (charging). When the laptop is not connected to
>   AC (battery-mode), it has performance issues (slow boot and slow
>   application launching). I was trying all day long to fix the problem.
>   I removed everything that had to do with power-saving, reinstalled,
>   re-tweaked for performance, tried different kernels but had no luck.
>   While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that
>   my laptop had. The results are:
>
>   * On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
>   * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)
>
>   This explains everyting. That's why I'm having a slow boot and slow
>   application launching!
>
>   Commands "lspci" and "dmesg" say that the error comes from the following
> device:
>   00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root
> Port #6 (rev f1)
>
>   I will attach lspci and dmesg output on a tar.gz file.
>
>   
> --
>   UPDATE: When the laptop is fully charged and still on AC (but not
> charging since it is 100% charged), the errors appear again but the SSD
> speed is normal (~500 Read/Write).
>   
> --
>   UPDATE: I installed 'tlp' Advanced Power Management package and when
> using the command 'tlp ac', the SSD speed gets back to normal! The option
> does not persist across reboots.
>   
> --
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: linux-image-4.10.0-37-generic 4.10.0-37.41
>   ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
>   Uname: Linux 4.10.0-37-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu4.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  georgem2557 F pulseaudio
>   CurrentDesktop: Unity:Unity7
>   Date: Sun Oct 22 23:17:57 2017
>   InstallationDate: Installed on 2017-10-20 (2 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 13d3:3496 IMC Networks
>Bus 001 Device 003: ID 13d3:5a01 IMC Networks
>Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. X542UQ
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed
> root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-37-generic N/A
>linux-backports-modules-4.10.0-37-generic  N/A
>linux-firmware 1.164.1
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/18/2017
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: X542UQ.202
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: X542UQ
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0

[Kernel-packages] [Bug 1661763] Re: screen turns off during standby, doesn't wake up on resume

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

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

Title:
  screen turns off during standby, doesn't wake up on resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  screen turns off during standby, doesn't wake up on resume

  had to reboot to recover

  Feb  2 22:51:59 ubuntu8 kernel: [318555.548546] [ cut here 
]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548650] WARNING: CPU: 3 PID: 14496 at 
/build/linux-RZGRu0/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:14328 
skl_max_scale.part.120+0x75/0x80 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548654] WARN_ON_ONCE(!crtc_clock || 
cdclk < crtc_clock)
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548657] Modules linked in: msr ccm 
rfcomm bnep hid_multitouch i2c_designware_platform i2c_designware_core hp_wmi 
sparse_keymap nls_iso8859_1 arc4 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp 
snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_dsp snd_hda_ext_core 
kvm_intel snd_soc_sst_match kvm iwlmvm snd_soc_core irqbypass crct10dif_pclmul 
snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
crc32_pclmul mac80211 snd_hda_core ghash_clmulni_intel snd_hwdep aesni_intel 
snd_pcm aes_x86_64 lrw snd_seq_midi glue_helper snd_seq_midi_event ablk_helper 
snd_rawmidi cryptd iwlwifi snd_seq snd_seq_device snd_timer input_leds cfg80211 
joydev serio_raw rtsx_pci_ms memstick snd soundcore uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 shpchp videobuf2_core videodev media mei_me 
idma64 mei virt_dma btusb btrtl intel_lpss_pci intel_pch_thermal 
processor_thermal_device intel_soc_dts_iosf ucsi int3403_thermal hci_uart btbcm 
btqca btintel bluetooth intel_lpss_acpi intel_lpss hp_accel lis3lv02d 
input_polldev int3402_thermal int3406_thermal int340x_thermal_zone tpm_crb 
mac_hid int3400_thermal acpi_thermal_rel acpi_pad dptf_power hp_wireless 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq 
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect 
nvme sysimgblt fb_sys_fops nvme_core drm ahci rtsx_pci libahci i2c_hid wmi hid 
video fjes
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548904] CPU: 3 PID: 14496 Comm: Xorg 
Not tainted 4.8.0-34-generic #36-Ubuntu
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548907] Hardware name: HP HP ENVY 
Notebook/81D1, BIOS F.28 10/05/2016
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548911]  0286 
8055b5e8 975531437930 8e430a22
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548924]  975531437980 
 975531437970 8e08319b
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548930]  37f88e1a9a80 
975412ad86c0 97555c5b3c00 9755660a6000
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548936] Call Trace:
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548948]  [] 
dump_stack+0x63/0x81
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548957]  [] 
__warn+0xcb/0xf0
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548965]  [] 
warn_slowpath_fmt+0x5f/0x80
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548998]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549068]  [] 
skl_max_scale.part.120+0x75/0x80 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549131]  [] 
intel_check_primary_plane+0xc6/0xe0 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549151]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549211]  [] 
intel_plane_atomic_check+0x132/0x1f0 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549230]  [] 
drm_atomic_helper_check_planes+0x84/0x200 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549292]  [] 
intel_atomic_check+0x155/0x760 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549339]  [] 
drm_atomic_check_only+0x187/0x610 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549377]  [] 
drm_atomic_commit+0x17/0x60 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549397]  [] 
drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549430]  [] 
__setplane_internal+0x17b/0x270 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549436]  [] ? 
unix_stream_read_generic+0x24f/0x920
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549467]  [] 
drm_mode_cursor_universal+0x139/0x240 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549498]  [] 
drm_mode_cursor_common+0x7e/0x180 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549530]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549555]  [] 
drm_ioctl+0x200/0x4f0 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549585]  [] ? 
drm_mode_setcrtc+0x580/0x580 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549592]  [] ?

[Kernel-packages] [Bug 1594011] [NEW] Radeon GPU driver crashes while playing games

You have been subscribed to a public bug:

This happens every time i play Team Fortress 2. Sometimes the game
freezes completely and after 10-20 seconds it recovers itself. Looking
at dmesg output seems like the GPU driver crashes and restarts. I'm
using the open drivers with a Radeon R9 270.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libdrm-radeon1 2.4.67-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 18 20:13:23 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libdrm2 2.4.67-1ubuntu0.16.04.1
 libgcc1 1:6.0.1-0ubuntu1
InstallationDate: Installed on 2016-04-22 (56 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: libdrm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug radeon xenial
-- 
Radeon GPU driver crashes while playing games
https://bugs.launchpad.net/bugs/1594011
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1569436] [NEW] amdgpu system sometimes takes an extremely long time to boot

You have been subscribed to a public bug:

I noticed this problem after I corrected the system clock from another
OS (fixing the time on any of my OSs causes the others to display an
incorrect time...). Ordinarily Ubuntu 16.04 starts in about 30 seconds
on my system and displays the splash screen during early initialization.
When the system clock is wrong, the splash screen is not displayed and
the system takes about 5 minutes to start.

Additionally, when the screen saver is on, it takes about 5 minutes from
moving the mouse for the screens to turn on (there are two, if that
matters)

I think this is related to libdrm-amdgpu1 because dmesg gives me
hundreds of messages looking like:

[  308.832210] Failed to send Message.
[  309.230389] Failed to send Previous Message.

These messages originate from a drm source file:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/powerplay/smumgr/tonga_smumgr.c
(There's another amdgpu file with the same messages but my GPU is tonga 
architecture)

I'm not entirely sure that the system clock is responsible but this
seems to be an intermittent problem and I haven't noticed any other
contributing factors.

$ lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

$ apt-cache policy libdrm-amdgpu1
libdrm-amdgpu1:
  Installed: 2.4.67-1
  Candidate: 2.4.67-1
  Version table:
 *** 2.4.67-1 500
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libdrm-amdgpu1 2.4.67-1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
BootLog:

CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 12 11:33:56 2016
Dependencies:
 gcc-6-base 6-20160405-0ubuntu2
 libc6 2.23-0ubuntu2
 libdrm2 2.4.67-1
 libgcc1 1:6-20160405-0ubuntu2
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Tonga PRO [Radeon R9 285/380] 
[1458:229d]
InstallationDate: Installed on 2016-03-21 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
MachineType: Gigabyte Technology Co., Ltd. X58A-UD5
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=b3ebe998-0b62-447a-9406-abf7f5e1f94c ro quiet splash vt.handoff=7
SourcePackage: libdrm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FD
dmi.board.name: X58A-UD5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd02/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: X58A-UD5
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Apr 12 11:21:51 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
amdgpu system sometimes takes an extremely long time to boot
https://bugs.launchpad.net/bugs/1569436
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1723986] Re: Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

2017-11-10 Thread Bin Li

After install the linux-image-extra, and removed the i2c_i801 from
blacklist, I found the touchpad and trackpoint work fine.

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

Title:
  Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Synaptics devices on Lenovo X1C6 and X280 can not work via PS/2 mode, it show:
  [   11.366996] psmouse serio1: synaptics: Touchpad model: 1, fw: 9.16, id: 
0x1e2a1, caps: 0xf001a3/0x940300/0x12e800/0x50, board id: 3382, fw id: 
2629663
  [   11.367002] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [   11.781876] psmouse serio2: Failed to reset mouse on synaptics-pt/serio0
  [   30.390508] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [   30.862260] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  Enable SMBus mode on these devices will make them work.

  Cherrypick 3 patches from patchwork as sauce patches on Ubuntu Artful
  kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723986/+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 1661763] [NEW] screen turns off during standby, doesn't wake up on resume

You have been subscribed to a public bug:

screen turns off during standby, doesn't wake up on resume

had to reboot to recover

Feb  2 22:51:59 ubuntu8 kernel: [318555.548546] [ cut here 
]
Feb  2 22:51:59 ubuntu8 kernel: [318555.548650] WARNING: CPU: 3 PID: 14496 at 
/build/linux-RZGRu0/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:14328 
skl_max_scale.part.120+0x75/0x80 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.548654] WARN_ON_ONCE(!crtc_clock || 
cdclk < crtc_clock)
Feb  2 22:51:59 ubuntu8 kernel: [318555.548657] Modules linked in: msr ccm 
rfcomm bnep hid_multitouch i2c_designware_platform i2c_designware_core hp_wmi 
sparse_keymap nls_iso8859_1 arc4 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp 
snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_dsp snd_hda_ext_core 
kvm_intel snd_soc_sst_match kvm iwlmvm snd_soc_core irqbypass crct10dif_pclmul 
snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
crc32_pclmul mac80211 snd_hda_core ghash_clmulni_intel snd_hwdep aesni_intel 
snd_pcm aes_x86_64 lrw snd_seq_midi glue_helper snd_seq_midi_event ablk_helper 
snd_rawmidi cryptd iwlwifi snd_seq snd_seq_device snd_timer input_leds cfg80211 
joydev serio_raw rtsx_pci_ms memstick snd soundcore uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 shpchp videobuf2_core videodev media mei_me 
idma64 mei virt_dma btusb btrtl intel_lpss_pci intel_pch_thermal 
processor_thermal_device intel_soc_dts_iosf ucsi int3403_thermal hci_uart btbcm 
btqca btintel bluetooth intel_lpss_acpi intel_lpss hp_accel lis3lv02d 
input_polldev int3402_thermal int3406_thermal int340x_thermal_zone tpm_crb 
mac_hid int3400_thermal acpi_thermal_rel acpi_pad dptf_power hp_wireless 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq 
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect 
nvme sysimgblt fb_sys_fops nvme_core drm ahci rtsx_pci libahci i2c_hid wmi hid 
video fjes
Feb  2 22:51:59 ubuntu8 kernel: [318555.548904] CPU: 3 PID: 14496 Comm: Xorg 
Not tainted 4.8.0-34-generic #36-Ubuntu
Feb  2 22:51:59 ubuntu8 kernel: [318555.548907] Hardware name: HP HP ENVY 
Notebook/81D1, BIOS F.28 10/05/2016
Feb  2 22:51:59 ubuntu8 kernel: [318555.548911]  0286 
8055b5e8 975531437930 8e430a22
Feb  2 22:51:59 ubuntu8 kernel: [318555.548924]  975531437980 
 975531437970 8e08319b
Feb  2 22:51:59 ubuntu8 kernel: [318555.548930]  37f88e1a9a80 
975412ad86c0 97555c5b3c00 9755660a6000
Feb  2 22:51:59 ubuntu8 kernel: [318555.548936] Call Trace:
Feb  2 22:51:59 ubuntu8 kernel: [318555.548948]  [] 
dump_stack+0x63/0x81
Feb  2 22:51:59 ubuntu8 kernel: [318555.548957]  [] 
__warn+0xcb/0xf0
Feb  2 22:51:59 ubuntu8 kernel: [318555.548965]  [] 
warn_slowpath_fmt+0x5f/0x80
Feb  2 22:51:59 ubuntu8 kernel: [318555.548998]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549068]  [] 
skl_max_scale.part.120+0x75/0x80 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549131]  [] 
intel_check_primary_plane+0xc6/0xe0 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549151]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549211]  [] 
intel_plane_atomic_check+0x132/0x1f0 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549230]  [] 
drm_atomic_helper_check_planes+0x84/0x200 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549292]  [] 
intel_atomic_check+0x155/0x760 [i915]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549339]  [] 
drm_atomic_check_only+0x187/0x610 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549377]  [] 
drm_atomic_commit+0x17/0x60 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549397]  [] 
drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549430]  [] 
__setplane_internal+0x17b/0x270 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549436]  [] ? 
unix_stream_read_generic+0x24f/0x920
Feb  2 22:51:59 ubuntu8 kernel: [318555.549467]  [] 
drm_mode_cursor_universal+0x139/0x240 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549498]  [] 
drm_mode_cursor_common+0x7e/0x180 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549530]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549555]  [] 
drm_ioctl+0x200/0x4f0 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549585]  [] ? 
drm_mode_setcrtc+0x580/0x580 [drm]
Feb  2 22:51:59 ubuntu8 kernel: [318555.549592]  [] ? 
timerqueue_add+0x59/0xb0
Feb  2 22:51:59 ubuntu8 kernel: [318555.549599]  [] ? 
enqueue_hrtimer+0x3d/0x80
Feb  2 22:51:59 ubuntu8 kernel: [318555.549606]  [] ? 
hrtimer_start_range_ns+0x1c0/0x3d0
Feb  2 22:51:59 ubuntu8 kernel: [318555.549612]  [] 
do_vfs_ioctl+0xa3/0x610
Feb  2 22:51:59 ubuntu8 kernel: [318555.549617]  [] ? 
__sys_recvmsg+0x51/0x90
Feb  2 22:51:59 ubuntu8 kernel:

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

2017-11-10 Thread Frank Heimes

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

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  This bug is fixed by mainline commit ba385c0594, which is in mainline
  as of v4.14-rc2.  It was also cc'd to upstream stable.  It has already
  been accepted in upstream v4.13.y, so Artful and Bionic have the fix
  via the 4.13.5 stable updates.

  == Fix ==
  commit ba385c0594e723d41790ecfb12c610e6f90c7785
  Author: Gerald Schaefer 
  Date:   Mon Sep 18 16:51:51 2017 +0200

  s390/mm: fix write access check in gup_huge_pmd()

  
  == Regression Potential ==
  This patch is specific to s390.  It has also been accepted by upstream 
stable, so additional upstream review has been done.


  
  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
    gup_huge_pmd() is the wrong way around. It must not be set
    for write==1, and not be checked for write==0. Allowing
    write==1 with protection bit set, instead of breaking out
    to the slow path, will result in a missing faultin_page()
    to clear the protection bit (for valid writable mappings),
    and the async I/O write operation will fail to write to
    such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
    also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
    hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+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 1724796] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  Picture is heavily malformed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On boot screen with disk decrypt password and gdm are heavily deformed
  (check attachment). After login wayland session is also deformed, then
  if I logout and login to Xorg, picture is fine. After that if I logout
  and login back to Wayland session picture is also fine.

  GDM -> https://imgur.com/a/MhHbd
  Disk decrypt -> https://imgur.com/a/UP0rL

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 12:29:31 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (54 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724796/+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 1724796] Re: Picture is heavily malformed

has little to do with libdrm

and if you use external ppa's there's no support

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

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

Title:
  Picture is heavily malformed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On boot screen with disk decrypt password and gdm are heavily deformed
  (check attachment). After login wayland session is also deformed, then
  if I logout and login to Xorg, picture is fine. After that if I logout
  and login back to Wayland session picture is also fine.

  GDM -> https://imgur.com/a/MhHbd
  Disk decrypt -> https://imgur.com/a/UP0rL

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 12:29:31 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (54 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724796/+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 1724796] [NEW] Picture is heavily malformed

You have been subscribed to a public bug:

On boot screen with disk decrypt password and gdm are heavily deformed
(check attachment). After login wayland session is also deformed, then
if I logout and login to Xorg, picture is fine. After that if I logout
and login back to Wayland session picture is also fine.

GDM -> https://imgur.com/a/MhHbd
Disk decrypt -> https://imgur.com/a/UP0rL

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 12:29:31 2017
DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
InstallationDate: Installed on 2017-08-25 (54 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-AR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful corruption third-party-packages ubuntu 
wayland-session
-- 
Picture is heavily malformed
https://bugs.launchpad.net/bugs/1724796
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

2017-11-10 Thread Colin Ian King

Thanks for taking the time and effort for verifying this, much
appreciated!

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

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

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

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718388/+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 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

2017-11-10 Thread Thadeu Lima de Souza Cascardo

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

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  This bug is fixed by mainline commit ba385c0594, which is in mainline
  as of v4.14-rc2.  It was also cc'd to upstream stable.  It has already
  been accepted in upstream v4.13.y, so Artful and Bionic have the fix
  via the 4.13.5 stable updates.

  == Fix ==
  commit ba385c0594e723d41790ecfb12c610e6f90c7785
  Author: Gerald Schaefer 
  Date:   Mon Sep 18 16:51:51 2017 +0200

  s390/mm: fix write access check in gup_huge_pmd()

  
  == Regression Potential ==
  This patch is specific to s390.  It has also been accepted by upstream 
stable, so additional upstream review has been done.


  
  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
    gup_huge_pmd() is the wrong way around. It must not be set
    for write==1, and not be checked for write==0. Allowing
    write==1 with protection bit set, instead of breaking out
    to the slow path, will result in a missing faultin_page()
    to clear the protection bit (for valid writable mappings),
    and the async I/O write operation will fail to write to
    such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
    also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
    hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+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 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

2017-11-10 Thread Jesse Sung

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

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

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

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

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718388/+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 1729280] Re: linux-aws: 4.4.0-1040.49 -proposed tracker

2017-11-10 Thread Kleber Sacilotto de Souza

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-aws: 4.4.0-1040.49 -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 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:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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
  kernel-stable-master-bug: 1731264
  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/1729280/+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 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

2017-11-10 Thread Thadeu Lima de Souza Cascardo

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Thadeu Lima de Souza Cascardo 
(cascardo)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Thadeu Lima de Souza Cascardo 
(cascardo)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Khaled El Mously (kmously) => Thadeu Lima de Souza Cascardo 
(cascardo)

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

Title:
  linux: 4.4.0-101.124 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

  backports: 1731266
  derivatives:

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1731264/+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 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

2017-11-10 Thread gerald.yang

Verified linux-image-4.4.0-100-generic on AS7712, it works find,
all broadcom modules are loaded and bcm0 interface is created successfully.

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

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

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

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718388/+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 1731455] [NEW] generic/166 test for btrfs from xfstests will hang

2017-11-10 Thread Po-Hsu Lin

Public bug reported:

>From the log you will see it stuck after generic/165 for the btrfs filesystem:
08:40:48 DEBUG| [stdout] generic/163 16s
08:41:01 DEBUG| [stdout] generic/164 12s
08:41:15 DEBUG| [stdout] generic/165 14s

And it will be killed by the time-out setting.
This issue can be spotted across different kernel, and it looks like a test 
case issue.

Possible fix could be found in upstream repo:
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/tests/generic/166?id=132f37916d2c5f64b857ecaf2072ce7891c5f5ba

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20~16.04.1
ProcVersionSignature: User Name 4.13.0-17.20~16.04.1-lowlatency 4.13.8
Uname: Linux 4.13.0-17-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Nov 10 10:11:21 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-hwe-edge
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed uec-images xenial

** Changed in: linux-hwe-edge (Ubuntu)
   Status: New => Triaged

** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu)

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

Title:
  generic/166 test for btrfs from xfstests will hang

Status in linux package in Ubuntu:
  Triaged

Bug description:
  From the log you will see it stuck after generic/165 for the btrfs filesystem:
  08:40:48 DEBUG| [stdout] generic/163   16s
  08:41:01 DEBUG| [stdout] generic/164   12s
  08:41:15 DEBUG| [stdout] generic/165   14s

  And it will be killed by the time-out setting.
  This issue can be spotted across different kernel, and it looks like a test 
case issue.

  Possible fix could be found in upstream repo:
  
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/tests/generic/166?id=132f37916d2c5f64b857ecaf2072ce7891c5f5ba

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20~16.04.1
  ProcVersionSignature: User Name 4.13.0-17.20~16.04.1-lowlatency 4.13.8
  Uname: Linux 4.13.0-17-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov 10 10:11:21 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731455/+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 1731455] [NEW] generic/166 test for btrfs from xfstests will hang

You have been subscribed to a public bug:

>From the log you will see it stuck after generic/165 for the btrfs filesystem:
08:40:48 DEBUG| [stdout] generic/163 16s
08:41:01 DEBUG| [stdout] generic/164 12s
08:41:15 DEBUG| [stdout] generic/165 14s

And it will be killed by the time-out setting.
This issue can be spotted across different kernel, and it looks like a test 
case issue.

Possible fix could be found in upstream repo:
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/tests/generic/166?id=132f37916d2c5f64b857ecaf2072ce7891c5f5ba

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20~16.04.1
ProcVersionSignature: User Name 4.13.0-17.20~16.04.1-lowlatency 4.13.8
Uname: Linux 4.13.0-17-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Nov 10 10:11:21 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-hwe-edge
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed uec-images xenial
-- 
generic/166 test for btrfs from xfstests will hang
https://bugs.launchpad.net/bugs/1731455
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1730415] Re: Display goes to sleep watching video

2017-11-10 Thread Dario Figliuzzi

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

Title:
  Display goes to sleep watching video

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The display goes to sleep watching movie on YouTube, Streaming sites and VLC 
(not only on full screen). In the older Ubuntu release, this problem did not 
exist.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dario  1319 F pulseaudio
   /dev/snd/controlC1:  dario  1319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d6737712-48f0-4337-8624-456a2586f119
  InstallationDate: Installed on 2017-10-20 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. X555LD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=97cdb369-b2d0-4b93-8f9d-7372fb001259 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LD.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LD.402:bd10/29/2015:svnASUSTeKCOMPUTERINC.:pnX555LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

--- Comment From heinz-werner_se...@de.ibm.com 2017-11-10 05:00 EDT---
As mentioned within a previous comment, this is a preventiv fix, which should 
be applied to Ubuntu 16.04 and newer. Fix is already upstream with kernel 4.14 
rc2 and should be applied to the distros in the field..

--- Comment From heinz-werner_se...@de.ibm.com 2017-11-10 05:06 EDT---
Addl information:"in reply to comment #2 yes, tested that the patch fixes the 
issue"

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  This bug is fixed by mainline commit ba385c0594, which is in mainline
  as of v4.14-rc2.  It was also cc'd to upstream stable.  It has already
  been accepted in upstream v4.13.y, so Artful and Bionic have the fix
  via the 4.13.5 stable updates.

  == Fix ==
  commit ba385c0594e723d41790ecfb12c610e6f90c7785
  Author: Gerald Schaefer 
  Date:   Mon Sep 18 16:51:51 2017 +0200

  s390/mm: fix write access check in gup_huge_pmd()

  
  == Regression Potential ==
  This patch is specific to s390.  It has also been accepted by upstream 
stable, so additional upstream review has been done.


  
  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
    gup_huge_pmd() is the wrong way around. It must not be set
    for write==1, and not be checked for write==0. Allowing
    write==1 with protection bit set, instead of breaking out
    to the slow path, will result in a missing faultin_page()
    to clear the protection bit (for valid writable mappings),
    and the async I/O write operation will fail to write to
    such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
    also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
    hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+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 1723986] Re: Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

2017-11-10 Thread Bin Li

@Aaron,

 After reboot I found the touchpad couldn't work, a little weird, and I
removed i2c_801, but the i2c_i801 was not loaded, I tried to install it
by manual, found that this module is not exist.

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

Title:
  Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Synaptics devices on Lenovo X1C6 and X280 can not work via PS/2 mode, it show:
  [   11.366996] psmouse serio1: synaptics: Touchpad model: 1, fw: 9.16, id: 
0x1e2a1, caps: 0xf001a3/0x940300/0x12e800/0x50, board id: 3382, fw id: 
2629663
  [   11.367002] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [   11.781876] psmouse serio2: Failed to reset mouse on synaptics-pt/serio0
  [   30.390508] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [   30.862260] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  Enable SMBus mode on these devices will make them work.

  Cherrypick 3 patches from patchwork as sauce patches on Ubuntu Artful
  kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723986/+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 1726159] Re: PCIe BUS Error causing really slow laptop performance

Can you attach the output of `hdparm -I /dev/sda`? Assume /dev/sda is
the SSD.

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

Title:
  PCIe BUS Error causing really slow laptop performance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought the following laptop:
  Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB)

  It came pre-installed with Win10 and I did a fresh install of Ubuntu
  16.04 LTS. The screen was flickering for some reason and installing
  Ubuntu 17.04 fixed the issue.

  The real problem is that when I'm booting the laptop, the following
  error is being shown on my screen:

  [   12.866073] pcieport :00:1c.5: can't find device of ID00e5
  [   12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
  [   12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  [   12.898491] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=2041/2000
  [   12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First)
  [   12.898493] pcieport :00:1c.5:[ 6] Bad TLP

  I know that this error can be hid with one of the following kernel boot 
arguments:
  pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf.

  The weird thing is that the above output is only being shown when the
  laptop is on AC Power (charging). When the laptop is not connected to
  AC (battery-mode), it has performance issues (slow boot and slow
  application launching). I was trying all day long to fix the problem.
  I removed everything that had to do with power-saving, reinstalled,
  re-tweaked for performance, tried different kernels but had no luck.
  While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that
  my laptop had. The results are:

  * On AC Power: 522MB/s (READ) | 416MB/s (WRITE)
  * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE)

  This explains everyting. That's why I'm having a slow boot and slow
  application launching!

  Commands "lspci" and "dmesg" say that the error comes from the following 
device:
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)

  I will attach lspci and dmesg output on a tar.gz file.

  --
  UPDATE: When the laptop is fully charged and still on AC (but not charging 
since it is 100% charged), the errors appear again but the SSD speed is normal 
(~500 Read/Write).
  --
  UPDATE: I installed 'tlp' Advanced Power Management package and when using 
the command 'tlp ac', the SSD speed gets back to normal! The option does not 
persist across reboots.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  georgem2557 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Oct 22 23:17:57 2017
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X542UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X542UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

2017-11-10 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.10.0-40.44 -proposed tracker

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

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

  backports: 1731270
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 09. November 2017 15:01 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

2017-11-10 Thread Łukasz Zemczak

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.10.0-40.44 -proposed tracker

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

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

  backports: 1731270
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 09. November 2017 15:01 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

Re: [Kernel-packages] [Bug 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU