[Kernel-packages] [Bug 1751202] Re: test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on Bionic

[Po-Hsu Lin]

** Summary changed:

- test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on AMD64 
Bionic
+ test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on Bionic

** Description changed:

+ This issue could be found on AMD64, ppc64le, ARM64, s390x (not sure about 
i386, which was not tested because of the deployment issue in the last cycle)
  Steps:
-  1. Deploy an AMD64 system with Bionic
-  2. sudo apt-get install git python-minimal -y
-  3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
-  4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
-  5. rm -fr autotest/client/tests
-  6. ln -sf ~/autotest-client-tests autotest/client/tests
-  7. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_qrt_kernel_security/control
+  1. Deploy an AMD64 system with Bionic
+  2. sudo apt-get install git python-minimal -y
+  3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
+  4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
+  5. rm -fr autotest/client/tests
+  6. ln -sf ~/autotest-client-tests autotest/client/tests
+  7. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_qrt_kernel_security/control
  
-   ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
-   kernel addresses in kallsyms and modules are zeroed out
-   --
-   Traceback (most recent call last):
- File "./test-kernel-security.py", line 1508, in 
test_095_kernel_symbols_missing
-   self._check_pK_files(expected)
- File "./test-kernel-security.py", line 1440, in _check_pK_files
-   expected)
- File "./test-kernel-security.py", line 1401, in _read_twice
-   self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % 
(filename, address))
-   ValueError: invalid literal for int() with base 16: '(null)'
+   ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
+   kernel addresses in kallsyms and modules are zeroed out
+   --
+   Traceback (most recent call last):
+ File "./test-kernel-security.py", line 1508, in 
test_095_kernel_symbols_missing
+   self._check_pK_files(expected)
+ File "./test-kernel-security.py", line 1440, in _check_pK_files
+   expected)
+ File "./test-kernel-security.py", line 1401, in _read_twice
+   self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % 
(filename, address))
+   ValueError: invalid literal for int() with base 16: '(null)'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
-  crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
+  crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  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:
  CurrentDmesg:
-  
+ 
  Date: Fri Feb 23 06:57:48 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R320
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-10-generic N/A
-  linux-backports-modules-4.15.0-10-generic  N/A
-  linux-firmware 1.171
+  linux-restricted-modules-4.15.0-10-generic N/A
+  linux-backports-modules-4.15.0-10-generic  N/A
+  linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  

[Kernel-packages] [Bug 1751207] Re: test_072_config_security_apparmor in ubuntu_qrt_kernel_security failed on AMD64 Bionic

[Po-Hsu Lin]

** Description changed:

+ This issue could be found on AMD64, ppc64le, ARM64, s390x (not sure
+ about i386, which was not tested because of the deployment issue in the
+ last cycle)
+ 
  Result:
-   FAIL: test_072_config_security_apparmor (__main__.KernelSecurityTest)
-   CONFIG_SECURITY_APPARMOR enabled
-   --
-   Traceback (most recent call last):
- File "./test-kernel-security.py", line 676, in 
test_072_config_security_apparmor
-   self.assertEqual(self._get_config(default_apparmor_option), 'y')
-   AssertionError: None != 'y'
-   
+   FAIL: test_072_config_security_apparmor (__main__.KernelSecurityTest)
+   CONFIG_SECURITY_APPARMOR enabled
+   --
+   Traceback (most recent call last):
+ File "./test-kernel-security.py", line 676, in 
test_072_config_security_apparmor
+   self.assertEqual(self._get_config(default_apparmor_option), 'y')
+   AssertionError: None != 'y'
+ 
  For the config in Bionic:
- $ grep -i apparmor /boot/config-4.15.0-10-generic 
+ $ grep -i apparmor /boot/config-4.15.0-10-generic
  CONFIG_SECURITY_APPARMOR=y
  CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
  CONFIG_SECURITY_APPARMOR_HASH=y
  CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
  # CONFIG_SECURITY_APPARMOR_DEBUG is not set
  CONFIG_DEFAULT_SECURITY_APPARMOR=y
  CONFIG_DEFAULT_SECURITY="apparmor"
  
  And for the code itself:
- # Hardy and newer (Gutsy was a direct patch)
- def test_072_config_security_apparmor(self):
- '''CONFIG_SECURITY_APPARMOR enabled'''
+ # Hardy and newer (Gutsy was a direct patch)
+ def test_072_config_security_apparmor(self):
+ '''CONFIG_SECURITY_APPARMOR enabled'''
  
- default_apparmor_option = 'DEFAULT_SECURITY_APPARMOR'
- if self.kernel_at_least('4.13'):
- default_apparmor_option = 'SECURITY_APPARMOR_STACKED'
+ default_apparmor_option = 'DEFAULT_SECURITY_APPARMOR'
+ if self.kernel_at_least('4.13'):
+ default_apparmor_option = 'SECURITY_APPARMOR_STACKED'
  
- self.assertEqual(self._get_config('SECURITY_APPARMOR'), 'y')
- self.assertEqual(self._get_config(default_apparmor_option), 'y')
- 
self.assertEqual(self._get_config('SECURITY_APPARMOR_BOOTPARAM_VALUE'), '1')
+ self.assertEqual(self._get_config('SECURITY_APPARMOR'), 'y')
+ self.assertEqual(self._get_config(default_apparmor_option), 'y')
+ 
self.assertEqual(self._get_config('SECURITY_APPARMOR_BOOTPARAM_VALUE'), '1')
  
- 
- It's using CONFIG_DEFAULT_SECURITY_APPARMOR=y again in 4.15 kernel. Not sure 
if this is expected but I think this is the cause.
+ It's using CONFIG_DEFAULT_SECURITY_APPARMOR=y again in 4.15 kernel. Not
+ sure if this is expected but I think this is the cause.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
-  crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
+  crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  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:
  CurrentDmesg:
-  
+ 
  Date: Fri Feb 23 07:11:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R320
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-10-generic N/A
-  linux-backports-modules-4.15.0-10-generic  N/A
-  linux-firmware 1.171
+  linux-restricted-modules-4.15.0-10-generic N/A
+  linux-backports-modules-4.15.0-10-generic  N/A
+  linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

O.k., confirming that this series of patches fixes the issue:

~/linux$ git log --oneline|head -3
bc6d6fd2f916 i40e: Add programming descriptors to cleaned_count
69949b3bd674 i40e: Fix memory leak related filter programming status
b32038eb34ee UBUNTU: Ubuntu-4.13.0-32.35

Can you build the same thing on top of the latest 4.13 set? Seems some
special gcc foo is needed to make the retpoline stuff working there

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

[ChristianEhrhardt]

I think there is no general "mirror all" policy.
It just seems to me that this is requiring an architecture expert which would 
be at IBM.

I'll subscribe manoj/jfh and let them decide.

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

Title:
  ubuntu-kvm-unit test failed with emulator test on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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

[Kernel-packages] [Bug 1751207] 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 1751207

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

Title:
  test_072_config_security_apparmor in ubuntu_qrt_kernel_security failed
  on AMD64 Bionic

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue could be found on AMD64, ppc64le, ARM64, s390x (not sure
  about i386, which was not tested because of the deployment issue in
  the last cycle)

  Result:
    FAIL: test_072_config_security_apparmor (__main__.KernelSecurityTest)
    CONFIG_SECURITY_APPARMOR enabled
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 676, in 
test_072_config_security_apparmor
    self.assertEqual(self._get_config(default_apparmor_option), 'y')
    AssertionError: None != 'y'

  For the config in Bionic:
  $ grep -i apparmor /boot/config-4.15.0-10-generic
  CONFIG_SECURITY_APPARMOR=y
  CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
  CONFIG_SECURITY_APPARMOR_HASH=y
  CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
  # CONFIG_SECURITY_APPARMOR_DEBUG is not set
  CONFIG_DEFAULT_SECURITY_APPARMOR=y
  CONFIG_DEFAULT_SECURITY="apparmor"

  And for the code itself:
  # Hardy and newer (Gutsy was a direct patch)
  def test_072_config_security_apparmor(self):
  '''CONFIG_SECURITY_APPARMOR enabled'''

  default_apparmor_option = 'DEFAULT_SECURITY_APPARMOR'
  if self.kernel_at_least('4.13'):
  default_apparmor_option = 'SECURITY_APPARMOR_STACKED'

  self.assertEqual(self._get_config('SECURITY_APPARMOR'), 'y')
  self.assertEqual(self._get_config(default_apparmor_option), 'y')
  
self.assertEqual(self._get_config('SECURITY_APPARMOR_BOOTPARAM_VALUE'), '1')

  It's using CONFIG_DEFAULT_SECURITY_APPARMOR=y again in 4.15 kernel.
  Not sure if this is expected but I think this is the cause.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
   crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  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:
  CurrentDmesg:

  Date: Fri Feb 23 07:11:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R320
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751202] 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 1751202

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

Title:
  test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed
  on Bionic

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue could be found on AMD64, ppc64le, ARM64, s390x (not sure
  about i386, which was not tested because of the deployment issue in
  the last cycle)

  Steps:
   1. Deploy an AMD64 system with Bionic
   2. sudo apt-get install git python-minimal -y
   3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   5. rm -fr autotest/client/tests
   6. ln -sf ~/autotest-client-tests autotest/client/tests
   7. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_qrt_kernel_security/control

    ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
    kernel addresses in kallsyms and modules are zeroed out
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 1508, in 
test_095_kernel_symbols_missing
    self._check_pK_files(expected)
  File "./test-kernel-security.py", line 1440, in _check_pK_files
    expected)
  File "./test-kernel-security.py", line 1401, in _read_twice
    self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % 
