[Kernel-packages] [Bug 1791015] [NEW] Problems with touchpad

[Ruben]

Public bug reported:

Version: Ubuntu 18.04.1 LTS

Laptop: Satellite R630

The Touchpad doesnt work

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ruben  1166 F pulseaudio
Date: Thu Sep  6 09:02:15 2018
InstallationDate: Installed on 2018-08-12 (24 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: TOSHIBA Satellite R630
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=79f7d43d-b31f-44aa-9f51-ddb542e69e1b ro quiet splash vt.handoff=1
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.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/20/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.40
dmi.board.asset.tag: 00
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.40:bd07/20/2010:svnTOSHIBA:pnSatelliteR630:pvrPT31LE-00P00HGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.family: 00
dmi.product.name: Satellite R630
dmi.product.version: PT31LE-00P00HGR
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug bionic

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

Title:
  Problems with touchpad

Status in linux package in Ubuntu:
  New

Bug description:
  Version: Ubuntu 18.04.1 LTS

  Laptop: Satellite R630

  The Touchpad doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruben  1166 F pulseaudio
  Date: Thu Sep  6 09:02:15 2018
  InstallationDate: Installed on 2018-08-12 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite R630
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=79f7d43d-b31f-44aa-9f51-ddb542e69e1b ro quiet splash vt.handoff=1
  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.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.40
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.40:bd07/20/2010:svnTOSHIBA:pnSatelliteR630:pvrPT31LE-00P00HGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: Satellite R630
  dmi.product.version: PT31LE-00P00HGR
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1788766] Re: linux: 4.4.0-135.161 -proposed tracker

[Po-Hsu Lin]

4.4.0-135.161 - lowlatency
Regression test CMPL, RTB.

Test case ubuntu_ramfs_stress does not exist in the database, please check
42 / 49 tests were run, missing: ubuntu_bpf_jit, ubuntu_cts_kernel, 
ubuntu_cve_kernel, ubuntu_ecryptfs, ubuntu_ltp_syscalls, ubuntu_zfs_fstest, 
ubuntu_zfs_xfs_generic, xfstests
Issue to note in amd64:
  ubuntu_kvm_unit_tests - 18 failed on harpo
  ubuntu_lxc - network issue, failed to fetch GPG key

4.4.0-135.161 - generic
Regression test CMPL, RTB.

48 / 49 tests were run, missing: ubuntu_vfat_stress
Issue to note in amd64:
  ubuntu_kvm_unit_tests - 28 failed on amaura, 20 failed on michael, 28 failed 
on pepe
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)
  xfstests - xfs generic/476 timed out

43 / 44 tests were run, missing: xfstests
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_cts_kernel - tool issue (bug 1789566)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)
  xfstests - xfs/438 timed out

Issue to note in i386:
  ubuntu_cts_kernel - tool issue (bug 1789566)
  ubuntu_kvm_unit_tests - 25 failed on pepe
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)
  xfstests - xfs generic/308 timed out, bug 1738152

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)

Issue to note in s390x (zKVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - 12 failed
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)

Issue to note in s390x (zVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_ecryptfs - passed after re-test
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)

Note: missing ppc64le test results, testing node broken.
Note: ubuntu_vfat_stress manually tested and passed on generic kernel
Note: xfstests on arm64 will fail to generate report
Note: missing test cases in lowlatency kernel need to be investigated (bug 
1791016)

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.4.0-135.161 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security se

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Steve Langasek]

Hello Alberto, or anyone else affected,

Accepted nvidia-prime into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.8.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nvidia-prime (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  
  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  
  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

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

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Steve Langasek]

Hello Alberto, or anyone else affected,

Accepted nvidia-settings into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/390.77-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nvidia-settings (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  
  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  
  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

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

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

[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)

[Kleber Sacilotto de Souza]

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

Title:
  Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
  state disabled (performance)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-09-04
  00:50:14 ==

  The CPUs remain in snooze state on an idle system when only the
  shallow states disabled resulting in increased power consumption.

  The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of  snooze 
to deeper idle state") introduced a timeout for the snooze idle state so that 
it could be eventually be promoted to a deeper idlestate. The snooze 
timeout value is static and set to the target  residency of the next idle 
state, which would train the cpuidle governor to pick the next idle state 
eventually.
  
  The unfortunate side-effect of this is that if the next idle state(s)  is 
disabled, the CPU will forever remain in snooze, despite the fact that the 
system is completely idle, and other deeper idle states are available.
  
  This patch fixes the issue by dynamically setting the snooze timeout  to the 
target residency of the next enabled state on the device.
  
  Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | Nap  | Fast
   0|   8|   0| 96.41|  0.00|  0.00
   0|   8|   1| 96.43|  0.00|  0.00
   0|   8|   2| 96.47|  0.00|  0.00
   0|   8|   3| 96.35|  0.00|  0.00
   0|   8|   4| 96.37|  0.00|  0.00
   0|   8|   5| 96.37|  0.00|  0.00
   0|   8|   6| 96.47|  0.00|  0.00
   0|   8|   7| 96.47|  0.00|  0.00
  
  POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2) 
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | 
stop
   0|  16|   0| 89.79|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   1| 90.12|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   2| 90.21|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   3| 90.29|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
  


  After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | Nap  | Fast
   0|   8|   0| 16.58|  0.00| 77.21
   0|   8|   1| 18.42|  0.00| 75.38
   0|   8|   2|  4.70|  0.00| 94.09
   0|   8|   3| 17.06|  0.00| 81.73
   0|   8|   4|  3.06|  0.00| 95.73
   0|   8|   5|  7.00|  0.00| 96.80
   0|   8|   6|  1.00|  0.00| 98.79
   0|   8|   7|  5.62|  0.00| 94.17
  
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,  
stop2) disabled:
  
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | 
stop
   0|   0|   0|  0.69|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  9.39| 
89.70
   0|   0|   1|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05| 
93.21
   0|   0|   2|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
89.93
   0|   0|   3|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
