date:20180910

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

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

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => 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: 1788744
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Tuesday, 11. September 2018 06:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Tuesday, 11. September 2018 06:01 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1788754

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1788844] Re: -Excessive undersized/giant packets with intel nic's

2018-09-10 Thread Bas van den Dikkenberg

Correction it takes longer but it's still there reverted to linux-
image-4.15.0-32-generic


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

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

Title:
  -Excessive undersized/giant packets with intel nic's

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

Bug description:
  With new kernel we get on our switch the following error:
  W 08/24/18 12:34:47 00327 FFI: ST2-CMDR: port 2/31-Excessive undersized/giant 
packets. See help.
  W 08/24/18 12:35:28 00327 FFI: ST2-CMDR: port 2/34-Excessive undersized/giant 
packets. See help.
  W 08/24/18 12:37:10 00327 FFI: ST2-CMDR: port 2/33-Excessive undersized/giant 
packets. See help.

  The problem is resolved by booting back to kernel 4.15.0-32-generic

  These are network specifications:
  root@lb1:~# lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 06)
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:16.1 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#2 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#6 (rev f1)
  00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#7 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e 
[Pilot] ServerEngines (SEP1) (rev 05)
  01:00.1 Co-processor: Emulex Corporation ServerView iRMC HTI
  02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
  03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
  04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)
  04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)
  04:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)
  04:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-33-generic 4.15.0-33.36
  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 Aug 24 12:39 seq
   crw-rw 1 root audio 116, 33 Aug 24 12:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Aug 24 12:57:11 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU PRIMERGY RX1330 M3
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=d69c3457-31e5-4daf-8d31-1d2022f93c25 ro text
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2018
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.11 R1.18.0 for D3375-B1x
  dmi.board.name: D3375-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3375-B12 WGS03 GS01
  dmi.chassis.asset.tag: LB1
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.

[Kernel-packages] [Bug 1788844] Re: -Excessive undersized/giant packets with intel nic's

2018-09-10 Thread Bas van den Dikkenberg

isue is resolved in 4.15.0-34-generic

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

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

Title:
  -Excessive undersized/giant packets with intel nic's

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

Bug description:
  With new kernel we get on our switch the following error:
  W 08/24/18 12:34:47 00327 FFI: ST2-CMDR: port 2/31-Excessive undersized/giant 
packets. See help.
  W 08/24/18 12:35:28 00327 FFI: ST2-CMDR: port 2/34-Excessive undersized/giant 
packets. See help.
  W 08/24/18 12:37:10 00327 FFI: ST2-CMDR: port 2/33-Excessive undersized/giant 
packets. See help.

  The problem is resolved by booting back to kernel 4.15.0-32-generic

  These are network specifications:
  root@lb1:~# lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 06)
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
  00:16.1 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#2 (rev 31)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller 
[AHCI mode] (rev 31)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#6 (rev f1)
  00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#7 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
  01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e 
[Pilot] ServerEngines (SEP1) (rev 05)
  01:00.1 Co-processor: Emulex Corporation ServerView iRMC HTI
  02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
  03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
  04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)
  04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)
  04:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)
  04:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network 
Connection (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-33-generic 4.15.0-33.36
  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 Aug 24 12:39 seq
   crw-rw 1 root audio 116, 33 Aug 24 12:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Aug 24 12:57:11 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU PRIMERGY RX1330 M3
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=d69c3457-31e5-4daf-8d31-1d2022f93c25 ro text
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2018
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.11 R1.18.0 for D3375-B1x
  dmi.board.name: D3375-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3375-B12 WGS03 GS01
  dmi.chassis.asset.tag: LB1
  dmi.chassis.type: 23
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: RX1330M3R6
  dmi.modalias: 
dmi:bvnFUJITSU//A

[Kernel-packages] [Bug 1786057] Re: qeth: don't clobber buffer on async TX completion

2018-09-10 Thread Frank Heimes

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

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

Title:
  qeth: don't clobber buffer on async TX completion

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

Bug description:
  
  == SRU Justification ==
  IBM is requesting this commit for s390.  This fixes a bug introduced by
  mainline commit 0da9581ddb0f.  The symptom of the bug is Failing transmissions
  on af_iucv HiperTransport socket.

  Xenial also needs this patch, but it required a backport, so it will be
  SRU'd separately.

  == Fix ==
  ce28867fd20c ("s390/qeth: don't clobber buffer on async TX completion")

  == Regression Potential ==
  Low.  Limited to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Description:  qeth: don't clobber buffer on async TX completion

  Symptom:  Failing transmissions on af_iucv HiperTransport socket.

  Problem:  If qeth_qdio_output_handler() detects that a transmit
    requires async completion, it replaces the pending buffer's
    metadata object (qeth_qdio_out_buffer) so that this queue
    buffer can be re-used while the data is pending completion.
    Later when the CQ indicates async completion of such a
    metadata object, qeth_qdio_cq_handler() tries to free any
    data associated with this object (since HW has now completed
    the transfer). By calling qeth_clear_output_buffer(), it
    erronously operates on the queue buffer that _previously_
    belonged to this transfer ... but which has been potentially
    re-used several times by now. This results in double-free's
    of the buffer's data, and failing transmits as the buffer
    descriptor is scrubbed in mid-air.

  Solution: First only scrub the queue buffer when it is prepared
    for re-use, and later obtain the data addresses from
    the async-completion notifier (ie. the AOB), instead
    of the queue buffer.

  Reproduction: Heavy multi-connection workload on an af_iucv
    HiperTransport socket.

  Upstream-ID:  ce28867fd20c23cd769e78b4d619c4755bf71a1c

  Kernel 4.18

  Will be introduced with kernel 4.18 in Cosmic.
  But should also be applied to Bionic and Xenial

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

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

[Kernel-packages] [Bug 1791569] Re: some nvidia p1000 graphic cards hang during the boot

2018-09-10 Thread Hui Wang

** Description changed:

- Steps:
- 1. Make a usb stick.
- 2. Boot from the usb stick in the boot menu.
  
- Actual result:
- System hang at the Plymouth before entering the phase 1.
+ BugLink: https://bugs.launchpad.net/bugs/1791569
  
- Expected result:
- System can be installed smoothly.
+ This patch is in the 4.18 already, no need to send it to cosmic.
+ 
+ Due to the context conflict, if we want to apply this patch as it is, we
+ need to apply a large amount of patches ahead of this patch, it is possible
+ to introduce some regression. So I made some change in this patch, it is
+ some differnt from the orignal patch, but they have the same logic, and it
+ can be applied to bionic kernel.
+ 
+ [Impact]
+ We have 2 nvidia graphic cards, and the nouveau driver in the bionic kernel 
can't
+ work well with both of these 2 cards, one of the cards hang during the boot
+ process, we compared the output of lspci and vbios version of these 2 cards, 
they
+ are same; and according to nivida's reply, it is possible that they have some
+ difference on computational units 
(https://devtalk.nvidia.com/default/topic/1038973/
+ linux/2-same-quadro-p1000-cards-but-only-one-can-install-ubuntu-/), and 
kernel-4.18
+ fixed this problem, through bisect, this patch was found.
+ 
+ [Fix]
+ backport a upstream patch to fix this problem. without this patch, the number 
of tpc
+ (texture process cluster) is hardcoded to be 5 for some nv graphic families, 
but
+ in practice, the tpc number of many families is not 5. And the p1000 grphic 
card belong
+ to gp107 family, it is 3 intead of 5.
+ 
+ 
+ [Test Case]
+ tested this patch with P1000, P2000, P620 and P500 graphic cards, all work 
well as before.
+ 
+ [Regression Potential]
+ Very low, this patch comes from upstream, and I have tested it with many nv 
graphic
+ cards, they all worked well as before.

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

Title:
  some nvidia p1000 graphic cards hang during the boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  BugLink: https://bugs.launchpad.net/bugs/1791569

  This patch is in the 4.18 already, no need to send it to cosmic.

  Due to the context conflict, if we want to apply this patch as it is, we
  need to apply a large amount of patches ahead of this patch, it is possible
  to introduce some regression. So I made some change in this patch, it is
  some differnt from the orignal patch, but they have the same logic, and it
  can be applied to bionic kernel.

  [Impact]
  We have 2 nvidia graphic cards, and the nouveau driver in the bionic kernel 
can't
  work well with both of these 2 cards, one of the cards hang during the boot
  process, we compared the output of lspci and vbios version of these 2 cards, 
they
  are same; and according to nivida's reply, it is possible that they have some
  difference on computational units 
(https://devtalk.nvidia.com/default/topic/1038973/
  linux/2-same-quadro-p1000-cards-but-only-one-can-install-ubuntu-/), and 
kernel-4.18
  fixed this problem, through bisect, this patch was found.

  [Fix]
  backport a upstream patch to fix this problem. without this patch, the number 
of tpc
  (texture process cluster) is hardcoded to be 5 for some nv graphic families, 
but
  in practice, the tpc number of many families is not 5. And the p1000 grphic 
card belong
  to gp107 family, it is 3 intead of 5.

  
  [Test Case]
  tested this patch with P1000, P2000, P620 and P500 graphic cards, all work 
well as before.

  [Regression Potential]
  Very low, this patch comes from upstream, and I have tested it with many nv 
graphic
  cards, they all worked well as before.

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

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

[Kernel-packages] [Bug 796588] Re: Fine-grained network mediation

2018-09-10 Thread John Johansen

No disagreement that this is a high priority item. There is some work
around fine grained mediation happening but I am unsure when it will
land.

The problem is that this is not the only high priority item that needs
to be addressed. Changing priority of these items can certainly be
discussed again.

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

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

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

[Kernel-packages] [Bug 796588] Re: Fine-grained network mediation

2018-09-10 Thread Nicholas Zatkovich

More to the point, implementing this would give snaps the ability to add
fine-grained network permissions for plugs, and this would suddenly make
snaps a very attractive alternative to Docker images for server apps. I
think this should be considered for priority.

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

2018-09-10 Thread Carl Reinke

1c8c5a9 has the bug.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 796588] Re: Fine-grained network mediation

