[Kernel-packages] [Bug 1790249] Re: desktop sharing won't start after upgrading to 18.04

2018-10-01 Thread Kai-Heng Feng
Do you use Unity or GNOME?

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

Title:
  desktop sharing won't start after upgrading to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  First time destop sharing was started the system detected a problem
  which was reported -- so there should be some info for you there
  already.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mat1234 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Sep  1 11:17:29 2018
  HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668
  InstallationDate: Installed on 2017-02-12 (565 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE GB-BACE-3000
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago)
  dmi.bios.date: 03/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBSWAP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GB-BACE-3000
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

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


[Kernel-packages] [Bug 1793849] Re: dazzle dvc 80 usb video capture card

2018-10-01 Thread m
I'm on ubuntu 18.04 not sure how to check kernel version and I don't
want to mess with it on this computer. I haven't used the card for a
long time and the last time was on windows. Just thought I'd plug it in
and try, unfortunately it seems to fail.

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

Title:
  dazzle dvc 80 usb video capture card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is my first bug report hope I did alright

  see

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/302728

  my dazzle card didn't give any input into vlc open capture device tv
  analog.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  apt-cache policy vlc
  vlc:
Installed: 3.0.3-1-1ubuntu1
Candidate: 3.0.3-1-1ubuntu1
Version table:
   *** 3.0.3-1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.0.1-3build1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   mitch  3894 F...m pulseaudio
   /dev/snd/controlC0:  mitch  3894 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 22 00:27:26 2018
  HibernationDevice: RESUME=UUID=d312420c-13df-48ae-9f72-e529f9de1a33
  InstallationDate: Installed on 2017-04-24 (515 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System76, Inc. Kudu
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=7a07e949-7c6b-40db-bff1-f3ae8ef18501 ro acpi_backlight=vendor quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Kudu
  dmi.board.vendor: System76, Inc.
  dmi.board.version: kudu2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08RSA1:bd03/31/2016:svnSystem76,Inc.:pnKudu:pvrkudu2:rvnSystem76,Inc.:rnKudu:rvrkudu2:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Kudu
  dmi.product.version: kudu2
  dmi.sys.vendor: System76, Inc.

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

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


[Kernel-packages] [Bug 1717856] Re: Kernel security test test_021_aslr_dapper_libs failed on 3.2 Precise i386

2018-10-01 Thread Po-Hsu Lin
** 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/1717856

Title:
  Kernel security test test_021_aslr_dapper_libs failed on 3.2 Precise
  i386

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Confirmed

Bug description:
  Kernel: 3.2.0-131 Precise (i386)

  This is not a regression, as this issue can be reproduced on older kernel.
  AMD64 system does not have this issue. 

  FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
  ASLR of libs
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 1827, in test_021_aslr_dapper_libs
  self._test_aslr('libs', expected)
  File "./test-kernel-security.py", line 1790, in _test_aslr
  self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1767, in _test_aslr_all
  self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1760, in _test_aslr_exec
  self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
  self.assertEqual(expected, rc, msg + result + report)
  AssertionError: unlimited stack libs native:
  Got exit code 1, expected 0
  Command: './aslr', 'libs', '--verbose'
  Output:
  Checking ASLR of libs:
  0x4002bd80
  0x4002bd80
  0x4002bd80
  FAIL: ASLR not functional (libs always at 0x4002bd80)

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

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


[Kernel-packages] [Bug 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

2018-10-01 Thread Po-Hsu Lin
** 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/1747630

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

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

Bug description:
  This issue can be reproduced in 3.2.0-133 in proposed and 3.2.0-131.
  So it should not be considered as a regression.

  We didn't spot this issue before, until I'm testing 3.2 kernel on one
  of the laptop (CID 201307-13930) in Cert lab instead of using our
  regular regression-testing test pool from kernel team this cycle.

    ==
    FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
    ASLR of vdso
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
    self._test_aslr('vdso', expected)
  File "./test-kernel-security.py", line 1795, in _test_aslr
    self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1772, in _test_aslr_all
    self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1765, in _test_aslr_exec
    self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
    self.assertEqual(expected, rc, msg + result + report)
    AssertionError: unlimited stack vdso native:
    Got exit code 1, expected 0
    Command: './aslr', 'vdso', '--verbose'
    Output:
    Checking ASLR of vdso:
     0x40022000
     0x40022000
     0x40022000
    FAIL: ASLR not functional (vdso always at 0x40022000)

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

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


[Kernel-packages] [Bug 1795541] Re: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?]

2018-10-01 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1757008 ***
https://bugs.launchpad.net/bugs/1757008

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1757008, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- bcmwl-kernel-source (not installed): bcmwl kernel module failed to build
+ bcmwl-kernel-source (not installed): bcmwl kernel module failed to build 
[error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’?]

** This bug has been marked a duplicate of bug 1757008
   Broadcom wireless drivers failed to build [error: implicit declaration of 
function ‘init_timer’]

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

Title:
  bcmwl-kernel-source (not installed): bcmwl kernel module failed to
  build [error: implicit declaration of function ‘init_timer’; did you
  mean ‘init_timers’?]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  just find

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-34-generic
  Date: Mon Sep 24 09:05:43 2018
  DuplicateSignature: dkms:bcmwl-kernel-source:(not 
installed):/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  PackageVersion: (not installed)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-10-01 Thread 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 1775068

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

Title:
  Volume control not working Dell XPS 27 (7760)

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

Bug description:
  Pressing vol up/vol down show OSD change up/down but volume all time
  is at 100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1610 F pulseaudio
   /dev/snd/controlC1:  trolinka   1610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (121 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.
  ---

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

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


[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

2018-10-01 Thread Kai-Heng Feng
That means the workaround (increases the input length to 64) that works
for me doesn't work for you.

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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


[Kernel-packages] [Bug 1795256] Re: frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-01 Thread Daniel van Vugt
Looks like the kernel crash is related to networking. If you can please
try disabling wifi and using a wired ethernet connection for testing.
Does that avoid it?

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

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
  00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

  
  aravind@comp:~$ sudo lshw
  [sudo] password for aravind: 
  comp
  description: Notebook
  product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
  vendor: Acer
  version: V1.25
  serial: NXGDWSI034717145457600
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
*-core
 description: Motherboard
 product: Ironman_SK
 vendor: Acer
 physical id: 0
 version: V1.25
 serial: NBGD411006717145457600
 slot: Type2 - Board Chassis Location
   *-firmware
description: BIOS
vendor: Insyde Corp.
physical id: 0
version: V1.25
date: 03/03/2017
size: 128KiB
capacity: 4544KiB
capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
   *-cpu
description: CPU
product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
flush_l1d cpufreq
configuration: cores=2 enabledcores=2 

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

2018-10-01 Thread 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/1795256

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
  00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

  
  aravind@comp:~$ sudo lshw
  [sudo] password for aravind: 
  comp
  description: Notebook
  product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
  vendor: Acer
  version: V1.25
  serial: NXGDWSI034717145457600
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
*-core
 description: Motherboard
 product: Ironman_SK
 vendor: Acer
 physical id: 0
 version: V1.25
 serial: NBGD411006717145457600
 slot: Type2 - Board Chassis Location
   *-firmware
description: BIOS
vendor: Insyde Corp.
physical id: 0
version: V1.25
date: 03/03/2017
size: 128KiB
capacity: 4544KiB
capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
   *-cpu
description: CPU
product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
flush_l1d cpufreq
configuration: cores=2 enabledcores=2 threads=4
  *-cache:0
   description: L1 cache
 

[Kernel-packages] [Bug 1795256] Re: frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-01 Thread Daniel van Vugt
Thanks. Unfortunately that only shows minor app crashes in the past
month.

Looking back at your CurrentDmesg.txt though, I can see one kernel crash
which is probably more relevant:

[ 1878.739957] WARNING: CPU: 2 PID: 0 at 
/build/linux-SlLHxe/linux-4.15.0/net/core/dev.c:5645 net_rx_action+0x2cb/0x3a0
[ 1878.739959] Modules linked in: rfcomm ccm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) bnep binfmt_misc 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp 
snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_codec_realtek intel_rapl snd_hda_codec_generic 
x86_pkg_temp_thermal intel_powerclamp snd_hda_intel snd_hda_codec kvm_intel kvm 
snd_hda_core irqbypass snd_hwdep crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_pcm btusb pcbc arc4 aesni_intel snd_seq_midi 
snd_seq_midi_event input_leds btrtl sch_fq_codel joydev aes_x86_64 btbcm 
rtsx_pci_ms crypto_simd btintel bluetooth ath10k_pci snd_rawmidi serio_raw 
ath10k_core ath glue_helper cryptd intel_cstate snd_seq snd_seq_device 
snd_timer intel_rapl_perf
[ 1878.739987]  intel_wmi_thunderbolt uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media snd mac80211 
acer_wmi memstick ecdh_generic sparse_keymap wmi_bmof intel_pch_thermal 
soundcore cfg80211 idma64 mei_me mei acpi_pad shpchp virt_dma intel_lpss_pci 
intel_lpss mac_hid coretemp parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse rtsx_pci r8169 mii drm 
ahci libahci wmi video
[ 1878.740010] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G   OE
4.15.0-34-generic #37-Ubuntu
[ 1878.740011] Hardware name: Acer Aspire E5-575G/Ironman_SK  , BIOS V1.25 
03/03/2017
[ 1878.740013] RIP: 0010:net_rx_action+0x2cb/0x3a0
[ 1878.740014] RSP: 0018:8db72ed03ec8 EFLAGS: 00010297
[ 1878.740015] RAX: 0041 RBX: 0040 RCX: 8db71e2f1e28
[ 1878.740016] RDX: 8db4f4402000 RSI: fe01 RDI: c084b280
[ 1878.740016] RBP: 8db72ed03f38 R08: 0002 R09: 
[ 1878.740017] R10: 2f30 R11: 0001 R12: 
[ 1878.740017] R13:  R14: 0003 R15: 8db71e2f7b60
[ 1878.740019] FS:  () GS:8db72ed0() 
knlGS:
[ 1878.740019] CS:  0010 DS:  ES:  CR0: 80050033
[ 1878.740020] CR2: 7fa94f598000 CR3: 00026180a002 CR4: 003606e0
[ 1878.740021] Call Trace:
[ 1878.740022]  
[ 1878.740025]  __do_softirq+0xe4/0x2bb
[ 1878.740028]  irq_exit+0xb8/0xc0
[ 1878.740029]  do_IRQ+0x8a/0xd0
[ 1878.740031]  common_interrupt+0x84/0x84
[ 1878.740031]  
[ 1878.740034] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
[ 1878.740034] RSP: 0018:a9d440d1be68 EFLAGS: 0246 ORIG_RAX: 
ffd9
[ 1878.740035] RAX: 8db72ed22880 RBX: 01b56d9c6a1a RCX: 001f
[ 1878.740036] RDX: 01b56d9c6a1a RSI: fffb7a9ba1ce RDI: 
[ 1878.740037] RBP: a9d440d1bea8 R08: 058c R09: 03c3
[ 1878.740037] R10: a9d440d1be38 R11: 04fe R12: 8db72ed2c700
[ 1878.740038] R13: 0006 R14: a0171d38 R15: 
[ 1878.740040]  ? cpuidle_enter_state+0x97/0x2f0
[ 1878.740042]  cpuidle_enter+0x17/0x20
[ 1878.740044]  call_cpuidle+0x23/0x40
[ 1878.740045]  do_idle+0x18c/0x1f0
[ 1878.740047]  cpu_startup_entry+0x73/0x80
[ 1878.740048]  start_secondary+0x1ab/0x200
[ 1878.740050]  secondary_startup_64+0xa5/0xb0
[ 1878.740051] Code: 24 08 49 83 c4 18 89 d9 44 89 f2 4c 89 fe e8 dd 2c 3b 00 
4d 8b 14 24 4d 85 d2 75 e1 4c 8b 65 90 44 89 f0 39 c3 0f 8d 85 fe ff ff <0f> 0b 
39 c3 0f 8f 83 fe ff ff 49 8b 47 10 a8 04 75 74 49 83 7f 
[ 1878.740074] ---[ end trace ea9ec2e49eac7947 ]---

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

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

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

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB 

[Kernel-packages] [Bug 1795256] [NEW] frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I had same problem in Ubuntu 16.04.3. But not frequent. It was happening
when I play HD video. But now after installing Ubuntu 18.04 the same
problem even when browsing. Its too frequent.

I have tried to reinstall Intel-microcode, bumblebee, xorg video
drivers. No improvement.

The system don't crash even show error message in dmesg and journalctl.

aravind@comp:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter (rev 31)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 12)


aravind@comp:~$ sudo lshw
[sudo] password for aravind: 
comp
description: Notebook
product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
vendor: Acer
version: V1.25
serial: NXGDWSI034717145457600
width: 64 bits
capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
  *-core
   description: Motherboard
   product: Ironman_SK
   vendor: Acer
   physical id: 0
   version: V1.25
   serial: NBGD411006717145457600
   slot: Type2 - Board Chassis Location
 *-firmware
  description: BIOS
  vendor: Insyde Corp.
  physical id: 0
  version: V1.25
  date: 03/03/2017
  size: 128KiB
  capacity: 4544KiB
  capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
 *-cpu
  description: CPU
  product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
  vendor: Intel Corp.
  physical id: 4
  bus info: cpu@0
  version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
  serial: To Be Filled By O.E.M.
  slot: U3E1
  size: 799MHz
  capacity: 4005MHz
  width: 64 bits
  clock: 100MHz
  capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce 
cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
flush_l1d cpufreq
  configuration: cores=2 enabledcores=2 threads=4
*-cache:0
 description: L1 cache
 physical id: 5
 slot: L1 Cache
 size: 128KiB
 capacity: 128KiB
 capabilities: synchronous internal write-back unified
 configuration: level=1
*-cache:1
 description: L2 cache
 physical id: 6
 slot: L2 Cache
 size: 512KiB
 capacity: 512KiB
 capabilities: synchronous internal write-back unified
 configuration: level=2
*-cache:2
 

[Kernel-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)

2018-10-01 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => 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/1775068

Title:
  Volume control not working Dell XPS 27 (7760)

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pressing vol up/vol down show OSD change up/down but volume all time
  is at 100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1610 F pulseaudio
   /dev/snd/controlC1:  trolinka   1610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (121 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.
  ---

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

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


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

2018-10-01 Thread Daniel van Vugt
Oh. Except comment #13 says not.

** Changed in: canonical-devices-system-image
   Status: Fix Released => Confirmed

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

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5 when phone
  initiates connection

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

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


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

2018-10-01 Thread Daniel van Vugt
I assume this was released...

https://code.launchpad.net/~bluetooth/bluez/new-rel-5-37-plus-touch-
xenial-sync/+merge/283734

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

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5 when phone
  initiates connection

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

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


[Kernel-packages] [Bug 1795541] Re: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build

2018-10-01 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source (not installed): bcmwl kernel module failed to
  build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  just find

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-34-generic
  Date: Mon Sep 24 09:05:43 2018
  DuplicateSignature: dkms:bcmwl-kernel-source:(not 
installed):/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  PackageVersion: (not installed)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1795541] [NEW] bcmwl-kernel-source (not installed): bcmwl kernel module failed to build

2018-10-01 Thread Liangliang
Public bug reported:

just find

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
DKMSKernelVersion: 4.15.0-34-generic
Date: Mon Sep 24 09:05:43 2018
DuplicateSignature: dkms:bcmwl-kernel-source:(not 
installed):/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
PackageVersion: (not installed)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: bcmwl
Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  bcmwl-kernel-source (not installed): bcmwl kernel module failed to
  build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  just find

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-34-generic
  Date: Mon Sep 24 09:05:43 2018
  DuplicateSignature: dkms:bcmwl-kernel-source:(not 
installed):/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  PackageVersion: (not installed)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source (not installed): bcmwl kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

2018-10-01 Thread Guilherme G. Piccoli
Hi Guo, thanks for your tests!

So, to confirm:

a) With Ubuntu kernel 4.15.0-34, using the kernel parameter
"nvme_core.multipath=0", you _don't_ see the issue;