(filename, address))
    ValueError: invalid literal for int() with base 16: '(null)'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
   crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  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:
  CurrentDmesg:

  Date: Fri Feb 23 06:57:48 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R320
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751207] [NEW] test_072_config_security_apparmor in ubuntu_qrt_kernel_security failed on AMD64 Bionic

[Po-Hsu Lin]

Public bug reported:

Result:
  FAIL: test_072_config_security_apparmor (__main__.KernelSecurityTest)
  CONFIG_SECURITY_APPARMOR enabled
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 676, in 
test_072_config_security_apparmor
  self.assertEqual(self._get_config(default_apparmor_option), 'y')
  AssertionError: None != 'y'
  
For the config in Bionic:
$ grep -i apparmor /boot/config-4.15.0-10-generic 
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
CONFIG_SECURITY_APPARMOR_HASH=y
CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
# CONFIG_SECURITY_APPARMOR_DEBUG is not set
CONFIG_DEFAULT_SECURITY_APPARMOR=y
CONFIG_DEFAULT_SECURITY="apparmor"

And for the code itself:
# Hardy and newer (Gutsy was a direct patch)
def test_072_config_security_apparmor(self):
'''CONFIG_SECURITY_APPARMOR enabled'''

default_apparmor_option = 'DEFAULT_SECURITY_APPARMOR'
if self.kernel_at_least('4.13'):
default_apparmor_option = 'SECURITY_APPARMOR_STACKED'

self.assertEqual(self._get_config('SECURITY_APPARMOR'), 'y')
self.assertEqual(self._get_config(default_apparmor_option), 'y')
self.assertEqual(self._get_config('SECURITY_APPARMOR_BOOTPARAM_VALUE'), 
'1')


It's using CONFIG_DEFAULT_SECURITY_APPARMOR=y again in 4.15 kernel. Not sure if 
this is expected but I think this is the cause.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
 crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.8-0ubuntu10
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:
CurrentDmesg:
 
Date: Fri Feb 23 07:11:44 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R320
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-10-generic N/A
 linux-backports-modules-4.15.0-10-generic  N/A
 linux-firmware 1.171
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.4
dmi.board.name: 0DY523
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R320
dmi.sys.vendor: Dell Inc.

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug bionic uec-images

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  test_072_config_security_apparmor in ubuntu_qrt_kernel_security failed
  on AMD64 Bionic

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Result:
FAIL: test_072_config_security_apparmor (__main__.KernelSecurityTest)
CONFIG_SECURITY_APPARMOR enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 676, in 
test_072_config_security_apparmor
self.assertEqual(self._get_config(default_apparmor_option), 'y')
AssertionError: None != 'y'

  For the config in Bionic:
  $ grep -i apparmor /boot/config-4.15.0-10-generic 
  CONFIG_SECURITY_APPARMOR=y
  CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
  CONFIG_SECURITY_APPARMOR_HASH=y
  CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
  # CONFIG_SECURITY_APPARMOR_DEBUG is not set
  CONFIG_DEFAULT_SECURITY_APPARMOR=y
  CONFIG_DEFAULT_SECURITY="apparmor"

  And for the code itself:
  # Hardy and newer (Gutsy was a direct patch)
  def test_072_config_security_apparmor(self):
  '''CONFIG_SECURITY_APPARMOR enabled'''

  default_apparmor_option = 'DEFAULT_SECURITY_APPARMOR'
  if self.kernel_at_least('4.13'):
  

[Kernel-packages] [Bug 1751202] [NEW] test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on AMD64 Bionic

[Po-Hsu Lin]

Public bug reported:

Steps:
 1. Deploy an AMD64 system with Bionic
 2. sudo apt-get install git python-minimal -y
 3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
 4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
 5. rm -fr autotest/client/tests
 6. ln -sf ~/autotest-client-tests autotest/client/tests
 7. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
  kernel addresses in kallsyms and modules are zeroed out
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 1508, in 
test_095_kernel_symbols_missing
  self._check_pK_files(expected)
File "./test-kernel-security.py", line 1440, in _check_pK_files
  expected)
File "./test-kernel-security.py", line 1401, in _read_twice
  self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % 
(filename, address))
  ValueError: invalid literal for int() with base 16: '(null)'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb 23 04:53 seq
 crw-rw 1 root audio 116, 33 Feb 23 04:53 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.8-0ubuntu10
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:
CurrentDmesg:
 
Date: Fri Feb 23 06:57:48 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R320
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-10-generic N/A
 linux-backports-modules-4.15.0-10-generic  N/A
 linux-firmware 1.171
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.4
dmi.board.name: 0DY523
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R320
dmi.sys.vendor: Dell Inc.

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug bionic uec-images

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed
  on AMD64 Bionic

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Steps:
   1. Deploy an AMD64 system with Bionic
   2. sudo apt-get install git python-minimal -y
   3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   5. rm -fr autotest/client/tests
   6. ln -sf ~/autotest-client-tests autotest/client/tests
   7. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_qrt_kernel_security/control

ERROR: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
kernel addresses in kallsyms and modules are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1508, in 
test_095_kernel_symbols_missing
self._check_pK_files(expected)
  File "./test-kernel-security.py", line 1440, in _check_pK_files
expected)
  File "./test-kernel-security.py", line 1401, in _read_twice
self.assertEqual(expected, 0 == int(address, 16), "%s: user saw %s" % 
(filename, address))
ValueError: invalid literal for int() with base 16: '(null)'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Mythological]

Kaan Akşit:  You are going down the same rabbit hole that I did and it
won't work, and will just mess up your system.  The problem is not the
nVidia driver, it's the kernel upgrade.  Go to the thread at
https://ubuntuforums.org/showthread.php?t=2385621=13742281#post13742281
and you will see what you need to do.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Kaan Akşit]

Having the exact same issue with nvidia-390 package at my Ubuntu 16.04,
rolled back to nvidia-387 and had the same issue. And later I rolled
back nvidia-384, and still the same issue.

Then I downloaded NVIDIA-Linux-x86_64-384.111.run from Nvidia's website
to see if I am able to get it up and running as Jason claimed in his
earlier post. Started installing the manual driver by killing the x
server. It prompt as unable to load the kernel module 'Nvidia.ko'.
Simply installation failed.

I am curious to find out how Jason switched to that version of Nvidia
drivers.

So for the one last time I tried removing all nvidia-* packages, and
tried installin nvidia-331 package from the repository... and the result
is the same on my end.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1675395] Re: ubuntu_bpf test fail to build on aarch64 system

[Po-Hsu Lin]

** Tags added: 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/1675395

Title:
  ubuntu_bpf test fail to build on aarch64 system

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

Bug description:
  # make
  for TARGET in bpf; do \
make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
  In file included from test_verifier.c:23:0:
  /usr/include/linux/bpf_perf_event.h:13:17: error: field ‘regs’ has incomplete 
type
struct pt_regs regs;
   ^~~~
  : recipe for target 'test_verifier' failed
  make[1]: *** [test_verifier] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  Makefile:18: recipe for target 'all' failed
  make: *** [all] Error 2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  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:
  Date: Thu Mar 23 12:23:15 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT

[Alvin Huan]

** Changed in: amd
   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/1742759

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1742759/+subscriptions

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[chipschap]

FWIW some NVIDIA-related changes were apparently made in 114:

2018-02-09 - Khalid Elmously 
linux (4.4.0-114.137) xenial; urgency=medium
* linux: 4.4.0-114.137 -proposed tracker (LP: #1748484)
* ALSA backport missing NVIDIA GPU codec IDs to patch table to
Ubuntu 16.04 LTS Kernel (LP: #1744117)
- ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table
* Shutdown hang on 16.04 with iscsi targets (LP: #1569925)

I don't know if this caused the problem, but regressing from 116 to 112
also solved it for me (after about an hour of utter frustration).

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

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

[bugproxy]

--- Comment From shriy...@in.ibm.com 2018-02-22 03:29 EDT---
Hi ,

Trying to setup the kernel : facing this issue :

dpkg: dependency problems prevent configuration of 
linux-image-extra-4.13.0-17-generic:
linux-image-extra-4.13.0-17-generic depends on linux-image-4.13.0-17-generic; 
however:
Package linux-image-4.13.0-17-generic is not installed.

dpkg: error processing package linux-image-extra-4.13.0-17-generic (--install):
dependency problems - leaving unconfigured
Setting up linux-libc-dev:ppc64el (4.13.0-17.20) ...
Setting up linux-source-4.13.0 (4.13.0-17.20) ...
dpkg: dependency problems prevent configuration of linux-tools-4.13.0-17:
linux-tools-4.13.0-17 depends on libbinutils (<< 2.29.2); however:
Version of libbinutils:ppc64el on system is 2.30-5ubuntu1.

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

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

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

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Scott Moser]

** Attachment added: "installation console log"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060821/+files/install-serial.log

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Scott Moser]

** Attachment added: "first boot console log"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060822/+files/boot-serial.log

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Scott Moser]

>From the install log you can see that we install grub2 at 
>2.02~beta2-36ubuntu3.17.
   ..
   Unpacking grub2-common (2.02~beta2-36ubuntu3.17)
   ..


'dpkg-reconfigure grub-pc' and 'grub-install /dev/vda' are run