2018-09-10 Thread Nicholas Zatkovich

I suppose it's time for the bi-annual nudge on this.

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

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

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

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

This change was made by a bot.

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

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   66 May 22 09:36:27 d960-ubu2

[Kernel-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

2018-09-10 Thread Daniel van Vugt

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

Status in linux package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port

[Kernel-packages] [Bug 1791822] Re: [regression] MacBookPro14, 3 internal display is blank with kernel 4.18

2018-09-10 Thread Daniel van Vugt

** Summary changed:

- Internal display is blank
+ [regression] MacBookPro14,3 internal display is blank with kernel 4.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/1791822

Title:
  [regression] MacBookPro14,3 internal display is blank with kernel 4.18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading all packages and rebooting today, the internal display
  is blank.  An external display works fine.  I believe I also ran
  upgrades on Friday, so it was a fairly recent package.  This is a
  MacBookPro14,3.  I believe there was a kernel upgrade, not sure if
  there was an Xorg upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 16:34:45 2018
  DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   applespi, 0.1, 4.17.0-9-generic, x86_64: installed
   applespi, 0.1, 4.18.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
  InstallationDate: Installed on 2018-09-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. MacBookPro14,3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP143.88Z.0178.B00.1806261159
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1787089] Re: [AEP-bug] ext4: more rare direct I/O vs unmap failures

2018-09-10 Thread quanxian

Intel upstream developer no longer works at Intel and without test case
left. Currently we have no way to test it. Sorry about that.

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

Title:
  [AEP-bug] ext4: more rare direct I/O vs unmap failures

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Description:
  Even with the ext4_break_layouts() support added by "ext4: handle layout 
changes to pinned DAX mappings" Still seeing occasional cases with unit test 
where we are truncating a page that has an elevated reference count. 
Investigate.

  —

  The root cause of this issue is that while the ei->i_mmap_sem provides
  synchronization between ext4_break_layouts() and page faults, it doesn't
  provide synchronize us with the direct I/O path. This exact same issue exists
  in XFS AFAICT, with the synchronization tool there being the XFS_MMAPLOCK.

  This allows the direct I/O path to do I/O and raise & lower page->_refcount
  while we're executing a truncate/hole punch. This leads to us trying to free
  a page with an elevated refcount.

  Here's one instance of the race:

  CPU 0 CPU 1
  - -
  ext4_punch_hole()
  ext4_break_layouts() # all pages have refcount=1

  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page() # elevates refcount

  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount, WARN_ON_ONCE()

  A similar race occurs when the refcount is being dropped while we're running
  ext4_break_layouts(), and this is the one that my test was actually hitting:

  CPU 0 CPU 1
  - -
  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page()

  elevates refcount of page X
  ext4_punch_hole()
  ext4_break_layouts() # two pages, X & Y, have refcount == 2
  __wait_var_event() # called for page X
  __put_devmap_managed_page()

  drops refcount of X to 1
  __wait_var_events() checks X's refcount in "if (condition)", and breaks.
  We never actually called ext4_wait_dax_page(), so 'retry' in
  ext4_break_layouts() is still false. Exit do/while loop in
  ext4_break_layouts, never attempting to wait on page Y which still has an
  elevated refcount of 2.
  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount for Y, WARN_ON_ONCE()

  Essentially the solution will most likely involve adding
  synchronization between the direct I/O path and truncate/hole punch
  type operations, and it'll need to happen for both ext4 and XFS, so
  the filesystem folks need to be involved.

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

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

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

This change was made by a bot.

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

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

Title:
  not able to change my brightness [Asus GL502VMK]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i am not able to change my brightness wint my keybord buttons or in
  the settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 22:38:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106M [GeForce GTX 1060 Mobile 6GB] 
[1043:1800]
  InstallationDate: Installed on 2018-09-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=edde470d-ddb4-42e8-9a61-62c31bf664ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: neetishborkar
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.203:bd11/23/2016:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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/1791770/+subscriptions

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

[Kernel-packages] [Bug 1791770] Re: not able to change my brightness

2018-09-10 Thread Daniel van Vugt

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

** Summary changed:

- not able to change my brightness
+ not able to change my brightness [Asus GL502VMK]

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

Title:
  not able to change my brightness [Asus GL502VMK]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i am not able to change my brightness wint my keybord buttons or in
  the settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 22:38:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106M [GeForce GTX 1060 Mobile 6GB] 
[1043:1800]
  InstallationDate: Installed on 2018-09-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=edde470d-ddb4-42e8-9a61-62c31bf664ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: neetishborkar
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.203:bd11/23/2016:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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/1791770/+subscriptions

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

[Kernel-packages] [Bug 1791770] [NEW] not able to change my brightness

You have been subscribed to a public bug:

i am not able to change my brightness wint my keybord buttons or in the
settings.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 22:38:24 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP106M [GeForce GTX 1060 Mobile 6GB] 
[1043:1800]
InstallationDate: Installed on 2018-09-08 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK COMPUTER INC. GL502VMK
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=edde470d-ddb4-42e8-9a61-62c31bf664ed ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL502VMK.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL502VMK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: neetishborkar
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.203:bd11/23/2016:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL502VMK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
not able to change my brightness
https://bugs.launchpad.net/bugs/1791770
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for

2018-09-10 Thread NJ

I have the same problem - on a 2018 Thinkpad with integrated Intel
graphics.

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

Title:
  pci driver messages - BAR 13: no space for

Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  pci driver messages - BAR 13: no space for 

  ---uname output---
  3.18.0-12-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  Install Ubuntu 15.04 daily build running bare-metal
  After the installation following messages are seen in dmesg. 
  Not sure if these indicate a problem. Can some one look at these and confirm 
if this is problem or can be ignored ?

  Messages from dmesg log

  [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4
  [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit]
  [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit]
  [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe081ff]
  [0.714581] pci 0001:00:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0817f]
  [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 
0x3fe08180-0x3fe08183]
  [0.714595] pci 0001:01:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 
0x3b101000-0x3b101fff 64bit pref]
  [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 
0x3b102000-0x3b102fff 64bit pref]
  [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 
0x3b103000-0x3b103fff 64bit pref]
  [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0807f]
  [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 
0x3fe08080-0x3fe080ff]
  [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 
0x3fe08100-0x3fe0817f]
  [0.714611] pci 0001:02:01.0: BAR 13: no space for [io  size 0x1000]
  [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714614] pci 0001:02:08.0: BAR 13: no space for [io  size 0x1000]
  [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714618] pci 0001:02:09.0: BAR 13: no space for [io  size 0x1000]
  [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 
0x3fe08000-0x3fe08003 pref]
  [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 
0x3fe08004-0x3fe08007 pref]
  [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 
0x3fe08008-0x3fe080083fff 64bit]
  [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 
0x3fe080084000-0x3fe080087fff 64bit]
  [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 
0x3fe080088000-0x3fe080088fff 64bit]
  [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 
0x3fe080089000-0x3fe080089fff 64bit]
  [0.714685] pci 0001:03:00.0: BAR 4: no space for [io  size 0x0100]
  [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io  size 0x0100]
  [0.714688] pci 0001:03:00.1: BAR 4: no space for [io  size 0x0100]
  [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io  size 0x0100]
  [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03]

  # lspci 
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:10.0 PCI bridge:

[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker

2018-09-10 Thread Łukasz Zemczak

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1788744
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1791321] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187299/+files/PulseList.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1791321] Re: No video on laptop display after suspend/resume

3cd091a773936c54344a519f7ee1379ccb620bee is the first bad commit
commit 3cd091a773936c54344a519f7ee1379ccb620bee
Author: Rafael J. Wysocki 
Date:   Fri Feb 9 22:55:28 2018 +0100

ACPI / EC: Restore polling during noirq suspend/resume phases

Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a
regression) modified the ACPI EC driver so that it doesn't switch
over to busy polling mode during noirq stages of system suspend and
resume in an attempt to fix an issue resulting from that behavior.

However, that modification introduced a system resume regression on
Thinkpad X240, so make the EC driver switch over to the polling mode
during noirq stages of system suspend and resume again, which
effectively reverts the problematic commit.

Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression)
Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863
Reported-by: Markus Demleitner 
Tested-by: Markus Demleitner 
Signed-off-by: Rafael J. Wysocki 

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

** Bug watch added: Linux Kernel Bug Tracker #197863
   https://bugzilla.kernel.org/show_bug.cgi?id=197863

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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-09-10 Thread Gary Chapman

Yes, this worked, thank you. OFB communication also still works as
documented in comment #9

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

Title:
  [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
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 1791321] CRDA.txt

apport information

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

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1791321/+attachment/5187293/+files/Lspci.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187297/+files/ProcInterrupts.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187291/+files/CurrentDmesg.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1791321/+attachment/5187294/+files/Lsusb.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1791321] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187292/+files/IwConfig.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/1791321

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187298/+files/ProcModules.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1791321] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187296/+files/ProcCpuinfoMinimal.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/1791321

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1791321/+attachment/5187300/+files/UdevDb.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187295/+files/ProcCpuinfo.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1791321] Re: No video on laptop display after suspend/resume

apport information

** Tags added: apport-collected bionic

** Description changed:

  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.
  
  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  john   1100 F pulseaudio