b) With kernel 4.17.0-041700rc1-generic, even using the parameter
"nvme_core.multipath=0", you *can reproduce* the issue.

Right?


I've noticed that the fix patch is present in v4.17-rc4, but I see a "rc1" in 
your kernel version - it could explain why even in this 4.17 version you can 
reproduce the issue.
I'll build an upstream 4.17 and re-test in my environment, to double-check if 
it fixes for me.

Cheers,


Guilherme

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

Title:
  nvme name floated after boot with 4.15.0 kernel

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

Bug description:
  nvme device name such as /dev/nvme?n?p? would be floated that is
  symbol link to different real ssd device after reboot in 4.15.0 kernel
  for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA-
  kernel ( 4.4.0)

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

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


[Kernel-packages] [Bug 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2018-10-01 Thread Joseph Salisbury
A bionic test kernel is also available with commits 3dbe97efe8bf and
9f0e89359775 applied.

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

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

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

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

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

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


[Kernel-packages] [Bug 1795116] Re: large performance regression (~20-40%) in wifi with 4.15.0-33 and later

2018-10-01 Thread arQon
marked as confirmed per #3 and #4.

i have the apport file stashed away and can upload it as an attachment
upon request if anyone's interested.

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

Title:
  large performance regression (~20-40%) in wifi with 4.15.0-33 and
  later

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  16.04 install using the HWE stack. after several weeks of uptime on
  -32, an update to -34 showed a major drop in wifi throughput,
  dependent solely on the kernel chosen:

  $  uname -a && ./wifibench.sh 
  Linux brix 4.15.0-32-generic #35~16.04.1-Ubuntu SMP Fri Aug 10 21:54:34 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Tue 25-Sep-18 06:07
  PlatformSDK-SVR2003R2.iso
  429,840,384 100%8.41MB/s0:00:48 (xfr#1, to-chk=0/1)
  sent 429,945,420 bytes  received 35 bytes  8,685,766.77 bytes/sec

  $  uname -a && ./wifibench.sh 
  Linux brix 4.15.0-34-generic #37~16.04.1-Ubuntu SMP Tue Aug 28 10:44:06 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Tue 25-Sep-18 06:14
  PlatformSDK-SVR2003R2.iso
  429,840,384 100%4.83MB/s0:01:24 (xfr#1, to-chk=0/1)
  sent 429,945,420 bytes  received 35 bytes  5,028,601.81 bytes/sec

  (the script is a simple rsync from a NAS. nothing in the NAS, or the
  router, or the physical positions of the devices or etc etc has
  changed, let alone in those 7 minutes).

  there is no interference, no other devices connected, etc.
  prior to the transfer, the link quality is 62-64 and the signal similarly 
weaker because of power saving, but once packets are in flight it looks perfect:

  $  iwconfig 
  wlan0 IEEE 802.11  ESSID:""
Mode:Managed  Frequency:2.452 GHz  Access Point:    
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=70/70  Signal level=10 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:15   Missed beacon:0

  the client is a J1900-based (baytrail) machine with a RTL8723BE wifi module. 
average performance while on -32 was consistently 70-80 Mb/s, over a period of 
several weeks. with -33 and later, it's generally 50-65.
  (that machine has no access to launchpad. i'll try apport-cli over the 
weekend).

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

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


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

2018-10-01 Thread Luiz
Correction:

xrandr --output eDP-1-1 --set "PRIME Synchronization" 1
xrandr --output HDMI-1-1 --set "PRIME Synchronization" 1

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

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

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

Bug description:
  SRU Request:

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

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

  The solution involves the following changes:

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

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

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

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

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

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

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

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

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

  5) Log out and log back in

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

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

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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


[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

2018-10-01 Thread Ascaris
Kai-Heng Feng,

I installed the kernel as linked in post #18.  It installed without a
problem and booted and ran on the laptop just like the official kernels.
I've confirmed it is 4.19.1 running.

Unfortunately, dmesg still reports many multiples of the error in
question each time I use the touchpad (about 100 instances of this error
per second the whole time I am using the touchpad):

i2c_hid i2c-ELAN0501:00: i2c_hid_get_input: incomplete report (64/65535)

Note that the 14/65535 from the previous kernels has changed to
64/65535.  I don't have any idea what the significance of that is, but
it's a change.

Do you need another udevadm report for this kernel too?  I will be happy
to provide one if it will help.

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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


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

2018-10-01 Thread Luiz
I am ubuntu on 18.04.1 LTS.

With intel integrated gpu things are normal. With my nvidia gpu occured
two problems:

* I disabled login screen because it was creating two intances of Xorg
and gnome-shell each. I can see these with top and nvidia-smi. It
decreased cpu temps a lot even in idle time.

* the other is drop down fps while playing steam games. I create a
session autostart script to enable prime synchronization on my external
monitor. It solves drop down fps were sometimes unplayable.

that's the script: prime.sh ( gnome-session-properties add tool )

#!/bin/bash
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --output HDMI-1-1 --primary
xrandr --output eDP-1-1 --set "PRIME Synchronization" 0
xrandr --output HDMI-1-1 --set "PRIME Synchronization" 0

For some reason when I switch monitor from integrated notebook display
to my external monitor, the prime synchronization doesn't occurs. One
prove of that is mouse trail(while nvidia profile is loaded) and in
games variation fps with drop down. sometimes over 60 others below 5fps.

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

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

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

Bug description:
  SRU Request:

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

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

  The solution involves the following changes:

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

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

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

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

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

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

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

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

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

  5) Log out and log back in

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

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

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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

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

2018-10-01 Thread 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/1795509

Title:
  Kernel bug after removing Hauppauge WinTV-dualHD (em28xx/si2157)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This kernel bug happens right after removing the usb connector. No
  streams were running.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.18.0-7-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Mon Oct  1 23:06:15 2018
  HibernationDevice: RESUME=UUID=7185b930-4c2c-4378-ad3c-78672310683f
  IwConfig:
   tun0  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/hostname-root ro consoleblank=0 quiet noresume
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-01 (0 days ago)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: J3160DC-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/31/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ3160DC-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

2018-10-01 Thread Joseph Salisbury
I built a Bionic test kernel with a patch from upstream. The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1736390

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

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  In Progress
Status in openvswitch package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Won't Fix
Status in openvswitch source package in Artful:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in openvswitch source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  In Progress
Status in openvswitch source package in Cosmic:
  Invalid

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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


[Kernel-packages] [Bug 1795509] [NEW] Kernel bug after removing Hauppauge WinTV-dualHD (em28xx/si2157)

2018-10-01 Thread Morty
Public bug reported:

This kernel bug happens right after removing the usb connector. No
streams were running.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-7-generic 4.18.0-7.8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.18.0-7-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Date: Mon Oct  1 23:06:15 2018
HibernationDevice: RESUME=UUID=7185b930-4c2c-4378-ad3c-78672310683f
IwConfig:
 tun0  no wireless extensions.
 
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/hostname-root ro consoleblank=0 quiet noresume
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-7-generic N/A
 linux-backports-modules-4.18.0-7-generic  N/A
 linux-firmware1.175
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-01 (0 days ago)
dmi.bios.date: 03/31/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: J3160DC-ITX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/31/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ3160DC-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Kernel bug after removing Hauppauge WinTV-dualHD (em28xx/si2157)

Status in linux package in Ubuntu:
  New

Bug description:
  This kernel bug happens right after removing the usb connector. No
  streams were running.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.18.0-7-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Mon Oct  1 23:06:15 2018
  HibernationDevice: RESUME=UUID=7185b930-4c2c-4378-ad3c-78672310683f
  IwConfig:
   tun0  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/hostname-root ro consoleblank=0 quiet noresume
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  

[Kernel-packages] [Bug 1795413] Re: linux-kvm: 4.18.0-1002.2 -proposed tracker

2018-10-01 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the 4.18.0-1002.2 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 --
  kernel-master-bug: 1791663
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Monday, 01. October 2018 20:33 UTC

** Description changed:

  This bug is for tracking the 4.18.0-1002.2 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 --
  kernel-master-bug: 1791663
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Monday, 01. October 2018 20:33 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-kvm: 4.18.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.0-1002.2 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 --
  kernel-master-bug: 1791663
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

2018-10-01 Thread Dmitry
I have HP Elitebook 850 G5 and I'm experiencing this issue too.
Here is my udevadm info -e.

** Attachment added: "udevadm info -e"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+attachment/5195454/+files/udevadm.info.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/1784152

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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


[Kernel-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

2018-10-01 Thread Dan Watkins
** Changed in: cloud-images
   Status: Confirmed => Fix Released

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  [SRU Justfication, Artful]

  [Impact]

  Booting the 4.13 Artful kernel with vagrant using VirtualBox trips the
  warning:

  [ 61.010337] VFS: brelse: Trying to free free buffer
  [ 61.114875] [ cut here ]
  [ 61.114886] WARNING: CPU: 0 PID: 683 at 
/build/linux-XO_uEE/linux-4.13.0/fs/buffer.c:1205 __brelse+0x21/0x30

  and a failed resize of a partition.  The root cause has been bisected
  down to the following commmit:

  commit c20cfc27a47307e811346f85959cf3cc07ae42f9
  Author: Christoph Hellwig 
  Date: Wed Apr 5 19:21:07 2017 +0200

  block: stop using blkdev_issue_write_same for zeroing

  
  [Fix]
  The Upstream commit directly fixes this issue:

  commit d5ce4c31d6df518dd8f63bbae20d7423c5018a6c
  Author: Ilya Dryomov 
  Date:   Mon Oct 16 15:59:10 2017 +0200

  block: cope with WRITE ZEROES failing in blkdev_issue_zeroout()

  ..however we also require a backport of the following upstream commit
  to apply the above commit cleanly.

  commit 425a4dba7953e35ffd096771973add6d2f40d2ed
  Author: Ilya Dryomov 
  Date:   Mon Oct 16 15:59:09 2017 +0200

  block: factor out __blkdev_issue_zero_pages()

  [Testscase]

  On Ubuntu Xenial:

  1. sudo apt-get install virtualbox vagrant
  2. edit /etc/group and add one's user name to the vboxusers group
  3. log out log back
  4. vagrant init ubuntu/artful64
  5. vagrant up
  6. vagrant ssh
  7. dmesg | grep "VFS: brelse"

  without the fix one will see the VFS brelse warning message and the /
  partition will not have been resized.

  with a fixed system there is is no VFS vbrelse warning and / as been
  resized as expected.

  [Regresion potential]
  These patches touch the blk library so potentially it could break the block 
layer and corrupt data on disk.  However these are upstream fixes that address 
the buggy commit c20cfc27a47307e811346f85959cf3cc07ae42f9 and are known to 
address the bug.

  ---


  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  With artful64, the size of /dev/sda1 is reported as 2.2G, which
  results in 97% of disk usage immediately after building, even though
  the disk size is 10G, as reported by the fdisk:

  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  Almost any additional installation results in a "No space left on
  device" error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

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


[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails

2018-10-01 Thread Joseph Salisbury
I built a second test kernel.

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

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

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

Title:
  Mounting SOFS SMB shares fails

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

Bug description:
  Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
  cifs-utils 2:6.8-1

  Mounting scale-out SMB shares is failing.

  mount -t cifs -o 
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs 
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  What works:
  * mounting the share from a 16.04 host
  * mounting standalone smb3 shares

  Relevant error from the log (full logs attached separately):
  Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9 
STATUS_NETWORK_NAME_DELETED
  Sep 14 11:12:05 r07-u13 kernel: 
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status 
code 0xc0c9 to POSIX err -5

  Share server os: Windows Server 2016 10.0.14393
  PS C:\Users\jujuadmin> get-smbshare glance-images | fl *

  ShareState: Online
  AvailabilityType  : ScaleOut
  ShareType : FileSystemDirectory
  FolderEnumerationMode : Unrestricted
  CachingMode   : Manual
  SmbInstance   : Default
  CATimeout : 0
  ConcurrentUserLimit   : 0
  ContinuouslyAvailable : True
  CurrentUsers  : 2
  Description   :
  EncryptData   : False
  Name  : glance-images
  Path  : C:\ClusterStorage\Volume1\GLANCE-IMAGES
  Scoped: True
  ScopeName : S2DSCALEOUT
  ShadowCopy: False
  Special   : False
  Temporary : False
  Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  7 16:51 seq
   crw-rw 1 root audio 116, 33 Sep  7 16:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  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:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R710
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-33-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.4.0
  dmi.board.name: 0YDJK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R710
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1693123] Re: nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory

2018-10-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin
  /nvidia-persistenced: No such file or directory

Status in Nvidia:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-persistenced package in Ubuntu:
  Confirmed

Bug description:
  If you install the nvidia-384 package, you get an enabled nvidia
  persistenced.service that fails to start up on boot, because it tries
  to launch /usr/bin/nvidia-persistenced which doesn’t exist (the binary
  is actually at /usr/lib/nvidia-384/bin/nvidia-persistenced).

  $ systemctl status nvidia-persistenced.service
  ● nvidia-persistenced.service - NVIDIA Persistence Daemon
 Loaded: loaded (/lib/systemd/system/nvidia-persistenced.service; static; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Wed 2017-12-20 19:20:45 EST; 7min 
ago
Process: 1265 ExecStopPost=/bin/rm -rf /var/run/nvidia-persistenced 
(code=exited, status=0/SUCCESS)
Process: 1262 ExecStart=/usr/bin/nvidia-persistenced --user 
nvidia-persistenced --no-persistence-mode --verbose (code=exited, 
status=203/EXEC)

  Dec 20 19:20:45 change-mode systemd[1]: Starting NVIDIA Persistence Daemon...
  Dec 20 19:20:45 change-mode systemd[1262]: nvidia-persistenced.service: 
Failed to execute command: No such file or directory
  Dec 20 19:20:45 change-mode systemd[1262]: nvidia-persistenced.service: 
Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or 
directory
  Dec 20 19:20:45 change-mode systemd[1]: nvidia-persistenced.service: Control 
process exited, code=exited status=203
  Dec 20 19:20:45 change-mode systemd[1]: nvidia-persistenced.service: Failed 
with result 'exit-code'.
  Dec 20 19:20:45 change-mode systemd[1]: Failed to start NVIDIA Persistence 
Daemon.

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

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


[Kernel-packages] [Bug 1795413] Re: linux-kvm: 4.18.0-1002.2 -proposed tracker

2018-10-01 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.18.0-1002.2 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 --
  kernel-master-bug: 1791663
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Monday, 01. October 2018 19:33 UTC

** Description changed:

  This bug is for tracking the 4.18.0-1002.2 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 --
  kernel-master-bug: 1791663
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Monday, 01. October 2018 19:33 UTC
+ phase: Uploaded

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

Title:
  linux-kvm: 4.18.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.0-1002.2 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 --
  kernel-master-bug: 1791663
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1793837] Re: xorg gives low resolution on HDMI port

2018-10-01 Thread Peter Jaeckel
No better luck with 4.19.0-041900rc6-generic.
Upon reboot, running at 1920x1080 *interlaced*. No good - I am getting the 
shakes just watching the screen. And it is slightly blurred.
Thanks for all the help and hard work!
pj

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

Title:
  xorg gives low resolution on HDMI port

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is a Zotac CI547 box. It has to video outputs: one HDMI and one
  DisplayPort. The HDMI port appears as DP-1 in the logs, the
  DisplayPort as DP-2. The hardware is Intel HD 620 and is allegedly
  able to run two displays simultaneously at 4K. I have one WQHD monitor
  (=2560x1440) and I get that full resolution over the DisplayPort.
  However, I would like to also get that resolution over the HDMI port
  (in order to connect two identical monitors), but over HDMI I only get
  1024x768. Updating the kernel to the latest 4.18.8 using UKUU made no
  difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.18.8-041808-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Sep 22 00:21:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 620 [8086:]
  InstallationDate: Installed on 2018-09-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.8-041808-generic 
root=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef ro quiet splash 
acpi_backlight=native pci=nomsi 
resume=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef resume_offset=34816 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P206
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P206:bd04/25/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: NA
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1793837] Re: xorg gives low resolution on HDMI port

2018-10-01 Thread Peter Jaeckel
No change with kernel 4.19.0-041900rc5-generic, alas.

The bizarre thing is the Xorg log (~/.local/share/xorg/Xorg.0.log)
saying

 [11.016] (II) modeset(0): Supported established timings:

and subsequently the finest mode being 1280x1024@75Hz. Then, in the
section(s) called

 [11.017] (II) modeset(0): Supported detailed timing:

it does include a mode with "clock: 241.5 MHz" and 2560x1440. It also
says later:

 [11.017] (--) modeset(0): HDMI max TMDS frequency 25KHz

so it is happy up to 250MHz. And much later, it says

 [11.906] (II) modeset(0): Printing DDC gathered Modelines:
 [11.906] (II) modeset(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)

and so on, i.e., including a 2560x1440 mode.

I do not understand that parts are happily talking about the maximum
resolution of the monitor via HDMI, and other parts seem to not know
anything about it.

Any help welcome. Would you like me to try the intel driver (again)?

pj

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

Title:
  xorg gives low resolution on HDMI port

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is a Zotac CI547 box. It has to video outputs: one HDMI and one
  DisplayPort. The HDMI port appears as DP-1 in the logs, the
  DisplayPort as DP-2. The hardware is Intel HD 620 and is allegedly
  able to run two displays simultaneously at 4K. I have one WQHD monitor
  (=2560x1440) and I get that full resolution over the DisplayPort.
  However, I would like to also get that resolution over the HDMI port
  (in order to connect two identical monitors), but over HDMI I only get
  1024x768. Updating the kernel to the latest 4.18.8 using UKUU made no
  difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.18.8-041808-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Sep 22 00:21:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 620 [8086:]
  InstallationDate: Installed on 2018-09-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.8-041808-generic 
root=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef ro quiet splash 
acpi_backlight=native pci=nomsi 
resume=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef resume_offset=34816 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P206
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P206:bd04/25/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: NA
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1785780] Re: TB 16 issue on Dell Lattitude 7490 with large amount of data

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1786902] Re: [18.10 FEAT] SMC-Direct