And also:

  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-116-generic 
/boot/vmlinuz-4.4.0-116-generic
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-4.4.0-9025-euclid
  Found initrd image: /boot/initrd.img-4.4.0-9025-euclid
  Found linux image: /boot/vmlinuz-4.4.0-116-generic
  Found initrd image: /boot/initrd.img-4.4.0-116-generic
/run/lvm/lvmetad.socket: connect failed: No such file or directory

Then during boot we see

[0.00] Command line:
BOOT_IMAGE=/ROOT/zfsroot@/boot/vmlinuz-4.4.0-9025-euclid
root=ZFS=rpool/ROOT/zfsroot ro console=ttyS0

So we have successfully booted from root on a zfs system.





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

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Scott Moser]

Hi.
I've confirmed this fix by using curtin's "vmtest" test harness.

I've applied the attached patch to curtin at 82622f129b.
The patch does:
a.) remove the work arounds we had in place to make zfs root work on xenial.
b.) enable proposed

Then I've run an install of a system that does a installation of zfs on root.
   ./tools/jenkins-runner 
examples/tests/zfsroot.yaml:tests/vmtests/test_zfsroot.py:XenialGATestZfsRoot

I'll attach the boot and install logs of that system also.



** Patch added: "applied curtin diff"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/+attachment/5060820/+files/curtin.diff

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions

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

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT

[Zhang Junwei]

Verified the hwe kernel 4.13.0-36.40~16.04.1, including the fix patch.
The WestenXT is able to be controlled by pm-runtime normally.

Jerry

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

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1742759/+subscriptions

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Scott Moser]

I've removed the verification-failed-xenial tag.
The problem reported in bug 1750732 may be related to a grub upgrade, but
surely is not related to this specific grub upgrade.

Please see the changes 
 
http://launchpadlibrarian.net/354651271/grub2_2.02~beta2-36ubuntu3.16_2.02~beta2-36ubuntu3.17.diff.gz
for justification.

The only change made there is a 'setenv' call.


** Tags removed: verification-failed-xenial

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions

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

[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[Daniel van Vugt]

** Tags added: artful trusty

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

[dann frazier]

The failure mentioned in Comment #15 is a test suite bug - see LP:
#1751167. I applied a hot-fix, re-ran the test, and it 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/1749040

Title:
  KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  In Progress

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

[dann frazier]

** Attachment added: "Gigabyte R120 (ACPI mode ThunderX)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5060797/+files/submission_2018-02-23T00.42.57.591881.html

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

Title:
  KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  In Progress

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

[dann frazier]

** Attachment added: "Cavium CRB (ThunderX) results"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5060796/+files/submission_2018-02-23T00.42.54.821054.html

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

Title:
  KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  In Progress

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[Daniel van Vugt]

Please clarify exactly which kernel versions you have tested. It will
help us to narrow down the problem.

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Vi+]

iBART, dmesg @ YEPO 737A (obtained after closing the cover and opening
it back after preliminary login - touchpad works with fully workable
mouse and both buttons after that) is attached.

I used next cmds in order to automatically enter into
4.16.0-041600rc1-lowlatency after reboot:

yep ~ # wget -c 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/linux-headers-4.16.0-041600rc1-lowlatency_4.16.0-041600rc1.201802120030_amd64.deb
 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/linux-image-4.16.0-041600rc1-lowlatency_4.16.0-041600rc1.201802120030_amd64.deb
yep ~ # dpkg -i *.deb
yep ~ # reboot


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5060765/+files/dmesg.txt

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[Pavel Francírek]

This happens my Mint too. Bluetooth keyboard is working after resume from 
suspend but mouse (Logitech M720 Triatlon) is not. bluetoothctl says Connected: 
yes  .. no .. yes .. no 
But bluetoothctl: agent off/on helps (no need to use power and pair commands).

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Wadcutter]

Not only same video issue as others on Trusty with Nvidia 340.102 driver
for GEForce 8400GS, but am also unable to log in.Entering PW just keeps
flipping me back to "Enter PW box". Old 112 kernel works just fine so I
will stick with that until a fix is 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/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Jason]

Add me to the List of People with this problem, nvidia 384.111 worked
great until this kernel now same problem as original poster.  Had to go
back to 112 to get it to work.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1749826] Re: [LENOVO 20A8S0UU00] hibernate/resume failure

[marcos]

Thanks Joseph for your help. I have always had this problem with this
machine.

I installed the new kernel v4.16 [0] and now the computer hibernates and
resumes successfully. I edited the tags and I put 'kernel-fixed-
upstream' and "Confirmed" in the status, is that right?


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

** Tags added: 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/1749826

Title:
  [LENOVO 20A8S0UU00] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problems in the hibernate process

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1099 F pulseaudio
marcos 1507 F pulseaudio
   /dev/snd/controlC1:  gdm1099 F pulseaudio
marcos 1507 F pulseaudio
  Date: Thu Feb 15 20:11:56 2018
  DuplicateSignature: hibernate/resume:LENOVO 20A8S0UU00:GRET32WW (1.09 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=fc8e6022-be7a-46fa-bf16-7f01ff4f07e6
  InstallationDate: Installed on 2018-02-01 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129)
  InterpreterPath: /usr/bin/python3.6
  MachineType: LENOVO 20A8S0UU00
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=864f7255-7e0e-4960-850a-8c64143a61ff ro quiet splash
  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.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [LENOVO 20A8S0UU00] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET32WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: CS064994
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET32WW(1.09):bd02/13/2014:svnLENOVO:pn20A8S0UU00:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S0UU00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon 2nd
  dmi.product.name: 20A8S0UU00
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1749815] Re: [LENOVO 20A8S0UU00] suspend/resume failure

[marcos]

Thanks Joseph for your help. I have always had this problem with this
machine.

I installed the new kernel v4.16 [0] and now the computer hibernates and
resumes successfully. But in the suspend process the computer does not
get resume. The computer never gets out of the suspend state.

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

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

Title:
  [LENOVO 20A8S0UU00] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My lenovo thinmkpad Carbon X1 did not reboot after suspend. It always
  stayed in the led intermittent. Some information about:

  Error in /var/log/pm-suspend  
  Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend:
  Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or 
directory
  /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success.

  Error in /var/log/pm-powersave.log
  Running hook /usr/lib/pm-utils/power.d/pcie_aspm false:
  sh: echo: I/O error
  /usr/lib/pm-utils/power.d/pcie_aspm false: success.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1091 F pulseaudio
marcos 1505 F pulseaudio
   /dev/snd/controlC0:  gdm1091 F pulseaudio
marcos 1505 F pulseaudio
  Date: Thu Feb 15 18:42:17 2018
  DuplicateSignature: suspend/resume:LENOVO 20A8S0UU00:GRET32WW (1.09 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=fc8e6022-be7a-46fa-bf16-7f01ff4f07e6
  InstallationDate: Installed on 2018-02-01 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129)
  InterpreterPath: /usr/bin/python3.6
  MachineType: LENOVO 20A8S0UU00
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=864f7255-7e0e-4960-850a-8c64143a61ff 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.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [LENOVO 20A8S0UU00] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET32WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: CS064994
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET32WW(1.09):bd02/13/2014:svnLENOVO:pn20A8S0UU00:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S0UU00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon 2nd
  dmi.product.name: 20A8S0UU00
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1749815] Re: [LENOVO 20A8S0UU00] suspend/resume failure

[marcos]

** Tags added: kernel-bug-exists-upstream

** Tags removed: kernel-bug-exists-upstream resume suspend
** Tags added: kernel-fixed-upstream

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

** Tags removed: suspend
** Tags added: suspend-resume

** Tags removed: suspend-resume
** Tags added: resume suspend

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

Title:
  [LENOVO 20A8S0UU00] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My lenovo thinmkpad Carbon X1 did not reboot after suspend. It always
  stayed in the led intermittent. Some information about:

  Error in /var/log/pm-suspend  
  Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend:
  Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or 
directory
  /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success.

  Error in /var/log/pm-powersave.log
  Running hook /usr/lib/pm-utils/power.d/pcie_aspm false:
  sh: echo: I/O error
  /usr/lib/pm-utils/power.d/pcie_aspm false: success.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1091 F pulseaudio
marcos 1505 F pulseaudio
   /dev/snd/controlC0:  gdm1091 F pulseaudio
marcos 1505 F pulseaudio
  Date: Thu Feb 15 18:42:17 2018
  DuplicateSignature: suspend/resume:LENOVO 20A8S0UU00:GRET32WW (1.09 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=fc8e6022-be7a-46fa-bf16-7f01ff4f07e6
  InstallationDate: Installed on 2018-02-01 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129)
  InterpreterPath: /usr/bin/python3.6
  MachineType: LENOVO 20A8S0UU00
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=864f7255-7e0e-4960-850a-8c64143a61ff 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.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [LENOVO 20A8S0UU00] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET32WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: CS064994
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET32WW(1.09):bd02/13/2014:svnLENOVO:pn20A8S0UU00:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S0UU00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon 2nd
  dmi.product.name: 20A8S0UU00
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1749826] Re: [LENOVO 20A8S0UU00] hibernate/resume failure

[marcos]

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  [LENOVO 20A8S0UU00] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problems in the hibernate process

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1099 F pulseaudio
marcos 1507 F pulseaudio
   /dev/snd/controlC1:  gdm1099 F pulseaudio