+  /dev/snd/controlC0:  john   1100 F pulseaudio
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
+ InstallationDate: Installed on 2017-02-01 (586 days ago)
+ InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ MachineType: LENOVO 20EN001AUS
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
+ ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-23-generic N/A
+  linux-backports-modules-4.15.0-23-generic  N/A
+  linux-firmware 1.173.1
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic
+ Uname: Linux 4.15.0-23-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 03/28/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N1EET77W (1.50 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20EN001AUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40705 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad P50
+ dmi.product.name: 20EN001AUS
+ dmi.product.version: ThinkPad P50
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1791321/+attachment/5187289/+files/AlsaInfo.txt

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

Title:
  No video on laptop display after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

2018-09-10 Thread Eric Desrochers

** Tags added: sts

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

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0 
  [684766.669194] Oops:  [#1] SMP 
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00 
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  The Call Trace is similar with the one that is describe in this upstream patch
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05

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

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

[Kernel-packages] [Bug 1791804] Re: kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

2018-09-10 Thread Dimitri John Ledkov

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

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

** Package changed: makedumpfile (Ubuntu Bionic) => kexec-tools (Ubuntu
Bionic)

** Changed in: kexec-tools (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Status in kexec-tools package in Ubuntu:
  Fix Committed
Status in kexec-tools source package in Bionic:
  New
Status in kexec-tools source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Without this fix, kexec won't be able to load kernels on amd64.

  [Test Case]
  kexec has been tested to be able to load a 4.18 kernel.

  [Regression Potential]
  As the fix is only applied to the x86_64 portion of kexec, only this platform 
should be affected. Package with fix has been tested there.

  
  When running kexec with 4.18, it fails.

  $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
  Unhandled rela relocation: R_X86_64_PLT32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1791804/+subscriptions

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

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

2018-09-10 Thread Mauricio Faria de Oliveira

The debian-installer images in trusty-proposed work correctly; changing
verification tags to done.

I tested in the following platforms, with plain and LVM partitioning (details 
in comment #10).
- amd64 bare-metal & qemu-kvm guest
- i386 qemu-kvm guest
- arm64 qemu guest
- ppc64el qemu guest

The installer boots with the new kernel, installs it to the system, and
the installed system boots correctly with it.

The NIC enablement has been validated previously by the customer with
the updated kernel package used in these d-i images.

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

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

Title:
  Enable basic support for Solarflare 8000 series NIC

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

Bug description:
  SRU Justification:

  [Impact]

   * Users cannot use Solarflare 8000 series NICs.

   * Servers with only this NIC cannot do netboot.

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

  [Test Case]

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

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

  [Regression Potential]

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

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

  [Other Info]

   * There are known error messages on device probe.

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

  ---

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

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

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

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

  ---

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1791804] Re: kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

** Description changed:

+ [Impact]
+ Without this fix, kexec won't be able to load kernels on amd64.
+ 
+ [Test Case]
+ kexec has been tested to be able to load a 4.18 kernel.
+ 
+ [Regression Potential]
+ As the fix is only applied to the x86_64 portion of kexec, only this platform 
should be affected. Package with fix has been tested there.
+ 
+ 
  When running kexec with 4.18, it fails.
  
  $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
  Unhandled rela relocation: R_X86_64_PLT32

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

Title:
  kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Status in kexec-tools package in Ubuntu:
  Fix Committed
Status in kexec-tools source package in Bionic:
  New
Status in kexec-tools source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Without this fix, kexec won't be able to load kernels on amd64.

  [Test Case]
  kexec has been tested to be able to load a 4.18 kernel.

  [Regression Potential]
  As the fix is only applied to the x86_64 portion of kexec, only this platform 
should be affected. Package with fix has been tested there.

  
  When running kexec with 4.18, it fails.

  $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
  Unhandled rela relocation: R_X86_64_PLT32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1791804/+subscriptions

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

2018-09-10 Thread Szilard Cserey

** Attachment added: "Call Trace from dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+attachment/5187255/+files/DMESG_CALL_TRACE.log

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

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0 
  [684766.669194] Oops:  [#1] SMP 
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00 
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  The Call Trace is similar with the one that is describe in this upstream patch
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05

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

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

[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker

2018-09-10 Thread Łukasz Zemczak

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1788744
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

2018-09-10 Thread Szilard Cserey

** Attachment added: ""bt" and "bt -l" from Kernel crashdump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+attachment/5187256/+files/CRASH_BT.log

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

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0 
  [684766.669194] Oops:  [#1] SMP 
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00 
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  The Call Trace is similar with the one that is describe in this upstream patch
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05

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

-- 
Mailing list: https://launchpad.net/~kerne

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

This change was made by a bot.

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

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

Title:
  Internal display is blank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading all packages and rebooting today, the internal display
  is blank.  An external display works fine.  I believe I also ran
  upgrades on Friday, so it was a fairly recent package.  This is a
  MacBookPro14,3.  I believe there was a kernel upgrade, not sure if
  there was an Xorg upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 16:34:45 2018
  DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   applespi, 0.1, 4.17.0-9-generic, x86_64: installed
   applespi, 0.1, 4.18.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
  InstallationDate: Installed on 2018-09-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. MacBookPro14,3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP143.88Z.0178.B00.1806261159
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1791804] Re: kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

** Patch added: "Fix for "Unhandled rela relocation: R_X86_64_PLT32" error"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1791804/+attachment/5187253/+files/kexec-tools_2.0.16-1ubuntu3.diff

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

Title:
  kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  When running kexec with 4.18, it fails.

  $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
  Unhandled rela relocation: R_X86_64_PLT32

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

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

[Kernel-packages] [Bug 1791804] Re: kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Build with upstream patch and tested on my system, it fixes the problem.
Attaching the debdiff.

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

Title:
  kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  When running kexec with 4.18, it fails.

  $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
  Unhandled rela relocation: R_X86_64_PLT32

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

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

[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1788744
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1791822] Re: Internal display is blank

2018-09-10 Thread Larry Reaves

I can confirm that this is caused by the kernel update.  When booting
4.17.0-9-generic the screen works correctly.

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

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

Title:
  Internal display is blank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading all packages and rebooting today, the internal display
  is blank.  An external display works fine.  I believe I also ran
  upgrades on Friday, so it was a fairly recent package.  This is a
  MacBookPro14,3.  I believe there was a kernel upgrade, not sure if
  there was an Xorg upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 16:34:45 2018
  DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   applespi, 0.1, 4.17.0-9-generic, x86_64: installed
   applespi, 0.1, 4.18.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
  InstallationDate: Installed on 2018-09-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. MacBookPro14,3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP143.88Z.0178.B00.1806261159
  dmi.board.name: Mac-551B86E5744E2388
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro14,3
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-551B86E5744E2388
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro14,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1788744
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1787390] Re: linux-azure: 4.15.0-1022.22~14.04.1 -proposed tracker

2018-09-10 Thread Marcelo Cerri

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

** This bug has been marked a duplicate of bug 1788754
   linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker

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

Title:
  linux-azure: 4.15.0-1022.22~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1022.22~14.04.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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1787149
  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/1787390/+subscriptions

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

[Kernel-packages] [Bug 1791822] [NEW] Internal display is blank

You have been subscribed to a public bug:

After upgrading all packages and rebooting today, the internal display
is blank.  An external display works fine.  I believe I also ran
upgrades on Friday, so it was a fairly recent package.  This is a
MacBookPro14,3.  I believe there was a kernel upgrade, not sure if there
was an Xorg upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 16:34:45 2018
DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
 applespi, 0.1, 4.17.0-9-generic, x86_64: installed
 applespi, 0.1, 4.18.0-7-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 
450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Radeon Pro 555 [106b:017a]
InstallationDate: Installed on 2018-09-05 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Apple Inc. MacBookPro14,3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago)
dmi.bios.date: 06/26/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP143.88Z.0178.B00.1806261159
dmi.board.name: Mac-551B86E5744E2388
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,3
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-551B86E5744E2388
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.94-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic regression reproducible ubuntu
-- 
Internal display is blank
https://bugs.launchpad.net/bugs/1791822
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

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: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 10. September 2018 20:34 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: 1788766
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 10. September 2018 20:34 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1788769

Title:
  linux-aws: 4.4.0-1067.77 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  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/1788769/+subscriptions

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

[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker

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: 1788744
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 10. September 2018 20:30 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: 1788744
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 10. September 2018 20:30 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1788758

Title:
  linux-gcp: 4.15.0-1019.20~16.04.1 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788758/+subscriptions

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

[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker

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: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 10. September 2018 20:34 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: 1788766
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 10. September 2018 20:34 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788771

Title:
  linux-kvm: 4.4.0-1033.39 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
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 Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  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/1788771/+subscriptions

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

[Kernel-packages] [Bug 1791794] Re: linux-azure: build and include the tcm_loop module to the main kernel package

2018-09-10 Thread Marcelo Cerri

https://lists.ubuntu.com/archives/kernel-team/2018-September/095356.html


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

** Changed in: linux-azure (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Description changed:

  Azure users rely on the tcm_loop module. Since linux-azure doesn't
- install the extra package by default, the module should be include to
+ install the extra package by default, the module should be included to
  the main package.

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

Title:
  linux-azure: build and include the tcm_loop module to the main kernel
  package

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

Bug description:
  Azure users rely on the tcm_loop module. Since linux-azure doesn't
  install the extra package by default, the module should be included to
  the main package.

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

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

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

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

apport-collect 1791806

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25

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

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

[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 10. September 2018 20:01 UTC
+ kernel-stable-phase:Promoted to security

** 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: 1788744
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 10. September 2018 20:01 UTC
- kernel-stable-phase:Promoted to security

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

Title:
  linux-gcp: 4.15.0-1019.20~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 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788758/+subscriptions

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

[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by incomplete backport for bug 1597908

2018-09-10 Thread Steven Haber

Attaching logs gathered by the apport utility. This is for one of our HP
boxes running kernel 4.4.0-131.

** Attachment added: "apport.linux.4RjMFB.apport"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+attachment/5187217/+files/apport.linux.4RjMFB.apport

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

Title:
Kernel hang on drive pull caused by incomplete backport for bug
1597908

Status in linux package in Ubuntu:
Confirmed

Bug description:
A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.

This patch changes the context in which timeout work is scheduled for
block devices in the kernel. Previously, timeout work was executed
directly from the timer callback that fired when a deadline was met.
After the patch, timeout work is scheduled using a background work
queue. This means that by the time the work executes, the device queue
which originally scheduled the work could be torn down. In order to
prevent this, the patch takes a reference on the device queue when
executing the timeout work.

The problem is that the last reference to this queue can be removed
before the timeout work can be executed. During teardown, the block
system executes a freeze followed by a drain. The freeze drops the
last reference on the queue. The drain tries to clean up any
outstanding work, including timeout work. After a freeze, the timeout
work in the background queue is unable to obtain a reference, and
exits early without completing work. The work is now permanently stuck
in the queue and it will never be completed. The drain in the device
teardown path spins indefinitely.

The bug manifests as a hang that looks like this:
[] schedule+0x35/0x80
[] hpsa_scan_start+0x109/0x140 [hpsa]
[] ? wake_atomic_t_function+0x60/0x60
[] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
[] process_one_work+0x165/0x480
[] worker_thread+0x4b/0x4c0
[] ? process_one_work+0x480/0x480
[] kthread+0xd8/0xf0
[] ? kthread_create_on_node+0x1e0/0x1e0
[] ret_from_fork+0x3f/0x70
[] ? kthread_create_on_node+0x1e0/0x1e0

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.

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

We hit this bug nearly 100% of the time on some of our HP hardware.
The HPSA driver has a tendency to aggressively remove missing devices,
so it widens the race. As a result, we've been building our own kernel
with this patch applied. It would be really nice if we could get it
into mainline Ubuntu.

Let me know what additional information is needed. Thanks!

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

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

[Kernel-packages] [Bug 1791806] [NEW] alsa does not detech headphone output on Clevo P651RS laptop

2018-09-10 Thread Lehel Gyuro

Public bug reported:

Even though there is a duplex S/Pdif + Headphones out output the
following line is observed:

[   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
[   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
[   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
[   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
[   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
[   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
[   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
[   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1791806

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25

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

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

[Kernel-packages] [Bug 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-09-10 Thread Lehel Gyuro

upload=true&script=true&cardinfo=
!!
!!ALSA Information Script v 0.4.64
!!

!!Script ran on: Mon Sep 10 19:14:28 UTC 2018


!!Linux Distribution
!!--

Ubuntu 18.04.1 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
18.04.1 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
18.04.1 LTS" HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
/privacy-policy" UBUNTU_CODENAME=bionic


!!DMI Information
!!---

Manufacturer:  Notebook
Product Name:  P65_67RSRP
Product Version:   Not Applicable  
Firmware Version:  1.05.04


!!Kernel Information
!!--

Kernel release:4.15.0-33-lowlatency
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: x86_64
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: k4.15.0-33-lowlatency
Library version:1.1.3
Utilities version:  1.1.3


!!Loaded ALSA modules
!!---

snd_hda_intel


!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x2fff02 irq 130


!!PCI Soundcards installed in the system
!!--

00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev
31)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---

00:1f.3 0403: 8086:a170 (rev 31)
Subsystem: 1558:6a02


!!Modprobe options (Sound related)
!!

snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2


!!Loaded sound module options
!!---

!!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
jackpoll_ms : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
model : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
patch : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
pm_blacklist : Y
position_fix : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
power_save : 0
power_save_controller : Y
probe_mask : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
probe_only : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
single_cmd : -1
snoop : -1


!!HDA-Intel Codec information
!!---
--startcollapse--

Codec: Realtek ALC898
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0899
Subsystem Id: 0x15586a02
Revision Id: 0x13
No Modem Function Group found
Default PCM:
rates [0x5f0]: 32000 44100 48000 88200 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
  Power states:  D0 D1 D2 D3 CLKSTOP EPSS
  Power: setting=D0, actual=D0
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x411: Stereo
  Device: name="ALC898 Analog", type="Audio", device=0
  Converter: stream=1, channel=0
  PCM:
rates [0x5e0]: 44100 48000 88200 96000 192000

[Kernel-packages] [Bug 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-09-10 Thread Lehel Gyuro

Affects Ubuntu 18.04, 17.10, 17.04

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25

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

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

[Kernel-packages] [Bug 1791804] [NEW] kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Public bug reported:

When running kexec with 4.18, it fails.

$ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
Unhandled rela relocation: R_X86_64_PLT32

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

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

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

Title:
  kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"

Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  When running kexec with 4.18, it fails.

  $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd 
/boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`"
  Unhandled rela relocation: R_X86_64_PLT32

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

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

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

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

apport-collect 1791790

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

Title:
Kernel hang on drive pull caused by incomplete backport for bug
1597908

Status in linux package in Ubuntu:
Incomplete

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.

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

Let me know what additional information is needed. Thanks!

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

[Kernel-packages] [Bug 1788563] Re: L1TF mitigation not effective in some CPU and RAM combinations

** Description changed:

  == SRU Justification ==
- This regression has been reported in multiple bugs and affects Trust,
+ This bug has been reported in multiple bugs and affects Trusty,
  Xenial and Bionic.  All releases need different backports, so T and X
  will be sent in separate SRU requests.
  
  Due to this bug in the original L1TF patch set, L1TF mitigation not
  effective in certain CPU and installed RAM configurations.
  
  == Fixes ==
  9df9516940a6 ("x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 
32bit")
  b0a182f87568 ("x86/speculation/l1tf: Fix off-by-one error when warning that 
system has too much RAM")
  cc51e5428ea5 ("x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+")
  
  == Regression Potential ==
  Low.  These are security fixes and have all been cc'd to upstream
  stable, so they have had additional upstream review.
  
  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.
  
  Lenovo Thinkpad W530 system with 32 GB RAM
  
  dmesg | grep -i l1tf
  [0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation 
not effective.
  [ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html 
for details.
  
  Related:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1105536
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgera  2809 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 23 03:38:40 2018
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 24382LU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24382LU
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 24382LU
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

Title:
  L1TF mitigation not effective in some CPU and RAM combinations

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification ==
  This bug has been reported in multiple bugs and affects Trusty,
  Xenial and Bionic.  All releases need different backports, so T and X
  will be sent in separate SRU requests.

  Due to this bug in the original L1TF patch set, L1TF mitigation not
  effective in certain CPU and installed RAM configurations.

  == Fixes ==
  9df9516940a6 ("x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 
32bit")
  b0a182f87568 ("x86/speculation/l1tf: Fix off-by-one error when warning that 
system has too much RAM")
  cc51e5428ea5 ("x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+")

  == Regression Potential ==
  Low.  These are security fixes and have all been cc'd to upstream
  stable, so they have had additional upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  Lenovo Thinkpad W530 system with 32 GB RAM

  dmesg | grep -i l1tf
  [0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation 
not effective.
  [ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html 
for details.

  Related:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1105536

  Pr

[Kernel-packages] [Bug 1791794] [NEW] linux-azure: build and include the tcm_loop module to the main kernel package

2018-09-10 Thread Marcelo Cerri

Public bug reported:

Azure users rely on the tcm_loop module. Since linux-azure doesn't
install the extra package by default, the module should be include to
the main package.

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

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

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

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

Title:
  linux-azure: build and include the tcm_loop module to the main kernel
  package

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  New

Bug description:
  Azure users rely on the tcm_loop module. Since linux-azure doesn't
  install the extra package by default, the module should be include to
  the main package.

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

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

[Kernel-packages] [Bug 1791790] [NEW] Kernel hang on drive pull caused by incomplete backport for bug 1597908

2018-09-10 Thread Steven Haber

Public bug reported:

A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.

The problem is that the last reference to this queue can be removed
before the timeout work can be executed. During teardown, the block
system executes a freeze followed by a drain. The freeze drops the last
reference on the queue. The drain tries to clean up any outstanding
work, including timeout work. After a freeze, the timeout work in the
background queue is unable to obtain a reference, and exits early
without completing work. The work is now permanently stuck in the queue
and it will never be completed. The drain in the device teardown path
spins indefinitely.

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's most
recent 4.4 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af

We hit this bug nearly 100% of the time on some of our HP hardware. The
HPSA driver has a tendency to aggressively remove missing devices, so it
widens the race. As a result, we've been building our own kernel with
this patch applied. It would be really nice if we could get it into
mainline Ubuntu.

Let me know what additional information is needed. Thanks!

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

Title:
Kernel hang on drive pull caused by incomplete backport for bug
1597908

Status in linux package in Ubuntu:
New

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.

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

Let me know what additional informatio

[Kernel-packages] [Bug 1787089] Re: [AEP-bug] ext4: more rare direct I/O vs unmap failures

Cosmic request:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095337.html

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

Title:
  [AEP-bug] ext4: more rare direct I/O vs unmap failures

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Description:
  Even with the ext4_break_layouts() support added by "ext4: handle layout 
changes to pinned DAX mappings" Still seeing occasional cases with unit test 
where we are truncating a page that has an elevated reference count. 
Investigate.

  —

  The root cause of this issue is that while the ei->i_mmap_sem provides
  synchronization between ext4_break_layouts() and page faults, it doesn't
  provide synchronize us with the direct I/O path. This exact same issue exists
  in XFS AFAICT, with the synchronization tool there being the XFS_MMAPLOCK.

  This allows the direct I/O path to do I/O and raise & lower page->_refcount
  while we're executing a truncate/hole punch. This leads to us trying to free
  a page with an elevated refcount.

  Here's one instance of the race:

  CPU 0 CPU 1
  - -
  ext4_punch_hole()
  ext4_break_layouts() # all pages have refcount=1

  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page() # elevates refcount

  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount, WARN_ON_ONCE()

  A similar race occurs when the refcount is being dropped while we're running
  ext4_break_layouts(), and this is the one that my test was actually hitting:

  CPU 0 CPU 1
  - -
  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page()

  elevates refcount of page X
  ext4_punch_hole()
  ext4_break_layouts() # two pages, X & Y, have refcount == 2
  __wait_var_event() # called for page X
  __put_devmap_managed_page()

  drops refcount of X to 1
  __wait_var_events() checks X's refcount in "if (condition)", and breaks.
  We never actually called ext4_wait_dax_page(), so 'retry' in
  ext4_break_layouts() is still false. Exit do/while loop in
  ext4_break_layouts, never attempting to wait on page Y which still has an
  elevated refcount of 2.
  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount for Y, WARN_ON_ONCE()

  Essentially the solution will most likely involve adding
  synchronization between the direct I/O path and truncate/hole punch
  type operations, and it'll need to happen for both ext4 and XFS, so
  the filesystem folks need to be involved.

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

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

[Kernel-packages] [Bug 1771248] Re: [ICL] SPI support

Commit a13c93b3a will be applied to 18.10 via bug 1771245.

Commit 22d71a5097 is now in the Ubuntu-4.18.0-8 18.10 kernel via
upstream stable updates.

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

** Changed in: intel
   Status: Triaged => Fix Committed

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

Title:
  [ICL] SPI support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Description:

  Should be similar as in CNL.
  Adding CSE DMA access capability to SPI and UART controller.

  Target Release: 18.10
  Target Kernel:4.19

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

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

[Kernel-packages] [Bug 1787089] Re: [AEP-bug] ext4: more rare direct I/O vs unmap failures

** Information type changed from Private to Public

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

Title:
  [AEP-bug] ext4: more rare direct I/O vs unmap failures

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Description:
  Even with the ext4_break_layouts() support added by "ext4: handle layout 
changes to pinned DAX mappings" Still seeing occasional cases with unit test 
where we are truncating a page that has an elevated reference count. 
Investigate.

  —

  The root cause of this issue is that while the ei->i_mmap_sem provides
  synchronization between ext4_break_layouts() and page faults, it doesn't
  provide synchronize us with the direct I/O path. This exact same issue exists
  in XFS AFAICT, with the synchronization tool there being the XFS_MMAPLOCK.

  This allows the direct I/O path to do I/O and raise & lower page->_refcount
  while we're executing a truncate/hole punch. This leads to us trying to free
  a page with an elevated refcount.

  Here's one instance of the race:

  CPU 0 CPU 1
  - -
  ext4_punch_hole()
  ext4_break_layouts() # all pages have refcount=1

  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page() # elevates refcount

  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount, WARN_ON_ONCE()

  A similar race occurs when the refcount is being dropped while we're running
  ext4_break_layouts(), and this is the one that my test was actually hitting:

  CPU 0 CPU 1
  - -
  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page()

  elevates refcount of page X
  ext4_punch_hole()
  ext4_break_layouts() # two pages, X & Y, have refcount == 2
  __wait_var_event() # called for page X
  __put_devmap_managed_page()

  drops refcount of X to 1
  __wait_var_events() checks X's refcount in "if (condition)", and breaks.
  We never actually called ext4_wait_dax_page(), so 'retry' in
  ext4_break_layouts() is still false. Exit do/while loop in
  ext4_break_layouts, never attempting to wait on page Y which still has an
  elevated refcount of 2.
  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount for Y, WARN_ON_ONCE()

  Essentially the solution will most likely involve adding
  synchronization between the direct I/O path and truncate/hole punch
  type operations, and it'll need to happen for both ext4 and XFS, so
  the filesystem folks need to be involved.

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

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

[Kernel-packages] [Bug 1788004] Re: File System inaccessible after 18.04 upgrade

2018-09-10 Thread Chris Siebenmann

Based on inspecting the ZFS source code, this looks like a ZFS inode
where there is a mismatch between the claimed size of the inode's (ZFS)
ACL and how it's stored. If you're willing to do some work, it might be
possible to narrow this down to identify a specific inode and what's
wrong with it, which could help fixing this (in Ubuntu and upstream).
Unfortunately this will be a somewhat involved process involving zdb,
because you need to dump on-disk structures. If you're interested and
willing to tackle this, your best approach is probably to ask for help
on the ZFS on Linux mailing list, because it will be easier to give the
details there.

It is possible that a 'zfs send | zfs receive' sequence will allow you
to recover a usable version of the filesystem (and I believe you can do
this without the filesystem being mounted and thus without the risk of
panic). If you have, say, a spare external USB drive, it might be worth
trying this.

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

Title:
  File System inaccessible after 18.04 upgrade

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  ZPool was functioning before upgrading to Ubuntu 18.04.  Unfortunately
  didn't confirm pool working before upgrading the pool so can't roll
  back.  Can't access file system anymore, though a scrub did succeed.

  Simple 'ls -la' segfaults, and this shows up in dmesg:
  [  320.449464] detected buffer overflow in memmove
  [  320.449489] [ cut here ]
  [  320.449492] kernel BUG at 
/build/linux-wuhukg/linux-4.15.0/lib/string.c:1052!
  [  320.449503] invalid opcode:  [#1] SMP PTI
  [  320.449506] Modules linked in: thunderbolt nls_iso8859_1 zfs(PO) 
zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) snd_
  hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm snd_hda_codec_ca0132 irqbypass crct10dif_pclmu
  l crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hda_intel 
snd_hda_codec aes_x86_64 crypto_simd snd_hda_core glue_helper crypt
  d intel_cstate snd_hwdep intel_rapl_perf snd_pcm intel_wmi_thunderbolt 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_de
  vice snd_timer snd soundcore input_leds mac_hid mei_me mei shpchp acpi_pad 
intel_pch_thermal sch_fq_codel vhba(OE) parport_pc ppdev l
  p parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 mxm_wmi 
e1000e i2c_algo_bit ptp drm_kms_helper pps_core syscopyarea 
  sysfillrect
  [  320.449599]  sysimgblt fb_sys_fops alx drm mdio ahci libahci wmi video
  [  320.449617] CPU: 3 PID: 3202 Comm: updatedb.mlocat Tainted: PW  OE 
   4.15.0-32-generic #35-Ubuntu
  [  320.449621] Hardware name: Gigabyte Technology Co., Ltd. To be filled by 
O.E.M./Z170X-Gaming 7, BIOS F8 08/26/2016
  [  320.449632] RIP: 0010:fortify_panic+0x13/0x22
  [  320.449636] RSP: 0018:a85fc5d27898 EFLAGS: 00010282
  [  320.449641] RAX: 0023 RBX: a85fc5d279a8 RCX: 

  [  320.449645] RDX:  RSI: 97dc51d96498 RDI: 
97dc51d96498
  [  320.449649] RBP: a85fc5d27898 R08:  R09: 
058c
  [  320.449652] R10: 97dc2916501c R11: b895380d R12: 
0001
  [  320.449656] R13: 97dc2a717460 R14: 0070 R15: 
97dc21e40300
  [  320.449661] FS:  7fb9bd9c4540() GS:97dc51d8() 
knlGS:
  [  320.449665] CS:  0010 DS:  ES:  CR0: 80050033
  [  320.449669] CR2: 7fa69800e778 CR3: 000812c88005 CR4: 
003606e0
  [  320.449673] DR0:  DR1:  DR2: 

  [  320.449677] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  320.449680] Call Trace:
  [  320.449779]  zfs_acl_node_read.constprop.15+0x33d/0x340 [zfs]
  [  320.449867]  zfs_zaccess_aces_check+0x96/0x380 [zfs]
  [  320.449874]  ? mutex_lock+0x12/0x40
  [  320.449879]  ? _cond_resched+0x19/0x40
  [  320.449929]  ? arc_buf_access+0x14a/0x270 [zfs]
  [  320.449977]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  320.450056]  zfs_zaccess_common+0xda/0x1f0 [zfs]
  [  320.450062]  ? _cond_resched+0x19/0x40
  [  320.450139]  zfs_zaccess+0xd4/0x3d0 [zfs]
  [  320.450235]  ? rrw_enter_read_impl+0xae/0x160 [zfs]
  [  320.450327]  zfs_lookup+0x1c5/0x3a0 [zfs]
  [  320.450415]  zpl_lookup+0xc9/0x1e0 [zfs]
  [  320.450424]  lookup_slow+0xab/0x170
  [  320.450432]  walk_component+0x1c3/0x470
  [  320.450438]  ? _cond_resched+0x19/0x40
  [  320.450444]  ? mutex_lock+0x12/0x40
  [  320.450451]  path_lookupat+0x84/0x1f0
  [  320.450458]  ? ___slab_alloc+0xf2/0x4b0
  [  320.450545]  ? zfs_readdir+0x267/0x460 [zfs]
  [  320.450552]  ? ___slab_alloc+0xf2/0x4b0
  [  320.450560]  filename_lookup+0xb6/0x190
  [  320.450569]  ? __check_object_size+0xaf/0x1b0
  [  320.450578]  ? strncpy_from_user+0x4d/0x170
  [  320.4

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

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:35 UTC

** Description changed:

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

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

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

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

Status in Kernel SRU Workflow:
  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:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788755/+subscriptions

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

[Kernel-packages] [Bug 1788764] Re: linux: 3.13.0-158.208 -proposed tracker

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
  
  backports: bug 1788765 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:38 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1788765 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 10. September 2018 18:38 UTC

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

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

Title:
  linux: 3.13.0-158.208 -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:
  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:
  Invalid
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:
  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 Trusty:
  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: bug 1788765 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  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/1788764/+subscriptions

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial)
  derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 
(linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to updates
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:39 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial)
  derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 
(linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to proposed
+ phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to updates
- kernel-stable-phase-changed:Monday, 10. September 2018 18:39 UTC

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

Title:
  linux: 4.4.0-135.161 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Confirmed
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 Xenial:
  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: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial)
  derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 
(linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to 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/1788766/+subscriptions

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

[Kernel-packages] [Bug 1788765] Re: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker

** 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: 1788764
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to updates
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:38 UTC

** Description changed:

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

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

Title:
  linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788764
  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/1788765/+subscriptions

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

[Kernel-packages] [Bug 1788767] Re: linux-aws: 4.4.0-1029.32 -proposed tracker

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: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:39 UTC

** Description changed:

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

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

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

Title:
  linux-aws: 4.4.0-1029.32 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  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 Trusty:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  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/1788767/+subscriptions

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

[Kernel-packages] [Bug 1788752] Re: linux-gcp: 4.15.0-1019.20 -proposed tracker

This bug was fixed in the package linux-gcp - 4.15.0-1019.20~16.04.1

---
linux-gcp (4.15.0-1019.20~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker (LP: #1788758)

  * linux-gcp: 4.15.0-1019.20 -proposed tracker (LP: #1788752)

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin SQ and RQ mem

[Kernel-packages] [Bug 1788750] Re: linux-aws: 4.15.0-1021.21 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:33 UTC

** Description changed:

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

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

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

Title:
  linux-aws: 4.15.0-1021.21 -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 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788750/+subscriptions

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

[Kernel-packages] [Bug 1788752] Re: linux-gcp: 4.15.0-1019.20 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:34 UTC

** Description changed:

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

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

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

Title:
  linux-gcp: 4.15.0-1019.20 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Bionic:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788752/+subscriptions

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

[Kernel-packages] [Bug 1788752] Re: linux-gcp: 4.15.0-1019.20 -proposed tracker

This bug was fixed in the package linux-gcp - 4.15.0-1019.20~16.04.1

---
linux-gcp (4.15.0-1019.20~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker (LP: #1788758)

  * linux-gcp: 4.15.0-1019.20 -proposed tracker (LP: #1788752)

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin SQ and RQ mem

[Kernel-packages] [Bug 1766823] Re: zram module not found in 4.4/4.15 KVM kernel

This bug was fixed in the package linux-kvm - 4.4.0-1033.39

---
linux-kvm (4.4.0-1033.39) xenial; urgency=medium

  * linux-kvm: 4.4.0-1033.39 -proposed tracker (LP: #1788771)

  * zram module not found in 4.4/4.15 KVM kernel (LP: #1766823)
- [Config]: enable CONFIG_ZRAM
- [Config]: enable CONFIG_ZRAM (continued)

  [ Ubuntu: 4.4.0-135.161 ]

  * linux: 4.4.0-135.161 -proposed tracker (LP: #1788766)
  * [Regression] APM Merlin boards fail to recover link after interface down/up
(LP: #1785739)
- net: phylib: fix interrupts re-enablement in phy_start
- net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT
  * qeth: don't clobber buffer on async TX completion (LP: #1786057)
- s390/qeth: don't clobber buffer on async TX completion
  * nvme: avoid cqe corruption (LP: #1788035)
- nvme: avoid cqe corruption when update at the same time as read
  * CacheFiles: Error: Overlong wait for old active object to go away.
(LP: #1776254)
- cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
- cachefiles: Wait rather than BUG'ing on "Unexpected object collision"
  * fscache cookie refcount updated incorrectly during fscache object allocation
(LP: #1776277) // fscache cookie refcount updated incorrectly during fscache
object allocation (LP: #1776277)
- fscache: Fix reference overput in fscache_attach_object() error handling
  * FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false (LP: #1774336)
- Revert "UBUNTU: SAUCE: CacheFiles: fix a read_waiter/read_copier race"
- fscache: Allow cancelled operations to be enqueued
- cachefiles: Fix refcounting bug in backing-file read monitoring
  * linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
walinuxagent.service (LP: #1739107)
- [Debian] hyper-v -- Ensure that hv-kvp-daemon.service starts before
  walinuxagent.service

 -- Khalid Elmously   Mon, 27 Aug 2018
00:14:00 -0400

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  zram module not found in 4.4/4.15 KVM kernel

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Xenial:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released

Bug description:
  == Justification ==
  In the Xenial / Bionic KVM kernel, the CONFIG_ZRAM was not set, it's 
impossible for users to use zram module on it. And the ubuntu_zram_smoke_test 
regression test is failing due to the missing  module.

  == Test ==
  Before enabling CONFIG_ZRAM and the related configs, the zram module cannot 
be found.
  After that, the zram module can be inserted and pass the 
ubuntu_zram_smoke_test.

  Test kernels could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1766823-zram/

  == Fix ==
  [bionic/linux-kvm][xenial/linux-kvm][SRU][PATCH] UBUNTU: [Config]: enable 
CONFIG_ZRAM

  == Regression Potential ==
  Minimal.
  No code changes, just a config changes without disabling any other configs.


  --

  The ubuntu_zram_smoke_test will fail due to the lack of the zram
  module.

  07:32:19 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zram_smoke_test/ubuntu_zram_smoke_test.sh'
  07:32:19 ERROR| [stderr] modprobe: FATAL: Module zram not found in directory 
/lib/modules/4.15.0-1008-kvm
  07:32:19 DEBUG| [stdout] FAILED: cannot load zram module
  07:32:19 ERROR| Exception escaping from test:

  There is no zram config in the Bionic KVM kernel config file.
  $ grep -i zram debian.kvm/config/config.common.ubuntu
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
  ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
  Uname: Linux 4.15.0-1008-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 07:32:47 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766823/+subscriptions

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

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

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
  
  backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:32 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 10. September 2018 18:32 UTC

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

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

Title:
  linux: 4.15.0-34.37 -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:
  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:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: 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/1788744/+subscriptions

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

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

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:34 UTC

** Description changed:

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

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

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

Title:
  linux-azure: 4.15.0-1023.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:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  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-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788751/+subscriptions

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

[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker

This bug was fixed in the package linux-gcp - 4.15.0-1019.20~16.04.1

---
linux-gcp (4.15.0-1019.20~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker (LP: #1788758)

  * linux-gcp: 4.15.0-1019.20 -proposed tracker (LP: #1788752)

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin SQ and RQ mem

[Kernel-packages] [Bug 1788753] Re: linux-kvm: 4.15.0-1021.21 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1788744
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:35 UTC

** Description changed:

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

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

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

Title:
  linux-kvm: 4.15.0-1021.21 -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 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 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:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788744
  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/1788753/+subscriptions

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

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

This bug was fixed in the package linux-aws - 4.4.0-1067.77

---
linux-aws (4.4.0-1067.77) xenial; urgency=medium

  * linux-aws: 4.4.0-1067.77 -proposed tracker (LP: #1788769)


  [ Ubuntu: 4.4.0-135.161 ]

  * linux: 4.4.0-135.161 -proposed tracker (LP: #1788766)
  * [Regression] APM Merlin boards fail to recover link after interface down/up
(LP: #1785739)
- net: phylib: fix interrupts re-enablement in phy_start
- net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT
  * qeth: don't clobber buffer on async TX completion (LP: #1786057)
- s390/qeth: don't clobber buffer on async TX completion
  * nvme: avoid cqe corruption (LP: #1788035)
- nvme: avoid cqe corruption when update at the same time as read
  * CacheFiles: Error: Overlong wait for old active object to go away.
(LP: #1776254)
- cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
- cachefiles: Wait rather than BUG'ing on "Unexpected object collision"
  * fscache cookie refcount updated incorrectly during fscache object allocation
(LP: #1776277) // fscache cookie refcount updated incorrectly during fscache
object allocation (LP: #1776277)
- fscache: Fix reference overput in fscache_attach_object() error handling
  * FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false (LP: #1774336)
- Revert "UBUNTU: SAUCE: CacheFiles: fix a read_waiter/read_copier race"
- fscache: Allow cancelled operations to be enqueued
- cachefiles: Fix refcounting bug in backing-file read monitoring
  * linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
walinuxagent.service (LP: #1739107)
- [Debian] hyper-v -- Ensure that hv-kvp-daemon.service starts before
  walinuxagent.service

 -- Khalid Elmously   Mon, 27 Aug 2018
00:05:13 -0400

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => Fix Released

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker

This bug was fixed in the package linux-kvm - 4.4.0-1033.39

---
linux-kvm (4.4.0-1033.39) xenial; urgency=medium

  * linux-kvm: 4.4.0-1033.39 -proposed tracker (LP: #1788771)

  * zram module not found in 4.4/4.15 KVM kernel (LP: #1766823)
- [Config]: enable CONFIG_ZRAM
- [Config]: enable CONFIG_ZRAM (continued)

  [ Ubuntu: 4.4.0-135.161 ]

  * linux: 4.4.0-135.161 -proposed tracker (LP: #1788766)
  * [Regression] APM Merlin boards fail to recover link after interface down/up
(LP: #1785739)
- net: phylib: fix interrupts re-enablement in phy_start
- net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT
  * qeth: don't clobber buffer on async TX completion (LP: #1786057)
- s390/qeth: don't clobber buffer on async TX completion
  * nvme: avoid cqe corruption (LP: #1788035)
- nvme: avoid cqe corruption when update at the same time as read
  * CacheFiles: Error: Overlong wait for old active object to go away.
(LP: #1776254)
- cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
- cachefiles: Wait rather than BUG'ing on "Unexpected object collision"
  * fscache cookie refcount updated incorrectly during fscache object allocation
(LP: #1776277) // fscache cookie refcount updated incorrectly during fscache
object allocation (LP: #1776277)
- fscache: Fix reference overput in fscache_attach_object() error handling
  * FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false (LP: #1774336)
- Revert "UBUNTU: SAUCE: CacheFiles: fix a read_waiter/read_copier race"
- fscache: Allow cancelled operations to be enqueued
- cachefiles: Fix refcounting bug in backing-file read monitoring
  * linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
walinuxagent.service (LP: #1739107)
- [Debian] hyper-v -- Ensure that hv-kvp-daemon.service starts before
  walinuxagent.service

 -- Khalid Elmously   Mon, 27 Aug 2018
00:14:00 -0400

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => Fix Released

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

Title:
  linux-kvm: 4.4.0-1033.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:
  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:
  Invalid
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:
  Invalid
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 Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1788766
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1766823] Re: zram module not found in 4.4/4.15 KVM kernel

This bug was fixed in the package linux-kvm - 4.15.0-1021.21

---
linux-kvm (4.15.0-1021.21) bionic; urgency=medium

  * linux-kvm: 4.15.0-1021.21 -proposed tracker (LP: #1788753)

  * zram module not found in 4.4/4.15 KVM kernel (LP: #1766823)
- [Config]: enable CONFIG_ZRAM

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin S

[Kernel-packages] [Bug 1786313] Re: [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy

This bug was fixed in the package linux-azure - 4.15.0-1023.24~16.04.1

---
linux-azure (4.15.0-1023.24~16.04.1) xenial; urgency=medium

  * linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker (LP: #1788755)

  * linux-azure: 4.15.0-1023.24 -proposed tracker (LP: #1788751)

  * [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy
(LP: #1786313)
- hv_netvsc: Fix napi reschedule while receive completion is busy

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos

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

** Changed in: kernel-sru-workflow/promote-to-security
   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 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 10. September 2018 18:02 UTC
+ kernel-stable-phase:Promoted to security

** 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 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 10. September 2018 18:02 UTC
- kernel-stable-phase:Promoted to security

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

Title:
  linux: 4.15.0-34.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 
(linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 
1788761 (linux-hwe-edge)
  derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 
(linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to 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/1788744/+subscriptions

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

[Kernel-packages] [Bug 1786313] Re: [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy

This bug was fixed in the package linux-azure - 4.15.0-1023.24~16.04.1

---
linux-azure (4.15.0-1023.24~16.04.1) xenial; urgency=medium

  * linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker (LP: #1788755)

  * linux-azure: 4.15.0-1023.24 -proposed tracker (LP: #1788751)

  * [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy
(LP: #1786313)
- hv_netvsc: Fix napi reschedule while receive completion is busy

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos

[Kernel-packages] [Bug 1786313] Re: [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy

This bug was fixed in the package linux-azure - 4.15.0-1023.24

---
linux-azure (4.15.0-1023.24) bionic; urgency=medium

  * linux-azure: 4.15.0-1023.24 -proposed tracker (LP: #1788751)

  * [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy
(LP: #1786313)
- hv_netvsc: Fix napi reschedule while receive completion is busy

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer up

[Kernel-packages] [Bug 1766823] Re: zram module not found in 4.4/4.15 KVM kernel

This bug was fixed in the package linux-kvm - 4.15.0-1021.21

---
linux-kvm (4.15.0-1021.21) bionic; urgency=medium

  * linux-kvm: 4.15.0-1021.21 -proposed tracker (LP: #1788753)

  * zram module not found in 4.4/4.15 KVM kernel (LP: #1766823)
- [Config]: enable CONFIG_ZRAM

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin S

[Kernel-packages] [Bug 1786313] Re: [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy

This bug was fixed in the package linux-azure - 4.15.0-1023.24

---
linux-azure (4.15.0-1023.24) bionic; urgency=medium

  * linux-azure: 4.15.0-1023.24 -proposed tracker (LP: #1788751)

  * [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy
(LP: #1786313)
- hv_netvsc: Fix napi reschedule while receive completion is busy

  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer up

[Kernel-packages] [Bug 1776277] Re: fscache cookie refcount updated incorrectly during fscache object allocation

This bug was fixed in the package linux - 4.4.0-135.161

---
linux (4.4.0-135.161) xenial; urgency=medium

  * linux: 4.4.0-135.161 -proposed tracker (LP: #1788766)

  * [Regression] APM Merlin boards fail to recover link after interface down/up
(LP: #1785739)
- net: phylib: fix interrupts re-enablement in phy_start
- net: phy: fix phy_start to consider PHY_IGNORE_INTERRUPT

  * qeth: don't clobber buffer on async TX completion (LP: #1786057)
- s390/qeth: don't clobber buffer on async TX completion

  * nvme: avoid cqe corruption (LP: #1788035)
- nvme: avoid cqe corruption when update at the same time as read

  * CacheFiles: Error: Overlong wait for old active object to go away.
(LP: #1776254)
- cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
- cachefiles: Wait rather than BUG'ing on "Unexpected object collision"

  * fscache cookie refcount updated incorrectly during fscache object allocation
(LP: #1776277) // fscache cookie refcount updated incorrectly during fscache
object allocation (LP: #1776277)
- fscache: Fix reference overput in fscache_attach_object() error handling

  * FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false (LP: #1774336)
- Revert "UBUNTU: SAUCE: CacheFiles: fix a read_waiter/read_copier race"
- fscache: Allow cancelled operations to be enqueued
- cachefiles: Fix refcounting bug in backing-file read monitoring

  * linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
walinuxagent.service (LP: #1739107)
- [Debian] hyper-v -- Ensure that hv-kvp-daemon.service starts before
  walinuxagent.service

 -- Khalid Elmously   Sun, 26 Aug 2018
23:56:50 -0400

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

Title:
  fscache cookie refcount updated incorrectly during fscache object
  allocation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==

  [Impact]
  Oops during heavy NFS + FSCache + Cachefiles use:

   kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/internal.h:321!
   kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/cookie.c:639!

  [Cause]
   1)Two threads are trying to do operate on a cookie and two objects.
   2a)One thread tries to unmount the filesystem and in process goes over
     a huge list of objects marking them dead and deleting the objects.
     cookie->usage is also decremented in following path
    nfs_fscache_release_super_cookie
     -> __fscache_relinquish_cookie
  ->__fscache_cookie_put
  ->BUG_ON(atomic_read(&cookie->usage) <= 0);

   2b)second thread tries to lookup an object for reading data in
  following path
   
   fscache_alloc_object
    1) cachefiles_alloc_object
-> fscache_object_init 
  -> assign cookie, but usage not bumped.
   2) fscache_attach_object -> fails in cant_attach_object because the 
  cookie's backing object or cookie's->parent object are going away
   3)fscache_put_object
     -> cachefiles_put_object
      ->fscache_object_destroy
        ->fscache_cookie_put
     ->BUG_ON(atomic_read(&cookie->usage) <= 0);
  [Fix]
   Bump up the cookie usage in fscache_object_init,
   when it is first being assigned a cookie atomically such that the cookie
   is added and bumped up if its refcount is not zero.
   remove the assignment in the attach_object.

  [Testcase]
  A user has run ~100 hours of NFS stress tests and not seen this bug recur.

  [Regression Potential]
   - Limited to fscache/cachefiles.

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

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

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

This bug was fixed in the package linux-gcp - 4.15.0-1019.20

---
linux-gcp (4.15.0-1019.20) bionic; urgency=medium

  * linux-gcp: 4.15.0-1019.20 -proposed tracker (LP: #1788752)


  [ Ubuntu: 4.15.0-34.37 ]

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)
  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin SQ and RQ memory if QP create fails
- RDMA/bnxt_re: Fix system crash during load/unload
- ne

[Kernel-packages] [Bug 1776277] Re: fscache cookie refcount updated incorrectly during fscache object allocation

This bug was fixed in the package linux - 3.13.0-158.208

---
linux (3.13.0-158.208) trusty; urgency=medium

  * linux: 3.13.0-158.208 -proposed tracker (LP: #1788764)

  * CVE-2018-3620 // CVE-2018-3646
- SAUCE: x86/fremap: Invert the offset when converting to/from a PTE

  * BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
(LP: #1780470)
- VSOCK: sock_put wasn't safe to call in interrupt context
- VSOCK: Fix lockdep issue.
- VSOCK: Detach QP check should filter out non matching QPs.

  * CacheFiles: Error: Overlong wait for old active object to go away.
(LP: #1776254)
- cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
- cachefiles: Wait rather than BUG'ing on "Unexpected object collision"

  * fscache cookie refcount updated incorrectly during fscache object allocation
(LP: #1776277)
- fscache: Fix reference overput in fscache_attach_object() error handling

  * FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false (LP: #1774336)
- Revert "UBUNTU: SAUCE: CacheFiles: fix a read_waiter/read_copier race"
- fscache: Allow cancelled operations to be enqueued
- cachefiles: Fix refcounting bug in backing-file read monitoring

 -- Kleber Sacilotto de Souza   Fri, 24 Aug
2018 15:08:23 +

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

Title:
  fscache cookie refcount updated incorrectly during fscache object
  allocation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==

  [Impact]
  Oops during heavy NFS + FSCache + Cachefiles use:

   kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/internal.h:321!
   kernel BUG at /build/linux-Y09MKI/linux-4.4.0/fs/fscache/cookie.c:639!

  [Cause]
   1)Two threads are trying to do operate on a cookie and two objects.
   2a)One thread tries to unmount the filesystem and in process goes over
     a huge list of objects marking them dead and deleting the objects.
     cookie->usage is also decremented in following path
    nfs_fscache_release_super_cookie
     -> __fscache_relinquish_cookie
  ->__fscache_cookie_put
  ->BUG_ON(atomic_read(&cookie->usage) <= 0);

   2b)second thread tries to lookup an object for reading data in
  following path
   
   fscache_alloc_object
    1) cachefiles_alloc_object
-> fscache_object_init 
  -> assign cookie, but usage not bumped.
   2) fscache_attach_object -> fails in cant_attach_object because the 
  cookie's backing object or cookie's->parent object are going away
   3)fscache_put_object
     -> cachefiles_put_object
      ->fscache_object_destroy
        ->fscache_cookie_put
     ->BUG_ON(atomic_read(&cookie->usage) <= 0);
  [Fix]
   Bump up the cookie usage in fscache_object_init,
   when it is first being assigned a cookie atomically such that the cookie
   is added and bumped up if its refcount is not zero.
   remove the assignment in the attach_object.

  [Testcase]
  A user has run ~100 hours of NFS stress tests and not seen this bug recur.

  [Regression Potential]
   - Limited to fscache/cachefiles.

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

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

[Kernel-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

This bug was fixed in the package linux - 4.15.0-34.37

---
linux (4.15.0-34.37) bionic; urgency=medium

  * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744)

  * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352)
- MIPS: c-r4k: Fix data corruption related to cache coherence
- MIPS: ptrace: Expose FIR register through FP regset
- MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs
- KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"
- affs_lookup(): close a race with affs_remove_link()
- fs: don't scan the inode cache before SB_BORN is set
- aio: fix io_destroy(2) vs. lookup_ioctx() race
- ALSA: timer: Fix pause event notification
- do d_instantiate/unlock_new_inode combinations safely
- mmc: sdhci-iproc: remove hard coded mmc cap 1.8v
- mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register
- mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus
- libata: Blacklist some Sandisk SSDs for NCQ
- libata: blacklist Micron 500IT SSD with MU01 firmware
- xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
- drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros
- arm64: lse: Add early clobbers to some input/output asm operands
- powerpc/64s: Clear PCR on boot
- IB/hfi1: Use after free race condition in send context error path
- IB/umem: Use the correct mm during ib_umem_release
- idr: fix invalid ptr dereference on item delete
- Revert "ipc/shm: Fix shmat mmap nil-page protection"
- ipc/shm: fix shmat() nil address after round-down when remapping
- mm/kasan: don't vfree() nonexistent vm_area
- kasan: free allocated shadow memory on MEM_CANCEL_ONLINE
- kasan: fix memory hotplug during boot
- kernel/sys.c: fix potential Spectre v1 issue
- KVM: s390: vsie: fix < 8k check for the itdba
- KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed
- kvm: x86: IA32_ARCH_CAPABILITIES is always supported
- powerpc/64s: Improve RFI L1-D cache flush fallback
- powerpc/pseries: Restore default security feature flags on setup
- powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()
- MIPS: generic: Fix machine compatible matching
- mac80211: mesh: fix wrong mesh TTL offset calculation
- ARC: Fix malformed ARC_EMUL_UNALIGNED default
- ptr_ring: prevent integer overflow when calculating size
- arm64: dts: rockchip: fix rock64 gmac2io stability issues
- arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire
- libata: Fix compile warning with ATA_DEBUG enabled
- selftests: sync: missing CFLAGS while compiling
- selftest/vDSO: fix O=
- selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m
- selftests: memfd: add config fragment for fuse
- ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt
- ARM: OMAP3: Fix prm wake interrupt for resume
- ARM: OMAP2+: Fix sar_base inititalization for HS omaps
- ARM: OMAP1: clock: Fix debugfs_create_*() usage
- tls: retrun the correct IV in getsockopt
- xhci: workaround for AMD Promontory disabled ports wakeup
- IB/uverbs: Fix method merging in uverbs_ioctl_merge
- IB/uverbs: Fix possible oops with duplicate ioctl attributes
- IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy
- arm64: dts: rockchip: Fix DWMMC clocks
- ARM: dts: rockchip: Fix DWMMC clocks
- iwlwifi: mvm: fix security bug in PN checking
- iwlwifi: mvm: fix IBSS for devices that support station type API
- iwlwifi: mvm: always init rs with 20mhz bandwidth rates
- NFC: llcp: Limit size of SDP URI
- rxrpc: Work around usercopy check
- MD: Free bioset when md_run fails
- md: fix md_write_start() deadlock w/o metadata devices
- s390/dasd: fix handling of internal requests
- xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos
- mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4
- mac80211: fix a possible leak of station stats
- mac80211: fix calling sleeping function in atomic context
- cfg80211: clear wep keys after disconnection
- mac80211: Do not disconnect on invalid operating class
- mac80211: Fix sending ADDBA response for an ongoing session
- gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle
- gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle
- md raid10: fix NULL deference in handle_write_completed()
- drm/exynos: g2d: use monotonic timestamps
- drm/exynos: fix comparison to bitshift when dealing with a mask
- drm/meson: fix vsync buffer update
- arm64: perf: correct PMUVer probing
- RDMA/bnxt_re: Unpin SQ and RQ memory if QP create fails
- RDMA/bnxt_re: Fix system crash during load/unload
- net/mlx5e: Return error if prio is specified when offloading eswitch vlan
  push
- locking/xchg/al

[Kernel-packages] [Bug 1780470] Re: BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)

This bug was fixed in the package linux - 3.13.0-158.208

---
linux (3.13.0-158.208) trusty; urgency=medium

  * linux: 3.13.0-158.208 -proposed tracker (LP: #1788764)

  * CVE-2018-3620 // CVE-2018-3646
- SAUCE: x86/fremap: Invert the offset when converting to/from a PTE

  * BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
(LP: #1780470)
- VSOCK: sock_put wasn't safe to call in interrupt context
- VSOCK: Fix lockdep issue.
- VSOCK: Detach QP check should filter out non matching QPs.

  * CacheFiles: Error: Overlong wait for old active object to go away.
(LP: #1776254)
- cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
- cachefiles: Wait rather than BUG'ing on "Unexpected object collision"

  * fscache cookie refcount updated incorrectly during fscache object allocation
(LP: #1776277)
- fscache: Fix reference overput in fscache_attach_object() error handling

  * FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false (LP: #1774336)
- Revert "UBUNTU: SAUCE: CacheFiles: fix a read_waiter/read_copier race"
- fscache: Allow cancelled operations to be enqueued
- cachefiles: Fix refcounting bug in backing-file read monitoring

 -- Kleber Sacilotto de Souza   Fri, 24 Aug
2018 15:08:23 +

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

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

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

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

Title:
  BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and
  late)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  It has been brought to my attention that VMware Guest[1] randomly crashes 
after moving the VMs from a VMware "5.5" env to VMware 6.5 env.

  Notes:
  * The crashes wasn't present in VMware 5.5 (with the same VMs). Only started 
to happens with Vmware 6.5
  * The Trusty HWE kernel (Ubuntu-4.4.0-X) doesn't exhibit the situation on 
VMware 6.5.

  Here's the stack trace took from the .vmss converted to be readable by
  Linux debugger:

  [17007961.187411] BUG: scheduling while atomic: swapper/3/0/0x0100
  [17007961.189794] Modules linked in: arc4 md4 nls_utf8 cifs nfsv3 nfs_acl 
nfsv4 nfs lockd sunrpc fscache veth ipt_MASQUERADE nf_conntrack_netlink 
nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat 
nf_conntrack bridge stp llc aufs vmw_vsock_vmci_transport vsock ppdev vmwgfx 
serio_raw coretemp ttm drm vmw_balloon vmw_vmci shpchp i2c_piix4 parport_pc 
mac_hid xfs lp libcrc32c parport psmouse floppy vmw_pvscsi vmxnet3 pata_acpi
  [17007961.189856] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 
3.13.0-135-generic #184-Ubuntu
  [17007961.189862] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 10/22/2013
  [17007961.189867]  88042f263b90 8172d959 
88042f263d30
  [17007961.189874] 88042f273180 88042f263ba0 81726d8c 
88042f263c00
  [17007961.189879] 81731c8f 880428c29800 00013180 
880428c25fd8
  [17007961.189885] Call Trace:
  [17007961.189889]  [] dump_stack+0x64/0x82
  [17007961.189913] [] __schedule_bug+0x4c/0x5a
  [17007961.189922] [] __schedule+0x6af/0x7f0
  [17007961.189929] [] schedule+0x29/0x70
  [17007961.189935] [] schedule_timeout+0x279/0x310
  [17007961.189947] [] ? select_task_rq_fair+0x56b/0x6f0
  [17007961.189955] [] ? enqueue_task_fair+0x422/0x6d0
  [17007961.189962] [] ? sched_clock_cpu+0xb5/0x100
  [17007961.189971] [] wait_for_completion+0xa6/0x150
  [17007961.189977] [] ? wake_up_state+0x20/0x20
  [17007961.189987] [] ? __call_rcu+0x2d0/0x2d0
  [17007961.189993] [] wait_rcu_gp+0x4b/0x60
  [17007961.18] [] ? 
ftrace_raw_output_rcu_utilization+0x50/0x50
  [17007961.190006] [] synchronize_sched+0x3a/0x50
  [17007961.190047] [] vmci_event_unsubscribe+0x76/0xb0 
[vmw_vmci]
  [17007961.190063] [] vmci_transport_destruct+0x21/0xe0 
[vmw_vsock_vmci_transport]
  [17007961.190078] [] vsock_sk_destruct+0x17/0x60 [vsock]
  [17007961.190087] [] __sk_free+0x1f/0x180
  [17007961.190092] [] sk_free+0x19/0x20
  [17007961.190102] [] 
vmci_transport_recv_stream_cb+0x200/0x2f0 [vmw_vsock_vmci_transport]
  [17007961.190114] [] 
vmci_datagram_invoke_guest_handler+0xbc/0xf0 [vmw_vmci]
  [17007961.190126] [] vmci_dispatch_dgs+0xcf/0x230 [vmw_vmci]
  [17007961.190138] [] tasklet_action+0x11e/0x130
  [17007961.190145] [] __do_softirq+0xfc/0x310
  [17007961.190153] [] irq_exit+0x105/0x110
  [17007961.190161] [] do_IRQ+0x56/0xc0
  [17007961.190170] [] common_interrupt+0x6d/0x6d
  [17007961.190173]  []

[Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message