2018-10-01 Thread Andrew Cloke
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [18.10 FEAT] SMC-Direct

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

Bug description:
  Provide support for next generation HiperSockets.
  SMC-local (Shared Memory Communications -- local) provides a new architecture 
for high performance networking within a CEC. Buffers in the HSA can be shared 
between LPARs and will be used for communication.
  A new socket family will be used to eliminate TCP overhead. Integration with 
existing tooling through TCP handshaking.
  A preload library can be used to enable applications to use the new socket 
family transparently

  Backport from kernel 4.19 will be attached.

  For SMC enabling following kernel config has to be set
  CONFIG_HAVE_PNETID.

  With this setting an additoiponal modul need to be build : pnet.ko

  @canonical kernel team:
  please cherrypick:
  Here you go - sorry for the delay!
  In sequence, from oldest to latest:

  ddb457c6993babbcdd41fca638b870d2a2fc3941
  be6a3f38ff2a2bfd2e591fdc566940a0d4d9428c
  0afff91c6f5ecef27715ea71e34dc2baacba1060
  c6ba7c9ba43de1b57e9a53946e7ff988554c84ed
  1619f770589a183af56f248de261534b255122de
  c758dfddc1b5b1c9b8c64e5e4bb9bf24b74f4a59
  be244f28d22f77d939ba2b973c102ad2b49d3496
  413498440e30bfe381ac99dfc31628a3d8d4382a
  4b1b7d3b30a6d32ac1a1dcede284e76ef8a8542d
  c601171d7a60b5b09d7c2fe0579953323a80744e
  bac6de7b637018f4caacfdf2b4ad8c8749de7420
  00e5fb263f9f5f2af60754b79b7dcec0d5e88154
  144ce4b9b5a788953b5373162a1921267497fb38
  48bf5231771c7e3961c8326353b6027b1bed6eb5
  12c36dcfd6f48ece2fce4dc8e6ce68224d005d37
  2e3bbe46b4a18d16314dab0c0efdba0c079a5ed0
  947541f36c561b5e0ca639ffc450a8c5221de467
  7005ada68d1774d7c1109deaba0c2cd8e46f5091
  603cc1498455cf57f5ca4483b600efb37ea2c56c
  0d18a0cb4b1585d9e5a3b300d5df9ed866561ffb
  dd979b4df817e9976f18fb6f9d134d6bc4a3c317
  0d86caff06363151df21603eb1f4e3207ea91bd2

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

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