marcos 1507 F pulseaudio
  Date: Thu Feb 15 20:11:56 2018
  DuplicateSignature: hibernate/resume:LENOVO 20A8S0UU00:GRET32WW (1.09 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=fc8e6022-be7a-46fa-bf16-7f01ff4f07e6
  InstallationDate: Installed on 2018-02-01 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129)
  InterpreterPath: /usr/bin/python3.6
  MachineType: LENOVO 20A8S0UU00
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=864f7255-7e0e-4960-850a-8c64143a61ff ro quiet splash
  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.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [LENOVO 20A8S0UU00] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET32WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: CS064994
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET32WW(1.09):bd02/13/2014:svnLENOVO:pn20A8S0UU00:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S0UU00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon 2nd
  dmi.product.name: 20A8S0UU00
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Martin Dünkelmann]

Still happen with 4.13 Kernel Updates.

Need to manually reinstall the bcmwl package after every kernel upgrade.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Dave Chiluk]

@kmously I see that you marked this fix as Fix Committed in Artful, but
I do not see it in the master-next branch of artful.  I'm moving this
back to In progress in artful as this does not appear to have been
pushed to master-next for artful yet.  Feel free to push it back to Fix
Committed when you accept or merge the patch into master-next.

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => 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/1729674

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Erik Kratzenberg]

This also seems to affect ZFS on Linux modules:

zavl: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Roman Shipovskij]

LibreOffice Base works fine on Xenial i386 with last test kernel:

~$ uname -a
Linux WS 4.4.0-112-generic #135~lp1699772v5 SMP Thu Feb 22 20:41:29 UTC 2018 
i686 i686 i686 GNU/Linux

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Joseph Salisbury]

I built the next test kernel with commits a010365, 8105a5d, 028383b,
393d9b1 and 88a1685 reverted.

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

Can you test this kernel and see if it resolves this bug?

Thanks in advance!

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Mythological]

Bill Miller, I can ssh into the system and install packages - apt-get
still works, etc.  Right now the only thing I can't do is get into the
desktop; it shows a login screen but won't accept my password (even
though my password works fine in ssh).  I think it is because when I
tried to install the nVida Linux drivers it removed Noveau, and I can't
seem to get it back.

What I am not understanding is what you meant by "the -112" - I assume
you are talking about a version number or something, but of what?  I
went to that link but they are using Synaptic and I have no way to get
to that because I can't get into the desktop.  Also, unlike that guy, as
far as i know I did not "made the mistake of purging the functional
kernel" which means that the previous kernel is probably still around on
the hard drive, I just don't know how you would set it up to boot into
the previous kernel rather than the new kernel.

Rather than continue this discussion here I suggest we move it to
https://ubuntuforums.org/showthread.php?t=2385621=13742281#post13742281
as this is probably not appropriate for the bug tracker, and I suspect
many others are affected by this and would like to find a solution.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To 

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
b73948811b253d868aba711e1b8cfcc045c9cc50

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

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

Thanks in advance

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

[dann frazier]

1 unexpected failure on the HP m400 - disk/disk_stress_ng_sda. Needs
investigation.

** Attachment added: "Test results from an HP m400 (X-Gene) system"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5060703/+files/submission_2018-02-22T21.10.47.863617.html

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

Title:
  KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  In Progress

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-384 (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/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

The kernel is still good. The error happened again in the virtual
machine, here's dmesg:

[ 6730.708866] EXT4-fs error (device sda1): htree_dirblock_to_tree:976: inode 
#418562: comm updatedb.mlocat: Directory block failed checksum
[ 6730.710121] Aborting journal on device sda1-8.
[ 6730.711514] EXT4-fs (sda1): Remounting filesystem read-only
[ 6730.713087] EXT4-fs error (device sda1): ext4_journal_check_start:60: 
Detected aborted journal
[ 7030.415582] audit: type=1400 audit(1519269087.344:26): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=2851 comm="cupsd" 
capability=12  capname="net_admin"
[67539.479651] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
[67539.479670] clocksource:   'kvm-clock' wd_now: 
55b3d2da2f60 wd_last: 269f11d4c146 mask: 
[67539.479673] clocksource:   'tsc' cs_now: 422f92c80a6a 
cs_last: 422e9dc07f56 mask: 

what do you think? My disk is /dev/sda1 on the virtual machine, so no
NVME... I'm using KVM spice

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no 

[Kernel-packages] [Bug 1750937] 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/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

[Milan Masic]

After
xinput set-prop 10 "libinput Horizontal Scroll Enabled" 0
button #2 appeared in xev again.

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
   Reporting 7 classes:
    Class originated from: 9. Type: XIButtonClass
    Buttons supported: 24
    Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" 
"Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown"
    Button state:
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
   Reporting 6 classes:
    Class originated from: 10. Type: XIButtonClass
    Buttons supported: 7
    Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
    Button state:
    Class originated from: 10. Type: XIKeyClass
    Keycodes supported: 248
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0

  Does anyone have an idea how I can attempt to further debug that issue? Or 
maybe even a solution? Should I consider this issue a bug? Can I provide more 
info?
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toby  11625 F pulseaudio
   /dev/snd/controlC0:  toby  11625 F pulseaudio
   /dev/snd/pcmC1D0p:   toby  11625 F...m pulseaudio
   /dev/snd/controlC1:  toby  11625 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6
  InstallationDate: Installed on 2014-04-24 (749 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 

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

[Joseph Salisbury]

** Also affects: crash (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: crash (Ubuntu Bionic)
   Importance: Critical
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: In Progress

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

-- 
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:
  Triaged
Status in crash package in Ubuntu:
  In Progress
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  New
Status in crash source package in Bionic:
  In Progress

Bug description:
  ---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 1748768] Re: System won't boot 4.13.0-32 kernel

[Joseph Salisbury]

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

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

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

Title:
  System won't boot 4.13.0-32 kernel

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Invalid

Bug description:
  Ever since the update to the 4.13.0-32 kernel, my system won't boot.
  When I turn off the splash screen and quiet, I see repeated messages
  about not connecting to lvmetad and falling back to device scanning.

  The disk has a boot partition and a logical volume partition.  The
  logical volume partition is encrypted with LUKS.

  I can boot the 4.13.0-31 kernel with no problems (that's where the
  data for this bug was collected).  I'm not sure how to troubleshoot
  this further.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim5303 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Feb 11 11:01:02 2018
  HibernationDevice: RESUME=UUID=ff4e1c78-1dec-4f38-8cc2-e28a35635b6b
  InstallationDate: Installed on 2017-01-16 (391 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 2436CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-31 (103 days ago)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 2436CTO
  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/1748768/+subscriptions

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Mythological]

Bob Miller, how do I install "-112"? I am afraid I have already dug
myself into so deep a hole I don't want to make any more mistakes, and I
have no idea what you mean by "-112". Please explain, or point me to a
page that does.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Mythological]

Bo9b Miller, how do I install "-112"?  I am afraid I have already dug
myself into so deep a hole I don't want to make any more mistakes, and I
have no idea what you mean by "-112".  Please explain, or point me to a
page that does.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Bill Miller]

Mythological, you have to fix the system to the point that you can
install packages. I am not sure you are that point yet from your
description.  Once you are there, you can install an old kernel by
following the procedure outlined here
https://askubuntu.com/questions/928146/install-an-older-kernel-14-04-lts
If you can only log into a terminal, you need to identify the 4 kernel
packages you want and install them with sudo apt install [packagenames]

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1527727] [grub2/xenial] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of grub2 from xenial-proposed
was performed and bug 1750732 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed-
xenial" tag from this bug report and add the tag "bot-stop-nagging" to
bug 1750732 (not this bug). Thanks!

** Tags added: verification-failed-xenial

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Nicolás Abel Carbone]

Tested the new kernel. It still has the bug.

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[gumbeto]

Same thing here on 16.04, with nvidia driver 384.111. 
Kernel 4.4.0-112: no problems
kernel 4.4.0-116: Low res and can't login on graphical mode. 

I have tried to uninstall and reinstall nvidia drivers to no effect.

I did a diff for dmesg output on both cases. The relevant bits are:

> Spectre V2 mitigation: Mitigation: Full generic retpoline
> Spectre V2 mitigation: Speculation control IBPB not-supported IBRS 
> not-supported

and

< nvidia: module license 'NVIDIA' taints kernel.
< Disabling lock debugging due to kernel taint
< nvidia: module verification failed: signature and/or required key missing - 
tainting kernel
---
> nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions ' should 
> be '4.4.0-116-generic SMP mod_unload modversions retpoline '
> nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions ' should 
> be '4.4.0-116-generic SMP mod_unload modversions retpoline '


** Also affects: nvidia-graphics-drivers-384 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1739102] Re: Lenovo 11e Input Freeze

[Aaron Prisk]

Sorry for the delay.
The input issues first crop up in 4.13-rc1. I also noticed that the latest 
4.16-rc2 doesn't seem to be affected by the issue.

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

Title:
  Lenovo 11e Input Freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We're been running into an issue that so far seems to be limited to our 
Lenovo 11e laptops and Ubuntu 17.10. 
  On first boot, the touchpad and keyboard will work sporadically with random 
keys occasionally being registered as being pressed. After some time, both the 
touchpad and keyboard completely stop functioning. We've replicated the issue 
on other 11e laptops to ensure it wasn't a hardware problem.

  Touchpad and keyboard both work perfectly on Ubuntu 16.04.3

  
  dmesg is showing a bunch of the following:

  psmouse serio1: Touchpad at isa0060/serio1/input0 lost synchronization, 