93.26

  
  This fix  (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze 
if next state disabled") is in the -next branch of the powerpc tree and 
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions

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

[Kernel-packages] [Bug 1766176] Re: initramfs-tools returns error while installing the proposed Bionic kernel

[Po-Hsu Lin]

Can't reproduce this on Bionic ARM64 ThunderX server.
Will need to verify with the s390x next.

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

Title:
  initramfs-tools returns error while installing the proposed Bionic
  kernel

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

Bug description:
  This issue was spotted on a ThunderX ARM64 system and s390x, AMD64
  system does not have this issue

  Steps:
1. Deploy a ThunderX ARM64 node
2. Enable -proposed, commence apt update and dist-upgrade

  Result:
  Setting up linux-generic (4.15.0.19.20) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-15-generic
  W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
  Ignoring old or unknown version 4.15.0-15-generic (latest is 
4.15.0-19-generic)
  Use --force if you want version 4.15.0-15-generic.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
2
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
  flash-kernel: deferring update (trigger activated)
  /etc/kernel/postinst.d/zz-flash-kernel:
  flash-kernel: deferring update (trigger activated)
  /etc/kernel/postinst.d/zz-update-grub:
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.15.0-19-generic
  Found initrd image: /boot/initrd.img-4.15.0-19-generic
  Found linux image: /boot/vmlinuz-4.15.0-15-generic
  Found initrd image: /boot/initrd.img-4.15.0-15-generic
  Adding boot menu entry for EFI firmware configuration
  done
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ubuntu@starmie-kernel:~$ 

  
  For error on s390x:
  Setting up linux-modules-extra-4.15.0-19-generic (4.15.0-19.20) ...
  Setting up linux-image-generic (4.15.0.19.20) ...
  Setting up linux-headers-generic (4.15.0.19.20) ...
  Setting up linux-generic (4.15.0.19.20) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-17-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (0200).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (0200).
  Done.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: User Name 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 23 04:36 seq
   crw-rw 1 root audio 116, 33 Apr 23 04:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Apr 23 06:00:17 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c8

[Kernel-packages] [Bug 1791030] [NEW] package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for configuration ca

[Eric Cosnard]

Public bug reported:

bug during update (???)
Cordially

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-131-generic 4.4.0-131.157
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eric   6073 F pulseaudio
 /dev/snd/seq:timidity   1500 F timidity
Date: Thu Sep  6 09:48:42 2018
ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
HibernationDevice: RESUME=UUID=2fd83354-6537-4d4a-9080-0fd25e636274
InstallationDate: Installed on 2012-07-21 (2237 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic 
root=UUID=e2cf79c0-5225-4f68-9c25-bde3c11e9747 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: grub-pc 2.02~beta2-36ubuntu3.18
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to 
install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0301
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO GEN3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd09/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package 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/1791030

Title:
  package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to
  install/upgrade: package linux-image-extra-4.4.0-131-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux package in Ubuntu:
  New

Bug description:
  bug during update (???)
  Cordially

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-131-generic 4.4.0-131.157
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   6073 F pulseaudio
   /dev/snd/seq:timidity   1500 F timidity
  Date: Thu Sep  6 09:48:42 2018
  ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=2fd83354-6537-4d4a-9080-0fd25e636274
  InstallationDate: Installed on 2012-07-21 (2237 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic 
root=UUID=e2cf79c0-5225-4f68-9c25-bde3c11e9747 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: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to 
install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.mod

[Kernel-packages] [Bug 1788769] Re: linux-aws: 4.4.0-1067.77 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux-aws: 4.4.0-1067.77 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
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:
  New

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: 1788766
  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/1788769/+subscriptions

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

[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Bionic)
   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/1790636

Title:
  Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 ==

  Problem:
  ---
  Kernel panics and Hardlockup messages when kernel crash was triggered to test 
kdump.
   
  There are two patches for a problem during a kernel crash:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff

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

  Only the first was marked for stable (and is currently present in
  18.04.1), but both should really be included to fix the problems in
  the commit log.  Can you include the second one, too?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions

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

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

[Ubuntu Kernel Bot]

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

Title:
  Problems with touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04.1 LTS

  Laptop: Satellite R630

  The Touchpad doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruben  1166 F pulseaudio
  Date: Thu Sep  6 09:02:15 2018
  InstallationDate: Installed on 2018-08-12 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite R630
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=79f7d43d-b31f-44aa-9f51-ddb542e69e1b ro quiet splash vt.handoff=1
  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.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.40
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.40:bd07/20/2010:svnTOSHIBA:pnSatelliteR630:pvrPT31LE-00P00HGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: Satellite R630
  dmi.product.version: PT31LE-00P00HGR
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[ Christian Ehrhardt ]

Reproduced:
2018-09-06T08:25:22.816912Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x8101 inconsistent with Host index 0xfd: delta 0x8004
2018-09-06T08:25:22.816963Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
2018-09-06T08:25:22.817478Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

I need to break this out of the test automation and then in the Bionic
guest set up different kernels to find which mismatch it is.

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

Title:
  KVM live migration fails

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

Bug description:
  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions

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

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

[Ubuntu Kernel Bot]

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

Title:
  package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to
  install/upgrade: package linux-image-extra-4.4.0-131-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bug during update (???)
  Cordially

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-131-generic 4.4.0-131.157
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   6073 F pulseaudio
   /dev/snd/seq:timidity   1500 F timidity
  Date: Thu Sep  6 09:48:42 2018
  ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=2fd83354-6537-4d4a-9080-0fd25e636274
  InstallationDate: Installed on 2012-07-21 (2237 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic 
root=UUID=e2cf79c0-5225-4f68-9c25-bde3c11e9747 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: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to 
install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd09/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1783922] Re: ubuntu_qrt_apparmor will hang with Bionic kernel on KVM / Azure instance (mmap test timeout)

[Po-Hsu Lin]

In this cycle, issue spotted on the following Azure nodes with 4.15 kernel:
* Standard_B4ms
* Standard_D4_v3
* Standard_DS1
* Standard_DS12_v2
* Standard_DS13
* Standard_DS13_v2
* Standard_DS14_v2
* Standard_E32-8s_v3
* Standard_GS5-8

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

Title:
  ubuntu_qrt_apparmor will hang with Bionic kernel on KVM / Azure
  instance (mmap test timeout)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This test will timeout on a KVM instance (1G ram) with Bionic kernel.

  This is the last test executed on this system:
  Jul 26 10:10:54 zeppo kernel: [ 2140.591600] audit: type=1400 
audit(1532599854.772:275036): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/tmp/testlibJOdhfr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap"
 pid=24072 comm="apparmor_parser"

    Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok
    test_regression_testsuite (__main__.ApparmorTestsuites)
   preparing apparmor_2.12-4ubuntu5.dsc...  done
    Timer expired (10800 sec.), nuking pid 20299

  $ watch free -m
  totalusedfree  shared  buff/cache   available
  Mem:985 445  72   0 467 
355
  Swap:  1443   71436

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 26 09:35 seq
   crw-rw 1 root audio 116, 33 Jul 26 09:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Jul 27 02:28:52 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1783922/+subscriptions

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

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[ Christian Ehrhardt ]

I can also confirm that driving the same case on x86 is not affected.

I'd be glad to pull in PPC-Developers in case they know of any virtio
bugfix that was done in qemu and/or kernel that might be related.

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

Title:
  KVM live migration fails

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

Bug description:
  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions

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

[Kernel-packages] [Bug 1791030] Re: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for configuration cann

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to
  install/upgrade: package linux-image-extra-4.4.0-131-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bug during update (???)
  Cordially

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-131-generic 4.4.0-131.157
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   6073 F pulseaudio
   /dev/snd/seq:timidity   1500 F timidity
  Date: Thu Sep  6 09:48:42 2018
  ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=2fd83354-6537-4d4a-9080-0fd25e636274
  InstallationDate: Installed on 2012-07-21 (2237 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic 
root=UUID=e2cf79c0-5225-4f68-9c25-bde3c11e9747 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: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to 
install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd09/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

[James Buren]

Issue resolved by BIOS update.

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

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

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1790884] Re: Xenial update to 4.4.143 stable release

[Stefan Bader]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.143 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.143 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.143 stable release shall be
- applied:
+ The following patches from the 4.4.143 stable release shall be applied:
+ * compiler, clang: suppress warning for unused static inline functions
+ * compiler, clang: properly override 'inline' for clang
+ * compiler, clang: always inline when CONFIG_OPTIMIZE_INLINING is disabled
+ * compiler-gcc.h: Add __attribute__((gnu_inline)) to all inline declarations
+ * x86/asm: Add _ASM_ARG* constants for argument registers to 
+ * ocfs2: subsystem.su_mutex is required while accessing the item->ci_parent
+ * bcm63xx_enet: correct clock usage
+ * bcm63xx_enet: do not write to random DMA channel on BCM6345
+ * crypto: crypto4xx - remove bad list_del
+ * crypto: crypto4xx - fix crypto4xx_build_pdr, crypto4xx_build_sdr leak
+ * atm: zatm: Fix potential Spectre v1
+ * net: dccp: avoid crash in ccid3_hc_rx_send_feedback()
+ * net: dccp: switch rx_tstamp_last_feedback to monotonic clock
+ * net/mlx5: Fix incorrect raw command length parsing
+ * net: sungem: fix rx checksum support
+ * qed: Limit msix vectors in kdump kernel to the minimum required count.
+ * r8152: napi hangup fix after disconnect
+ * tcp: fix Fast Open key endianness
+ * tcp: prevent bogus FRTO undos with non-SACK flows
+ * vhost_net: validate sock before trying to put its fd
+ * net_sched: blackhole: tell upper qdisc about dropped packets
+ * net/mlx5: Fix command interface race in polling mode
+ * net: cxgb3_main: fix potential Spectre v1
+ * rtlwifi: rtl8821ae: fix firmware is not ready to run
+ * MIPS: Call dump_stack() from show_regs()
+ * MIPS: Use async IPIs for arch_trigger_cpumask_backtrace()
+ * netfilter: ebtables: reject non-bridge targets
+ * KEYS: DNS: fix parsing multiple options
+ * rds: avoid unenecessary cong_update in loop transport
+ * net/nfc: Avoid stalls when nfc_alloc_send_skb() returned NULL.
+ * Linux 4.4.143

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

Title:
  Xenial update to 4.4.143 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.143 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.143 stable release shall be applied:
  * compiler, clang: suppress warning for unused static inline functions
  * compiler, clang: properly override 'inline' for clang
  * compiler, clang: always inline when CONFIG_OPTIMIZE_INLINING is disabled
  * compiler-gcc.h: Add __attribute__((gnu_inline)) to all inline declarations
  * x86/asm: Add _ASM_ARG* constants for argument registers to 
  * ocfs2: subsystem.su_mutex is required while accessing the item->ci_parent
  * bcm63xx_enet: correct clock usage
  * bcm63xx_enet: do not write to random DMA channel on BCM6345
  * crypto: crypto4xx - remove bad list_del
  * crypto: crypto4xx - fix crypto4xx_build_pdr, crypto4xx_build_sdr leak
  * atm: zatm: Fix potential Spectre v1
  * net: dccp: avoid crash in ccid3_hc_rx_send_feedback()
  * net: dccp: switch rx_tstamp_last_feedback to monotonic clock
  * net/mlx5: Fix incorrect raw command length parsing
  * net: sungem: fix rx checksum support
  * qed: Limit msix vectors in kdump kernel to the minimum required count.
  *

[Kernel-packages] [Bug 1788751] Re: linux-azure: 4.15.0-1023.24 -proposed tracker

[Po-Hsu Lin]

4.15.0-1023.24 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ebizzy - failed on Standard_A0, passed on the rest
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3, passed on the rest
  monotonic_time - all two tests (or just tsc test) failed on some instances, 
passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will 
crash E4 nodes (bug 1747892)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) quotactl01 failed (bug 1790028)
  ubuntu_lttng_smoke_test - package installation issue (bug 1791032), passed on 
the rest
  ubuntu_lxc - network issue on some node, passed on the rest
  ubunut_qrt_apparmor - mmap test timed out on some nodes (bug 1783922)
  ubuntu_unionmount_overlayfs_suite - Rename empty dir and rename back failed 
(bug 1727290)

Skipped / blacklisted:
  * libhugetlbfs
  * ubuntu_nbd_smoke_test
  * ubuntu_seccomp


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-azure: 4.15.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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: 1788744
  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/1788751/+subscriptions

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

[Kernel-packages] [Bug 1746088] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for crash has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+subscriptions

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 7.2.3+real-1~16.04.1

---
crash (7.2.3+real-1~16.04.1) xenial; urgency=medium

  * Backport to xenial. LP: #1746088
- Build-Depends on debhelper 9.

 -- Thadeu Lima de Souza Cascardo   Tue, 26 Jun
2018 14:32:30 -0300

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

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+subscriptions

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

[Kernel-packages] [Bug 1783922] Re: ubuntu_qrt_apparmor will hang with Bionic kernel on KVM / Azure instance (mmap test timeout)

[Po-Hsu Lin]

For Azure 4.15 kernel on Xenial:
* Standard_B1s
* Standard_B4ms
* Standard_DS12_v2
* Standard_DS14_v2
* Standard_DS14_v2_promo
* Standard_DS1_v2
* Standard_E4_v3
* Standard_D32s_v3

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

Title:
  ubuntu_qrt_apparmor will hang with Bionic kernel on KVM / Azure
  instance (mmap test timeout)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This test will timeout on a KVM instance (1G ram) with Bionic kernel.

  This is the last test executed on this system:
  Jul 26 10:10:54 zeppo kernel: [ 2140.591600] audit: type=1400 
audit(1532599854.772:275036): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="/tmp/testlibJOdhfr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap"
 pid=24072 comm="apparmor_parser"

    Run parser regression tests ... (Applying patch 
0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying 
patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok
    test_regression_testsuite (__main__.ApparmorTestsuites)
   preparing apparmor_2.12-4ubuntu5.dsc...  done
    Timer expired (10800 sec.), nuking pid 20299

  $ watch free -m
  totalusedfree  shared  buff/cache   available
  Mem:985 445  72   0 467 
355
  Swap:  1443   71436

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 26 09:35 seq
   crw-rw 1 root audio 116, 33 Jul 26 09:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Jul 27 02:28:52 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1783922/+subscriptions

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

[Kernel-packages] [Bug 1788755] Re: linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker

[Po-Hsu Lin]

4.15.0-1023.24~16.04.1 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ebizzy - failed on Standard_A0, passed on the rest
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3, passed on the rest
  monotonic_time - all two tests (or just tsc test) failed on some instances, 
passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will 
crash E4 nodes (bug 1747892)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) quotactl01 failed (bug 1790028)
  ubuntu_lttng_smoke_test - package installation issue (bug 1791032), passed on 
the rest
  ubuntu_lxc - lxc-test-ubuntu (Failed creating ubuntu-cloud container), 
lxc-test-autostart (container didn't stop on Standard_DS14_v2, 
Standard_E64-16s_v3), Failed creating ubuntu container (unable to download 
package on Standard_F4s)
  ubunut_qrt_apparmor - mmap test timed out on some nodes (bug 1783922)
  ubuntu_stress_smoke_test - sysfs caused kernel oopsed on some instances (bug 
1757057)
  ubuntu_vfat_stress - failed on StandardB1s only
  ubuntu_zram_smoke_test - zram test timed out (bug 1787076)

Skipped / blacklisted:
  * ubuntu_ltp
  * ubuntu_nbd_smoke_test
  * ubuntu_seccomp
  * ubuntu_sysdig_smoke_test


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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: 1788744
  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/1788755/+subscriptions

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

[Kernel-packages] [Bug 1790511] Re: General protection fault while trying to discover a nvmeof target

[Pradeep]

Issue occurs on a system that was installed from scratch. No upgrades
were made.

Tried testing this on 4.19-rc2 kernel, the system crashes during
mellanox driver init. Not able to make make progress.

[6.846269] BUG: unable to handle kernel NULL pointer dereference at 
0050
[6.846740] PGD 0 P4D 0 
[6.847170] Oops:  [#1] SMP PTI
[6.847631] CPU: 1 PID: 591 Comm: systemd-udevd Not tainted 
4.19.0-041900rc2-generic #201809022230
[6.848059] Hardware name: Supermicro SYS-6019U-TN4RT/X11DPU, BIOS 2.0b 
02/24/2018
[6.848513] RIP: 0010:mlx5_accel_tls_device_caps+0xd/0x20 [mlx5_core]

I will try on the next rc build for 4.19 when its available.

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

Title:
  General protection fault while trying to discover a nvmeof target

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  nvme discover command times out and results in general protection
  fault in kernel.

  # nvme discover -t rdma -a 10.1.1.6 -s 4420
  Failed to write to /dev/nvme-fabrics: Input/output error^M
  # 
  # [16900.248129] nvme nvme0: Connect command failed, error wo/DNR bit: 7
  [16900.248182] nvme nvme0: failed to connect queue: 0 ret=7
  [16900.253138] nvme nvme0: Reconnecting in 10 seconds...
  [16910.300029] general protection fault:  [#1] SMP PTI
  [16910.300069] Modules linked in: mlx4_en mlx4_ib mlx4_core nvme_rdma 
nvme_fabrics nvme_core rdma_ucm ib_umad ib_ucm ib_uverbs xt_conntrack 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_addrtype 
overlay aufs joydev input_leds ipmi_ssif intel_rapl skx_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
intel_cstate intel_rapl_perf mei_me mei ioatdma lpc_ich shpchp sch_fq_codel 
ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid acpi_power_meter 
iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc 
arp_tables ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov
  [16910.300534]  async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx5_ib ib_core hid_generic usbhid hid 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd mlx5_core ast mlxfw i2c_algo_bit devlink ttm 
drm_kms_helper ixgbe syscopyarea sysfillrect sysimgblt fb_sys_fops dca ptp drm 
pps_core mdio ahci libahci wmi [last unloaded: nvme_core]
  [16910.300794] CPU: 33 PID: 3173 Comm: kworker/u146:1 Not tainted 
4.15.0-33-generic #36-Ubuntu
  [16910.300845] Hardware name: Supermicro SYS-6019U-TN4RT/X11DPU, BIOS 2.0b 
02/24/2018
  [16910.300898] Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma]
  [16910.300945] RIP: 0010:nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma]
  [16910.300984] RSP: 0018:9ba8a037be08 EFLAGS: 00010206
  [16910.301019] RAX:  RBX: 52404d65f5994178 RCX: 
8a0f78002820
  [16910.301063] RDX: c0b58600 RSI: c0b573ab RDI: 
8a0f70aec000
  [16910.301108] RBP: 9ba8a037be28 R08: 0334 R09: 

  [16910.301152] R10:  R11: 0337 R12: 
8a0f70aec000
  [16910.301195] R13:  R14: 0020 R15: 

  [16910.301240] FS:  () GS:8a0f7efc() 
knlGS:
  [16910.301289] CS:  0010 DS:  ES:  CR0: 80050033
  [16910.301326] CR2: 7ffc4e5cadb8 CR3: 00123ba0a003 CR4: 
007606e0
  [16910.301370] DR0:  DR1:  DR2: 

  [16910.301414] DR3:  DR6: fffe0ff0 DR7: 
0400
  [16910.301458] PKRU: 5554
  [16910.301477] Call Trace:
  [16910.301504]  nvme_rdma_configure_admin_queue+0x22/0x2d0 [nvme_rdma]
  [16910.301548]  nvme_rdma_reconnect_ctrl_work+0x27/0xd0 [nvme_rdma]
  [16910.301591]  process_one_work+0x1de/0x410
  [16910.301620]  worker_thread+0x32/0x410
  [16910.301651]  kthread+0x121/0x140
  [16910.301676]  ? process_one_work+0x410/0x410
  [16910.301707]  ? kthread_create_worker_on_cpu+0x70/0x70
  [16910.301744]  ? do_syscall_64+0x73/0x130
  [16910.301774]  ? SyS_exit_group+0x14/0x20
  [16910.301805]  ret_from_fork+0x35/0x40
  [16910.301831] Code: 89 e5 41 56 41 55 41 54 53 48 8d 1c c5 00 00 00 00 49 89 
fc 49 89 c5 49 89 d6 48 29 c3 48 c7 c2 00 86 b5 c0 48 c1 e3 04 48 03 1f <48> 89 
7b 18 48 8d 7b 58 c7 43 50 00 00 00 00 e8 20 d4 57 ef 45
  [16910.305367] RIP: nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] RSP: 
9ba8a037be08
  [16910.307146] ---[ end trace 3ae215b72b2ac870 ]---

  #
  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[ Christian Ehrhardt ]

4.15.0-33-generic Failed,
4.4.0-134-generic we know works.
I tested 4.13.0-46-generic and it worked (as expected after the positive 17.10 
report in comment #23)

checking different builds from there
Bionic builds (so even the 4.13.0-32.35 being "before" the tested -46 it is the 
Bionic build of it)
4.13.0-32.35 - the last 4.13 - working
4.14.0-16.19 - the last 4.14 - failing
4.15.0-9.10 -  early 4.15- failing

Note good as well as bad cases were the same guest (Bionic).
Just installing different kernels in that guest, rebooting into these kernels 
and then triggering the migration.

4.14.0-11.13 - early 4.14 - failing

So it seems 4.13->4.14 is the breaking point, I'll check if I can get a
git bisect inside this working ...

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

Title:
  KVM live migration fails

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

Bug description:
  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Andrew Cloke]

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

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Fix Released
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+subscriptions

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

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions

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

[Kernel-packages] [Bug 1788766] Re: linux: 4.4.0-135.161 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-135.161
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1788766

Title:
  linux: 4.4.0-135.161 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial)
  derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 
(linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1788766/+subscriptions

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

[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer

[Marcelo Cerri]

** Changed in: linux (Ubuntu Cosmic)
   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/1788222

Title:
  Bugfix for handling of shadow doorbell buffer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  This request is to pull in the following patch for NVMe bug from
  https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp
  kernel:

  ===
  This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
  function to ensure that the shadow doorbell is written before reading
  EventIdx from memory. This is a critical bugfix for initial patch that
  added support for shadow doorbell into NVMe driver[...].

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

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

[Kernel-packages] [Bug 1765379] Re: nfp: flower: fixes for cmesg processing timeouts

[Simon Horman]

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

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

Title:
  nfp: flower: fixes for cmesg processing timeouts

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS
   

   
  This patch-set improves control message handling making it more robust with   
   
  respect to timeouts caused by excessively large number of messages
   
  queued for processing in a workqueue. 
   

   
  The upstream commits, accepted for v4.16, are:
   
  cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists")  
   
  0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the 
workqueue")

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

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

[Kernel-packages] [Bug 1787635] Re: Apply NVMe bugfix from Google that bjf asked for

[Marcelo Cerri]

*** This bug is a duplicate of bug 1788222 ***
https://bugs.launchpad.net/bugs/1788222

** This bug has been marked a duplicate of bug 1788222
   Bugfix for handling of shadow doorbell buffer

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

Title:
  Apply NVMe bugfix from Google that bjf asked for

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New

Bug description:
  bjf asked for this fix in the google kernels:

  https://lore.kernel.org/patchwork/patch/974880/

  
  It looks like it's actually needed in bionic/master as well

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

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

[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-gcp (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/1788222

Title:
  Bugfix for handling of shadow doorbell buffer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  This request is to pull in the following patch for NVMe bug from
  https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp
  kernel:

  ===
  This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
  function to ensure that the shadow doorbell is written before reading
  EventIdx from memory. This is a critical bugfix for initial patch that
  added support for shadow doorbell into NVMe driver[...].

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

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

[Kernel-packages] [Bug 1790620] Re: Xenial update to 4.4.141 stable release

[Kleber Sacilotto de Souza]

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

Title:
  Xenial update to 4.4.141 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.141 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.141 stable release shall be applied:
  * MIPS: Fix ioremap() RAM check
  * ibmasm: don't write out of bounds in read handler
  * vmw_balloon: fix inflation with batching
  * ahci: Disable LPM on Lenovo 50 series laptops with a too old BIOS
  * USB: serial: ch341: fix type promotion bug in ch341_control_in()
  * USB: serial: cp210x: add another USB ID for Qivicon ZigBee stick
  * USB: serial: keyspan_pda: fix modem-status error handling
  * USB: yurex: fix out-of-bounds uaccess in read handler
  * USB: serial: mos7840: fix status-register error handling
  * usb: quirks: add delay quirks for Corsair Strafe
  * xhci: xhci-mem: off by one in xhci_stream_id_to_ring()
  * HID: usbhid: add quirk for innomedia INNEX GENESIS/ATARI adapter
  * tools build: fix # escaping in .cmd files for future Make
  * iw_cxgb4: correctly enforce the max reg_mr depth
  * x86/cpufeature: Move some of the scattered feature bits to x86_capability
  * x86/cpu: Provide a config option to disable static_cpu_has
  * x86/fpu: Add an XSTATE_OP() macro
  * x86/fpu: Get rid of xstate_fault()
  * x86/headers: Don't include asm/processor.h in asm/atomic.h
  * x86/cpufeature: Replace the old static_cpu_has() with safe variant
  * x86/cpufeature: Get rid of the non-asm goto variant
  * x86/alternatives: Add an auxilary section
  * x86/alternatives: Discard dynamic check after init
  * x86/vdso: Use static_cpu_has()
  * x86/boot: Simplify kernel load address alignment check
  * x86/cpufeature: Speed up cpu_feature_enabled()
  * x86/cpufeature, x86/mm/pkeys: Add protection keys related CPUID definitions
  * x86/mm/pkeys: Fix mismerge of protection keys CPUID bits
  * x86/cpu: Add detection of AMD RAS Capabilities
  * x86/cpufeature, x86/mm/pkeys: Fix broken compile-time disabling of pkeys
  * x86/cpufeature: Make sure DISABLED/REQUIRED macros are updated
  * x86/cpufeature: Add helper macro for mask check macros
  * uprobes/x86: Remove incorrect WARN_ON() in uprobe_init_insn()
  * netfilter: nf_queue: augment nfqa_cfg_policy
  * netfilter: x_tables: initialise match/target check parameter struct
  * loop: add recursion validation to LOOP_CHANGE_FD
  * PM / hibernate: Fix oops at snapshot_write()
  * UBUNTU: SAUCE: RDMA/ucm: Blacklist UCM module
  * loop: remember whether sysfs_create_group() was done
  * Linux 4.4.141

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

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

[Kernel-packages] [Bug 1790883] Re: Xenial update to 4.4.142 stable release

[Kleber Sacilotto de Souza]

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

Title:
  Xenial update to 4.4.142 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.142 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.142 stable release shall be applied:
  * Kbuild: fix # escaping in .cmd files for future Make
  * perf tools: Move syscall number fallbacks from perf-sys.h to
tools/arch/x86/include/asm/
  * Linux 4.4.142

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

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

[Kernel-packages] [Bug 1790884] Re: Xenial update to 4.4.143 stable release

[Kleber Sacilotto de Souza]

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

Title:
  Xenial update to 4.4.143 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.143 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.143 stable release shall be applied:
  * compiler, clang: suppress warning for unused static inline functions
  * compiler, clang: properly override 'inline' for clang
  * compiler, clang: always inline when CONFIG_OPTIMIZE_INLINING is disabled
  * compiler-gcc.h: Add __attribute__((gnu_inline)) to all inline declarations
  * x86/asm: Add _ASM_ARG* constants for argument registers to 
  * ocfs2: subsystem.su_mutex is required while accessing the item->ci_parent
  * bcm63xx_enet: correct clock usage
  * bcm63xx_enet: do not write to random DMA channel on BCM6345
  * crypto: crypto4xx - remove bad list_del
  * crypto: crypto4xx - fix crypto4xx_build_pdr, crypto4xx_build_sdr leak
  * atm: zatm: Fix potential Spectre v1
  * net: dccp: avoid crash in ccid3_hc_rx_send_feedback()
  * net: dccp: switch rx_tstamp_last_feedback to monotonic clock
  * net/mlx5: Fix incorrect raw command length parsing
  * net: sungem: fix rx checksum support
  * qed: Limit msix vectors in kdump kernel to the minimum required count.
  * r8152: napi hangup fix after disconnect
  * tcp: fix Fast Open key endianness
  * tcp: prevent bogus FRTO undos with non-SACK flows
  * vhost_net: validate sock before trying to put its fd
  * net_sched: blackhole: tell upper qdisc about dropped packets
  * net/mlx5: Fix command interface race in polling mode
  * net: cxgb3_main: fix potential Spectre v1
  * rtlwifi: rtl8821ae: fix firmware is not ready to run
  * MIPS: Call dump_stack() from show_regs()
  * MIPS: Use async IPIs for arch_trigger_cpumask_backtrace()
  * netfilter: ebtables: reject non-bridge targets
  * KEYS: DNS: fix parsing multiple options
  * rds: avoid unenecessary cong_update in loop transport
  * net/nfc: Avoid stalls when nfc_alloc_send_skb() returned NULL.
  * Linux 4.4.143

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

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

[Kernel-packages] [Bug 1791080] [NEW] Xenial update to 4.4.144 stable release

[Stefan Bader]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.144 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.144 stable release shall be
applied:

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  Xenial update to 4.4.144 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.144 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.144 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

[Frank Heimes]

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

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

Title:
  Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 ==

  Problem:
  ---
  Kernel panics and Hardlockup messages when kernel crash was triggered to test 
kdump.
   
  There are two patches for a problem during a kernel crash:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff

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

  Only the first was marked for stable (and is currently present in
  18.04.1), but both should really be included to fix the problems in
  the commit log.  Can you include the second one, too?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions

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

[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

[Mike Ranweiler]

Manoj - you are correct, neither is in, and having both in would be very
helpful.  I confused that with a different commit.

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

Title:
  Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 ==

  Problem:
  ---
  Kernel panics and Hardlockup messages when kernel crash was triggered to test 
kdump.
   
  There are two patches for a problem during a kernel crash:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff

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

  Only the first was marked for stable (and is currently present in
  18.04.1), but both should really be included to fix the problems in
  the commit log.  Can you include the second one, too?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions

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

[Kernel-packages] [Bug 1789215] Re: i40e NIC not recognized

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  i40e NIC not recognized

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

Bug description:
  == SRU Justification ==

  Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel
  box with a i40e NIC results in no network. The 3.13 i40e driver
  doesn't support the following HW:

  3d:00.0 Ethernet controller: Intel Corporation Device 37d2 (rev 02)
  Subsystem: Intel Corporation Device 35ce
  Flags: bus master, fast devsel, latency 0, IRQ 37
  Memory at ac00 (64-bit, prefetchable) [size=16M]
  Memory at ad808000 (64-bit, prefetchable) [size=32K]
  Expansion ROM at ad98 [disabled] [size=512K]
  Capabilities: 

  Base Board Information
  Manufacturer: Intel Corporation
  Product Name: S2600WFT

  This is a Canonical test system and having functional networking with
  a Trusty kernel would help with - well - testing :-)

  == Fix ==

  Add a backport driver in addition to the in-tree driver that supports
  newer versions of the i40e NIC.

  == Regression Potential ==

  Low. The new driver will only load for NICs that are not supported by
  the current in-tree driver.

  == Test Case ==

  Boot a patched kernel and verify the NIC is recognized and the network
  comes up.

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

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

[Kernel-packages] [Bug 1789459] Re: linux: 4.18.0-7.8 -proposed tracker

[Seth Forshee]

** Tags added: regression-testing-passed

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

Title:
  linux: 4.18.0-7.8 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.18.0-7.8 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 --
  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/1789459/+subscriptions

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

[Kernel-packages] [Bug 1789459] Re: linux: 4.18.0-7.8 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.18.0-7.8 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.18.0-7.8 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 --
  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/1789459/+subscriptions

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

[Kernel-packages] [Bug 1791105] [NEW] Cosmic update to v4.18.6 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.18.6 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.18.6 stable release shall be
applied:

PATCH scripts/kernel-doc
scripts/kernel-doc: Escape all literal braces in regexes
scsi: libsas: dynamically allocate and free ata host
xprtrdma: Fix disconnect regression
mei: don't update offset in write
cifs: add missing support for ACLs in SMB 3.11
CIFS: fix uninitialized ptr deref in smb2 signing
cifs: add missing debug entries for kconfig options
cifs: use a refcount to protect open/closing the cached file handle
cifs: check kmalloc before use
smb3: enumerating snapshots was leaving part of the data off end
smb3: Do not send SMB3 SET_INFO if nothing changed
smb3: don't request leases in symlink creation and query
smb3: fill in statfs fsid and correct namelen
btrfs: use correct compare function of dirty_metadata_bytes
btrfs: don't leak ret from do_chunk_alloc
Btrfs: fix mount failure after fsync due to hard link recreation
Btrfs: fix btrfs_write_inode vs delayed iput deadlock
Btrfs: fix send failure when root has deleted files still open
Btrfs: send, fix incorrect file layout after hole punching beyond eof
hwmon: (k10temp) 27C Offset needed for Threadripper2
bpf, arm32: fix stack var offset in jit
regulator: arizona-ldo1: Use correct device to get enable GPIO
iommu/arm-smmu: Error out only if not enough context interrupts
printk: Split the code for storing a message into the log buffer
printk: Create helper function to queue deferred console handling
printk/nmi: Prevent deadlock when accessing the main log buffer in NMI
kprobes/arm64: Fix %p uses in error messages
arm64: Fix mismatched cache line size detection
arm64: Handle mismatched cache type
arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid()
arm64: dts: rockchip: corrected uart1 clock-names for rk3328
KVM: arm/arm64: Fix potential loss of ptimer interrupts
KVM: arm/arm64: Fix lost IRQs from emulated physcial timer when blocked
KVM: arm/arm64: Skip updating PMD entry if no change
KVM: arm/arm64: Skip updating PTE entry if no change
s390/kvm: fix deadlock when killed by oom
perf kvm: Fix subcommands on s390
stop_machine: Reflow cpu_stop_queue_two_works()
stop_machine: Atomically queue and wake stopper threads
ext4: check for NUL characters in extended attribute's name
ext4: use ext4_warning() for sb_getblk failure
ext4: sysfs: print ext4_super_block fields as little-endian
ext4: reset error code in ext4_find_entry in fallback
ext4: fix race when setting the bitmap corrupted flag
x86/gpu: reserve ICL's graphics stolen memory
platform/x86: wmi: Do not mix pages and kmalloc
platform/x86: ideapad-laptop: Apply no_hw_rfkill to Y20-15IKBM, too
mm: move tlb_table_flush to tlb_flush_mmu_free
mm/tlb, x86/mm: Support invalidating TLB caches for RCU_TABLE_FREE
x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
x86/speculation/l1tf: Fix off-by-one error when warning that system has too 
much RAM
x86/speculation/l1tf: Suggest what to do on systems with too much RAM
x86/vdso: Fix vDSO build if a retpoline is emitted
x86/process: Re-export start_thread()
KVM: x86: ensure all MSRs can always be KVM_GET/SET_MSR'd
KVM: x86: SVM: Call x86_spec_ctrl_set_guest/host() with interrupts disabled
fuse: Don't access pipe->buffers without pipe_lock()
fuse: fix initial parallel dirops
fuse: fix double request_end()
fuse: fix unlocked access to processing queue
fuse: umount should wait for all requests
fuse: Fix oops at process_init_reply()
fuse: Add missed unlock_page() to fuse_readpages_fill()
lib/vsprintf: Do not handle %pO[^F] as %px
udl-kms: change down_interruptible to down
udl-kms: handle allocation failure
udl-kms: fix crash due to uninitialized memory
udl-kms: avoid division
b43legacy/leds: Ensure NUL-termination of LED name string
b43/leds: Ensure NUL-termination of LED name string
ASoC: dpcm: don't merge format from invalid codec dai
ASoC: zte: Fix incorrect PCM format bit usages
ASoC: sirf: Fix potential NULL pointer dereference
ASoC: wm_adsp: Correct DSP pointer for preloader control
soc: qcom: rmtfs-mem: fix memleak in probe error paths
pinctrl: freescale: off by one in imx1_pinconf_group_dbg_show()
scsi: qla2xxx: Fix stalled relogin
x86/vdso: Fix lsl operand order
x86/nmi: Fix NMI uaccess race against CR3 switching
x86/irqflags: Mark native_restore_fl extern inline
x86/spectre: Add missing family 6 check to microcode check
x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
hwmon: (nct6775) Fix potential Spectre

[Kernel-packages] [Bug 1783152] Re: Enable basic support for Solarflare 8000 series NIC

[Mauricio Faria de Oliveira]

The secure boot packages on trusty-proposed are now correct (LP: #1708245),
and the d-i rebuild on amd64 is in progress (verified successfully on PPA).

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

Title:
  Enable basic support for Solarflare 8000 series NIC

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-lts-xenial source package in Xenial:
  Invalid

Bug description:
  SRU Justification:

  [Impact]

   * Users cannot use Solarflare 8000 series NICs.

   * Servers with only this NIC cannot do netboot.

   * The patchset adds the PCI IDs and a basic fix.

  [Test Case]

   * Try to probe/netboot/use a Solarflare 8000
     series NIC.

   * It does not probe on the original kernel,
     but it does probe/netboot/install/stress
     (i.e., basic fuctionality works) on the
     patched kernel.

  [Regression Potential]

   * Users with Solarflare 8000 series NIC might hit
     problems on device probe or due to a new network
     interface coming up, now that the NIC comes up.

   * More specific features of the NIC or advanced
     tuning/setup might not work as expected or run
     into issues.

  [Other Info]

   * There are known error messages on device probe.

   * These are benign/non-fatal and will be addressed
     on another SRU cycle.

  ---

  The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 
series NIC.
  This prevents network installs on servers which only have that NIC.

  In order to get NIC detected, link up, and successful network install,
  only 2 commits are required:

  dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC
  93171b14a545 sfc: make TSO version a per-queue parameter

  This patchset is undergoing testing, and I will post the patches to
  the kernel-team mailing list.

  ---

  There are some kernel messages produced possibly due to additional commits 
missing,
  but are benign/non-fatal and allows the NIC probing and basic functionality 
to work.

  [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): 
Solarflare NIC detected
  [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part 
Number : SFN8042
  [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC 
command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0
  [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP 
support
  [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC 
command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0
  [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed 
to allocate PIO buffers (-1)
  ...
  [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 
1500)

  The PTP (precision time protocol / ieee 1588) support is a feature to 
synchronize clocks
  over a computer network with high precision, and is not required for basic 
functionality
  nor for this particular user.

  The failure to allocate PIO buffers is non-fatal, see
  sfc/ef10.c/efx_ef10_dimension_resources() comments.

  The additional patches to resolve the error messages will be worked on
  another SRU cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+subscriptions

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

[Kernel-packages] [Bug 1790606] Re: Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2


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

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

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

Title:
  Acer Aspire ES-512 cannot hibernate/suspend on newer kernels than 3.17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my Acer Aspire ES-512 suspend as well as hibernate freeze the
  kubuntu 18.04 that I installed on a 18G deleted partition. Apparently,
  suspend/hibernate succeed partially only, so that it cannot resume.

  The latest kernel where suspend/hibernate work is 3.17, which however
  has problems with touchpad. That is, I use 3.16.57. From 3.18 and all
  later kernels suspend/hibernate does not work.

  It does not help: 
   - to change /etc/default/grup adding RESUME=UUID= or 
nouveau.modeset=0 to GRUB_CMDLINE_LINUX. 
   - to enable hibernate in 
/var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. 
  - to use Feng's fixed kernel. 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). 
  - /sys/power/ files seems to be alright: cat disk mem_sleep state 
  [platform] shutdown reboot suspend test_resume 
  s2idle [deep]
  freeze mem disk
  
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close/1044270#1044270
  - busctl call org.freedesktop.login1 /org/freedesktop/login1 
org.freedesktop.login1.Manager CanSuspend: s "yes"

  If anyone want additional information, just let me know.

  I don't know how to update BIOS on Acer Aspire ES1-512 from Linux:
  https://help.ubuntu.com/community/BIOSUpdate

  I have tried the following kernels:

  Found installed: 3.17.1-031701.201410150735
  Found installed: 3.18.120-0318120.201808280231
  Found installed: 4.15.0.33.35
  Found installed: 3.18.18-031818.201507101433
  Found installed: 4.15.0-33.36
  Found installed: 3.16.45-031645.201707030336
  Found installed: 4.18.5-041805.201808241320
  Found installed: 3.18.1-031801.201412170637
  Found installed: 3.18.36-031836.201606230133
  Found installed: 4.15.0-29.31
  Found installed: 4.1.11-040111.201510261146
  Found installed: 3.17.8-031708.201501081837
  Found installed: 4.14.41-041441.201806042208
  Found installed: 3.16.57-031657.201806170831
  Found installed: 3.18.2-031802.201501082011

  ubuntu-bug linux 
  says that the bug is about a non-installed package (?)

  lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  cat /proc/version 
  Linux version 4.14.41-041441-generic (kernel@kathleen) (gcc version 7.3.0 
(Ubuntu 7.3.0-20ubuntu1)) #201806042208 SMP Mon Jun 4 22:10:20 UTC 2018

  debconf-show uswsusp
uswsusp/RSA_passphrase_v: (password omitted)
uswsusp/RSA_passphrase: (password omitted)
uswsusp/compress: true
uswsusp/image_size: 2147483647
uswsusp/max_loglevel:
uswsusp/resume_offset:
uswsusp/suspend_loglevel:
uswsusp/early_writeout: true
uswsusp/encrypt: false
uswsusp/no_swap:
uswsusp/RSA_key_file: /etc/uswsusp.key
uswsusp/compute_checksum: false
uswsusp/no_snapshot:
uswsusp/RSA_key_bits: 1024
uswsusp/continue_without_swap: true
uswsusp/shutdown_method: platform
uswsusp/snapshot_device:
uswsusp/create_RSA_key: false
uswsusp/resume_device: 
/dev/disk/by-uuid/aea65d92-3a0e-4ae2-a018-ac663635fefd

  
  lshw -short
  H/W path Device Class Description
  ==
  system Aspire ES1-512 (EA53_BM_083D_1.09)
  /0 bus Aspire ES1-512
  /0/0 memory 64KiB BIOS
  /0/4 processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz
  /0/4/8 memory 32KiB L1 cache
  /0/4/9 memory 1MiB L2 cache
  /0/7 memory 24KiB L1 cache
  /0/f memory 8GiB System Memory
  /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns)
  /0/f/1 memory SODIMM [empty]
  /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register
  /0/100/2 display Atom Processor Z36xxx/Z37xxx Series Graphics & Display
  /0/100/13 storage Atom Processor E3800 Series SATA AHCI Controller
  /0/100/14 bus Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI
  /0/100/14/0 usb3 bus xHCI Host Controller
  /0/100/14/1 usb2 bus xHCI Host Controller
  /0/100/14/1/3 bus USB2.0 Hub
  /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth
  /0/100/14/1/

[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2


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

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

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

Title:
  Line 6 POD HD500 driver fault

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";

  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  uname:

  Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15
  17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  lspci -vnvn  https://pastebin.com/7KM9bybk


  dmesg:

  usb 1-5: new high-speed USB device number 6 using xhci_hcd
  [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d
  [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 44.209072] usb 1-5: Product: POD HD500
  [ 44.209076] usb 1-5: Manufacturer: Line 6
  [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found
  [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached
  [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found
  [ 44.211289] usb 1-5: selecting invalid altsetting 1
  [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed
  [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected
  [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22
  [ 69.605987] nvidia-modeset: Allocated GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 69.606386] nvidia-modeset: Freed GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 153.206595] usb 1-5: USB disconnect, device number 6
  [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected
  [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd
  [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 165.843146] usb 1-1: New USB device found, idVendor=0e41,
  idProduct=414d
  [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 165.843149] usb 1-1: Product: POD HD500
  [ 165.843150] usb 1-1: Manufacturer: Line 6
  [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found
  [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached
  [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
  [ 165.844742] usb 1-1: selecting invalid altsetting 1
  [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed
  [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected
  [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-03 (63 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency 
root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-lowlatency N/A
   linux-backports-modules-4.15.0-33-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-lowlatency x86_64
  UpgradeStatus: No

[Kernel-packages] [Bug 1790594] Re: The system is not able to detect the touchsreen

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2


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

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

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

Title:
  The system is not able to detect the touchsreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I' m using a tablet that is sold with Windows 10.
  The firmware extracted from the special driver are already available here 
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
  (I discovered that the Mediacom drivers are the same as those for TrekStor, a 
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at 
SurfTab wintron 7.0 ST70416-6).
  That repository states that i need to recompile the kernel. 
  I don' t know how here 
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
 there is my question about this problem.
  It would be nice if the linux-kernel would support the tablet touchscreen by 
default. 
  My kernel is 4.15.0-33-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vegito 1554 F pulseaudio
   /dev/snd/controlC0:  vegito 1554 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 11
 Simple ctrls  : 1
  Card1.Amixer.info:
   Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
 Mixer name : ''
 Components : ''
 Controls  : 243
 Simple ctrls  : 213
  CurrentDesktop: LXDE
  Date: Tue Sep  4 09:57:45 2018
  HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
  InstallationDate: Installed on 2018-08-21 (13 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDIACOM WinPad 7 W10 - WPW700
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: MC.G.WI71C.MGBMRBA03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1 - Family
  dmi.product.name: WinPad 7 W10 - WPW700
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: MEDIACOM

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

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

[Kernel-packages] [Bug 1789459] Re: linux: 4.18.0-7.8 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

** Tags removed: block-proposed-cosmic

** Tags removed: block-proposed

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

Title:
  linux: 4.18.0-7.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.0-7.8 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 --
  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/1789459/+subscriptions

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

[Kernel-packages] [Bug 1758545] Re: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer

[Jon Champagne]

Is there any chance you can find a page in your bios like the one I've
attached and post it? For me I hit f12 (boot device  select), device
configuration, amd pbs, and firmware version. I'm having an identical
issue with my dell Inspiron 7375 and an Intel 7260 and am curious if I
can expect a fix from dell sometime soon.

** Attachment added: "IMG_20180906_103553.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758545/+attachment/5185667/+files/IMG_20180906_103553.jpg

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

Title:
  PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction
  Layer

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  My dmesg gets completely spammed with the following messages appearing over 
and over again, and this keep increasing the size of log file. I can use 
pci=noaer parameter to suppress these annoying messages, but not sure what this 
parameter do, will it make my pc lost some function.Is this a bug? below is 
part of the dmesg infomation
  
--

  [  397.076509] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  397.076517] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  397.076522] pcieport :00:01.1:[20] Unsupported Request(First)
  [  397.076526] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  397.081907] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  397.081914] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  397.081918] pcieport :00:01.1:[20] Unsupported Request(First)
  [  397.081923] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.983368] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.983376] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.983381] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.983385] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.984773] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.984779] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.984783] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.984788] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.994170] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.994176] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.994180] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.994185] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  399.333957] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  399.333964] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  399.333968] pcieport :00:01.1:[20] Unsupported Request(First)
  [  399.333973] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  399.339347] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  399.339353] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  399.339358] pcieport :00:01.1:[20] Unsupported Request(First)
  [  399.339362] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ven1747 F pulseaudio
   /dev/snd/controlC0:  ven1747 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 23:24:16 2018
  InstallationDate: Installed on 2018-03-07 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-r

[Kernel-packages] [Bug 1788744] Re: linux: 4.15.0-34.37 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-34.37
/bionic-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1788744

Title:
  linux: 4.15.0-34.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1788744/+subscriptions

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

[Kernel-packages] [Bug 1788762] Re: linux: 3.2.0-135.181 -proposed tracker

[Seth Forshee]

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

Title:
  linux: 3.2.0-135.181 -proposed tracker

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

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: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1788762/+subscriptions

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

[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial

[Joseph Salisbury]

** Changed in: iproute2 (Ubuntu)
   Status: Expired => Triaged

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

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

Title:
  iproute2: unable to add ip lwt mpls route on xenial

Status in iproute2 package in Ubuntu:
  Triaged

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

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

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

[Kernel-packages] [Bug 1791080] Re: Xenial update to 4.4.144 stable release

[Stefan Bader]

This upstream stable update contains the backport for CVE-2018-3639 (x86) aka 
Spectre v4/SSB.
* x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
  The upstream stable patch adds two previously unknown
  feature bits for word 18 which I added with a SAUCE
  patch.
* x86/cpufeatures: Add Intel feature bits for Speculation
  Control
  -> skip, no change
* x86/cpufeatures: Add AMD feature bits for Speculation
  Control
  -> skip, no change
* x86/msr: Add definitions for new speculation control
  MSRs
  -> skip, no change
* x86/pti: Do not enable PTI on CPUs which are not
  vulnerable to Meltdown
  -> skip, no change
* x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early
  Spectre v2 microcodes
  -> skip, we have actually reverted this at some point
* x86/speculation: Add basic IBPB (Indirect Branch
  Prediction Barrier) support
  -> Picked in reduced form (only adding definition for
 indirect_branch_prediction_barrier(). Not sure this
 will be needed in the end.
* x86/cpufeatures: Clean up Spectre v2 related CPUID
  flags
  -> Mostly can be skipped. Only picking up a small change
 to indirect_branch_prediction_barrier() which is still
 not used.
  Not picking up the firmware blacklist code.
* x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature
  bits on Intel
  -> skipped, no change

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639

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

Title:
  Xenial update to 4.4.144 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.144 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.144 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1791118] [NEW] No sound output on Medion Akoya S2218 Z3735F subnotebook

[Hanno]

Public bug reported:

Hello,

the Medion Akoya S2218 is a Z3735F-based subnotebook.

It is possible to install Ubuntu on it, but some devices are not
properly supported. I have installed a vanilla 18.04 Ubuntu 64 bit
system on it and then updated to the current development version of
18.10. I have also tried the distribution's current 4.17.0-9-generic
#10-Ubuntu kernel as well as current 4.19.0-rc kernels.

There is no sound output.

These audio-related modules are being loaded:

snd_soc_sst_cht_bsw_rt5645
snd_intel_sst_acpi
snd_intel_sst_core
snd_soc_sst_atom_hifi2_platform
snd_soc_rt5645
snd_soc_acpi
snd_soc_acpi_intel_match
snd_soc_rl6231
snd_soc_core
snd_compress
ac97_bus
snd_pcm_dmaengine
snd_seq_midi
snd_seq_midi_event
snd_pcm
snd_rawmidi
snd_seq
snd_seq_device
snd_timer
snd
soundcore

These are blacklisted:

blacklist r8723bs
blacklist snd_hdmi_lpe_audio

Pulseaudio still reports a "dummy device".

I have tried finding solutions on the internet. There are various fixes
for other Z3735F-based devices, including the tip to blacklist the
snd_hdmi_lpe_audio module. None of those fixes helped for mine.

I tried getting help at https://github.com/plbossart/UCM/issues/32 with
no response.

/var/log/syslog reports

Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:36 akoya pulseaudio[1075]: W: [pulseaudio] module-udev-detect.c: 
Tried to configure /devices/platform/80860F28:00/cht-bsw-rt5645/sound/card0 
(alsa_card.platform-cht-bsw-rt5645) more often than 5 times in 10s
Sep  6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
Sep  6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep  6 16:59:55 akoya pulseaudio[1732]: E:

[Kernel-packages] [Bug 1790753] Re: X1 yoga 3rd generation doesn't go to sleep

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2

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

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

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

Title:
  X1 yoga 3rd generation doesn't go to sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The laptop doesn't go to sleep. This is probably related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756105 which
  seems to be missing logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  myrti 16389 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Sep  4 20:35:07 2018
  HibernationDevice: RESUME=UUID=d105e0f8-28bb-49d5-badc-d2081f559c27
  InstallationDate: Installed on 2018-08-30 (5 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LES49J00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b23d1c6-f9bc-4bff-9420-8ab24cce52df ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET35W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES49J00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET35W(1.21):bd06/08/2018:svnLENOVO:pn20LES49J00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES49J00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES49J00
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

[Joseph Salisbury]

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Cosmic)
   Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: In Progress

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  In Progress

Bug description:
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline 
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
 s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

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

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

[Kernel-packages] [Bug 1790801] Re: Ubuntu 18.04 touchppad does not work smoothly in Lenono Thinkpad

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2

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

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

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

Title:
  Ubuntu 18.04 touchppad does not work smoothly in Lenono Thinkpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hallo,
  The touchpad is not working after installing Ubuntu 18.04.1 LTS in Lenovo 
Thinkpad laptop. After a lot of googling and trying around, I managed to make 
it work in the sense that i could move cursor here and there, but still it has 
numbers of problems. Here is the list of problems it still has:
  1. The scrolling does not work at all, it never worked.

  2. It is dead after each restart and I have to provide this commands to make 
it work, so that the cursor could move. 
sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=imps

  3. The typing of the keyboard does not work smoothly, which make me really 
difficult to work. For example: I ended up typing this
  ''he list Here is the pr to repoty I want thatoblem of t''
when I want to type:
  'Here is the list of problems that I want to report'

  4. The left and right touch is really hard.

  Here is the information on my touchpad
  1. pooja@pooja-thinkpad-x1:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech Optical USB Mouse  id=9[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Synaptics TouchPad id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=13   [slave  
keyboard (3)]

  2. pooja@pooja-thinkpad-x1:~$ xinput list 12
  PS/2 Synaptics TouchPad   id=12   [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 12. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right"
Button state:
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 15.00
  flags: 0x0
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: 15.00
 

[Kernel-packages] [Bug 1790658] Re: s390/pci: fix out of bounds access during irq setup

[Joseph Salisbury]

*** This bug is a duplicate of bug 1790480 ***
https://bugs.launchpad.net/bugs/1790480

** This bug has been marked a duplicate of bug 1790480
   random oopses on s390 systems using NVMe devices

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

Title:
  s390/pci: fix out of bounds access during irq setup

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New

Bug description:
  == SRU Justification ==

  IBM is requesting this commit (from 4.19) for s390: 
866f3576a72b2233a76dffb80290f8086dc49e17
  It fixes a problem with requesting more interrupts than supported on s390.
  The issue can finally lead to an out of bounds access.

  It needs to be applied to 18.04 and 16.04 (in addition to cosmic).

  == Fix ==

  commit 866f3576a72b2233a76dffb80290f8086dc49e17 upstream.

  During interrupt setup we allocate interrupt vectors, walk the list of msi
  descriptors, and fill in the message data. Requesting more interrupts than
  supported on s390 can lead to an out of bounds access.

  When we restrict the number of interrupts we should also stop walking the
  msi list after all supported interrupts are handled.

  == Regression Potential ==

  Low. The modification is limited to the following two lines in s390/pci:
  ...
  + if (hwirq >= msi_vecs)
  + break;
  ...

  https://lkml.org/lkml/2018/9/3/1125

  == Test Case ==

  A test case will be provided by IBM.
  And the test and verification will also be done by IBM.

  __

  Bug Description:

  s390/pci: fix out of bounds access during irq setup

  During interrupt setup we allocate interrupt vectors, walk the list of msi
  descriptors, and fill in the message data. Requesting more interrupts than
  supported on s390 can lead to an out of bounds access.

  When we restrict the number of interrupts we should also stop walking the
  msi list after all supported interrupts are handled.

  Upstream-ID:  866f3576a72b2233a76dffb80290f8086dc49e17
  kernel 4.19

  Also to be applied to 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790658/+subscriptions

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

[Kernel-packages] [Bug 1788603] Re: libvirt fails with failure to open mount namespace

[Andy Whitcroft]

Hello Thadeu, or anyone else affected,

Accepted libvirt into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/4.0.0-1ubuntu8.5 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libvirt (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  libvirt fails with failure to open mount namespace

Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in libvirt source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in libvirt source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress

Bug description:
  [Impact]

   * Libvirt will no more be able to start guests with newer kernels 
 (>=4.18)

   * We brought a fix upstream that we want to backport to potentially 
 affected releases (B+C)

  [Test Case]

  Note: This can but does not have to be tested in nested virtualization (Since 
we need to change the kernel it is probably the preferred way to do it in 
nested, so this is what I describe)
  1. Get a KVM guest with the Release to test (Cosmic as an example) and give 
it a size to be able to host a nested guest
$ sudo apt install uvtool-libvirt
$ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=cosmic label=daily
$ uvt-kvm create --cpu 8 --memory 4096 --password ubuntu c-nested-kvm-4.18 
arch=amd64 release=cosmic label=daily
$ uvt-kvm ssh c-nested-kvm-4.18
  2. In the guest set up another guest
$ uvt-kvm ssh c-nested-kvm-4.18
$ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=cosmic label=daily
$ uvt-kvm create --password ubuntu c-nested-guest arch=amd64 release=cosmic 
label=daily
$ sudo apt install uvtool-libvirt
  3. The above will work, now get a kernel >=4.18 e.g. the mainline kernels at
 https://wiki.ubuntu.com/Kernel/MainlineBuilds
 $ wget (link of the day)
 $ sudo dpkg -i *.deb
  4. reboot into the 4.18 kernel
 $ sudo reboot
  5. Start the guest again
 $ virsh start c-nested-guest

  Without fix this will fail like:
error: Failed to start domain c-nested-guest
error: internal error: child reported: Kernel does not provide mount 
namespace: Permission denied

  And an associated Dmesg/Apparmor entry:
  [ 519.529760] audit: type=1400 audit(1535364820.976:27): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/libvirtd" pid=1692 comm="libvirtd" 
requested_mask="read" denied_mask="read" 
peer="libvirt-4ae5dbbe-641c-4934-ae7c-956bcc8b9e2f"

  6. In the guest update from PPA/Proposed that you want to test to bring in 
the libvirt package with the updated rules (Example with the PPA).
$ sudo add-apt-repository ppa:ci-train-ppa-service/3381
$ sudo apt upgrade

  7. Start the guest again and it will now work
$ virsh start c-nested-guest

  [Regression Potential]

   * The change is "only" opening up the apparmor profile for libvirt a 
 little bit for the access now being reported as read in addition.
 That should in itself be rather regression free, but in addition it has
 an ack of Jamie Strandboge to be sure from Securities POV (you can 
 follow the upstreaming thread at to check:
   https://www.redhat.com/archives/libvir-list/2018-August/msg01597.html

  
  [Other Info]
   
   * This is no issue "yet" but would be one when the Cosmic Kernel becomes 
available as HWE kernel. We'd want to have the apparmor profile in libvirt 
ready at the time so that we never have users see this error in the Field on a 
Released Ubuntu version.

  ---

  $ virsh start cosmic-i386
  error: Failed to start domain cosmic-i386
  error: internal error: child reported: Kernel does not provide mount 
namespace: Permission denied

  Happens with 4.18 only, 4.17 is fine.

  27013 openat(AT_FDCWD, "/proc/

[Kernel-packages] [Bug 1790594] Re: The system is not able to detect the touchsreen

[Scorpion]

Or just install 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2/linux-headers-4.19.0-041900rc2-generic_4.19.0-041900rc2.201809022230_amd64.deb?
 
Is this the correct package?

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

Title:
  The system is not able to detect the touchsreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I' m using a tablet that is sold with Windows 10.
  The firmware extracted from the special driver are already available here 
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
  (I discovered that the Mediacom drivers are the same as those for TrekStor, a 
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at 
SurfTab wintron 7.0 ST70416-6).
  That repository states that i need to recompile the kernel. 
  I don' t know how here 
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
 there is my question about this problem.
  It would be nice if the linux-kernel would support the tablet touchscreen by 
default. 
  My kernel is 4.15.0-33-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vegito 1554 F pulseaudio
   /dev/snd/controlC0:  vegito 1554 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 11
 Simple ctrls  : 1
  Card1.Amixer.info:
   Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
 Mixer name : ''
 Components : ''
 Controls  : 243
 Simple ctrls  : 213
  CurrentDesktop: LXDE
  Date: Tue Sep  4 09:57:45 2018
  HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
  InstallationDate: Installed on 2018-08-21 (13 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDIACOM WinPad 7 W10 - WPW700
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: MC.G.WI71C.MGBMRBA03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1 - Family
  dmi.product.name: WinPad 7 W10 - WPW700
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: MEDIACOM

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

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

[Kernel-packages] [Bug 1790991] Re: package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal script subprocess returned

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to
  install/upgrade: installed linux-image-4.15.0-30-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Impossible to boot the operating system since it wasn't able to detect
  2 external USB drives that should be unmounted, maybe was caused by a
  false unmount of those devices

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-30-generic 4.15.0-30.32
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio 883 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xd540 irq 31'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,104313f3,00100302 
HDA:80862804,80860101,0010'
 Controls  : 26
 Simple ctrls  : 9
  Date: Wed Sep  5 15:37:19 2018
  ErrorMessage: installed linux-image-4.15.0-30-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-09 (88 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK Computer Inc. K52F
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=44bcc84e-8292-4053-a854-a6997dcfc6af ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to 
install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52F.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52F
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52F.218:bd07/12/2011:svnASUSTeKComputerInc.:pnK52F:pvr1.0:rvnASUSTeKComputerInc.:rnK52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K52F
  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/1790991/+subscriptions

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

[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)

[Joseph Salisbury]

** Tags added: kernel-da-key

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

Title:
  Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
  state disabled (performance)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-09-04
  00:50:14 ==

  The CPUs remain in snooze state on an idle system when only the
  shallow states disabled resulting in increased power consumption.

  The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of  snooze 
to deeper idle state") introduced a timeout for the snooze idle state so that 
it could be eventually be promoted to a deeper idlestate. The snooze 
timeout value is static and set to the target  residency of the next idle 
state, which would train the cpuidle governor to pick the next idle state 
eventually.
  
  The unfortunate side-effect of this is that if the next idle state(s)  is 
disabled, the CPU will forever remain in snooze, despite the fact that the 
system is completely idle, and other deeper idle states are available.
  
  This patch fixes the issue by dynamically setting the snooze timeout  to the 
target residency of the next enabled state on the device.
  
  Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | Nap  | Fast
   0|   8|   0| 96.41|  0.00|  0.00
   0|   8|   1| 96.43|  0.00|  0.00
   0|   8|   2| 96.47|  0.00|  0.00
   0|   8|   3| 96.35|  0.00|  0.00
   0|   8|   4| 96.37|  0.00|  0.00
   0|   8|   5| 96.37|  0.00|  0.00
   0|   8|   6| 96.47|  0.00|  0.00
   0|   8|   7| 96.47|  0.00|  0.00
  
  POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2) 
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | 
stop
   0|  16|   0| 89.79|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   1| 90.12|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   2| 90.21|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   3| 90.29|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
  


  After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | Nap  | Fast
   0|   8|   0| 16.58|  0.00| 77.21
   0|   8|   1| 18.42|  0.00| 75.38
   0|   8|   2|  4.70|  0.00| 94.09
   0|   8|   3| 17.06|  0.00| 81.73
   0|   8|   4|  3.06|  0.00| 95.73
   0|   8|   5|  7.00|  0.00| 96.80
   0|   8|   6|  1.00|  0.00| 98.79
   0|   8|   7|  5.62|  0.00| 94.17
  
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,  
stop2) disabled:
  
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | 
stop
   0|   0|   0|  0.69|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  9.39| 
89.70
   0|   0|   1|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05| 
93.21
   0|   0|   2|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
89.93
   0|   0|   3|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
93.26

  
  This fix  (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze 
if next state disabled") is in the -next branch of the powerpc tree and 
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions

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

[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2

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

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

Title:
  touchpad not detected/ not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  docs attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.5-041805-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2

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

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

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

Title:
  amdgpu.dc dual monitor issues when trying to sleep / power off the
  monitors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a problem with my dual monitor setup on an AMD RX 580: when I lock the 
screen and Gnome try to power off both monitors the following happens:
  1) the second monitor goes to sleep before the first one, this is normal and 
expected because the first monitor has a longer time to sleep
  2) after some seconds the second monitor turn on back again and prevents the 
first one to sleep at all
  3) gnome detects inactivity on the lock screen for some time and try to power 
off the monitors again
  4) step 1 all over again in an infinite loop

  When I login back from the lock screen the windows inside my Gnome
  session can sometimes be rearranged from one screen to the other.

  After discovering this behavior I tried to power off the monitors
  manually with `xset dpms force off` and I can confirm that the same
  happens: the monitors wont really power off because the second one
  turns back on and prevents the first one to sleep.

  My guess was that somehow when the second monitor was turning off it
  delivered some kind of "monitors changed, you should reset" message to
  the GPU which in order did some kind of "reset everything and power on
  the monitors back again" action.

  Searching for a fix to this problem I tried to upgrade my amdgpu mesa
  drivers using the oibaf/graphics-drivers ppa and after this I tried to
  upgrade my whole distribution too, moving from bionic to cosmic.

  Nothing worked.

  In the end I discovered the existence of amdgpu.dc and tried to
  disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did
  the trick but it is still a workaround.

  I'm not sure this is the right place to report this kind of issues but as the 
issue is somehow critical (the first I entered the power on/off loop I didn't 
notice it and my monitor cycled power for two hours) I hope this will help 
other people.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.17.0-9-generic.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,104385b0,00100302'
 Controls  : 50
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100700'
 Controls  : 42
 Simple ctrls  : 6
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2
  InstallationDate: Installed on 2018-09-01 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic
  Uname: Linux 4.17.0-9-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chas

[Kernel-packages] [Bug 1790636] Re: Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

[Joseph Salisbury]

** Tags added: kernel-da-key

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

Title:
  Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler - 2018-09-04 01:38:39 ==

  Problem:
  ---
  Kernel panics and Hardlockup messages when kernel crash was triggered to test 
kdump.
   
  There are two patches for a problem during a kernel crash:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de6e5d38417e6cdb005843db420a2974993d36ff

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

  Only the first was marked for stable (and is currently present in
  18.04.1), but both should really be included to fix the problems in
  the commit log.  Can you include the second one, too?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790636/+subscriptions

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

[Kernel-packages] [Bug 1790880] [NEW] apt-get source linux-image-$(uname -r) does not work on 18.04.1 LTS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I cannot get the source code and therefore cannot build a driver for
Ubuntu 18.04.1 LTS

See link

https://ubuntuforums.org/showthread.php?t=2397649

Other people have seen the same problem.

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Incomplete

-- 
apt-get source linux-image-$(uname -r) does not work on 18.04.1 LTS
https://bugs.launchpad.net/bugs/1790880
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 1766993] Re: dpkg-reconfigure bcmwl-kernel-source : modprobe: ERROR: could not insert 'wl': Exec format error

[Seb Bonnard]

I was building the kernel module with the wrong gcc version.

I was using gcc version 4.9 instead of the original gcc-4.8 from Ubuntu
LTS Trusty 14.04.5

Sorry for this bug which wasn't one.

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

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

Title:
  dpkg-reconfigure bcmwl-kernel-source : modprobe: ERROR: could not
  insert 'wl': Exec format error

Status in bcmwl package in Ubuntu:
  Invalid

Bug description:
  Hi,

  The bcmwl driver cannot be build upon the linux-header
  v4.4.0-121-generic :

  $ sudo dpkg-reconfigure bcmwl-kernel-source 
  [sudo] password for sebastien:  
  Removing all DKMS Modules
  Done.
  Loading new bcmwl-6.30.223.248+bdcom DKMS files...
  Building only for 4.4.0-121-generic
  Building for architecture x86_64
  Building initial module for 4.4.0-121-generic
  Done.

  wl:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-121-generic/updates/dkms/

  depmod

  DKMS: install completed.
  modprobe: ERROR: could not insert 'wl': Exec format error
  update-initramfs: deferring update (trigger activated)
  Traitement des actions différées (« triggers ») pour initramfs-tools 
(0.103ubuntu4.10) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Traitement des actions différées (« triggers ») pour shim-signed 
(1.32~14.04.2+0.9+1474479173.6c180c6-1ubuntu1) ...
  Secure Boot not enabled on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-121.145~14.04.1-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 26 00:03:47 2018
  InstallationDate: Installed on 2016-09-22 (580 days ago)
  InstallationMedia: Kubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1791030] Re: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for configuration cann

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to
  install/upgrade: package linux-image-extra-4.4.0-131-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  bug during update (???)
  Cordially

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-131-generic 4.4.0-131.157
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   6073 F pulseaudio
   /dev/snd/seq:timidity   1500 F timidity
  Date: Thu Sep  6 09:48:42 2018
  ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=2fd83354-6537-4d4a-9080-0fd25e636274
  InstallationDate: Installed on 2012-07-21 (2237 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic 
root=UUID=e2cf79c0-5225-4f68-9c25-bde3c11e9747 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: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-131-generic 4.4.0-131.157 failed to 
install/upgrade: package linux-image-extra-4.4.0-131-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0301:bd09/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1

[Joseph Salisbury]

** Tags added: cosmic kernel-da-key

** Tags removed: kernel-da-key
** Tags added: kernel-key

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
   Status: Confirmed

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

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

Title:
  Oracle cosmic image does not find broadcom network device in Shape
  VMStandard2.1

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

Bug description:
  I tried to register and boot a cosmic image to verify new changes in it and 
in cloud-init.
  The image failed to bring up networking in the initramfs, and thus failed to 
find iscsi root.
  this could be user error.

  Here is what I did to publish the image.

   - use oci build tool [1].
 following
 
https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage
   - Download a livefs build from cloudware
 https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/
 example: livecd.ubuntu-cpc.oracle_bare_metal.img
 My image had version 20180821.1

   - oci os bucket create --name=smoser-devel
   - oci os object put \
--parallel-upload-count=4 \
--part-size=10 \
--bucket-name=smoser-devel \
--file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \
--name=cosmic-20180821.1.img

   - import the object
  $ oci compute image import from-object \
  --display-name=smoser-cosmic-20180821.1.img \
  --launch-mode=NATIVE \
  --namespace=intcanonical \
  --bucket-name=smoser-devel \
  --name=cosmic-20180821.1.img \
  --source-image-type=QCOW2

  Then I launched from the web UI a VM.Standard2.1.

  --
   https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm

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

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

[Kernel-packages] [Bug 1790688] Re: x86/pti: 32-Bit x86 systems support already available.

[Joseph Salisbury]

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

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

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

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

Title:
  x86/pti: 32-Bit x86 systems support already available.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Linux kernel v4.19 release candidate [1], finally have kernel page-
  table isolation ('PTI', previously known as 'KAISER') support for
  x86_32 architecture. As we know, 'PTI' provides protection against
  attack, known as the "Meltdown" (CVE-2017-5754), that breaks isolation
  between user applications and the operating system etc. However,
  kernel page-table isolation wasn't available on 32-Bit x86 systems.
  Until now.

  So, I would like to ask a question: are there any plans to backport
  kernel page-table isolation patches for Linux kernels available in
  "Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I
  mean x86_32 bit architecture, of course. I'm asking, because it seems,
  that pretty much no developers run 32-bit any more. However, there
  still are many 32-bit users out there.

  For more informations about how 'PTI' was implementing on 32-Bit x86
  architecture, plase check - for example - commit '7757d607c6b31'
  ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for x86_32"). Here are
  messages about 'PTI' support (PATCH v7, v8) for x86_32 [1]. Next,
  'PTI' fixes for x86-32 [2] and more patches related to 'x86/mm/pti'
  [3]. There is also a short report for the first half of the 4.19
  kernel merge window [4].

  I'm sorry for such a long message, but I'm very happy that 'PTI'
  support is already available for x86_32 architecture and I hope, that
  it will be backported to all Ubuntu LTS releases etc.

  Thanks, best regards.
  __

  [1] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03578.html (please see 
every next patches etc.)
  http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03181.html 
  http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html 
  [2] http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05516.html
  [3] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03161.html
  [4] https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)

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

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

[Kernel-packages] [Bug 1790739] Re: kernel 3.13.0-157 breaks ext2/ext3 filesystem with non-zero stride setting and block size less than 4096

[Joseph Salisbury]

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

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

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

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

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

** Tags added: needs-bisect

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

Title:
  kernel 3.13.0-157 breaks ext2/ext3 filesystem with non-zero stride
  setting and block size less than 4096

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

Bug description:
  Kernel 3.13.0-157 causes errors writing to an ext2 or ext3 filesystem with a 
non-zero stride setting.
  The issue does not happen with kernel 3.13.0-155.

  Steps to reproduce:

  root@manager:~# mkdir mnt 

 
  root@manager:~# dd if=/dev/zero of=file.img bs=1MB count=32   

   
  [...]
  root@manager:~# mke2fs -E stride=256 file.img 

   
  [...]
  root@manager:~# mount -o loop file.img mnt/   

   
  root@manager:~# dd if=/dev/zero of=mnt/bigfile bs=1MB count=20

  
  dd: error writing ‘mnt/bigfile’: No space left on device
  16+0 records in
  15+0 records out
  15937536 bytes (16 MB) copied, 0.0780797 s, 204 MB/s
  root@manager:~# df -h
  [...]
  /dev/loop0  30M   16M   13M  56% /root/mnt

  
  The relevant lines from syslog are:
  Sep  4 23:16:40 manager kernel: [ 2385.432802] EXT4-fs (loop0): mounted 
filesystem with ordered data mode. Opts: (null)
  Sep  4 23:19:22 manager kernel: [ 2546.581246] EXT4-fs (loop0): mounting ext2 
file system using the ext4 subsystem
  Sep  4 23:19:22 manager kernel: [ 2546.581610] EXT4-fs (loop0): mounted 
filesystem without journal. Opts: (null)
  Sep  4 23:19:26 manager kernel: [ 2550.695870] EXT4-fs error (device loop0): 
ext4_validate_block_bitmap:376: comm dd: bg 3: block 25714: invalid block bitmap
  Sep  4 23:19:26 manager kernel: [ 2550.720622] EXT4-fs error (device loop0): 
ext4_validate_block_bitmap:376: comm dd: bg 3: block 25714: invalid block bitmap
  Sep  4 23:19:26 manager kernel: [ 2550.723530] EXT4-fs error (device loop0): 
ext4_validate_block_bitmap:376: comm dd: bg 3: block 25714: invalid block bitmap
  [...]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-157-generic 3.13.0-157.207
  ProcVersionSignature: Ubuntu 3.13.0-157.207-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-157-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  4 22:37 seq
   crw-rw 1 root audio 116, 33 Sep  4 22:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Sep  4 23:07:52 2018
  HibernationDevice: RESUME=UUID=025ae749-5b92-41f8-9ae8-fa27251e7e49
  InstallationDate: Installed on 2013-09-26 (1804 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-157-generic 
root=/dev/mapper/hostname--pro-root ro nosplash nomodeset ipv6.disable=0
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-157-generic N/A
   linux-backports-modules-3.13.0-157-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  StagingDrivers: bpctl_mod
  UpgradeStatus: Upgraded to trusty on 2018-04-17 (140 days ago)
  dmi.bios.date: 07/10/2014
  dmi.bios.v

[Kernel-packages] [Bug 1790880] Re: apt-get source linux-image-$(uname -r) does not work on 18.04.1 LTS

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  apt-get source linux-image-$(uname -r) does not work on 18.04.1 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot get the source code and therefore cannot build a driver for
  Ubuntu 18.04.1 LTS

  See link

  https://ubuntuforums.org/showthread.php?t=2397649

  Other people have seen the same problem.

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

-- 
Mailing list: https://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 1790888] Re: touchpad not detected/ not working

[lucian]

Hi,

tested  with Kernel 19, same result.
'kernel-bug-exists-upstream'.
"Confirmed".

it's a new laptop with the1st installation

in AIDA96 windows the HID was identified as
[ Human Interface Devices / I2C HID Device ]
 Device Properties:
Driver Description  I2C HID Device
Driver Date  21/06/2006
Driver Version  10.0.17134.1
Driver Provider  Microsoft
INF File  hidi2c.inf
INF Section  hidi2c_Device.NT
Hardware ID  ACPI\VEN_UNIW&DEV_0001

Is it any manner to force it using  the kernel  I2C-HID driver

thanks

On Thu, 6 Sep 2018 at 18:11, Joseph Salisbury
 wrote:
>
> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.19 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1790888
>
> Title:
>   touchpad not detected/ not working
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   docs attached
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   InstallationDate: Installed on 2018-09-04 (1 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
> (20180725)
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: linux (not installed)
>   Tags:  bionic
>   Uname: Linux 4.18.5-041805-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790888/+subscriptions

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

Title:
  touchpad not detected/ not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  docs attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.5-041805-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1790888] Re: touchpad not detected/ not working

[lucian]

Hi,

tested  with Kernel 19, same result.
'kernel-bug-exists-upstream'.
"Confirmed".

it's a new laptop with the1st installation

in AIDA96 windows the HID was identified as
[ Human Interface Devices / I2C HID Device ]
 Device Properties:
Driver Description  I2C HID Device
Driver Date  21/06/2006
Driver Version  10.0.17134.1
Driver Provider  Microsoft
INF File  hidi2c.inf
INF Section  hidi2c_Device.NT
Hardware ID  ACPI\VEN_UNIW&DEV_0001

Is it any manner to force it using  the kernel  I2C-HID driver

thanks

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

Title:
  touchpad not detected/ not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  docs attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.5-041805-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors

[Giacomo Graziosi]

Did the test on 4.19.0-041900rc2-generic, issue is still there.

** Tags added: bug-exists-upstream

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

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

Title:
  amdgpu.dc dual monitor issues when trying to sleep / power off the
  monitors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a problem with my dual monitor setup on an AMD RX 580: when I lock the 
screen and Gnome try to power off both monitors the following happens:
  1) the second monitor goes to sleep before the first one, this is normal and 
expected because the first monitor has a longer time to sleep
  2) after some seconds the second monitor turn on back again and prevents the 
first one to sleep at all
  3) gnome detects inactivity on the lock screen for some time and try to power 
off the monitors again
  4) step 1 all over again in an infinite loop

  When I login back from the lock screen the windows inside my Gnome
  session can sometimes be rearranged from one screen to the other.

  After discovering this behavior I tried to power off the monitors
  manually with `xset dpms force off` and I can confirm that the same
  happens: the monitors wont really power off because the second one
  turns back on and prevents the first one to sleep.

  My guess was that somehow when the second monitor was turning off it
  delivered some kind of "monitors changed, you should reset" message to
  the GPU which in order did some kind of "reset everything and power on
  the monitors back again" action.

  Searching for a fix to this problem I tried to upgrade my amdgpu mesa
  drivers using the oibaf/graphics-drivers ppa and after this I tried to
  upgrade my whole distribution too, moving from bionic to cosmic.

  Nothing worked.

  In the end I discovered the existence of amdgpu.dc and tried to
  disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did
  the trick but it is still a workaround.

  I'm not sure this is the right place to report this kind of issues but as the 
issue is somehow critical (the first I entered the power on/off loop I didn't 
notice it and my monitor cycled power for two hours) I hope this will help 
other people.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.17.0-9-generic.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,104385b0,00100302'
 Controls  : 50
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100700'
 Controls  : 42
 Simple ctrls  : 6
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2
  InstallationDate: Installed on 2018-09-01 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic
  Uname: Linux 4.17.0-9-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/1790861/+subscriptions

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

[Kernel-packages] [Bug 1790594] Re: The system is not able to detect the touchsreen

[Scorpion]

Yes i can try so this kernel will support the silead module (or touchscreen 
somehow)?
I should use 
`git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
 v4.19-rc2` and the apply the patches?

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

Title:
  The system is not able to detect the touchsreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I' m using a tablet that is sold with Windows 10.
  The firmware extracted from the special driver are already available here 
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
  (I discovered that the Mediacom drivers are the same as those for TrekStor, a 
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at 
SurfTab wintron 7.0 ST70416-6).
  That repository states that i need to recompile the kernel. 
  I don' t know how here 
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
 there is my question about this problem.
  It would be nice if the linux-kernel would support the tablet touchscreen by 
default. 
  My kernel is 4.15.0-33-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vegito 1554 F pulseaudio
   /dev/snd/controlC0:  vegito 1554 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 11
 Simple ctrls  : 1
  Card1.Amixer.info:
   Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
 Mixer name : ''
 Components : ''
 Controls  : 243
 Simple ctrls  : 213
  CurrentDesktop: LXDE
  Date: Tue Sep  4 09:57:45 2018
  HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
  InstallationDate: Installed on 2018-08-21 (13 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDIACOM WinPad 7 W10 - WPW700
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: MC.G.WI71C.MGBMRBA03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1 - Family
  dmi.product.name: WinPad 7 W10 - WPW700
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: MEDIACOM

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

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

[Kernel-packages] [Bug 1788764] Re: linux: 3.13.0-158.208 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-158.208
/trusty-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1788764

Title:
  linux: 3.13.0-158.208 -proposed tracker

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

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: bug 1788765 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1788764/+subscriptions

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

[Kernel-packages] [Bug 1791015] Re: Problems with touchpad

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2


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

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

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

Title:
  Problems with touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Version: Ubuntu 18.04.1 LTS

  Laptop: Satellite R630

  The Touchpad doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruben  1166 F pulseaudio
  Date: Thu Sep  6 09:02:15 2018
  InstallationDate: Installed on 2018-08-12 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite R630
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=79f7d43d-b31f-44aa-9f51-ddb542e69e1b ro quiet splash vt.handoff=1
  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.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.40
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.40:bd07/20/2010:svnTOSHIBA:pnSatelliteR630:pvrPT31LE-00P00HGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: Satellite R630
  dmi.product.version: PT31LE-00P00HGR
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1790905] Re: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to
  install/upgrade: installed linux-image-4.15.0-33-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I don't know what happen after I updated Ubuntu. Now my speakers are
  not working. It shows dummy output in Sound Setting. I tried to search
  on net but none of the solution worked for me. Please help

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-generic:amd64: Remove
   linux-image-generic:amd64: Remove
   linux-image-4.15.0-33-generic:amd64: Remove
   linux-image-unsigned-4.15.0-33-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Sep  5 21:35:12 2018
  ErrorMessage: installed linux-image-4.15.0-33-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=a8ac24cf-125b-48f3-9d3d-8625a57a061c
  InstallationDate: Installed on 2018-07-18 (48 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d45cd3c9-bc33-4ff7-8960-736eb1e90811 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3
  SourcePackage: linux
  Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to 
install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN40WW:bd04/13/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1788686] [NEW] Acer laptop does not boot Ubuntu 16.04.5

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

***
*** Please change package to the appropriate one
***

Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu
16.04.5 LTS fails as per attached screenshots.

This is reproducible.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
Uname: Linux 4.4.0-133-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug 23 15:11:08 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-22 (397 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
Acer laptop does not boot Ubuntu 16.04.5
https://bugs.launchpad.net/bugs/1788686
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 1790594] Re: The system is not able to detect the touchsreen

[Scorpion]

Just installing 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2/linux-headers-4.19.0-041900rc2-generic_4.19.0-041900rc2.201809022230_amd64.deb
 i get an error.
sudo dpkg -i 
linux-headers-4.19.0-041900rc2-generic_4.19.0-041900rc2.201809022230_amd64.deb
(Reading database ... 182777 files and directories currently installed.)
Preparing to unpack 
linux-headers-4.19.0-041900rc2-generic_4.19.0-041900rc2.201809022230_amd64.deb 
...
Unpacking linux-headers-4.19.0-041900rc2-generic 
(4.19.0-041900rc2.201809022230) over (4.19.0-041900rc2.201809022230) ...
dpkg: dependency problems prevent configuration of 
linux-headers-4.19.0-041900rc2-generic:
 linux-headers-4.19.0-041900rc2-generic depends on 
linux-headers-4.19.0-041900rc2; however:
  Package linux-headers-4.19.0-041900rc2 is not installed.

dpkg: error processing package linux-headers-4.19.0-041900rc2-generic 
(--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-4.19.0-041900rc2-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/1790594

Title:
  The system is not able to detect the touchsreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I' m using a tablet that is sold with Windows 10.
  The firmware extracted from the special driver are already available here 
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
  (I discovered that the Mediacom drivers are the same as those for TrekStor, a 
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at 
SurfTab wintron 7.0 ST70416-6).
  That repository states that i need to recompile the kernel. 
  I don' t know how here 
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
 there is my question about this problem.
  It would be nice if the linux-kernel would support the tablet touchscreen by 
default. 
  My kernel is 4.15.0-33-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vegito 1554 F pulseaudio
   /dev/snd/controlC0:  vegito 1554 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 11
 Simple ctrls  : 1
  Card1.Amixer.info:
   Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
 Mixer name : ''
 Components : ''
 Controls  : 243
 Simple ctrls  : 213
  CurrentDesktop: LXDE
  Date: Tue Sep  4 09:57:45 2018
  HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
  InstallationDate: Installed on 2018-08-21 (13 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDIACOM WinPad 7 W10 - WPW700
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: MC.G.WI71C.MGBMRBA03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1 - Family
  dmi.product.name: WinPad 7 W10 - WPW700
  dmi.product.ver

[Kernel-packages] [Bug 1788686] Re: Acer laptop does not boot Ubuntu 16.04.5

[Paul White]

** Package changed: gedit (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/1788686

Title:
  Acer laptop does not boot Ubuntu 16.04.5

Status in linux package in Ubuntu:
  New

Bug description:
  ***
  *** Please change package to the appropriate one
  ***

  Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu
  16.04.5 LTS fails as per attached screenshots.

  This is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 23 15:11:08 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-22 (397 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1791080] Re: Xenial update to 4.4.144 stable release

[Stefan Bader]

Continue Spectre v4 review:
* x86/speculation: Update Speculation Control microcode
  blacklist
  -> skip, we do not carry the blacklist
* x86/speculation: Correct Speculation Control
  microcode blacklist again
  -> skip, again firmware blacklist
* x86/speculation: Clean up various Spectre related
  details
  -> pick, adjusted to match intended goals (low risk
 as this is only removing line breaks or updating
 printks).
* x86/speculation: Add  dependency
  -> skip, no change
* x86/spectre_v2: Don't check microcode versions when
  running under hypervisors
  -> skip, we do not check for bad microcode versions
* x86/speculation: Use IBRS if available before calling
  into firmware
  -> pick, adapted to current environment. We already
 had alternative_msr_write() ported.

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

Title:
  Xenial update to 4.4.144 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.144 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.144 stable release shall be
  applied:

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

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

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

[Ubuntu Kernel Bot]

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 1788686

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

Title:
  Acer laptop does not boot Ubuntu 16.04.5

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ***
  *** Please change package to the appropriate one
  ***

  Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu
  16.04.5 LTS fails as per attached screenshots.

  This is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 23 15:11:08 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-22 (397 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D

[Seth Forshee]

We already had e82f2e31f5597a3de44bd27b7427f577f637c552 as it was part
of 4.18. Added the other and the config update.

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1789934

Title:
  [18.10 FEAT] Add kernel config options for SMC-R/D

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

Bug description:
  Add folliowing options for SMC-R/D

  CONFIG_SMC=m
  CONFIG_SMC_DIAG=m
  CONFIG_ISM=m

  
  Already provided 
  CONFIG_HAVE_PNETID with bugzilla 
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+subscriptions

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

[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer

[Marcelo Cerri]

The 4.4 xenial kernel is not affected by the problem.

** No longer affects: linux (Ubuntu Xenial)

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

Title:
  Bugfix for handling of shadow doorbell buffer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  This request is to pull in the following patch for NVMe bug from
  https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp
  kernel:

  ===
  This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
  function to ensure that the shadow doorbell is written before reading
  EventIdx from memory. This is a critical bugfix for initial patch that
  added support for shadow doorbell into NVMe driver[...].

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

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

[Kernel-packages] [Bug 1781578] Re: Call trace observed while disabling PD on Ubuntu 16.04.4

[dann frazier]

The smartpqi driver is included in the linux-modules deb. If you are
trying to build/use an out-of-tree smartpqi driver (which your taint
flags suggest), please be clear about that. It could quite likely be a
bug in that out-of-tree driver vs. a bug with 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/1781578

Title:
  Call trace observed while disabling PD on Ubuntu 16.04.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am working on smartpqi linux driver for Microsemi.

  We have a storage controller managment application tool to manage storage 
behind our controller. One of the application option what we have is to disable 
physical device(PD).
  During disable PD opertaion, Disable PD command got timedout. Then I observed 
below mentioned call trace in dmesg log.
  Please note we are running IO stress test on the PD which is being disabled.

  Please let me know if there are any known issues specific to Ubuntu kernel 
with respect to this. 
  If its a known issue specific to Ubuntu 16.04.4 distro, does this issue 
already addressed in latest Ubuntu OS distro ?

  Thanks in advance!

  Sincerely,
  Murthy Bhat

  Call trace:
  smartpqi :92:00.0: removed 5:0:2:0 3d1701cf2001 Direct-Access ATA 
ST1000NX0303 AIO+ qd=32
  [ 1199.201495] Buffer I/O error on dev sdk, logical block 244190645, async 
page read
  [ 1343.006515] sdn:
  [ 1358.264503] INFO: task kworker/173:1:1620 blocked for more than 120 
seconds.
  [ 1358.271550] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.278966] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.286806] kworker/173:1 D 0 1620 2 0x
  [ 1358.286832] Workqueue: events pqi_rescan_worker [smartpqi]
  [ 1358.286836] Call trace:
  [ 1358.286844] [] __switch_to+0x90/0xa8
  [ 1358.286855] [] __schedule+0x35c/0x8b0
  [ 1358.286858] [] schedule+0x34/0x90
  [ 1358.286865] [] blk_mq_freeze_queue_wait+0x70/0xd8
  [ 1358.286869] [] blk_mq_freeze_queue+0x28/0x38
  [ 1358.286873] [] blk_freeze_queue+0x20/0x30
  [ 1358.286878] [] blk_cleanup_queue+0x78/0x128
  [ 1358.286883] [] __scsi_remove_device+0x64/0x128
  [ 1358.286884] [] scsi_remove_device+0x30/0x48
  [ 1358.286887] [] scsi_remove_target+0x188/0x1c8
  [ 1358.286899] [] sas_rphy_remove+0x78/0x98 
[scsi_transport_sas]
  [ 1358.286907] [] sas_port_delete+0x38/0x160 
[scsi_transport_sas]
  [ 1358.286918] [] pqi_free_sas_port+0x4c/0x88 [smartpqi]
  [ 1358.286926] [] pqi_remove_sas_device+0x24/0x38 [smartpqi]
  [ 1358.286933] [] pqi_update_device_list+0x520/0x818 
[smartpqi]
  [ 1358.286939] [] pqi_scan_scsi_devices+0x420/0x980 
[smartpqi]
  [ 1358.286946] [] pqi_rescan_worker+0x24/0x30 [smartpqi]
  [ 1358.286955] [] process_one_work+0x14c/0x420
  [ 1358.286957] [] worker_thread+0x12c/0x470
  [ 1358.286961] [] kthread+0x108/0x138
  [ 1358.286963] [] ret_from_fork+0x10/0x30
  [ 1358.287045] INFO: task pain:6788 blocked for more than 120 seconds.
  [ 1358.293326] Tainted: G OE 4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1358.300730] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1358.308567] pain D 0 6788 6633 0x

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

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

[Kernel-packages] [Bug 1788686] Re: Acer laptop does not boot Ubuntu 16.04.5

[peterzay]

Since the laptop cannot be booted, apport cannot be run.


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

Title:
  Acer laptop does not boot Ubuntu 16.04.5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ***
  *** Please change package to the appropriate one
  ***

  Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu
  16.04.5 LTS fails as per attached screenshots.

  This is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 23 15:11:08 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-22 (397 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D

[Andrew Cloke]

** Changed in: ubuntu-z-systems
   Status: Fix Released => 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/1789934

Title:
  [18.10 FEAT] Add kernel config options for SMC-R/D

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Add folliowing options for SMC-R/D

  CONFIG_SMC=m
  CONFIG_SMC_DIAG=m
  CONFIG_ISM=m

  
  Already provided 
  CONFIG_HAVE_PNETID with bugzilla 
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+subscriptions

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

[Kernel-packages] [Bug 1690085]

[kernel]

It appears that selecting the "Typical Current Idle" BIOS option (where
available) eliminates the "freeze when idle" problem (somehow).

That said, it also appears that this is *not* the default.

The need for the option appears to be Linux specific, or at least it is
not needed for W*nd*rs.

That said, I am damned if I can find any documentation for the option,
or any authoritative recommendation for its use with Linux.

So, anyone bitten by this problem may struggle to find their way to
selecting "Typical Current Idle".  Particularly as the symptoms have all
the appearance of a hardware issue -- possibly an overclocking step too
far.

Would it be possible for the Kernel to set whatever the "Typical Current
Idle" BIOS option sets ?  Or invoke some BIOS function to select the
option ?  That way, at least an up to date version of Linux would avoid
this problem "out of the box".

I have been clapping my hands vigorously for some time, but I am coming
to the conclusion that the platform_x86...@kernel-bugs.osdl.org fairy
does not, in fact, exist (or perhaps not in this universe).

While I am practising believing the regulation six impossible things
before breakfast, I note that the platform_x86...@kernel-bugs.osdl.org
fairy would have to be able to communicate with the AMD documentation
fairy... perhaps using a 56k ouija board ?

Finally and FWIW, I tried turning off "rcu_nocbs=0-15" and "Typical
Current Idle", and my Ryzen 7 1800X/ASUS X370-Pro/Linux 4.18/Fedora
froze within hours.  Before the "Typical Current Idle" option became
available, I was running "rcu_nocbs=0-15" (following the advice in this
thread), and my machine froze every week or so.  I have now been running
for some days with "Typical Current Idle" turned back on, but without
the "rcu_nocbs=0-15" voodoo -- so far, so good (as the man said as he
fell past the 7th floor).

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? 

[Kernel-packages] [Bug 1791143] [NEW] Suggestion to make zfsutils-linux a snap

[Sam Van den Eynde]

Public bug reported:

This circumvents the need to keep it on the same major version
throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is
the best approach as well.

Xenial still has zfsutils on generation 0.6, with the module on 0.7.
Even when patches are applied as needed that approach has its
limitations. E.g. the Bionic cycle might possibly see 2 major zfs
releases, who'll say.

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

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

Title:
  Suggestion to make zfsutils-linux a snap

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  This circumvents the need to keep it on the same major version
  throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is
  the best approach as well.

  Xenial still has zfsutils on generation 0.6, with the module on 0.7.
  Even when patches are applied as needed that approach has its
  limitations. E.g. the Bionic cycle might possibly see 2 major zfs
  releases, who'll say.

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

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

[Kernel-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Yotam Benshalom]

I suffer from this issue with gtx770 nvidia card. Annoyingly, this freezes gdm3 
so hard that I cannot even switch to a different tty.
The workaround above (in '/etc/gdm3/custom.conf' uncommenting 
#WaylandEnable=false) works for me.

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

Title:
  Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on
  a desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS; or

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
run:  sudo update-initramfs
and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)

[Kamal Mostafa]

I have added the package containing /usr/bin/cpupower (linux-tools-
common_4.15.0-35.38_all.deb) to the test-kernel download folder, as well
as the other arch-independent packages.

http://kernel.ubuntu.com/~kamal/lp1790636-lp1790602-ppc/linux-tools-
common_4.15.0-35.38_all.deb

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

Title:
  Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
  state disabled (performance)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-09-04
  00:50:14 ==

  The CPUs remain in snooze state on an idle system when only the
  shallow states disabled resulting in increased power consumption.

  The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of  snooze 
to deeper idle state") introduced a timeout for the snooze idle state so that 
it could be eventually be promoted to a deeper idlestate. The snooze 
timeout value is static and set to the target  residency of the next idle 
state, which would train the cpuidle governor to pick the next idle state 
eventually.
  
  The unfortunate side-effect of this is that if the next idle state(s)  is 
disabled, the CPU will forever remain in snooze, despite the fact that the 
system is completely idle, and other deeper idle states are available.
  
  This patch fixes the issue by dynamically setting the snooze timeout  to the 
target residency of the next enabled state on the device.
  
  Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | Nap  | Fast
   0|   8|   0| 96.41|  0.00|  0.00
   0|   8|   1| 96.43|  0.00|  0.00
   0|   8|   2| 96.47|  0.00|  0.00
   0|   8|   3| 96.35|  0.00|  0.00
   0|   8|   4| 96.37|  0.00|  0.00
   0|   8|   5| 96.37|  0.00|  0.00
   0|   8|   6| 96.47|  0.00|  0.00
   0|   8|   7| 96.47|  0.00|  0.00
  
  POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2) 
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | 
stop
   0|  16|   0| 89.79|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   1| 90.12|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   2| 90.21|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
   0|  16|   3| 90.29|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
 0.00
  


  After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | Nap  | Fast
   0|   8|   0| 16.58|  0.00| 77.21
   0|   8|   1| 18.42|  0.00| 75.38
   0|   8|   2|  4.70|  0.00| 94.09
   0|   8|   3| 17.06|  0.00| 81.73
   0|   8|   4|  3.06|  0.00| 95.73
   0|   8|   5|  7.00|  0.00| 96.80
   0|   8|   6|  1.00|  0.00| 98.79
   0|   8|   7|  5.62|  0.00| 94.17
  
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,  
stop2) disabled:
  
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | 
stop
   0|   0|   0|  0.69|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  9.39| 
89.70
   0|   0|   1|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05| 
93.21
   0|   0|   2|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
89.93
   0|   0|   3|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 
93.26

  
  This fix  (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze 
if next state disabled") is in the -next branch of the powerpc tree and 
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions

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

[Kernel-packages] [Bug 1790739] Re: kernel 3.13.0-157 breaks ext2/ext3 filesystem with non-zero stride setting and block size less than 4096

[Ludovico Cavedon]

I tested with 3.13.0-158-generic (from proposed updates) and the problem 
persists, like for 13.0-157-generic .
It does not happen with 3.13.0-155.


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

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

Title:
  kernel 3.13.0-157 breaks ext2/ext3 filesystem with non-zero stride
  setting and block size less than 4096

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

Bug description:
  Kernel 3.13.0-157 causes errors writing to an ext2 or ext3 filesystem with a 
non-zero stride setting.
  The issue does not happen with kernel 3.13.0-155.

  Steps to reproduce:

  root@manager:~# mkdir mnt 

 
  root@manager:~# dd if=/dev/zero of=file.img bs=1MB count=32   

   
  [...]
  root@manager:~# mke2fs -E stride=256 file.img 

   
  [...]
  root@manager:~# mount -o loop file.img mnt/   

   
  root@manager:~# dd if=/dev/zero of=mnt/bigfile bs=1MB count=20

  
  dd: error writing ‘mnt/bigfile’: No space left on device
  16+0 records in
  15+0 records out
  15937536 bytes (16 MB) copied, 0.0780797 s, 204 MB/s
  root@manager:~# df -h
  [...]
  /dev/loop0  30M   16M   13M  56% /root/mnt

  
  The relevant lines from syslog are:
  Sep  4 23:16:40 manager kernel: [ 2385.432802] EXT4-fs (loop0): mounted 
filesystem with ordered data mode. Opts: (null)
  Sep  4 23:19:22 manager kernel: [ 2546.581246] EXT4-fs (loop0): mounting ext2 
file system using the ext4 subsystem
  Sep  4 23:19:22 manager kernel: [ 2546.581610] EXT4-fs (loop0): mounted 
filesystem without journal. Opts: (null)
  Sep  4 23:19:26 manager kernel: [ 2550.695870] EXT4-fs error (device loop0): 
ext4_validate_block_bitmap:376: comm dd: bg 3: block 25714: invalid block bitmap
  Sep  4 23:19:26 manager kernel: [ 2550.720622] EXT4-fs error (device loop0): 
ext4_validate_block_bitmap:376: comm dd: bg 3: block 25714: invalid block bitmap
  Sep  4 23:19:26 manager kernel: [ 2550.723530] EXT4-fs error (device loop0): 
ext4_validate_block_bitmap:376: comm dd: bg 3: block 25714: invalid block bitmap
  [...]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-157-generic 3.13.0-157.207
  ProcVersionSignature: Ubuntu 3.13.0-157.207-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-157-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  4 22:37 seq
   crw-rw 1 root audio 116, 33 Sep  4 22:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Sep  4 23:07:52 2018
  HibernationDevice: RESUME=UUID=025ae749-5b92-41f8-9ae8-fa27251e7e49
  InstallationDate: Installed on 2013-09-26 (1804 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-157-generic 
root=/dev/mapper/hostname--pro-root ro nosplash nomodeset ipv6.disable=0
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-157-generic N/A
   linux-backports-modules-3.13.0-157-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  StagingDrivers: bpctl_mod
  UpgradeStatus: Upgraded to trusty on 2018-04-17 (140 days ago)
  dmi.bios.date: 07/10/2014
  dmi.bios.version: 2.3.3
  dmi.board.name: 0R5KP9
  dmi.board.version: A04
  dmi.chassis.type: 23
  dmi.modalias: 
dmi:bvn:bvr2.3.3:bd07/10/2014:svn:pn:pvr:rvn:rn0R5KP9:rvrA04:cvn:ct23:cvr:

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

-- 
Mailing list

[Kernel-packages] [Bug 1787898] Re: [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

[Gary Chapman]

Our product includes a linux module. In order to build with lp1787898 I
had to modify linux-headers-4.15.0-34-generic (exportroot tree) to copy
(older) s390x built tools in place of the incorrect x86 versions in
linux-headers-4.15.0-34-generic_4.15.0-34.37~lp1787898_s390x.deb:

scripts/sign-file
scripts/mod/mk_elfconfig
scripts/mod/modpost
scripts/basic/bin2c
scripts/basic/fixdep

With this in place, using the linux-modules* and the rest of lp1787898,
Open for Business communication is successful. Specifically all OfB
tests ended successfully, including deactivating a SSC-mode partition
(loaded with an SSC supported appliance) from the Support Element
console, and re-activating. Previously this left the partition in a
failed state (OfB not seen by SE). Here it works as designed.

Please fix linux-
headers-4.15.0-34-generic_4.15.0-34.37~lp1787898_s390x.deb. Would
appreciate a repost here, but this fix must be done for the kernel
release. 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/1787898

Title:
  [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: To boot an IBM Secure Service Container Appliance in an s390
  LPAR. we need to be able to send the Open for Business (OFB) message
  to signal that the appliance is up and running.

  Fix: Set CONFIG_SCLP_OFB=y.

  Regression Potential: The option enables only a few pieces of
  architecture-specific code, so the potential impact is limited.

  ---

  For successfully booting an IBM Secure Service Container Appliance in an s390 
LPAR, we need to be able to send the OFB (Open for Business) message to the 
Support Element to signal when the Appliance is fully up and running.
  Basic support for OFB was added to the kernel with the following commit
  
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688

  The kernel config option CONFIG_SCLP_OFB need to be set

  This update is mandatory for 18.04 , but need to be requested first
  for 18.10

  $ git grep SCLP_OFB
  debian.master/config/annotations:CONFIG_SCLP_OFB  
   policy<{'s390x': 'n'}>
  debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787898/+subscriptions

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

[Kernel-packages] [Bug 952080]

[benshalom]

The machine in question is no longer with me, alas...

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

Title:
  laptop immediately resumes after sending to standby

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  when i shut the lid of the laptop down or click on standby in the menu I 
expect the system to stand by and stay there till it gets a signal by me. 
However, the system immediately resumes after it did the normal 
standby-procedure. I didnt give any signal (not even touching the mouse).
  it does a normal resume, means everything works fine but the waiting for a 
signal.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  flo1893 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xf9f78000 irq 23'
     Mixer name : 'Nvidia MCP79/7A HDMI'
     Components : 'HDA:10ec0269,104383ce,0014 
HDA:10de0007,10de0101,00100100'
     Controls  : 21
     Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: ASUSTeK Computer INC. 1201N
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic 
root=UUID=ee27b24b-5962-4d50-8835-a53bcd480bf4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-17-generic N/A
   linux-backports-modules-3.2.0-17-generic  N/A
   linux-firmware1.71
  Tags:  precise
  Uname: Linux 3.2.0-17-generic i686
  UpgradeStatus: Upgraded to precise on 2012-03-11 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0326
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1201N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0326:bd04/29/2010:svnASUSTeKComputerINC.:pn1201N:pvrx.x:rvnASUSTeKComputerINC.:rn1201N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1201N
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Kernel-packages] [Bug 952080]

[pmenzel+bugzilla.kernel.org]

Ben, Alan, Rafael, could you please close it then?

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

Title:
  laptop immediately resumes after sending to standby

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  when i shut the lid of the laptop down or click on standby in the menu I 
expect the system to stand by and stay there till it gets a signal by me. 
However, the system immediately resumes after it did the normal 
standby-procedure. I didnt give any signal (not even touching the mouse).
  it does a normal resume, means everything works fine but the waiting for a 
signal.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  flo1893 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xf9f78000 irq 23'
     Mixer name : 'Nvidia MCP79/7A HDMI'
     Components : 'HDA:10ec0269,104383ce,0014 
HDA:10de0007,10de0101,00100100'
     Controls  : 21
     Simple ctrls  : 10
  DistroRelease: Ubuntu 12.04
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: ASUSTeK Computer INC. 1201N
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic 
root=UUID=ee27b24b-5962-4d50-8835-a53bcd480bf4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-17-generic N/A
   linux-backports-modules-3.2.0-17-generic  N/A
   linux-firmware1.71
  Tags:  precise
  Uname: Linux 3.2.0-17-generic i686
  UpgradeStatus: Upgraded to precise on 2012-03-11 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0326
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1201N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0326:bd04/29/2010:svnASUSTeKComputerINC.:pn1201N:pvrx.x:rvnASUSTeKComputerINC.:rn1201N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1201N
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Kernel-packages] [Bug 1791126] Re: L1TF Vulnerable

[Steve Beattie]

*** This bug is a duplicate of bug 1788563 ***
https://bugs.launchpad.net/bugs/1788563

>From your dmesg:

  L1TF: System has more than MAX_PA/2 memory. L1TF mitigation not
effective.

Marking this as a duplicate of LP: #1788563 . Please add any additional
comments there, thanks.

** Information type changed from Private Security to Public Security

** This bug has been marked a duplicate of bug 1788563
   L1TF mitigation not effective

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

Title:
  L1TF Vulnerable

Status in linux package in Ubuntu:
  New

Bug description:
  My xenial system with intel-microcode 3.20180807a.0ubuntu0.16.04.1 and
  linux-image-4.4.0-134-generic 4.4.0-134.160, with an Intel(R) Xeon(R)
  CPU E3-1220 V2 @ 3.10GHz, and "cat
  /sys/devices/system/cpu/vulnerabilities/l1tf" still reports
  "Vulnerable".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-134-generic 4.4.0-134.160
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  6 15:11 seq
   crw-rw 1 root audio 116, 33 Sep  6 15:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Thu Sep  6 18:01:09 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: Dell Inc. PowerEdge R210 II
  PciMultimedia:
   
  ProcEnviron:
   LC_CTYPE=UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 
BOOT_IMAGE=images/mutu/pxe_xenial_docker_web_multi/releases/vmlinuz-current-generic
 
initrd=images/mutu/pxe_xenial_docker_web_multi/releases/initrd.img-current-generic
 netboot=nonempty boot=live nouser 
fetch=http://10.41.2.6/images/mutu/pxe_xenial_docker_web_multi/releases/filesystem-current-generic.squashfs
 ethdevice-timeout=180 flex_pxelinux_hostname=pf42 noplymouth text nosplash 
flex_base_url=http://10.41.2.6/images/mutu/pxe_xenial_docker_web_multi/ 
ip=10.41.2.199:10.41.2.6:10.41.2.70:255.255.255.0 BOOTIF=01-d4-ae-52-ce-97-6a
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.1
  dmi.board.name: 03X6X0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.1:bd09/13/2013:svnDellInc.:pnPowerEdgeR210II:pvr:rvnDellInc.:rn03X6X0:rvrA06:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R210 II
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1787782] Re: Hanging keys on Thinkpad

[Ludwig S.]

I didn't have access to internet for a while. Now I checked it with the
upstream kernel v4.18.6. The bug still exists.

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Hanging keys on Thinkpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 18.04 the keys of my Thinkpad E480 are hanging very
  often. Then, instead of pressed once, the key seems to be not released
  and pressed continuously until another key is pressed. I have
  described the behavior in more detail under
  https://askubuntu.com/questions/1051508/hanging-keys-under-
  ubuntu-18-04.

  It does not occur when I boot in Windows or Ubuntu 16.04, so it is not 
related to the hardware.
  It does not occur when I plug in an external keyboard, so it is not related 
to general Ubuntu keyboard settings.
  It does not occur when the power cable (USB-C) is unplugged, only when t is 
plugged in. 

  /var/log/syslog logs the following when the cable is plugged in:
  "kernel: [ 9821.899727] thinkpad_acpi: EC reports that Thermal Table has 
changed"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ludwig 1919 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 00:21:56 2018
  InstallationDate: Installed on 2018-05-02 (108 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:2113 Acer, Inc 
   Bus 001 Device 002: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KQS00100
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=2ce0f255-4f53-4437-90ad-5e64f5a31b0f ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQS00100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET30W(1.07):bd11/27/2017:svnLENOVO:pn20KQS00100:pvrThinkPadE480:rvnLENOVO:rn20KQS00100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQS00100
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1785715] Re: ubuntu hynix ssd I/O Errors after some minutes

[Revisor]

Unfortunately i still couldnt get rid of the problem. Im still in the
state where everything works fine as long as i do not close the lid or
plug in AC adapter. Whenever i do that it reliably hangs and i cant do
anything anymore (not change to another TTY or do any keyboard input, so
i have to 7sec power-button-push to kill it). And still i cannot boot
via my currently installed default kernel (hangs at login-screen), but
have to enter root shell, exit it and then resume boot.

Was anyone able to reproduce it?
Do you think using an older linux kernel might fix it? (as from reading the 
other reports it seems like the kernel is the problem [in combination with my 
hardware]).

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

Title:
  ubuntu hynix ssd I/O Errors after some minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Maybe similar to Bug 1678184
  Im working on ubuntu 18.04 (with Kernel 4.15.0-29-generic) on a dell XPS 
15-9560
  After 20 - 180 Minutes the graphical interface hangs up (i can switch 
workspaces, but not much else) and entering commands like "ls" yields bash: 
input/output error
  Reboot is impossible via the command or the button. Short click on power 
button gives me a TTY like view prompting errors for nvme0 ext4 file system 
errors (i will post more exact text on next hangup)

  The hangups appear randomly, but often during shutting the lid or plugging in 
power cable, which makes me thing it might be something with ssd power states.
  For that reason i added grub parameters like 
"nvme_core.default_ps_max_latency_us=3000" (see Bug 1678184) and ended up fully 
disabling APST by setting it to 0, but the bug still occured.

  sudo nvme id-ctrl /dev/nvme0 yields:
  NVME Identify Controller:
  vid : 0x1c5c
  ssvid   : 0x1c5c
  sn  : EJ75N621210105PBR   
  mn  : PC300 NVMe SK hynix 1TB 
  fr  : 20005A00
  rab : 1
  ieee: ace42e
  cmic: 0
  mdts: 5
  cntlid  : 0
  ver : 10200
  rtd3r   : 90f560
  rtd3e   : ea60
  oaes: 0
  ctratt  : 0
  oacs: 0x16
  acl : 3
  aerl: 3
  frmw: 0x16
  lpa : 0x2
  elpe: 254
  npss: 4
  avscc   : 0x1
  apsta   : 0x1
  wctemp  : 361
  cctemp  : 363
  mtfa: 0
  hmpre   : 0
  hmmin   : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs   : 0
  edstt   : 60
  dsto: 1
  fwug: 0
  kas : 0
  hctma   : 0
  mntmt   : 0
  mxtmt   : 0
  sanicap : 0
  hmminds : 0
  hmmaxd  : 0
  sqes: 0x66
  cqes: 0x44
  maxcmd  : 0
  nn  : 1
  oncs: 0x1e
  fuses   : 0
  fna : 0
  vwc : 0x1
  awun: 255
  awupf   : 0
  nvscc   : 1
  acwu: 0
  sgls: 0
  subnqn  : 
  ioccsz  : 0
  iorcsz  : 0
  icdoff  : 0
  ctrattr : 0
  msdbd   : 0
  ps0 : mp:5.87W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps1 : mp:2.40W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps2 : mp:1.90W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps3 : mp:0.1000W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps4 : mp:0.0060W non-operational enlat:1000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-

  
  sudo nvme get-feature -f 0x0c -H /dev/nvme0 yields:
  get-feature:0xc (Autonomous Power State Transition), Current value:
Autonomous Power State Transition Enable (APSTE): Disabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
... and so on ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  revisor1593 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1bc0493d-0592-40d4-b0f4-938fbe12a990
  InstallationDate: Installed on 2018-07-12 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_I

[Kernel-packages] [Bug 1790594] Re: The system is not able to detect the touchsreen

[Scorpion]

I used git://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-crack v4.19-rc2

There isn' t the silead_dmi.c file  in v4.19-rc2/drivers/platform/x86.

Before i used sudo apt install linux-source-4.15.0 in in that folder i
have the silead_dmi.c file.

which i modified to use the firmware 
(https://github.com/onitake/gsl-firmware/blob/master/firmware/linux/silead/gsl1686-surftab-wintron70-st70416-6.fw)
 that i put in the tablet in /lib/firmware/silead.
And i made a custom kernel.

But i had no success the silead is loading the backup firmware 
(/lib/firmware/mssl1680.fw is the same firmware of github with the backup 
name). 
So the touchscreen now is detected but is totally unusable.
This is the section of the silead_dmi.c that is not working:
{
/* Mediacom WinPad 7.0 W700 */
.driver_data = (void *)&mediacom_w700_data,
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "INSYDE Corp."),
DMI_MATCH(DMI_PRODUCT_NAME, "WinPad 7 W10 - WPW700"),
DMI_MATCH(DMI_BIOS_VERSION, "MC.G.WI71C.MGBMRBA03"),
},
},
I used dmidecode to find the value of the filed.

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

Title:
  The system is not able to detect the touchsreen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I' m using a tablet that is sold with Windows 10.
  The firmware extracted from the special driver are already available here 
https://github.com/onitake/gsl-firmware/tree/master/firmware/trekstor/surftab7old.
  (I discovered that the Mediacom drivers are the same as those for TrekStor, a 
company that also works with Mediacom.Mediacom Winpad 7.0 W700 corresponds at 
SurfTab wintron 7.0 ST70416-6).
  That repository states that i need to recompile the kernel. 
  I don' t know how here 
https://unix.stackexchange.com/questions/466571/recompile-a-kernel-including-a-firmware?noredirect=1#comment850048_466571
 there is my question about this problem.
  It would be nice if the linux-kernel would support the tablet touchscreen by 
default. 
  My kernel is 4.15.0-33-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: bytcrrt5651 [bytcr-rt5651], device 0: 3 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vegito 1554 F pulseaudio
   /dev/snd/controlC0:  vegito 1554 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 11
 Simple ctrls  : 1
  Card1.Amixer.info:
   Card hw:1 'bytcrrt5651'/'bytcr-rt5651'
 Mixer name : ''
 Components : ''
 Controls  : 243
 Simple ctrls  : 213
  CurrentDesktop: LXDE
  Date: Tue Sep  4 09:57:45 2018
  HibernationDevice: RESUME=UUID=f8f953f2-ceb9-4989-9564-a4ba2fed3fd4
  InstallationDate: Installed on 2018-08-21 (13 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDIACOM WinPad 7 W10 - WPW700
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: MC.G.WI71C.MGBMRBA03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrMC.G.WI71C.MGBMRBA03:bd11/16/2015:svnMEDIACOM:pnWinPad7W10-WPW700:pvrType1-TBDbyOEM:rvnType2-BoardManuf

[Kernel-packages] [Bug 1788563] Re: L1TF mitigation not effective

[Steve Beattie]

It's possible this issue may have been addressed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4

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

Title:
  L1TF mitigation not effective

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Thinkpad W530 system with 32 GB RAM

  dmesg | grep -i l1tf
  [0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation 
not effective.
  [ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html 
for details.

  Related:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1105536

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgera  2809 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 23 03:38:40 2018
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 24382LU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24382LU
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 24382LU
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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