[Kernel-packages] [Bug 1791663] Re: linux: 4.18.0-8.9 -proposed tracker

2018-10-01 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports:
  derivatives: bug 1791664 (linux-azure)
  -- swm properties --
  backports: null
  derivatives: null
  phase: Promoted to proposed
+ kernel-phase-changed:Monday, 01. October 2018 19:02 UTC
+ kernel-phase:Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports:
  derivatives: bug 1791664 (linux-azure)
  -- swm properties --
  backports: null
  derivatives: null
- phase: Promoted to proposed
- kernel-phase-changed:Monday, 01. October 2018 19:02 UTC
- kernel-phase:Released
+ phase: Released

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

Title:
  linux: 4.18.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

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

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

  backports:
  derivatives: bug 1791664 (linux-azure)
  -- swm properties --
  backports: null
  derivatives: null
  phase: Released

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

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


[Kernel-packages] [Bug 1794067] Re: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34

2018-10-01 Thread Joseph Salisbury
The test kernel I posted is built on top of upstream 4.15.18.  To
confirm this is an Ubuntu specific bug, can you test 4.15.18?  It can be
downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/

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

Title:
  Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34

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

Bug description:
  Hello, just found a bug in selinux.

  Whats going wrong:

  Copy a link with "-a" option while selinux is on.

  steps to reproduce:

  ~$ mkdir -p a/b
  ~$ ln -s b a/c
  ~$ cp -a a b
  cp: failed to restore the default file creation context: Invalid argument

  Results of my investigation:

  The "cp" of coreutils is calling "setfscreatecon (NULL)" to restore
  the default file creation context (coreutils-8.30/src/copy.c:1771) as
  it is stated in the selinux api
  (/libselinux/include/selinux/selinux.h:71).

  As we see in the result of strace below, the kernel returns an -1 on
  try to restore the default file creation context. So in my opinion is
  the bug has to be in the selinux_setprocattr method in the
  security/selinux/hooks.c file.

  Part of "strace cp -a a b"

  lgetxattr("a/c", "security.selinux", "system_u:object_r:user_home_dir_t:s0", 
255) = 37
  readlink("a/c", "b", 2) = 1
  symlink("b", "b/a/c") = 0
  open("/proc/self/task/2136/attr/fscreate", O_RDWR|O_CLOEXEC) = 3
  write(3, NULL, 0) = -1 EINVAL (Invalid argument)
  close(3) = 0
  open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
  read(3, "# Locale name alias data base.\n#"..., 4096) = 2995
  read(3, "", 4096) = 0
  close(3)

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

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