throwing 4 bytes away.
  psmouse serio1: resync failed, issuing reconnect request
  psmouse serio1: synaptics: unable to initialize device

  
  What we expect to happen:
  Touchpad and Keyboard will allow user input

  
  What happened instead:
  Touchpad and Keyboard register random input or don't function at all.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tech970 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-12-12 (7 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20GBS00S00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8b4328ce-7dad-4e55-8229-df928776303b ro quiet splash acpi_osi=Linux 
acpi_lightback=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare 
scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 03/01/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0AET33W (1.16)
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K13467 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0AET33W(1.16):bd03/01/2017:svnLENOVO:pn20GBS00S00:pvrThinkPad11e3rdGen:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0K13467WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad 11e 3rd Gen
  dmi.product.name: 20GBS00S00
  dmi.product.version: ThinkPad 11e 3rd Gen
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1751131] Re: Bionic update to v4.15.5 stable release

[Seth Forshee]

** Description changed:

  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.15.5 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.15.5 stable release shall be
  applied:
  
  scsi: smartpqi: allow static build ("built-in")
  IB/umad: Fix use of unprotected device pointer
  IB/qib: Fix comparison error with qperf compare/swap test
  IB/mlx4: Fix incorrectly releasing steerable UD QPs when have only ETH ports
  IB/core: Fix two kernel warnings triggered by rxe registration
  IB/core: Fix ib_wc structure size to remain in 64 bytes boundary
  IB/core: Avoid a potential OOPs for an unused optional parameter
  selftests: seccomp: fix compile error seccomp_bpf
  kselftest: fix OOM in memory compaction test
  RDMA/rxe: Fix a race condition related to the QP error state
  RDMA/rxe: Fix a race condition in rxe_requester()
  RDMA/rxe: Fix rxe_qp_cleanup()
  cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
- swiotlb: suppress warning when __GFP_NOWARN is set
  PM / devfreq: Propagate error from devfreq_add_device()
  mwifiex: resolve reset vs. remove()/shutdown() deadlocks
  ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE
  trace_uprobe: Display correct offset in uprobe_events
  powerpc/radix: Remove trace_tlbie call from radix__flush_tlb_all
  powerpc/kernel: Block interrupts when updating TIDR
  powerpc/vas: Don't set uses_vas for kernel windows
  powerpc/numa: Invalidate numa_cpu_lookup_table on cpu remove
  powerpc/mm: Flush radix process translations when setting MMU type
  powerpc/xive: Use hw CPU ids when configuring the CPU queues
  dma-buf: fix reservation_object_wait_timeout_rcu once more v2
  s390: fix handling of -1 in set{,fs}[gu]id16 syscalls
  arm64: dts: msm8916: Correct ipc references for smsm
  ARM: lpc3250: fix uda1380 gpio numbers
  ARM: dts: STi: Add gpio polarity for "hdmi,hpd-gpio" property
  ARM: dts: nomadik: add interrupt-parent for clcd
  arm: dts: mt7623: fix card detection issue on bananapi-r2
  arm: spear600: Add missing interrupt-parent of rtc
  arm: spear13xx: Fix dmas cells
  arm: spear13xx: Fix spics gpio controller's warning
  x86/gpu: add CFL to early quirks
  x86/kexec: Make kexec (mostly) work in 5-level paging mode
  x86/xen: init %gs very early to avoid page faults with stack protector
  x86: PM: Make APM idle driver initialize polling state
  mm, memory_hotplug: fix memmap initialization
  x86/entry/64: Clear extra registers beyond syscall arguments, to reduce 
speculation attack surface
  x86/entry/64/compat: Clear registers for compat syscalls, to reduce 
speculation attack surface
  compiler-gcc.h: Introduce __optimize function attribute
  compiler-gcc.h: __nostackprotector needs gcc-4.4 and up
  crypto: sun4i_ss_prng - fix return value of sun4i_ss_prng_generate
  crypto: sun4i_ss_prng - convert lock to _bh in sun4i_ss_prng_generate
  powerpc/mm/radix: Split linear mapping on hot-unplug
  x86/mm/pti: Fix PTI comment in entry_SYSCALL_64()
  x86/speculation: Update Speculation Control microcode blacklist
  x86/speculation: Correct Speculation Control microcode blacklist again
  Revert "x86/speculation: Simplify indirect_branch_prediction_barrier()"
  KVM/x86: Reduce retpoline performance impact in slot_handle_level_range(), by 
always inlining iterator helper methods
  X86/nVMX: Properly set spec_ctrl and pred_cmd before merging MSRs
  KVM/nVMX: Set the CPU_BASED_USE_MSR_BITMAPS if we have a valid L02 MSR bitmap
  x86/speculation: Clean up various Spectre related details
  PM / runtime: Update links_count also if !CONFIG_SRCU
  PM: cpuidle: Fix cpuidle_poll_state_init() prototype
  platform/x86: wmi: fix off-by-one write in wmi_dev_probe()
  x86/entry/64: Clear registers for exceptions/interrupts, to reduce 
speculation attack surface
  x86/entry/64: Merge SAVE_C_REGS and SAVE_EXTRA_REGS, remove unused extensions
  x86/entry/64: Merge the POP_C_REGS and POP_EXTRA_REGS macros into a single 
POP_REGS macro
  x86/entry/64: Interleave XOR register clearing with PUSH instructions
  x86/entry/64: Introduce the PUSH_AND_CLEAN_REGS macro
  x86/entry/64: Use PUSH_AND_CLEAN_REGS in more cases
  x86/entry/64: Get rid of the ALLOC_PT_GPREGS_ON_STACK and SAVE_AND_CLEAR_REGS 
macros
  x86/entry/64: Indent PUSH_AND_CLEAR_REGS and POP_REGS properly
  x86/entry/64: Fix paranoid_entry() frame pointer warning
  x86/entry/64: Remove the unused 'icebp' macro
  selftests/x86: Fix vDSO selftest segfault for vsyscall=none
  selftests/x86: Clean up and document sscanf() 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Joseph Salisbury]

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no 

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Roman Shipovskij]

LibreOffice Base still crash with test kernel:

~$ uname -a
Linux WS 4.4.0-112-generic #135~lp1699772v4 SMP Thu Feb 22 18:45:01 UTC 2018 
i686 i686 i686 GNU/Linux

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

[Joseph Salisbury]

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

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

Bug description:
  == SRU Justification ==
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug in 
kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  == Fixes ==
  d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR write protection bit on 
Haswell/Broadwell")
  9d63f17661e2 ("spi-nor: intel-spi: Fix broken software sequencing codes")

  == Regression Potential ==
  Low, these patches fix an existing critical regression.


  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

[Kernel-packages] [Bug 1751111] Re: [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency issues

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

Title:
  [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency
  issues

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm trying to deploy Bionic on a MAAS node today and this is failing
  with the following dependency errors in the logs.  The node in
  question is booting in EFI mode with Secure Boot enabled.

  curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
  third party drivers not installed or necessary.
  Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8526 
kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 
kB]
  Fetched 9994 kB in 11s (902 kB/s)
  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-signed-generic : Depends: linux-signed-image-generic (= 4.15.0.10.11) 
but it is not going to be installed
  Depends: linux-headers-generic (= 4.15.0.10.11) but 
it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  Unexpected error while running command.
  Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
  Exit code: 100
  Reason: -
  Stdout: ''
  Stderr: ''
  curtin: Installation failed with exception: Unexpected error while running 
command.
  Command: ['curtin', 'curthooks']
  Exit code: 3
  Reason: -
  Stdout: Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease 
[65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 
[1016 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 
[8526 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 
Packages [151 kB]
  Fetched 9994 kB in 11s (902 kB/s)
  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   linux-signed-generic : Depends: linux-signed-image-generic (= 
4.15.0.10.11) but it is not going to be installed
  Depends: linux-headers-generic (= 
4.15.0.10.11) but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  Unexpected error while running command.
  Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
  Exit code: 100
  Reason: -
  Stdout: ''
  Stderr: ''
  
  Stderr: ''

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

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

[Kernel-packages] [Bug 1751131] [NEW] Bionic update to v4.15.5 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.15.5 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.15.5 stable release shall be
applied:

scsi: smartpqi: allow static build ("built-in")
IB/umad: Fix use of unprotected device pointer
IB/qib: Fix comparison error with qperf compare/swap test
IB/mlx4: Fix incorrectly releasing steerable UD QPs when have only ETH ports
IB/core: Fix two kernel warnings triggered by rxe registration
IB/core: Fix ib_wc structure size to remain in 64 bytes boundary
IB/core: Avoid a potential OOPs for an unused optional parameter
selftests: seccomp: fix compile error seccomp_bpf
kselftest: fix OOM in memory compaction test
RDMA/rxe: Fix a race condition related to the QP error state
RDMA/rxe: Fix a race condition in rxe_requester()
RDMA/rxe: Fix rxe_qp_cleanup()
cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
PM / devfreq: Propagate error from devfreq_add_device()
mwifiex: resolve reset vs. remove()/shutdown() deadlocks
ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE
trace_uprobe: Display correct offset in uprobe_events
powerpc/radix: Remove trace_tlbie call from radix__flush_tlb_all
powerpc/kernel: Block interrupts when updating TIDR
powerpc/vas: Don't set uses_vas for kernel windows
powerpc/numa: Invalidate numa_cpu_lookup_table on cpu remove
powerpc/mm: Flush radix process translations when setting MMU type
powerpc/xive: Use hw CPU ids when configuring the CPU queues
dma-buf: fix reservation_object_wait_timeout_rcu once more v2
s390: fix handling of -1 in set{,fs}[gu]id16 syscalls
arm64: dts: msm8916: Correct ipc references for smsm
ARM: lpc3250: fix uda1380 gpio numbers
ARM: dts: STi: Add gpio polarity for "hdmi,hpd-gpio" property
ARM: dts: nomadik: add interrupt-parent for clcd
arm: dts: mt7623: fix card detection issue on bananapi-r2
arm: spear600: Add missing interrupt-parent of rtc
arm: spear13xx: Fix dmas cells
arm: spear13xx: Fix spics gpio controller's warning
x86/gpu: add CFL to early quirks
x86/kexec: Make kexec (mostly) work in 5-level paging mode
x86/xen: init %gs very early to avoid page faults with stack protector
x86: PM: Make APM idle driver initialize polling state
mm, memory_hotplug: fix memmap initialization
x86/entry/64: Clear extra registers beyond syscall arguments, to reduce 
speculation attack surface
x86/entry/64/compat: Clear registers for compat syscalls, to reduce speculation 
attack surface
compiler-gcc.h: Introduce __optimize function attribute
compiler-gcc.h: __nostackprotector needs gcc-4.4 and up
crypto: sun4i_ss_prng - fix return value of sun4i_ss_prng_generate
crypto: sun4i_ss_prng - convert lock to _bh in sun4i_ss_prng_generate
powerpc/mm/radix: Split linear mapping on hot-unplug
x86/mm/pti: Fix PTI comment in entry_SYSCALL_64()
x86/speculation: Update Speculation Control microcode blacklist
x86/speculation: Correct Speculation Control microcode blacklist again
Revert "x86/speculation: Simplify indirect_branch_prediction_barrier()"
KVM/x86: Reduce retpoline performance impact in slot_handle_level_range(), by 
always inlining iterator helper methods
X86/nVMX: Properly set spec_ctrl and pred_cmd before merging MSRs
KVM/nVMX: Set the CPU_BASED_USE_MSR_BITMAPS if we have a valid L02 MSR bitmap
x86/speculation: Clean up various Spectre related details
PM / runtime: Update links_count also if !CONFIG_SRCU
PM: cpuidle: Fix cpuidle_poll_state_init() prototype
platform/x86: wmi: fix off-by-one write in wmi_dev_probe()
x86/entry/64: Clear registers for exceptions/interrupts, to reduce speculation 
attack surface
x86/entry/64: Merge SAVE_C_REGS and SAVE_EXTRA_REGS, remove unused extensions
x86/entry/64: Merge the POP_C_REGS and POP_EXTRA_REGS macros into a single 
POP_REGS macro
x86/entry/64: Interleave XOR register clearing with PUSH instructions
x86/entry/64: Introduce the PUSH_AND_CLEAN_REGS macro
x86/entry/64: Use PUSH_AND_CLEAN_REGS in more cases
x86/entry/64: Get rid of the ALLOC_PT_GPREGS_ON_STACK and SAVE_AND_CLEAR_REGS 
macros
x86/entry/64: Indent PUSH_AND_CLEAR_REGS and POP_REGS properly
x86/entry/64: Fix paranoid_entry() frame pointer warning
x86/entry/64: Remove the unused 'icebp' macro
selftests/x86: Fix vDSO selftest segfault for vsyscall=none
selftests/x86: Clean up and document sscanf() usage
selftests/x86/pkeys: Remove unused functions
selftests/x86: Fix build bug caused by the 5lvl test which has been moved to 
the VM directory
selftests/x86: Do not rely on "int $0x80" in test_mremap_vdso.c
gfs2: Fixes to 

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Joseph Salisbury]

I built the next test kernel with commits a010365, 8105a5d, 028383b and
393d9b1 reverted.

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

Can you test this kernel and see if it resolves this bug?

Thanks in advance!

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
9c58aebfd9d8c8d5b156898656c5c180a36e7a63

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

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

Thanks in advance

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751111] Re: [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency issues

[Jeff Lane]

Marking this as Invalid.  I've tried a few more times and have been
unable to reproduce this myself, so I'm going to chalk it up to
"incompatible bit-registration operators" (Per the BOFH excuses
generator).

If this happens again, I'll revisit it at that time, but for now, the issues 
seem resolved.  They incompatible bit-registration operators 
may also have been related to some equipment reboots occurring upstream too. 


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

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

Title:
  [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency
  issues

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm trying to deploy Bionic on a MAAS node today and this is failing
  with the following dependency errors in the logs.  The node in
  question is booting in EFI mode with Secure Boot enabled.

  curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
  third party drivers not installed or necessary.
  Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8526 
kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 
kB]
  Fetched 9994 kB in 11s (902 kB/s)
  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-signed-generic : Depends: linux-signed-image-generic (= 4.15.0.10.11) 
but it is not going to be installed
  Depends: linux-headers-generic (= 4.15.0.10.11) but 
it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  Unexpected error while running command.
  Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
  Exit code: 100
  Reason: -
  Stdout: ''
  Stderr: ''
  curtin: Installation failed with exception: Unexpected error while running 
command.
  Command: ['curtin', 'curthooks']
  Exit code: 3
  Reason: -
  Stdout: Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease 
[65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 
[1016 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 
[8526 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 
Packages [151 kB]
  Fetched 9994 kB in 11s (902 kB/s)
  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   linux-signed-generic : Depends: linux-signed-image-generic (= 
4.15.0.10.11) but it is not going to be installed
  Depends: linux-headers-generic (= 
4.15.0.10.11) but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  Unexpected error while running command.
  Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
  Exit code: 100
  Reason: -
  Stdout: ''
  Stderr: ''
  
  Stderr: ''

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

@Kristoffer, yes sounds like a different bug.  I'll continue the bisect
with Nicolas.  Probably best to open a separate bug report indeed.

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1750796] Re: xserver does not work with kernel 4.13.0-32

[Harald]

Hi Joseph,
I have installed kernel 4.16.0-041600rc2_4.16.0-041600rc2.201802190311 and - it 
works!!! 
I booted about 30 times, the xserver always runs and everything was fine. 

So it looks like the issue will be solved with kernel 4.16.

I hope the daily build of "Bionic Beaver" will received that kernel
soon.

Thank you for help
Harald




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

Title:
  xserver does not work with kernel 4.13.0-32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on one of my desktop computers (pls see file System.html) the xserver does 
not start anymore with kernel version 4.13.0-32. After logon, the KUbuntu 
splash appears, the HDD works some seconds, than the drive stops an the 
computer does not react anymore at all.
   
  Just a SSH connection is possible, but a reboot or shutdown command results 
only in "connection closed". The computer does not react on these commands.

  The computer has to be switched off be hard power off, reset or magic
  code REISUB. Using the xorg graphics driver instead the recommended
  nvidia driver does not fix the issue.

  But, the "problem computer" works fine with the old kernel version
  4.13.0-25 as well as older kernel versions.

  However, two other computers, both with other CPUs and motherboards,
  (one of them has the same graphics card and driver), works well with
  kernel 4.13.0-32.

  Thank you for help
  Harald

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

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

[Kernel-packages] [Bug 1751111] 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 175

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

** Tags added: 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/175

Title:
  [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency
  issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to deploy Bionic on a MAAS node today and this is failing
  with the following dependency errors in the logs.  The node in
  question is booting in EFI mode with Secure Boot enabled.

  curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
  third party drivers not installed or necessary.
  Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8526 
kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 
kB]
  Fetched 9994 kB in 11s (902 kB/s)
  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-signed-generic : Depends: linux-signed-image-generic (= 4.15.0.10.11) 
but it is not going to be installed
  Depends: linux-headers-generic (= 4.15.0.10.11) but 
it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  Unexpected error while running command.
  Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
  Exit code: 100
  Reason: -
  Stdout: ''
  Stderr: ''
  curtin: Installation failed with exception: Unexpected error while running 
command.
  Command: ['curtin', 'curthooks']
  Exit code: 3
  Reason: -
  Stdout: Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease 
[65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 
[1016 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 
[8526 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 
Packages [151 kB]
  Fetched 9994 kB in 11s (902 kB/s)
  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   linux-signed-generic : Depends: linux-signed-image-generic (= 
4.15.0.10.11) but it is not going to be installed
  Depends: linux-headers-generic (= 
4.15.0.10.11) but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
  Unexpected error while running command.
  Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
  Exit code: 100
  Reason: -
  Stdout: ''
  Stderr: ''
  

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Kristoffer Brissman]

Sounds like different bug indeed. For me it hangs pretty much
immediately after GRUB and I don't even see the plymouth screen with the
Ubuntu logo or the password promt for dm-crypt. Tried many times, same
result every time.

I have quite different system specs as well, not the Dell laptop
mentioned earlier, but rather a desktop based on the AMD Ryzen CPU.

Perhaps I should wait and see how this goes and I'f I encounter the
problem after Joseph's issue is fixed then I file my own bug report?

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Kristoffer Brissman]

$ uname -a
Linux kristoffer-ubuntu-desktop 4.13.0-33-generic 
#36~lp1751098Commit721530cf07670 SMP Thu Feb 22 17:22:43 UTC 201 x86_64 x86_64 
x86_64 GNU/Linux

Perhaps we are facing two different bugs?

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Nicolás Abel Carbone]

Maybe we are facing different bugs. In my case, it does boot, but it
hangs shortly after. If I hurry, I am even able to log in to the
desktop.

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.3 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. 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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1750986] Re: My wireless networ kard is 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.16 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.16-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/1750986

Title:
  My wireless networ kard is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after installing Kernel 4.13.0.36 it disables or stops my wireless
  card , i have tried that many times.

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

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

[Kernel-packages] [Bug 1751000] Re: pmu test in kvm-unit-test failed on X-hwe ARM64 system

[Joseph Salisbury]

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

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

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

Title:
  pmu test in kvm-unit-test failed on X-hwe ARM64 system

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This failure could be found on both Moonshot and Cavium ThunderX ARM64
  systems.

  Steps:
   1. Install necessary packages
   2. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
   3. cd kvm-unit-tests; ./configure; make
   4. TESTNAME=pmu TIMEOUT=90s ACCEL= ./arm/run arm/pmu.flat -smp 1

  Result:
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/pmu.flat -smp 1 # -initrd 
/tmp/tmp.H8ucGrg46U

  INFO: PMU version: 3
  INFO: pmu: PMU implementer/ID code/counters: 0(" ")/0/0
  FAIL: pmu: Control register
  Read 0 then 0.
  FAIL: pmu: Monotonically increasing cycle count
  instrs : cycles0 cycles1 ...
 4:0
  cycles not incrementing!
  FAIL: pmu: Cycle/instruction ratio
  SUMMARY: 3 tests, 3 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: arm64
  Date: Thu Feb 22 08:29:15 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 22 08:24 seq
   crw-rw 1 root audio 116, 33 Feb 22 08:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-36-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

Kristoffer, can you run uname -a to confirm you booted the test kernel?
Nicolas reports the test kernel does not boot.

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751111] [NEW] [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency issues

[Jeff Lane]

Public bug reported:

I'm trying to deploy Bionic on a MAAS node today and this is failing
with the following dependency errors in the logs.  The node in question
is booting in EFI mode with Secure Boot enabled.

curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
third party drivers not installed or necessary.
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8526 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB]
Fetched 9994 kB in 11s (902 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-signed-generic : Depends: linux-signed-image-generic (= 4.15.0.10.11) 
but it is not going to be installed
Depends: linux-headers-generic (= 4.15.0.10.11) but it 
is not going to be installed
E: Unable to correct problems, you have held broken packages.
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
curtin: Installation failed with exception: Unexpected error while running 
command.
Command: ['curtin', 'curthooks']
Exit code: 3
Reason: -
Stdout: Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 
kB]
Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1016 
kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 
[8526 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages 
[151 kB]
Fetched 9994 kB in 11s (902 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-signed-generic : Depends: linux-signed-image-generic (= 
4.15.0.10.11) but it is not going to be installed
Depends: linux-headers-generic (= 4.15.0.10.11) 
but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Unexpected error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp64l_1ty8/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-signed-generic']
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''

Stderr: ''

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


** Tags: hwcert-server

** Tags added: hwcert-server

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

Title:
  [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency
  issues

Status in linux package in Ubuntu:
  New

Bug description:
  I'm trying to deploy Bionic on a MAAS node today and this is failing
  with the following dependency errors in the logs.  The node in
  question is booting in EFI mode with Secure Boot enabled.

  curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1)
  third party drivers not installed or necessary.
  Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease

[Kernel-packages] [Bug 1750810] Re: qeth: fix calculation of required buffer elements for skb

[Joseph Salisbury]

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

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

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

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
number of needed IO buffer elements, resulting in
malformed TX buffer descriptors. When such a buffer is
presented to the HW, it triggers a Subchannel Program
Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16


  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

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

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

[Kernel-packages] [Bug 1751028] Re: impossible to start a xen domain on precise with the spectre/meltdown kernel

[Joseph Salisbury]

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

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

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

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

** Tags added: pti

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

Title:
  impossible to start a xen domain on precise with the spectre/meltdown
  kernel

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

Bug description:
  Hi,

  Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic -
  precise ESM), it's not possible to boot my xen domUs anymore (dom0 is
  fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic
  (lts-trusty with Spectre/Meltdown mitigations).

  This is with xen 4.1.6.1-0ubuntu0.12.04.13

  xend.log below :

  [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103) 
XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'], 
['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'], 
['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux', 
['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'], 
['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'], 
['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', 
['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]], 
['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'], 
['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac', 
'02:00:5B:BD:5E:E2')

  [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498) 
XendDomainInfo.constructDomain  

  
  [2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free; 
need 16384; done.   

   
  [2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2


   
  [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836) 
XendDomainInfo.initDomain: 2 256

  
  [2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863) 
_initDomain:shadow_memory=0x0, memory_static_max=0x18000, 
memory_static_min=0x0.  

  [2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2 
vcpus=1 

  
  [2018-02-22 10:56:03 1566] DEBUG (image:721) domid  = 2   


   
  [2018-02-22 10:56:03 1566] DEBUG (image:722) memsize= 6144


   
  [2018-02-22 10:56:03 1566] DEBUG (image:723) image  = /vmlinuz


   
  [2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn   = 1   


   
  [2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2   


   
  [2018-02-22 

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

[Po-Hsu Lin]

Hello Christian,
No I'm not debugging this. Not sure what's our policy for this kind of issue, 
do we always mirror them to IBM?

Came back on this because I saw the qemu update in bug 1712803, tracking
bugs found with regression-testing is a part of the SRU testing process.

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

Title:
  ubuntu-kvm-unit test failed with emulator test on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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

[Kernel-packages] [Bug 1750813] Re: qeth: fix L3 next-hop im xmit qeth hdr

[Joseph Salisbury]

Commit ec2c6726322f0d2 is in mainline as of v4.13-rc5, so Artful and
Bionic already contain the fix.  Are you requesting it in Xenial?

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

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

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury 
(jsalisbury)

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

Title:
  qeth: fix L3 next-hop im xmit qeth hdr

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:  qeth: fix L3 next-hop im xmit qeth hdr

  Symptom:  wrong destination address in qdio header

  Problem:  The current code accesses rtable->rt_gateway without checking
that rtable is a valid address. The accidental access to a
lowcore area results in a random next-hop address in the
qeth_hdr.
rtable (or more precisely, skb_dst(skb)) can be NULL in rare
cases (for instance together with AF_PACKET sockets).

  Solution: Add the missing NULL-ptr checks.
  Reproduction: AF_PACKET program sending raw data

  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Kristoffer Brissman]

That one ( http://kernel.ubuntu.com/~jsalisbury/lp1751098/ ) booted
successfully for me.

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Nicolás Abel Carbone]

Joseph, the bisected kernel (4.13.0-33) seems to have the bug. It hangs
my laptop just as 4.13.0-36

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

I started a kernel bisect between 4.13.0-32 and 4.13.0-36. The kernel
bisect will require testing of about 7-10 test kernels.

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

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

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


Thanks in advance

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Dave Chiluk]

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

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

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Roman Shipovskij]

LibreOffice Base still crash with test kernel:

~$ uname -a
Linux WS 4.4.0-112-generic #135~lp1699772v3 SMP Thu Feb 22 16:08:07 UTC 2018 
i686 i686 i686 GNU/Linux

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Kristoffer Brissman]

This kernel (4.13.0-36.40) hangs for me as well, but it's much earlier
in the boot process so it doesn't even get to the point where it would
ask me for my dm-crypt password. The fallback image (4.13.0-32.35) boots
fine though.

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

[Joseph Salisbury]

Before starting the bisect, can you see if the latest Artful kernel
still has the bug?  It is in the updates as kernel version 4.13.0-36.

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

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

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

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

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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

[Kernel-packages] [Bug 1750813] Re: qeth: fix L3 next-hop im xmit qeth hdr

[Dimitri John Ledkov]

This is already fix released, as the commit mentioned is in the v4.13+
kernels.

Is this a request to backport this to some previous release? Because
this is an invalid request for 18.04.

** Changed in: ubuntu-z-systems
   Status: Triaged => Invalid

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

Title:
  qeth: fix L3 next-hop im xmit qeth hdr

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Description:  qeth: fix L3 next-hop im xmit qeth hdr

  Symptom:  wrong destination address in qdio header

  Problem:  The current code accesses rtable->rt_gateway without checking
that rtable is a valid address. The accidental access to a
lowcore area results in a random next-hop address in the
qeth_hdr.
rtable (or more precisely, skb_dst(skb)) can be NULL in rare
cases (for instance together with AF_PACKET sockets).

  Solution: Add the missing NULL-ptr checks.
  Reproduction: AF_PACKET program sending raw data

  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

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

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

[Kernel-packages] [Bug 1750810] Re: qeth: fix calculation of required buffer elements for skb

[Dimitri John Ledkov]

Are there patches that should be attached and synced to launchpad for
this bug report? Or have they been sent to the Ubuntu kernel team
mailing for review and inclusion?

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

Title:
  qeth: fix calculation of required buffer elements for skb

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Description:  qeth: fix calculation of required buffer elements for
  skb

  Symptom:  Repeated device recovery due to Subchannel Program
  Checks

  Problem:  skbs of certain lengths cause qeth to miscalculate the
number of needed IO buffer elements, resulting in
malformed TX buffer descriptors. When such a buffer is
presented to the HW, it triggers a Subchannel Program
Check. qeth handles this by starting device recovery.

  Solution: Fix the buffer element calculation, so that qeth builds
proper TX buffer descriptors.

  Reproduction: Occurs for skbs where the last byte of the linear data
range / of a page frag sits on a page boundary.

  Upstream Git Commit:
  89271c65edd599207dd982007900506283c90ae3
  kernel 4.16


  backported to xenial/master-next

  Here's a backport of the upstream commit for pre-4.8 kernels.

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

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

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Marcelo Cerri]

** Changed in: linux-azure (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-azure (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** No longer affects: linux-azure (Ubuntu Artful)

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers. This 
is a
  regression introduced by commit e0edc8c54646.  This regression is fixed by 
mainline
  commit db5ff909798, which was added to mailine in v4.15-rc9.

  This commit has already been added to Bionic via upstream stable udpates.  
Xenial
  also needs this fix because it recieved the regression introducing commit 
e0edc8c54646
  via the 4.4.48 stable updates(See bug lp1663657).

  
  == Fix ==
  commit db5ff909798ef0099004ad50a0ff5fde92426fd1
  Author: Xinyu Lin 
  Date:   Sun Dec 17 20:13:39 2017 +0800

  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable to fix a regression, so it
  received extra upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Description ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers.  A 
fix for this issue has been submitted upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  At a high level the root cause of this problem is that the device only
  supports commands with a transfer size up to 512KB.  This worked fine
  with older versions of Linux but newer versions are attempting
  commands with a transfer size of 1280KB which is problematic for this
  device (LITEON EP1-KB480)

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

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

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

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

** Tags added: pti

** Tags added: performing-bisect

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751098] [NEW] Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Nicolás Abel Carbone]

Public bug reported:

After upgrading to linux 4.13.0-36 my laptop hangs shortly after
booting, even before logging in to the desktop. It starts with the
interface being unresponsive but the mouse cursor moving, and shortly
after that the mouse cursor also hangs intermittently and then
permanently.

Linux 4.13.0-32 works fine.

My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-36-generic 4.13.0-36.40
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USUARIOORDEN DE ACCESO PID
 /dev/snd/controlC0:  nicolas2111 F pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Feb 22 10:56:06 2018
InstallationDate: Installed on 2018-02-02 (20 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.169.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.2
dmi.board.name: 05HM5Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

[Joseph Salisbury]

I built the next test kernel with commits a010365, 8105a5d and 028383b
reverted.

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

Can you test this kernel and see if it resolves this bug?


Thanks in advance!

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1749250] Re: linux: 4.15.0-10.11 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-development-workflow/promote-to-release
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the 4.15.0-10.11 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
+ kernel-phase:Released
+ kernel-phase-changed:Thursday, 22. February 2018 16:30 UTC

** Description changed:

  This bug is for tracking the 4.15.0-10.11 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-phase:Released
- kernel-phase-changed:Thursday, 22. February 2018 16:30 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux: 4.15.0-10.11 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.15.0-10.11 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1545542] Re: Enable arm64 emulation of removed ARMv7 instructions

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

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

Title:
  Enable arm64 emulation of removed ARMv7 instructions

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Linux now supports emulation of three deprecated ARMv7 features that
  were removed from ARMv8: SWP(B), CP15ISB/DSB/DMB, and SETEND. At least
  CP15DMB is used by some armhf archive binaries (notably pandoc), so we
  need emulation enabled on the kernels that scalingstack uses.

  I haven't checked which version added which, but they appeared some
  time between 3.13 and 4.2, and I only care about 4.2 onwards. So
  please enable ARMV8_DEPRECATED, SWP_EMULATION, CP15_BARRIER_EMULATION
  and SETEND_EMULATION in arm64 kernels for wily onwards.

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  Fix Committed
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  Fix Released
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  Fix Released
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  Fix Released
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ 

[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

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

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

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

  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging

  -- swm 

[Kernel-packages] [Bug 1738523] Re: [SRU] External HDMI monitor failed to show screen on Lenovo X1 series

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

Title:
  [SRU] External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1738523/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1739939] Re: Update Ubuntu-4.15.0 config to support Intel Atom devices

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

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

Title:
  Update Ubuntu-4.15.0 config to support Intel Atom devices

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

Bug description:
  After the mainline kernel was patched with 'serdev: Add ACPI support'
  (commit 53c7626356c7584e82510d86394a6dcd80525614) and 'serdev: enable
  TTY port controller support by default' (commit
  22b276a4072087e7b7f1723ccd8a1aa18fab8bbf) and 'Bluetooth: hci_bcm: Add
  serdev support' (commit 33cd149e767be9afbab9fcd3d5165a2de62313c8) and
  'Bluetooth: avoid silent hci_bcm ACPI PM regression' (commit
  4294625e029028854596865be401b9c5c1f906ef) the mainline kernel the
  config needs CONFIG_SERIAL_DEV_BUS=m changing to
  CONFIG_SERIAL_DEV_BUS=y and both CONFIG_SERIAL_DEV_CTRL_TTYPORT=y and
  CONFIG_BT_HCIUART_BCM=y added to keep sound and BT working on Intel
  Atom devices.

  Currently the latest Ubuntu config for 4.15 (see 0006-configs-based-
  on-Ubuntu-4.15.0-2.3.patch) still only has CONFIG_SERIAL_DEV_BUS=m

  The config needs to be updated to take into consideration the
  implications of the aforementioned patches together with the settings
  identified.

To 

[Kernel-packages] [Bug 1747169] Re: Bionic update to v4.15.1 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

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

Title:
  Bionic update to v4.15.1 stable release

Status in linux package in Ubuntu:
  Fix Released

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 v4.15.1 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.15.1 stable release shall be
  applied:

  Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops
  tools/gpio: Fix build error with musl libc
  gpio: stmpe: i2c transfer are forbiden in atomic context
  gpio: Fix kernel stack leak to userspace
  ALSA: hda - Reduce the suspend time consumption for ALC256
  crypto: ecdh - fix typo in KPP dependency of CRYPTO_ECDH
  crypto: aesni - handle zero length dst buffer
  crypto: aesni - fix typo in 

[Kernel-packages] [Bug 1748072] Re: Bionic update to v4.15.2 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

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

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

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

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

Title:
  Bionic update to v4.15.2 stable release

Status in linux package in Ubuntu:
  Fix Released

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 v4.15.2 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.15.2 stable release shall be
  applied:

  KVM: x86: Make indirect calls in emulator speculation safe
  KVM: VMX: Make indirect call speculation safe
  module/retpoline: Warn about missing retpoline in module
  x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
  x86/cpufeatures: Add Intel feature bits for Speculation Control
  x86/cpufeatures: Add AMD feature bits for Speculation Control
  x86/msr: Add definitions for new speculation control MSRs
  x86/pti: Do not 

[Kernel-packages] [Bug 1747523] Re: support thunderx2 vendor pmu events

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-10.11

---
linux (4.15.0-10.11) bionic; urgency=medium

  * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)

  * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warning when __GFP_NOWARN is set
- drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in
(LP: #1744058)
- ALSA: hda/realtek - update ALC225 depop optimize

  * [Artful] Support headset mode for DELL WYSE (LP: #1723913)
- SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines

  * Bionic update to v4.15.3 stable release (LP: #1749191)
- ip6mr: fix stale iterator
- net: igmp: add a missing rcu locking section
- qlcnic: fix deadlock bug
- qmi_wwan: Add support for Quectel EP06
- r8169: fix RTL8168EP take too long to complete driver initialization.
- tcp: release sk_frag.page in tcp_disconnect
- vhost_net: stop device during reset owner
- ipv6: addrconf: break critical section in addrconf_verify_rtnl()
- ipv6: change route cache aging logic
- Revert "defer call to mem_cgroup_sk_alloc()"
- net: ipv6: send unsolicited NA after DAD
- rocker: fix possible null pointer dereference in
  rocker_router_fib_event_work
- tcp_bbr: fix pacing_gain to always be unity when using lt_bw
- cls_u32: add missing RCU annotation.
- ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only
- soreuseport: fix mem leak in reuseport_add_sock()
- net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
- net: sched: fix use-after-free in tcf_block_put_ext
- media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION
- media: soc_camera: soc_scale_crop: add missing
  MODULE_DESCRIPTION/AUTHOR/LICENSE
- media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
- gpio: uniphier: fix mismatch between license text and MODULE_LICENSE
- crypto: tcrypt - fix S/G table for test_aead_speed()
- Linux 4.15.3

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-5715 (Spectre v2 Intel)
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
- d-i: Add hfi1 to nic-modules

  * CVE-2017-5715 (Spectre v2 retpoline)
- [Packaging] retpoline -- add call site validation
- [Config] disable retpoline checks for first upload

  * Do not duplicate changelog entries assigned to more than one bug or CVE
(LP: #1743383)
- [Packaging] git-ubuntu-log -- handle multiple bugs/cves better

 -- Seth Forshee   Tue, 13 Feb 2018 11:33:58
-0600

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

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

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

Title:
  support thunderx2 vendor pmu events

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  ThunderX2 vendor pmu events are not supported.

  [Test Case]
  Successful output:
  $ sudo perf list | grep thunderx2
  thunderx2 imp def:
  $

  [Regression Risk]
  The code changes are restricted to the perf utility, so there's negligible 
risk to the kernel itself. All patches are clean cherry-picks except 1 where a 
hunk is dropped that was updating an API in code that didn't exist yet.

  I've tested on Cavium Sabre (a thunderx2 system), and smoke tested
  perf commands for regression on x86 (Dell XPS13 9350).

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

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