[Kernel-packages] [Bug 1784331] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding

2018-10-01 Thread Andrew Cloke
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic
  driver binding

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

Bug description:
  With the introduction of KVM crypto virtualization the driver bound to an AP 
queue device is no longer unique determined.
  This feature provides a deterministic hot plugging semantics of AP queues 
that may be bound to multiple drivers.
  In particular it enables to configure an AP queue (APQN) as being bound to a 
particular driver even if the associate HW gets intermittently lost and 
reconnected.

  Is planned as part of kernel 4.19. Therefore a backport to kernel 4.18
  will be required.

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

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


[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D

2018-10-01 Thread Andrew Cloke
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [18.10 FEAT] Add kernel config options for SMC-R/D

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

Bug description:
  Add folliowing options for SMC-R/D

  CONFIG_SMC=m
  CONFIG_SMC_DIAG=m
  CONFIG_ISM=m

  
  Already provided 
  CONFIG_HAVE_PNETID with bugzilla 
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902

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

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


[Kernel-packages] [Bug 1788097] Re: performance drop with ATS enabled

2018-10-01 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  performance drop with ATS enabled

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

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-08-16
  09:58:02 ==

  Witherspoon cluster now has ATS enabled with driver 396.42, CUDA
  version 9.2.148. They are running the CORAL benchmark LULESH with and
  without ATS, and they see a significant performance drop with ATS
  enabled.

  
  Below is the run with ATS:

  Run completed:
  Problem size = 160
  MPI tasks = 8
  Iteration count = 100
  Final Origin Energy = 1.605234e+09
  Testing Plane 0 of Energy Array on rank 0:
  MaxAbsDiff = 2.384186e-07
  TotalAbsDiff = 5.300015e-07
  MaxRelDiff = 1.631916e-12

  Elapsed time = 153.00 (s)
  Grind time (us/z/c) = 0.37352393 (per dom) (0.046690491 overall)
  FOM = 21417.637 (z/s)

  
  Here is the run without ATS:
  Run completed:
  Problem size = 160
  MPI tasks = 8
  Iteration count = 100
  Final Origin Energy = 1.605234e+09
  Testing Plane 0 of Energy Array on rank 0:
  MaxAbsDiff = 2.384186e-07
  TotalAbsDiff = 5.300015e-07
  MaxRelDiff = 1.631916e-12

  
  Elapsed time = 13.27 (s)
  Grind time (us/z/c) = 0.032394027 (per dom) (0.0040492534 overall)
  FOM = 246959.11 (z/s)
  

  Using ATS on a single node slows down the OpenACC version more than 10
  times, and for the version with OpenMP 4.5 and managed memory, they
  observe a 2x slowdown.

  Last comment from NVIDIA (Javier Cabezas - 07/29/2018 11:30 AM):
  We think we have found where's the issue.

  This behavior reproduces for any two concurrent processes that create
  CUDA contexts on the GPUs and heavily unmap memory (no need to launch
  any work on the GPUs). When the problem repros, perf shows that most
  of the time is spent in mmio_invalidate. However, this only happens
  when processes register GPUs attached to the same NPU. Thus, if
  process A, initializes GPU 0 and/or 1, and process B, initializes GPU
  2 and/or 3, we don't see the slowdown. This makes sense, because ATSDs
  on different NPUs are issued independently.

  After some code inspection in npu-dma.c (powerpc backend in the Linux
  kernel), Mark noticed that the problem could be in the utilization of
  test_and_set_bit_lock in get_mmio_atsd_reg. The implementation of
  test_and_set_bit_lock in powerpc relies on the ldarx/stdcx
  instructions (PPC_LLARX/PPC_STLCX in the snippet below):

  #define DEFINE_TESTOP(fn, op, prefix, postfix, eh)\
  static __inline__ unsigned long fn(   \
  unsigned long mask,   \
  volatile unsigned long *_p)   \
  { \
  unsigned long old, t; \
  unsigned long *p = (unsigned long *)_p;   \
  __asm__ __volatile__ (\
  prefix\
  "1:"PPC_LLARX(%0,0,%3,eh) "\n"\
  stringify_in_c(op) "%1,%0,%2\n"   \
  PPC405_ERR77(0,%3)\
  PPC_STLCX "%1,0,%3\n" \
  "bne- 1b\n"   \
  postfix   \
  : "=" (old), "=" (t)  \
  : "r" (mask), "r" (p) \
  : "cc", "memory");\
  return (old & mask);  \
  }

  According to the PowerPC manual, ldarx creates a memory reservation
  and a subsequent stwcx instruction from the same processor ensures an
  atomic read-modify-write operation. However, the reservation can be
  lost if a different processor executes any store instruction on the
  same address. That's why "bne- 1b" checks wether stwcx was successful
  and jumps back to retry, otherwise. Since DEFINE_TESTOP doesn't
  implement any back-off mechanism, two different processors trying to
  get an ATSD register can starve each other.

  Mark compiled a custom kernel which surrounds the calls to
  test_and_set_bit_lock in get_mmio_atsd_reg with a spinlock and I
  verified that it solves the issue. These are the execution times for
  LULESH:

  ATS OFF
  Elapsed time =  16.87 (s)

  ATS ON
  Elapsed time = 215.56 (s)

  ATS ON + Spinlock
  Elapsed time =  18.14 (s)

  
  Fixed with the following patch in the powerpc tree:
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=9eab9901b015

  == Comment: #1 - Michael Ranweiler  - 2018-08-20 
14:56:52 ==
  This is now in 

[Kernel-packages] [Bug 1793837] Re: xorg gives low resolution on HDMI port

2018-10-01 Thread Peter Jaeckel
No change with kernel 4.19.0-041900rc5-generic, alas.

The bizarre thing is the Xorg log (~/.local/share/xorg/Xorg.0.log)
saying

 [11.016] (II) modeset(0): Supported established timings:

and subsequently the finest mode being 1280x1024@75Hz. Then, in the
section(s) called

 [11.017] (II) modeset(0): Supported detailed timing:

it does include a mode with "clock: 241.5 MHz" and 2560x1440. It also
says later:

 [11.017] (--) modeset(0): HDMI max TMDS frequency 25KHz

so it is happy up to 250MHz. And much later, it says

 [11.906] (II) modeset(0): Printing DDC gathered Modelines:
 [11.906] (II) modeset(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)

and so on, i.e., including a 2560x1440 mode.

I do not understand that parts are happily talking about the maximum
resolution of the monitor via HDMI, and other parts seem to not know
anything about it.

Any help welcome. Would you like me to try the intel driver (again)?

pj

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

Title:
  xorg gives low resolution on HDMI port

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is a Zotac CI547 box. It has to video outputs: one HDMI and one
  DisplayPort. The HDMI port appears as DP-1 in the logs, the
  DisplayPort as DP-2. The hardware is Intel HD 620 and is allegedly
  able to run two displays simultaneously at 4K. I have one WQHD monitor
  (=2560x1440) and I get that full resolution over the DisplayPort.
  However, I would like to also get that resolution over the HDMI port
  (in order to connect two identical monitors), but over HDMI I only get
  1024x768. Updating the kernel to the latest 4.18.8 using UKUU made no
  difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.18.8-041808-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Sep 22 00:21:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 620 [8086:]
  InstallationDate: Installed on 2018-09-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.8-041808-generic 
root=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef ro quiet splash 
acpi_backlight=native pci=nomsi 
resume=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef resume_offset=34816 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P206
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P206:bd04/25/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: NA
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1787477] Re: Reconcile hns3 SAUCE patches with upstream

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1786902] Re: [18.10 FEAT] SMC-Direct

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1787945] Re: Tango platform uses __initcall without further checks

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1792349] Re: Memory leaking when running kubernetes cronjobs

2018-10-01 Thread Joseph Salisbury
** Tags removed: kernel-key
** 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/1792349

Title:
  Memory leaking when running kubernetes cronjobs

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

Bug description:
  We are using Kubernetes V1.8.15 with docker 18.03.1-ce.
  We schedule 50 Kubernetes cronjobs to run every 5 minutes. Each cronjob will 
create a simple busybox container, echo hello world, then terminate.

  In the data attached to the bug I let this run for 1 hour, and in this
  time the Available memory had reduced from 31256704 kB to 30461224 kB
  - so a loss of 776 MB. From previous longer runs we observe the
  available memory continues to drop.

  There doesn't appear to be any processes left behind, or any growth in
  any other processes to explain where the memory has gone.

  echo 3 > /proc/sys/vm/drop_caches causes some of the memory to be
  returned, but the majority remains leaked, and the only way to free it
  appears to be to reboot the system.

  We are currently running Ubuntu 4.15.0-32.35-generic 4.15.18 and have
  previously observed similar issues on Ubuntu 16.04 with Kernel
  4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 and
  Debian 9.4 running 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3
  (2018-03-02)

  The leak was more severe on the Debian system, and investigations
  there showed leaks in pcpu_get_vm_areas and were related to memory
  cgroups. Running with Kernel 4.17 on debian showed a leak at a similar
  rate to what we now observe on Ubuntu 18. This leak causes us issues
  as we need to run the cronjobs regularly and want the systems to
  remain up for months.

  Kubernetes will create a new cgroup each time the cronjob runs, but
  these are removed when the job completes (which takes a few seconds).
  If I use systemd-cgtop I don't see any increase in cgroups over time -
  but if I monitor /proc/cgroups over time I can see num_cgroups for
  memory increases.

  For the duration of the test I collected slabinfo, meminfo,
  vmallocinfo & cgroups - which I will attach to the bug. Each file is
  suffixed with the number of seconds since the start.

  *.0 & *.600 were taken before the test was started. The test was
  stopped shortly after the *.4200 files were generated. I then left the
  system idle for 10 minutes. I then ran echo 3 >
  /proc/sys/vm/drop_caches after *.4800 was generated. This seemed to
  free ~240MB - but this still leaves ~500MB lost. I then left the
  system idle for a further 20 minutes, and MemoryAvailable didn't seem
  to be increasing significantly.

  Note, the data attached is from running on kernel 4.18.7-041807-generic 
#201809090930 SMP Sun Sep 9 09:33:16 UTC 2018 (which I ran to verify the issue 
still exists in latest kernel) - however I was unable to run ubuntu-bug linux 
on this kernel as it complained about:
  *** Problem in linux-image-4.18.7-041807-generic

  The problem cannot be reported:

  This report is about a package that is not installed.

  So I switched back to 4.15.0-32.35-generic to raise the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 13 08:55 seq
   crw-rw 1 root audio 116, 33 Sep 13 08:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Sep 13 08:55:46 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic 
root=UUID=6a84f0e4-8522-41cd-8ecb-d4a6fbecef8a ro earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/13/2018
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.7.5-1.21
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 

[Kernel-packages] [Bug 1795492] [NEW] linux-aws: 4.18.0-1001.1 -proposed tracker

2018-10-01 Thread Marcelo Cerri
Public bug reported:

This bug is for tracking the 4.18.0-1001.1 upload package. This bug will
contain status and testing results related to that upload.

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-aws (Ubuntu Cosmic)
 Importance: Medium
 Status: Confirmed


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

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

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

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux-aws: 4.18.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU 

[Kernel-packages] [Bug 1795490] [NEW] linux: -proposed tracker

2018-10-01 Thread Marcelo Cerri
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/automated-testing
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Undecided
 Status: Invalid

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

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


** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: cosmic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => Invalid

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1794293] Re: Please include hid-bigbenff.c driver for 18.04 and later kernels

2018-10-01 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

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

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

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

Title:
  Please include hid-bigbenff.c driver for 18.04 and later kernels

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

Bug description:
  Hi there,

  my driver submission has just been accepted for the upcoming 4.20
  mainline kernel by the input maintainers:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/commit/?h=for-4.20/bigbenff=256a90ed9e46b270bbc4e15ef05216ff049c3721

  The BigBen Interactive PS3OFMINIPAD kids' gamepad is a Playstation3
  accessory and was designed for smaller hands. The Linux kernel didn't
  support its rumble effects, so the device's HID protocol needed to be
  reverse-engineered to write this driver.

  I originally wrote this driver for the Raspberry Pi and the Retropie
  software used by my kids. But now that Steam and Proton are here, we
  are using our Ubuntu boxes more and more often for gaming, so
  including this driver in the default kernel would be nice.

  The patch applies cleanly on the kernels of 18.04 and 18.10 with no
  changes, so there's no backporting to do.

  Thank you.

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

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


[Kernel-packages] [Bug 1774366] Re: Fix MCE handling for user access of poisoned device-dax mapping

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1795493] [NEW] netfilter: nf_conntrack: resolve clash for matching conntracks

2018-10-01 Thread Joshua R. Poulson
Public bug reported:

Per https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts
Kubernetes users are seeing DNS lookups from Pods taking 5 or more
seconds.

Please pick up the following patches to netfilter:
http://patchwork.ozlabs.org/patch/937963/
http://patchwork.ozlabs.org/patch/952939/

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

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

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

Title:
  netfilter: nf_conntrack: resolve clash for matching conntracks

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Per https://www.weave.works/blog/racy-conntrack-and-dns-lookup-
  timeouts Kubernetes users are seeing DNS lookups from Pods taking 5 or
  more seconds.

  Please pick up the following patches to netfilter:
  http://patchwork.ozlabs.org/patch/937963/
  http://patchwork.ozlabs.org/patch/952939/

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

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


[Kernel-packages] [Bug 1784331] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

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

2018-10-01 Thread Michal Hruby
Tested with Dell XPS 9560 and Ubuntu 18.04.

After installing the proposed packages and rebooting, everything booted
correctly, although the nvidia driver was still loaded (I had my system
set to use intel) and power use was quite high (~23W).

*But* after following the test case steps and switching to nvidia,
reboot and then back to intel (after logout+login), everything seems
good - the nvidia module isn't loaded, powertop reports ~12W and as a
bonus reboot/shutdown is much faster (used to stall waiting for
something GPUish).

Definitely much better than the LTS experience so far.

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

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

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

Bug description:
  SRU Request:

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

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

  The solution involves the following changes:

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

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

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

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

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

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

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

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

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

  5) Log out and log back in

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

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

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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


[Kernel-packages] [Bug 1788097] Re: performance drop with ATS enabled

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1789358] Re: Support Power Management for Thunderbolt Controller

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1790480] Re: random oopses on s390 systems using NVMe devices

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1789145] Re: Microphone cannot be detected with front panel audio combo jack on HP Z8-G4 machine

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

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

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1783651] Re: Please enable CONFIG_PAGE_POISONING

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1786878] Re: [Regression] kernel crashdump fails on arm64

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1791660] Re: Cosmic update to v4.18.7 stable release

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1791663] Re: linux: 4.18.0-8.9 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-8.9

---
linux (4.18.0-8.9) cosmic; urgency=medium

  * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663)

  * Cosmic update to v4.18.7 stable release (LP: #1791660)
- rcu: Make expedited GPs handle CPU 0 being offline
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- spi: davinci: fix a NULL pointer dereference
- spi: pxa2xx: Add support for Intel Ice Lake
- spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe
- spi: cadence: Change usleep_range() to udelay(), for atomic context
- mmc: block: Fix unsupported parallel dispatch of requests
- mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts
- mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS
- readahead: stricter check for bdi io_pages
- block: fix infinite loop if the device loses discard capability
- block: blk_init_allocated_queue() set q->fq as NULL in the fail case
- block: really disable runtime-pm for blk-mq
- blkcg: Introduce blkg_root_lookup()
- block: Introduce blk_exit_queue()
- block: Ensure that a request queue is dissociated from the cgroup 
controller
- apparmor: fix bad debug check in apparmor_secid_to_secctx()
- dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace
- libertas: fix suspend and resume for SDIO connected cards
- media: Revert "[media] tvp5150: fix pad format frame height"
- mailbox: xgene-slimpro: Fix potential NULL pointer dereference
- Replace magic for trusting the secondary keyring with #define
- Fix kexec forbidding kernels signed with keys in the secondary keyring to
  boot
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/64s: Fix page table fragment refcount race vs speculative 
references
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- powerpc/pkeys: Give all threads control of their key permissions
- powerpc/pkeys: Deny read/write/execute by default
- powerpc/pkeys: key allocation/deallocation must not change pkey registers
- powerpc/pkeys: Save the pkey registers before fork
- powerpc/pkeys: Fix calculation of total pkeys.
- powerpc/pkeys: Preallocate execute-only key
- powerpc/nohash: fix pte_access_permitted()
- powerpc64/ftrace: Include ftrace.h needed for enable/disable calls
- powerpc/powernv/pci: Work around races in PCI bridge enabling
- cxl: Fix wrong comparison in cxl_adapter_context_get()
- IB/mlx5: Honor cnt_set_id_valid flag instead of set_id
- IB/mlx5: Fix leaking stack memory to userspace
- IB/srpt: Fix srpt_cm_req_recv() error path (1/2)
- IB/srpt: Fix srpt_cm_req_recv() error path (2/2)
- IB/srpt: Support HCAs with more than two ports
- overflow.h: Add arithmetic shift helper
- RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
- ib_srpt: Fix a use-after-free in srpt_close_ch()
- ib_srpt: Fix a use-after-free in __srpt_close_all_ch()
- RDMA/rxe: Set wqe->status correctly if an unexpected response is received
- 9p: fix multiple NULL-pointer-dereferences
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm integrity: change 'suspending' variable from bool to int
- dm thin: stop no_space_timeout worker when switching to write-mode
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- dm cache metadata: set dirty on all cache blocks after a crash
- dm crypt: don't decrease device limits
- dm writecache: fix a crash due to reading past end of dirty_bitmap
- uart: fix race between uart_put_char() and uart_shutdown()
- Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()
- Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind()
- iio: sca3000: Fix missing return in switch
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- extcon: Release locking when sending the notification of connector state
- eventpoll.h: wrap casts in () properly
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- rtc: omap: fix resource leak in registration error path
- rtc: omap: fix potential crash on power off
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- printk/tracing: Do not trace printk_nmi_enter()
- livepatch: 

[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster

2018-10-01 Thread Joseph Salisbury
I tried to apply 2bf1071a8d50928a4ae366bb3108833166c2b70c to Bionic, but
it looks like a backport is needed.

It appears 2bf1071a8d5 is needed as a prereq for f08d08f3db5545.  Do you
happen to already have a backport of 2bf1071a8d5 already done for
Bionic?

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => 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/1792195

Title:
  Signal 7 error when running GPFS tracing in cluster

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

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

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

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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


[Kernel-packages] [Bug 1795486] [NEW] Cosmic update to 4.18.11 stable release

2018-10-01 Thread Thadeu Lima de Souza Cascardo
Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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


Linux 4.18.11
spi: Fix double IDR allocation with DT aliases
iw_cxgb4: only allow 1 flush on user qps
vmw_balloon: include asm/io.h
sched/fair: Fix vruntime_normalized() for remote non-migration wakeup
ext4, dax: set ext4_dax_aops for dax files
ext4, dax: add ext4_bmap to ext4_dax_aops
ext4: show test_dummy_encryption mount option in /proc/mounts
ext4: don't mark mmp buffer head dirty
ext4: fix online resizing for bigalloc file systems with a 1k block size
ext4: fix online resize's handling of a too-small final block group
ext4: recalucate superblock checksum after updating free blocks/inodes
ext4: avoid arithemetic overflow that can trigger a BUG
ext4: avoid divide by zero fault when deleting corrupted inline directories
ext4: check to make sure the rename(2)'s destination is not freed
tty: vt_ioctl: fix potential Spectre v1
drm/amdgpu: add new polaris pci id
drm: udl: Destroy framebuffer only if it was initialized
drm/vc4: Fix the "no scaling" case on multi-planar YUV formats
drm/nouveau/drm/nouveau: Prevent handling ACPI HPD events too early
drm/nouveau/drm/nouveau: Use pm_runtime_get_noresume() in connector_detect()
drm/nouveau/drm/nouveau: Fix deadlock with fb_helper with async RPM requests
drm/nouveau/drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement
drm/nouveau/drm/nouveau: Don't forget to cancel hpd_work on suspend/unload
drm/nouveau: Fix deadlocks in nouveau_connector_detect()
drm/nouveau: Remove duplicate poll_enable() in pmops_runtime_suspend()
drm/nouveau: Only write DP_MSTM_CTRL when needed
drm/nouveau: Reset MST branching unit before enabling
drm/i915/bdw: Increase IPS disable timeout to 100ms
ocfs2: fix ocfs2 read block panic
libata: mask swap internal and hardware tag
Revert "ubifs: xattr: Don't operate on deleted inodes"
scsi: target: iscsi: Use bin2hex instead of a re-implementation
scsi: target: iscsi: Use hex2bin instead of a re-implementation
Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member 
name"
bpf/verifier: disallow pointer subtraction
Revert "rpmsg: core: add support to power domains for devices"
mm: shmem.c: Correctly annotate new inodes for lockdep
mm: disable deferred struct page for 32-bit arches
fork: report pid exhaustion correctly
crypto: x86/aegis,morus - Do not require OSXSAVE for SSE2
ring-buffer: Allow for rescheduling when removing pages
Revert "PCI: Add ACS quirk for Intel 300 series"
spi: fix IDR collision on systems with both fixed and dynamic SPI bus numbers
xen/x86/vpmu: Zero struct pt_regs before calling into sample handling code
xen/netfront: don't bug in case of too many frags
platform/x86: alienware-wmi: Correct a memory leak
platform/x86: dell-smbios-wmi: Correct a memory leak
mtd: rawnand: denali: fix a race condition when DMA is kicked
mtd: devices: m25p80: Make sure the buffer passed in op is DMA-able
ALSA: oxfw: fix memory leak of private data
ALSA: oxfw: fix memory leak of discovered stream formats at error path
ALSA: oxfw: fix memory leak for model-dependent data at error path
ALSA: fireworks: fix memory leak of response buffer at error path
ALSA: firewire-tascam: fix memory leak of private data
ALSA: firewire-digi00x: fix memory leak of private data
ALSA: fireface: fix memory leak in ff400_switch_fetching_mode()
ALSA: emu10k1: fix possible info leak to userspace on SNDRV_EMU10K1_IOCTL_INFO
ALSA: bebob: use address returned by kmalloc() instead of kernel stack for 
streaming DMA mapping
ALSA: bebob: fix memory leak for M-Audio FW1814 and ProjectMix I/O at error path
ASoC: uapi: fix sound/skl-tplg-interface.h userspace compilation errors
ASoC: rsnd: fixup not to call clk_get/set under non-atomic
ASoC: tas6424: Save last fault register even when clear
ASoC: cs4265: fix MMTLR Data switch control
ASoC: wm9712: fix replace codec to component
NFC: Fix the number of pipes
NFC: Fix possible memory corruption when handling SHDLC I-Frame commands
net: rtnl_configure_link: fix dev flags changes arg to __dev_notify_flags
net: mvpp2: let phylink manage the carrier state
net/ipv6: do not copy dst flags on rt init
ipv6: use rt6_info members when dst is set in rt6_fill_node
bnxt_en: Fix VF mac address regression.
tls: fix currently broken MSG_PEEK behavior
socket: fix struct ifreq size in compat ioctl
net: dsa: mv88e6xxx: Fix ATU Miss Violation
hv_netvsc: fix schedule in RCU context

[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

2018-10-01 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

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

Bug description:
  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors 
   
  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com 
   
  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Witherspoon DD2.2 LC 
   
  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

[Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
[Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic   
 
  Ubuntu

System information
System configuration
System status log
Language
Rescan devices
Retrieve config from URL
Plugins (0)
Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  console-setup.service
  swapfile.swap
  ebtables.service
  systemd-udevd.service
  systemd-journald.service
  systemd-journal-flush.service
  systemd-tmpfiles-setup.service
  systemd-update-utmp.service
  [  100.997765] vio vio: uevent: failed to send synthetic uevent
  

[Kernel-packages] [Bug 1794426] Re: linux: 4.15.0-36.39 -proposed tracker

2018-10-01 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1794435 (linux-azure), bug 1794436 (linux-azure), bug 1794438 
(linux-azure-edge), bug 1794439 (linux-gcp), bug 1794441 (linux-hwe), bug 
1794442 (linux-hwe-edge)
  derivatives: bug 1794427 (linux-raspi2), bug 1794428 (linux-oem), bug 1794430 
(linux-aws), bug 1794431 (linux-azure), bug 1794432 (linux-gcp), bug 1794433 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 01. October 2018 18:06 UTC
+ kernel-stable-phase:Promoted to updates

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1794435 (linux-azure), bug 1794436 (linux-azure), bug 1794438 
(linux-azure-edge), bug 1794439 (linux-gcp), bug 1794441 (linux-hwe), bug 
1794442 (linux-hwe-edge)
  derivatives: bug 1794427 (linux-raspi2), bug 1794428 (linux-oem), bug 1794430 
(linux-aws), bug 1794431 (linux-azure), bug 1794432 (linux-gcp), bug 1794433 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to security
+ phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 01. October 2018 18:06 UTC
- kernel-stable-phase:Promoted to updates

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

Title:
  linux: 4.15.0-36.39 -proposed tracker

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

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

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

  backports: bug 1794435 (linux-azure), bug 1794436 (linux-azure), bug 1794438 
(linux-azure-edge), bug 1794439 (linux-gcp), bug 1794441 (linux-hwe), bug 
1794442 (linux-hwe-edge)
  derivatives: bug 1794427 (linux-raspi2), bug 1794428 (linux-oem), bug 1794430 
(linux-aws), bug 1794431 (linux-azure), bug 1794432 (linux-gcp), bug 1794433 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1794428] Re: linux-oem: 4.15.0-1021.24 -proposed tracker

2018-10-01 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 01. October 2018 18:06 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 01. October 2018 18:06 UTC
- kernel-stable-phase:Released

** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1794428

Title:
  linux-oem: 4.15.0-1021.24 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1794430] Re: linux-aws: 4.15.0-1023.23 -proposed tracker

2018-10-01 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 01. October 2018 18:07 UTC
+ kernel-stable-phase:Promoted to updates

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
- phase: Promoted to security
+ phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 01. October 2018 18:07 UTC
- kernel-stable-phase:Promoted to updates

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

Title:
  linux-aws: 4.15.0-1023.23 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1794428] Re: linux-oem: 4.15.0-1021.24 -proposed tracker

2018-10-01 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  linux-oem: 4.15.0-1021.24 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1792589] Re: Drop Cannonlake support from drm/i915

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through 

[Kernel-packages] [Bug 1794430] Re: linux-aws: 4.15.0-1023.23 -proposed tracker

2018-10-01 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  linux-aws: 4.15.0-1023.23 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through 

[Kernel-packages] [Bug 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-36.39

---
linux (4.15.0-36.39) bionic; urgency=medium

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation

  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux (4.15.0-35.38) bionic; urgency=medium

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)

  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests

  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+

  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests

  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT

  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled

  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled

  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page

  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.

  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB

  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM

  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup

  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y

  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
  response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix comments for
  hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for using wrong mask and
  shift in hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for reset_level default
  assignment probelm"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: 

[Kernel-packages] [Bug 1791725] Re: linux-aws: 4.15.0-1022.22 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794430 ***
https://bugs.launchpad.net/bugs/1794430

This bug was fixed in the package linux-aws - 4.15.0-1023.23

---
linux-aws (4.15.0-1023.23) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-aws (4.15.0-1022.22) bionic; urgency=medium

  * linux-aws: 4.15.0-1022.22 -proposed tracker (LP: #1791725)

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [Config] CONFIG_ARCH_SUPPORTS_ACPI=y

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
  response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix 

[Kernel-packages] [Bug 1794439] Re: linux-gcp: 4.15.0-1021.22~16.04.1 -proposed tracker

2018-10-01 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  linux-gcp: 4.15.0-1021.22~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1787898] Re: [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

2018-10-01 Thread Andrew Cloke
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

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

Bug description:
  SRU Justification

  Impact: To boot an IBM Secure Service Container Appliance in an s390
  LPAR. we need to be able to send the Open for Business (OFB) message
  to signal that the appliance is up and running.

  Fix: Set CONFIG_SCLP_OFB=y.

  Regression Potential: The option enables only a few pieces of
  architecture-specific code, so the potential impact is limited.

  ---

  For successfully booting an IBM Secure Service Container Appliance in an s390 
LPAR, we need to be able to send the OFB (Open for Business) message to the 
Support Element to signal when the Appliance is fully up and running.
  Basic support for OFB was added to the kernel with the following commit
  
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688

  The kernel config option CONFIG_SCLP_OFB need to be set

  This update is mandatory for 18.04 , but need to be requested first
  for 18.10

  $ git grep SCLP_OFB
  debian.master/config/annotations:CONFIG_SCLP_OFB  
   policy<{'s390x': 'n'}>
  debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set

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

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


[Kernel-packages] [Bug 1790605] Re: please include the kernel module IPIP

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-kvm - 4.15.0-1023.23

---
linux-kvm (4.15.0-1023.23) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-kvm (4.15.0-1022.22) bionic; urgency=medium

  * linux-kvm: 4.15.0-1022.22 -proposed tracker (LP: #1791731)

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [Config] CONFIG_ARCH_SUPPORTS_ACPI=y

  * please include the kernel module IPIP (LP: #1790605)
- kvm: [config] enable CONFIG_NET_IPIP

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
  response"
- Revert "UBUNTU: SAUCE: {topost} net: 

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-10-01 Thread Darksurf
I can confirm I also have this issue on an ACER Nitro 5 AN515-42-R5GT.
Ryzen 2500U + RX560X using latest BIOS available v1.08. I'm forced to
boot with noapic whether or not IOMMU is even enabled/disabled using
kernel 4.18.10.

Using 4.19.0rc2 I could get by using the GRUB additions:
i8042.nopnp ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 iommu=pt

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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


[Kernel-packages] [Bug 1790605] Re: please include the kernel module IPIP

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-kvm - 4.15.0-1023.23

---
linux-kvm (4.15.0-1023.23) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-kvm (4.15.0-1022.22) bionic; urgency=medium

  * linux-kvm: 4.15.0-1022.22 -proposed tracker (LP: #1791731)

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [Config] CONFIG_ARCH_SUPPORTS_ACPI=y

  * please include the kernel module IPIP (LP: #1790605)
- kvm: [config] enable CONFIG_NET_IPIP

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
  response"
- Revert "UBUNTU: SAUCE: {topost} net: 

[Kernel-packages] [Bug 1791724] Re: linux-oem: 4.15.0-1019.22 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794428 ***
https://bugs.launchpad.net/bugs/1794428

This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's 

[Kernel-packages] [Bug 1791731] Re: linux-kvm: 4.15.0-1022.22 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794433 ***
https://bugs.launchpad.net/bugs/1794433

This bug was fixed in the package linux-kvm - 4.15.0-1023.23

---
linux-kvm (4.15.0-1023.23) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-kvm (4.15.0-1022.22) bionic; urgency=medium

  * linux-kvm: 4.15.0-1022.22 -proposed tracker (LP: #1791731)

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [Config] CONFIG_ARCH_SUPPORTS_ACPI=y

  * please include the kernel module IPIP (LP: #1790605)
- kvm: [config] enable CONFIG_NET_IPIP

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for 

[Kernel-packages] [Bug 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through 

[Kernel-packages] [Bug 1791725] Re: linux-aws: 4.15.0-1022.22 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794430 ***
https://bugs.launchpad.net/bugs/1794430

This bug was fixed in the package linux-aws - 4.15.0-1023.23

---
linux-aws (4.15.0-1023.23) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-aws (4.15.0-1022.22) bionic; urgency=medium

  * linux-aws: 4.15.0-1022.22 -proposed tracker (LP: #1791725)

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [Config] CONFIG_ARCH_SUPPORTS_ACPI=y

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
  response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix 

[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-36.39

---
linux (4.15.0-36.39) bionic; urgency=medium

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation

  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux (4.15.0-35.38) bionic; urgency=medium

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)

  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests

  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+

  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests

  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT

  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled

  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled

  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page

  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.

  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB

  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM

  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup

  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y

  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
  response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix comments for
  hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for using wrong mask and
  shift in hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for reset_level default
  assignment probelm"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: 

[Kernel-packages] [Bug 1791728] Re: linux-gcp: 4.15.0-1020.21 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794432 ***
https://bugs.launchpad.net/bugs/1794432

This bug was fixed in the package linux-gcp - 4.15.0-1021.22~16.04.1

---
linux-gcp (4.15.0-1021.22~16.04.1) xenial; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-gcp (4.15.0-1020.21) bionic; urgency=medium

  * linux-gcp: 4.15.0-1020.21 -proposed tracker (LP: #1791728)

  * Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled
(LP: #1792393)
- SAUCE: xfs: fix build error with CONFIG_XFS_ONLINE_SCRUB enabled

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [config] update configs after rebase

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox 

[Kernel-packages] [Bug 1791728] Re: linux-gcp: 4.15.0-1020.21 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794432 ***
https://bugs.launchpad.net/bugs/1794432

This bug was fixed in the package linux-gcp - 4.15.0-1021.22

---
linux-gcp (4.15.0-1021.22) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-gcp (4.15.0-1020.21) bionic; urgency=medium

  * linux-gcp: 4.15.0-1020.21 -proposed tracker (LP: #1791728)

  * Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled
(LP: #1792393)
- SAUCE: xfs: fix build error with CONFIG_XFS_ONLINE_SCRUB enabled

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [config] update configs after rebase

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving 

[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through 

[Kernel-packages] [Bug 1793656] Re: linux-oem: 4.15.0-1020.23 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794428 ***
https://bugs.launchpad.net/bugs/1794428

This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's 

[Kernel-packages] [Bug 1794426] Re: linux: 4.15.0-36.39 -proposed tracker

2018-10-01 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  linux: 4.15.0-36.39 -proposed tracker

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

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

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

  backports: bug 1794435 (linux-azure), bug 1794436 (linux-azure), bug 1794438 
(linux-azure-edge), bug 1794439 (linux-gcp), bug 1794441 (linux-hwe), bug 
1794442 (linux-hwe-edge)
  derivatives: bug 1794427 (linux-raspi2), bug 1794428 (linux-oem), bug 1794430 
(linux-aws), bug 1794431 (linux-azure), bug 1794432 (linux-gcp), bug 1794433 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1794432] Re: linux-gcp: 4.15.0-1021.22 -proposed tracker

2018-10-01 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  linux-gcp: 4.15.0-1021.22 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1794433] Re: linux-kvm: 4.15.0-1023.23 -proposed tracker

2018-10-01 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

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

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

Title:
  linux-kvm: 4.15.0-1023.23 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1793338] Re: Fix unusable NVIDIA GPU after S3

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1021.24

---
linux-oem (4.15.0-1021.24) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-oem (4.15.0-1020.23) bionic; urgency=medium

  * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656)

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

linux-oem (4.15.0-1019.22) bionic; urgency=medium

  * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724)

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * Miscellaneous Ubuntu changes
- Rebase to 4.15.0-35.38
- [Config] update configs following rebase to 4.15.0-35.38

  * drm/i915: Drop backported support for Cannonlake. (LP: #1792589)

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through 

[Kernel-packages] [Bug 1791728] Re: linux-gcp: 4.15.0-1020.21 -proposed tracker

2018-10-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1794432 ***
https://bugs.launchpad.net/bugs/1794432

This bug was fixed in the package linux-gcp - 4.15.0-1021.22

---
linux-gcp (4.15.0-1021.22) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-gcp (4.15.0-1020.21) bionic; urgency=medium

  * linux-gcp: 4.15.0-1020.21 -proposed tracker (LP: #1791728)

  * Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled
(LP: #1792393)
- SAUCE: xfs: fix build error with CONFIG_XFS_ONLINE_SCRUB enabled

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [config] update configs after rebase

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving 

[Kernel-packages] [Bug 1792393] Re: Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled

2018-10-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-gcp - 4.15.0-1021.22

---
linux-gcp (4.15.0-1021.22) bionic; urgency=medium

  [ Ubuntu: 4.15.0-36.39 ]

  * CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
  * CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely

linux-gcp (4.15.0-1020.21) bionic; urgency=medium

  * linux-gcp: 4.15.0-1020.21 -proposed tracker (LP: #1791728)

  * Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled
(LP: #1792393)
- SAUCE: xfs: fix build error with CONFIG_XFS_ONLINE_SCRUB enabled

  * [Regression] kernel crashdump fails on arm64 (LP: #1786878)
- [config] update configs after rebase

  [ Ubuntu: 4.15.0-35.38 ]

  * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
  * device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
  * L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has 
too
  much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
  * CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
  * CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
  * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
  * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
  * Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
  * Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
  * CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
  * Support Power Management for Thunderbolt Controller  (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
  * random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
  * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
  * Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
  process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
  message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot 

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

2018-10-01 Thread aljosa
Tested before 5 minutes:

*
Fedora 29 Atomic Workstation beta:
pre-installation setup fully activates the touchpad.

*
Live USB - Ubuntu 18.10 beta:
touchpad completely dead.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 

[Kernel-packages] [Bug 1794432] Re: linux-gcp: 4.15.0-1021.22 -proposed tracker

2018-10-01 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 01. October 2018 18:00 UTC
+ kernel-stable-phase:Promoted to updates

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
- phase: Promoted to security
+ phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 01. October 2018 18:00 UTC
- kernel-stable-phase:Promoted to updates

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

Title:
  linux-gcp: 4.15.0-1021.22 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2018-10-01 Thread Joseph Salisbury
I built a test kernel with the two requested commits.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794110/cosmic

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

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

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

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

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


[Kernel-packages] [Bug 1794439] Re: linux-gcp: 4.15.0-1021.22~16.04.1 -proposed tracker

2018-10-01 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 01. October 2018 18:01 UTC
+ kernel-stable-phase:Promoted to updates

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
- phase: Promoted to security
+ phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 01. October 2018 18:01 UTC
- kernel-stable-phase:Promoted to updates

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

Title:
  linux-gcp: 4.15.0-1021.22~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1794426
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


  1   2   3   >