date:20190828

https://lists.ubuntu.com/archives/kernel-team/2019-August/103419.html Eoan
https://lists.ubuntu.com/archives/kernel-team/2019-August/103421.html 
linux-oem-osp1/bionic

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

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ On IceLake platforms there might be a thin, horizon strap of corruption
+ image at the top of screen randomly after some series of window
+ operations and disappears within a second or so. This is found on
+ multiple platforms and is quite annonying that results in bad user
+ experience.
+ 
+ [Fix]
+ The upstream bug has been filed for previous platforms, e.g. GeminiLake
+ for an year or so, still working in progress, and so far this only known
+ work-around is to turn off framebuffer compression on affected platforms.
+ 
+ [Test Case]
+ The most easy way is to observe if such corruption appears during the
+ transition from GDM to gnome-shell.
+ 
+ [Regression Risk]
+ Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
+ and has been backported to B/D.
+ 
+ === Original Description ==
+ 
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on IceLake
  platforms.
  
  Right after GDM is login screen is rendered, there might be a thin strap
  of corrupted image at top of the display for a short while. Like f-d-o
  bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times. Etc.
  
  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  D

[Kernel-packages] [Bug 1841736] Re: Intel Killer 1650s [8086:34f0] subsystem [1a56:1651] not supported

** Attachment added: "dmesg when correctly initialized with patched kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1841736/+attachment/5285317/+files/dmesg

** Summary changed:

- Intel Killer 1650s [8086:34f0] subsystem [1a56:1651] not supported
+ Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) 
[8086:34f0] subsystem [1a56:1651] not supported

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

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1841736] Re: Intel Killer 1650s [8086:34f0] subsystem [1a56:1651] not supported

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1841736/+attachment/5285268/+files/lspci

** Tags added: oem-priority originate-from-1839240 somerville

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

** No longer affects: linux-meta-oem-osp1 (Ubuntu)

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

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

** Also affects: linux-oem-osp1 (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-osp1 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-osp1 (Ubuntu Bionic)
   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/1841736

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1841736] Re: Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

This would take backport-iwlwifi version 8039[1] or newer, or iwlwifi-
fixes/pending[2] to have full support.

When enabled, it will take "iwlwifi-Qu-c0-hr-b0-*.ucode" instead of
currently requested "iwlwifi-QuQnj-b0-hr-b0-*.ucode" as firmware.

[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/commit/?id=895fe853f8ad30d8ac8460c02cf2d2943360fda4
[2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git/log/?h=pending

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

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

This change was made by a bot.

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

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

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

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Confirmed
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Packaging
- phase-changed: Tuesday, 27. August 2019 19:35 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 08:50 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 08:50 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:depwait,signed:depwait
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:depwait,signed:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1841747] [NEW] dev test in ubuntu_stress_smoke_test crashes AWS c5.large with Disco

2019-08-28 Thread Po-Hsu Lin

Public bug reported:

When testing the dev test in ubuntu_stress_smoke_test, the instance will
crash and gets rebooted.

Spotted on:
* c3.xlarge
* c4.large
* m3.large
* m4.large
* r3.large
* t2.small
* x1e.xlarge

Test output:
09:10:12 DEBUG| [stdout] dentry RETURNED 0
09:10:12 DEBUG| [stdout] dentry PASSED
09:10:12 DEBUG| [stdout] dev STARTING
packet_write_wait: Connection to 18.237.187.217 port 22: Broken pipe

tailing syslog:
Aug 28 09:10:07 ip-172-31-3-117 stress-ng: info:  [19659] dispatching hogs: 4 
dentry
Aug 28 09:10:12 ip-172-31-3-117 stress-ng: info:  [19659] successful run 
completed in 5.13s
Aug 28 09:10:12 ip-172-31-3-117 stress-ng: invoked with './stress-n' by user 0
Aug 28 09:10:12 ip-172-31-3-117 stress-ng: system: 'ip-172-31-3-117' Linux 
5.0.0-1012-aws #13-Ubuntu SMP Fri Aug 2 12:25:32 UTC 2019 x86_64
Aug 28 09:10:12 ip-172-31-3-117 stress-ng: memory (MB): total 3754.94, free 
3386.23, shared 0.06, buffer 145.52, swap 1024.00, free swap 951.48
Aug 28 09:10:12 ip-172-31-3-117 stress-ng: info:  [19674] dispatching hogs: 4 
dev
Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406432] PM: Marking nosave 
pages: [mem 0x-0x0fff]
Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406434] PM: Marking nosave 
pages: [mem 0x0009e000-0x000f]
Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406437] PM: Basic memory bitmaps 
created
Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406496] PM: Basic memory bitmaps 
freed
packet_write_wait: Connection to 18.237.187.217 port 22: Broken pipe

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1012-aws 5.0.0-1012.13
ProcVersionSignature: User Name 5.0.0-1012.13-aws 5.0.15
Uname: Linux 5.0.0-1012-aws x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
Date: Wed Aug 28 09:21:28 2019
Ec2AMI: ami-0b731fb4a9a36df8c
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2c
Ec2InstanceType: c4.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: stress-ng
 Importance: Undecided
 Assignee: Colin Ian King (colin-king)
 Status: New

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: 5.0 amd64 apport-bug aws disco ec2-images sru-20190812 
ubuntu-stress-smoke-test

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Description changed:

  When testing the dev test in ubuntu_stress_smoke_test, the instance will
- crash.
+ crash and gets rebooted.
  
  Spotted on:
  * c3.xlarge
  * c4.large
  * m3.large
  * m4.large
  * r3.large
  * t2.small
  * x1e.xlarge
  
  Test output:
  09:10:12 DEBUG| [stdout] dentry RETURNED 0
  09:10:12 DEBUG| [stdout] dentry PASSED
  09:10:12 DEBUG| [stdout] dev STARTING
  packet_write_wait: Connection to 18.237.187.217 port 22: Broken pipe
- 
  
  tailing syslog:
  Aug 28 09:10:07 ip-172-31-3-117 stress-ng: info:  [19659] dispatching hogs: 4 
dentry
  Aug 28 09:10:12 ip-172-31-3-117 stress-ng: info:  [19659] successful run 
completed in 5.13s
  Aug 28 09:10:12 ip-172-31-3-117 stress-ng: invoked with './stress-n' by user 0
  Aug 28 09:10:12 ip-172-31-3-117 stress-ng: system: 'ip-172-31-3-117' Linux 
5.0.0-1012-aws #13-Ubuntu SMP Fri Aug 2 12:25:32 UTC 2019 x86_64
  Aug 28 09:10:12 ip-172-31-3-117 stress-ng: memory (MB): total 3754.94, free 
3386.23, shared 0.06, buffer 145.52, swap 1024.00, free swap 951.48
  Aug 28 09:10:12 ip-172-31-3-117 stress-ng: info:  [19674] dispatching hogs: 4 
dev
  Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406432] PM: Marking nosave 
pages: [mem 0x-0x0fff]
  Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406434] PM: Marking nosave 
pages: [mem 0x0009e000-0x000f]
  Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406437] PM: Basic memory 
bitmaps created
  Aug 28 09:10:12 ip-172-31-3-117 kernel: [  481.406496] PM: Basic memory 
bitmaps freed
  packet_write_wait: Connection to 18.237.187.217 port 22: Broken pipe
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1012-aws 5.0.0-1012.13
  ProcVersionSignature: User Name 5.0.0-1012.13-aws 5.0.15
  Uname: Linux 5.0.0-1012-aws x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Wed Aug 28 09:21:28 2019
  Ec2AMI: ami-0b731fb4a9a36df8c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: c4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Tags added: 5.0 aws ubuntu-stress-smoke-test

** Tags added: sru-20190812

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

[Kernel-packages] [Bug 1841132] Re: mpt3sas - storage controller resets under heavy disk io

2019-08-28 Thread Drew Woodard

Stress tested bionic-proposed kernel 4.15.0-60-generic #67-Ubuntu for
6.5h with no errors so it appears to be patched in that version as
expected.


ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) BUG
ubuntu 18.04 proposed (kernel 4.15.0) (mpt3sas driver 17.100.00.00) working
ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) BUG
ubuntu 18.04 mainline (kernel 5.3.0-rc2) (mpt3sas driver 29.100.00.00) BUG
ubuntu 18.04 mainline (kernel 5.3.0-rc3) (mpt3sas driver 29.100.00.00) working
ubuntu 18.04 mainline (kernel 5.3.0-rc5) (mpt3sas driver 29.100.00.00) working
rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) working

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

Title:
  mpt3sas - storage controller resets under heavy disk io

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [summary]
  when a server running ubuntu 18.04 with an lsi sas controller experiences 
high disk io there is a chance the storage controller will reset
  this can take weeks or months, but once the controller resets it will keep 
resetting every few seconds or few minutes, dramatically degrading disk io
  the server must be rebooted to restore the controller to a normal state

  [hardware configuration]
  server: dell poweredge r7415, purchased 2019-02
  cpu/chipset: amd epyc naples
  storage controller: "dell hba330 mini" with chipset "lsi sas3008"
  drives: 4x samsung 860 pro 2TB ssd

  [software configuration]
  ubuntu 18.04 server
  mdadm raid6
  all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q)

  [what happened]
  server was operating as a vm host for months without issue
  one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag 
reset !!" and "Power-on or device reset occurred", along with unusably-slow 
disk io
  the server was removed from production and I looked for a way to reproduce 
the issue

  [how to reproduce the issue]
  there are probably many ways to product this issue, the hackish way I found 
to reliably reproduce it was:
  have the four ssds in a mdadm raid6 with ext4 filesystem
  create three 500GB files containing random data
  open three terminals. one calculates md5sum of file1 in a loop, another does 
the same for file2, the third does a copy of file3 to file3-temp in a loop
  the number of files is arbitrary, the goal is just to generate a lot of disk 
io on files too large to be cached in memory
  then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause 
even more drive thrashing
  within 1-15min the controller will enter the broken state. the longest I ever 
saw it take was 30min. I reproduced this several times
  rebooting the server restores the controller to a normal state
  if the server is not rebooted and the controller is left in this broken state 
eventually drives will fall out of the array, and sometimes array/filesystem 
corruption will occur

  [why this is being reported here]
  It's unlikely I am exceeding limits of the hardware since this server chassis 
can hold 24 drives and I am only using 4. The controller specs indicate I 
should not hit pcie bandwidth limits until at least 16 drives.
  My first thought was that the lsi controller firmware was at fault since they 
have been historically buggy, however I reproduced this with the newest 
firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be 
dell-specific).
  I then tried the most recent motherboard bios "1.9.3", and downgraded to 
"1.9.2", no change.
  I then wanted to eliminate the possibility of a bad drive. swapped out all 4 
drives with different ones of the same model, no change.
  I then upgraded from the standard 18.04 kernel to the newer backported hwe 
kernel, which also came with a newer mpt3sas driver, no change.
  I then ran the same test on the same array but with rhel 8, to my surprise I 
could no longer reproduce the issue.
  -
  tl;dr version:
  ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller 
breaks in 1-10min
  ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage 
controller breaks in 1-15min, max 30min
  rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same 
array for 19h, no errors

  [caveats]
  Server os misconfiguration is possible, however this is a rather basic vm 
host running kvm and no 3rd-party packages.
  I can't conclusively prove this isn't a hardware fault since I don't have a 
second unused identical server to test on right now, however the fact that the 
problem can be easily reproduced under ubuntu but not under rhel seems 
noteworthy.
  There is another bug (LP: #1810781) similar to this, I didn't post there 
because it's already marked as fixed.
  There is also a debian bug (Debian #926202) that encountered this on kernel 
4.19.0, but I'm unable to tell if it's the same issue.

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2019-08-28 Thread Dan Streetman

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

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

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez package in Debian:
  Unknown

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2019-08-28 Thread Dan Streetman

As many have commented, this is almost certainly a bug in the bluez udev
rule 'hid2hci', that is caused by the introduction of 'bind' and
'unbind' uevents.

Can anyone who can reproduce this bug test with the bluez package from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1759836

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez package in Debian:
  Unknown

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+

2019-08-28 Thread Seiichi Nakashima

I update kernel 5.3-rc6 another PC, that is Intel E8400 CPU and GeForce 8600GT.
I reboot twice, work fine.
kernel 5.3-rc6 at BIOS PCs in my environment, work fine.
but CMS(Compativility Support Module) PC do not work well, sometime purple 
screen blink for ever.

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

Title:
  ubuntu 18.04.3 startup purple screen blink and could not start with
  kernel 5.0.0+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-05-31 (83 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Tags: bionic third-party-packages
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-31 (86 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190421)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1841755] [NEW] Unable to build sysdig dkms module on D-AWS ARM64

2019-08-28 Thread Po-Hsu Lin

Public bug reported:

$ cat /var/lib/dkms/sysdig/0.24.1/build/make.log
DKMS make.log for sysdig-0.24.1 for kernel 5.0.0-1012-aws (aarch64)
Wed Aug 28 10:21:12 UTC 2019
make: Entering directory '/usr/src/linux-headers-5.0.0-1012-aws'
  CC [M]  /var/lib/dkms/sysdig/0.24.1/build/main.o
  CC [M]  /var/lib/dkms/sysdig/0.24.1/build/dynamic_params_table.o
  CC [M]  /var/lib/dkms/sysdig/0.24.1/build/fillers_table.o
  CC [M]  /var/lib/dkms/sysdig/0.24.1/build/flags_table.o
  CC [M]  /var/lib/dkms/sysdig/0.24.1/build/ppm_events.o
/var/lib/dkms/sysdig/0.24.1/build/main.c: In function ‘syscall_enter_probe’:
/var/lib/dkms/sysdig/0.24.1/build/main.c:1878:21: error: ‘SYSCALL_TABLE_ID0’ 
undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
  table_index = id - SYSCALL_TABLE_ID0;
 ^
 SYSCALL_TABLE_SIZE
/var/lib/dkms/sysdig/0.24.1/build/main.c:1878:21: note: each undeclared 
identifier is reported only once for each function it appears in
/var/lib/dkms/sysdig/0.24.1/build/main.c: In function ‘syscall_exit_probe’:
/var/lib/dkms/sysdig/0.24.1/build/main.c:1955:21: error: ‘SYSCALL_TABLE_ID0’ 
undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
  table_index = id - SYSCALL_TABLE_ID0;
 ^
 SYSCALL_TABLE_SIZE
make[1]: *** [scripts/Makefile.build:286: 
/var/lib/dkms/sysdig/0.24.1/build/main.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:1606: _module_/var/lib/dkms/sysdig/0.24.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.0.0-1012-aws'

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1012-aws 5.0.0-1012.13
ProcVersionSignature: User Name 5.0.0-1012.13-aws 5.0.15
Uname: Linux 5.0.0-1012-aws aarch64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: arm64
Date: Wed Aug 28 10:21:34 2019
Ec2AMI: ami-02be56c536191abdd
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2c
Ec2InstanceType: a1.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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


** Tags: 5.0 apport-bug arm64 aws disco ec2-images sru-20190812 
ubuntu-sysdig-smoke-test

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: 5.0 aws sru-20190812 ubuntu-sysdig-smoke-test

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

Title:
  Unable to build sysdig dkms module on D-AWS ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in sysdig package in Ubuntu:
  New

Bug description:
  $ cat /var/lib/dkms/sysdig/0.24.1/build/make.log
  DKMS make.log for sysdig-0.24.1 for kernel 5.0.0-1012-aws (aarch64)
  Wed Aug 28 10:21:12 UTC 2019
  make: Entering directory '/usr/src/linux-headers-5.0.0-1012-aws'
CC [M]  /var/lib/dkms/sysdig/0.24.1/build/main.o
CC [M]  /var/lib/dkms/sysdig/0.24.1/build/dynamic_params_table.o
CC [M]  /var/lib/dkms/sysdig/0.24.1/build/fillers_table.o
CC [M]  /var/lib/dkms/sysdig/0.24.1/build/flags_table.o
CC [M]  /var/lib/dkms/sysdig/0.24.1/build/ppm_events.o
  /var/lib/dkms/sysdig/0.24.1/build/main.c: In function ‘syscall_enter_probe’:
  /var/lib/dkms/sysdig/0.24.1/build/main.c:1878:21: error: ‘SYSCALL_TABLE_ID0’ 
undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
table_index = id - SYSCALL_TABLE_ID0;
   ^
   SYSCALL_TABLE_SIZE
  /var/lib/dkms/sysdig/0.24.1/build/main.c:1878:21: note: each undeclared 
identifier is reported only once for each function it appears in
  /var/lib/dkms/sysdig/0.24.1/build/main.c: In function ‘syscall_exit_probe’:
  /var/lib/dkms/sysdig/0.24.1/build/main.c:1955:21: error: ‘SYSCALL_TABLE_ID0’ 
undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
table_index = id - SYSCALL_TABLE_ID0;
   ^
   SYSCALL_TABLE_SIZE
  make[1]: *** [scripts/Makefile.build:286: 
/var/lib/dkms/sysdig/0.24.1/build/main.o] Error 1
  make[1]: *** Waiting for unfinished jobs
  make: *** [Makefile:1606: _module_/var/lib/dkms/sysdig/0.24.1/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-5.0.0-1012-aws'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1012-aws 5.0.0-1012.13
  ProcVersionSignature: User Name 5.0.0-1012.13-aws 5.0.15
  Uname: Linux 5.0.0-1012-aws aarch64
  ApportVersion: 2.20.10-0ubuntu27.1
  Arc

[Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader

2019-08-28 Thread Uwe Schindler

Hi Kai-Heng,
I was on vacation last week, will test this soon!

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

Title:
  New ID in ums-realtek module breaks cardreader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the
  Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly.

  Previously it accepted SD cards all the time. Now it looks like you
  have to insert the card on booting or shortly after booting to access
  it. If you wait longer, it no longer detects the card. The reason for
  this can be found in the kernel log (dmes). On boot it seems to detect
  a card in the reader, although there is none. After a while it says
  "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead
  device" and then resets the device. It tries this 3 times and then
  gives up completely. After that any real device plugged is no longer
  detected.

  The device is:  idVendor=0bda, idProduct=0153, bcdDevice=57.13

  Support for this was added in mainline kernel:
  
https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577

  And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE
  stack.

  Full log on boot (no card inserted):

  [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd
  [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [3.898319] usb 1-5.1: Product: USB2.0-CRW
  [3.898322] usb 1-5.1: Manufacturer: Generic
  [3.898324] usb 1-5.1: SerialNumber: 2012092657120
  [3.911571] usbcore: registered new interface driver usb-storage
  [3.914796] usbcore: registered new interface driver uas
  [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [3.924478] scsi host2: usb-storage 1-5.1:1.0
  [3.924649] usbcore: registered new interface driver ums-realtek
  [...]
  [   13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [   13.509592] scsi host2: usb-storage 1-5.1:1.0
  [   14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [   14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [   14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  170.961728] scsi 2:0:0:0: rejecting I/O to dead device
  [  170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  170.962073] scsi 2:0:0:0: [sdb] Sense not available.
  [  171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd
  [  172.194299] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [  172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  172.194327] usb 1-5.1: Product: USB2.0-CRW
  [  172.194338] usb 1-5.1: Manufacturer: Generic
  [  172.194346] usb 1-5.1: SerialNumber: 2012092657120
  [  172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [  172.212503] scsi host2: usb-storage 1-5.1:1.0
  [  173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [  173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [  173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  329.654468] usb 1-5.1: USB disconnect, device number 8
  [  329.665905] scsi 2:0:0:0: rejecting I/O to dead device
  [  329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  329.665976] scsi 2:0:0:0: [sdb] Sense not available.
  [  330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd
  [  330.910415] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [  330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  330.910444] usb 1-5.1: Product: USB2.0-CRW
  [  330.910455] usb 1-5.1: Manufacturer: Generic
  [  330.910463] usb 1-5.1: SerialNumber: 2012092657120
  [  330.917013] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [  330.932295] scsi host2: usb-storage 1-5.1:1.0
  [  331.952829] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [  331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [  331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  488.343981] usb 1-5.1: USB disconnect, device number 9
  [  488.354292] scsi 2:0:0:0: rejecting I/O to dead device
  [  488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  488.356458] scsi 2:0:0:0: [sdb] Sense not available.

  After time 488, any SD card inserted is no longer detected, because
  driver gave up.

  Please revert adding the device with idVendor=0bda, idProduct=0153 to
  ums-

[Kernel-packages] [Bug 1841757] [NEW] [SRU] Unable to boot dragonboard 410c after upgrade kernel to 4.15.0-1061

2019-08-28 Thread Gavin Lin

Public bug reported:

Issue description:
Unable to boot dragonboard 410c after upgrade kernel to 4.15.0-1061

Steps to reproduce:
1. Upgrade linux-snapdragon from 4.15.0-1060 to 4.15.0-1061.
2. reboot the system

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

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

Title:
  [SRU] Unable to boot dragonboard 410c after upgrade kernel to
  4.15.0-1061

Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  Issue description:
  Unable to boot dragonboard 410c after upgrade kernel to 4.15.0-1061

  Steps to reproduce:
  1. Upgrade linux-snapdragon from 4.15.0-1060 to 4.15.0-1061.
  2. reboot the system

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

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

[Kernel-packages] [Bug 1841541] Re: trusty/linux-aws: 4.4.0-1052.56 -proposed tracker

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 12:31 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:04 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1052.56 -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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:04 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
meta:queued,signed:queued
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 13:02 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
meta:queued,signed:queued
  variant: debs

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

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

[Kernel-packages] [Bug 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 08:36 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:01 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
+   promote-to-proposed: Pending -- ready for review
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:01 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

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

[Kernel-packages] [Bug 1841534] Re: xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 13:15 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:02 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  xenial/linux-kvm: 4.4.0-1056.63 -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 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 verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:02 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1841132] Re: mpt3sas - storage controller resets under heavy disk io

Drew,

Thanks for testing bionic-proposed!
So it will be resolved for bionic kernels shortly, when it hit bionic-updates.

Disco/19.04 will get this patch via stable updates in the near future
[1].

Eoan has it applied (LP: #1839588).

So this is all good.

Thanks again,
Mauricio

[1] https://lists.ubuntu.com/archives/kernel-
team/2019-August/103416.html

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Incomplete

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

** Also affects: linux (Ubuntu Disco)
   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/1841132

Title:
  mpt3sas - storage controller resets under heavy disk io

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete

Bug description:
  [summary]
  when a server running ubuntu 18.04 with an lsi sas controller experiences 
high disk io there is a chance the storage controller will reset
  this can take weeks or months, but once the controller resets it will keep 
resetting every few seconds or few minutes, dramatically degrading disk io
  the server must be rebooted to restore the controller to a normal state

  [hardware configuration]
  server: dell poweredge r7415, purchased 2019-02
  cpu/chipset: amd epyc naples
  storage controller: "dell hba330 mini" with chipset "lsi sas3008"
  drives: 4x samsung 860 pro 2TB ssd

  [software configuration]
  ubuntu 18.04 server
  mdadm raid6
  all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q)

  [what happened]
  server was operating as a vm host for months without issue
  one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag 
reset !!" and "Power-on or device reset occurred", along with unusably-slow 
disk io
  the server was removed from production and I looked for a way to reproduce 
the issue

  [how to reproduce the issue]
  there are probably many ways to product this issue, the hackish way I found 
to reliably reproduce it was:
  have the four ssds in a mdadm raid6 with ext4 filesystem
  create three 500GB files containing random data
  open three terminals. one calculates md5sum of file1 in a loop, another does 
the same for file2, the third does a copy of file3 to file3-temp in a loop
  the number of files is arbitrary, the goal is just to generate a lot of disk 
io on files too large to be cached in memory
  then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause 
even more drive thrashing
  within 1-15min the controller will enter the broken state. the longest I ever 
saw it take was 30min. I reproduced this several times
  rebooting the server restores the controller to a normal state
  if the server is not rebooted and the controller is left in this broken state 
eventually drives will fall out of the array, and sometimes array/filesystem 
corruption will occur

  [why this is being reported here]
  It's unlikely I am exceeding limits of the hardware since this server chassis 
can hold 24 drives and I am only using 4. The controller specs indicate I 
should not hit pcie bandwidth limits until at least 16 drives.
  My first thought was that the lsi controller firmware was at fault since they 
have been historically buggy, however I reproduced this with the newest 
firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be 
dell-specific).
  I then tried the most recent motherboard bios "1.9.3", and downgraded to 
"1.9.2", no change.
  I then wanted to eliminate the possibility of a bad drive. swapped out all 4 
drives with different ones of the same model, no change.
  I then upgraded from the standard 18.04 kernel to the newer backported hwe 
kernel, which also came with a newer mpt3sas driver, no change.
  I then ran the same test on the same array but with rhel 8, to my surprise I 
could no longer reproduce the issue.
  -
  tl;dr version:
  ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller 
breaks in 1-10min
  ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage 
controller breaks in 1-15min, max 30min
  rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same 
array for 19h, no errors

  [caveats]
  Server os misconfiguration is possible, however this is a rather basic vm 
host running kvm and no 3rd-party packages.
  I can't conclusively prove this isn't a hardware fault since I don't have a 
second unused identical server to test on right now, however the fact that the 
problem can be easily reproduced under ubuntu but not under rhel seems 
noteworthy.
  There is another bug (LP: #1810781) similar to this, I didn't post there 
because it's already marked as fixed.
  There is also a debi

[Kernel-packages] [Bug 1841536] Re: xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 10:36 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:03 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:03 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

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

[Kernel-packages] [Bug 1839979] Re: bionic/linux-snapdragon: 4.15.0-1061.68 -proposed tracker

2019-08-28 Thread Gavin Lin

Unable to boot dragonboard 410c after upgrade kernel to 4.15.0-1061

https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1841757

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

Title:
  bionic/linux-snapdragon: 4.15.0-1061.68 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841086
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Signoff
  phase-changed: Saturday, 24. August 2019 07:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839978
  variant: debs

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

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

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-08-28 Thread Anthony Wong

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

** Changed in: hwe-next
   Status: New => Triaged

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

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is actually a duplicate to
  https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for
  internal tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

[ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

[ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
[ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
[ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
[ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
[ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

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

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

[Kernel-packages] [Bug 1841533] Re: xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 10:35 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:02 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1092.103 -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 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 verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:02 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

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

[Kernel-packages] [Bug 1841539] Re: xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 11:05 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:03 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:03 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

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

[Kernel-packages] [Bug 1841761] [NEW] Flaky autopkgtest

2019-08-28 Thread Balint Reczey

Public bug reported:

Package's autopkgtest keeps failing due to trying to download dkms
packages which are already removed from the archive.

One example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/l/linux/20190813_212926_4bceb@/log.gz
...
II: dkms-build downloading zfs (zfs-dkms_0.8.1-1ubuntu7_all.deb)
--2019-08-13 21:14:21--
http://ftpmaster.internal/ubuntu/pool/universe/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb
Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99
Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2019-08-13 21:14:21 ERROR 404: Not Found.

--2019-08-13 21:14:21--
http://ftpmaster.internal/ubuntu/pool/main/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb
Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99
Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2019-08-13 21:14:21 ERROR 404: Not Found.

dpkg-deb: error: failed to read archive 'zfs-dkms_*.deb': No such file or
directory
make: *** [debian/rules.d/2-binary-arch.mk:220: install-generic] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit
status 2
...

Due to flakiness we have to keep bumping the brintey hints to migrate
other packages from -proposed.

Please fix the flakiness by moving the .deb download step closer to the
start of the autopkgtest or by other means.

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

Title:
Flaky autopkgtest

Status in linux package in Ubuntu:
Incomplete

Bug description:
Package's autopkgtest keeps failing due to trying to download dkms
packages which are already removed from the archive.

One example:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/l/linux/20190813_212926_4bceb@/log.gz
...
II: dkms-build downloading zfs (zfs-dkms_0.8.1-1ubuntu7_all.deb)
--2019-08-13 21:14:21--
http://ftpmaster.internal/ubuntu/pool/universe/z/zfs-linux/zfs-dkms_0.8.1-1ubuntu7_all.deb
Resolving ftpmaster.internal (ftpmaster.internal)... 91.189.89.99
Connecting to ftpmaster.internal (ftpmaster.internal)|91.189.89.99|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2019-08-13 21:14:21 ERROR 404: Not Found.

Due to flakiness we have to keep bumping the brintey hints to migrate
other packages from -proposed.

Please fix the flakiness by moving the .deb download step closer to
the start of the autopkgtest or by other means.

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

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

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

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

Title:
Flaky autopkgtest

Status in linux package in Ubuntu:
Incomplete

Bug description:
Package's autopkgtest keeps failing due to trying to download dkms
packages which are already removed from the archive.

One example:

Due to flakiness we have to keep bumping the brintey hints to migrate
other packages from -proposed.

Please fix the flakiness by moving the .deb download step closer to
the start of the autopkgtest or by other means.

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

[Kernel-packages] [Bug 1841132] Re: mpt3sas - storage controller resets under heavy disk io

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

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

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

Title:
  mpt3sas - storage controller resets under heavy disk io

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [summary]
  when a server running ubuntu 18.04 with an lsi sas controller experiences 
high disk io there is a chance the storage controller will reset
  this can take weeks or months, but once the controller resets it will keep 
resetting every few seconds or few minutes, dramatically degrading disk io
  the server must be rebooted to restore the controller to a normal state

  [hardware configuration]
  server: dell poweredge r7415, purchased 2019-02
  cpu/chipset: amd epyc naples
  storage controller: "dell hba330 mini" with chipset "lsi sas3008"
  drives: 4x samsung 860 pro 2TB ssd

  [software configuration]
  ubuntu 18.04 server
  mdadm raid6
  all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q)

  [what happened]
  server was operating as a vm host for months without issue
  one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag 
reset !!" and "Power-on or device reset occurred", along with unusably-slow 
disk io
  the server was removed from production and I looked for a way to reproduce 
the issue

  [how to reproduce the issue]
  there are probably many ways to product this issue, the hackish way I found 
to reliably reproduce it was:
  have the four ssds in a mdadm raid6 with ext4 filesystem
  create three 500GB files containing random data
  open three terminals. one calculates md5sum of file1 in a loop, another does 
the same for file2, the third does a copy of file3 to file3-temp in a loop
  the number of files is arbitrary, the goal is just to generate a lot of disk 
io on files too large to be cached in memory
  then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause 
even more drive thrashing
  within 1-15min the controller will enter the broken state. the longest I ever 
saw it take was 30min. I reproduced this several times
  rebooting the server restores the controller to a normal state
  if the server is not rebooted and the controller is left in this broken state 
eventually drives will fall out of the array, and sometimes array/filesystem 
corruption will occur

  [why this is being reported here]
  It's unlikely I am exceeding limits of the hardware since this server chassis 
can hold 24 drives and I am only using 4. The controller specs indicate I 
should not hit pcie bandwidth limits until at least 16 drives.
  My first thought was that the lsi controller firmware was at fault since they 
have been historically buggy, however I reproduced this with the newest 
firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be 
dell-specific).
  I then tried the most recent motherboard bios "1.9.3", and downgraded to 
"1.9.2", no change.
  I then wanted to eliminate the possibility of a bad drive. swapped out all 4 
drives with different ones of the same model, no change.
  I then upgraded from the standard 18.04 kernel to the newer backported hwe 
kernel, which also came with a newer mpt3sas driver, no change.
  I then ran the same test on the same array but with rhel 8, to my surprise I 
could no longer reproduce the issue.
  -
  tl;dr version:
  ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller 
breaks in 1-10min
  ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage 
controller breaks in 1-15min, max 30min
  rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same 
array for 19h, no errors

  [caveats]
  Server os misconfiguration is possible, however this is a rather basic vm 
host running kvm and no 3rd-party packages.
  I can't conclusively prove this isn't a hardware fault since I don't have a 
second unused identical server to test on right now, however the fact that the 
problem can be easily reproduced under ubuntu but not under rhel seems 
noteworthy.
  There is another bug (LP: #1810781) similar to this, I didn't post there 
because it's already marked as fixed.
  There is also a debian bug (Debian #926202) that encountered this on kernel 
4.19.0, but I'm unable to tell if it's the same issue.

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 08:50 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 08:50 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 27. August 2019 13:02 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 11:41 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
meta:queued,signed:queued
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 11:41 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1840704] Re: ZFS kernel modules lack debug symbols

** Description changed:

  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.
  
- Patches will be sent soon for linux and zfs/spl-linux,
- covering X/B/D/E/Unstable.
+ Patches are required in:
+ 1) linux kernel packaging, to add infrastructure to
+enable/build/strip/package debug symbols on DKMS.
+(this is sufficient on Eoan's zfs-linux.)
+ 2) zfs-linux and spl-linux, for the stable releases,
+which need a few patches to enable debug symbols.
+ 
+ Initially submitting the kernel patchset for Unstable,
+ for review/feedback.  It backports nicely into B/D/E,
+ should it be accepted; for X (doesn't use DKMS builds)
+ a simpler patch for the moment (until it does) works.
+ 
+ The zfs/spl-linux patches are ready, to be submitted
+ once the approach used by the kernel package settles.

** Description changed:

  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.
  
  Patches are required in:
+ 
  1) linux kernel packaging, to add infrastructure to
-enable/build/strip/package debug symbols on DKMS.
-(this is sufficient on Eoan's zfs-linux.)
+    enable/build/strip/package debug symbols on DKMS.
+    (this is sufficient with zfs-linux now in Eoan.)
+ 
  2) zfs-linux and spl-linux, for the stable releases,
-which need a few patches to enable debug symbols.
+    which need a few patches to enable debug symbols.
  
  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.
  
  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

Title:
  ZFS kernel modules lack debug symbols

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.

  Patches are required in:

  1) linux kernel packaging, to add infrastructure to
     enable/build/strip/package debug symbols on DKMS.
     (this is sufficient with zfs-linux now in Eoan.)

  2) zfs-linux and spl-linux, for the stable releases,
     which need a few patches to enable debug symbols.

  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.

  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

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

[Kernel-packages] [Bug 1841761] Re: Flaky autopkgtest

2019-08-28 Thread Balint Reczey

I referenced the logs in the bug text.

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

Title:
Flaky autopkgtest

Status in linux package in Ubuntu:
Confirmed

Bug description:
Package's autopkgtest keeps failing due to trying to download dkms
packages which are already removed from the archive.

One example:

Due to flakiness we have to keep bumping the brintey hints to migrate
other packages from -proposed.

Please fix the flakiness by moving the .deb download step closer to
the start of the autopkgtest or by other means.

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

[Kernel-packages] [Bug 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1841158 (bionic/linux-hwe-edge)
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 27. August 2019 18:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

Title:
  eoan/linux: 5.2.0-15.16 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1841158 (bionic/linux-hwe-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 27. August 2019 18:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1841158
  variant: debs

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 08:50 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 08:50 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  variant: debs

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

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

[Kernel-packages] [Bug 1840704] Re: ZFS kernel modules lack debug symbols

Test Build 1) Old behavior

goal: show limitations/issues.

- original packaging
- zfs not built with debug symbols
- zfs modules not present in debug package
- extra modules lack .gnu_debuglink section

Original packaging:

There are no ZFS modules in the debug package:

$ dpkg-deb -x linux-image-unsigned-5.3.0-8-generic-
dbgsym_5.3.0-8.9_amd64.ddeb ddeb-orig

$ ls ddeb-orig/usr/lib/debug/lib/modules/5.3.0-8-generic/kernel/zfs
...: No such file or directory

Accordingly, the ZFS modules are the only modules without
'.gnu_debuglink' section in the 'linux-modules' package:

$ dpkg-deb -x linux-modules-5.3.0-8-generic_5.3.0-8.9_amd64.deb
deb-modules

$ find deb-modules/ -name '*.ko' | while read ko; do objdump -h -j 
.gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link '$ko'"; 
done
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/icp.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/spl.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zavl.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zcommon.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zfs.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zlua.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/znvpair.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zunicode.ko'

By the way, this is also the case for *all* modules in the 
'linux-modules-extra' package:
(only modules in the 'linux-modules' package have '.gnu_debuglink' sections).

$ dpkg-deb -x linux-modules-
extra-5.3.0-8-generic_5.3.0-8.9_amd64.deb deb-modules-extras

$ find deb-modules-extras/ -name '*.ko' | wc -l
4508

$ find deb-modules-extras/ -name '*.ko' | while read ko; do objdump -h 
-j .gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link 
'$ko'"; done | wc -l
4508

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

Title:
  ZFS kernel modules lack debug symbols

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.

  Patches are required in:

  1) linux kernel packaging, to add infrastructure to
     enable/build/strip/package debug symbols on DKMS.
     (this is sufficient with zfs-linux now in Eoan.)

  2) zfs-linux and spl-linux, for the stable releases,
     which need a few patches to enable debug symbols
 (add option './configure --enable-debuginfo' and
 '(ZFS|SPL)_DKMS_ENABLE_DEBUGINFO' to dkms.conf.)

  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.

  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

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

[Kernel-packages] [Bug 1840704] Re: ZFS kernel modules lack debug symbols

Test Build 4) All debug symbols disabled

goal: show no zfs debug symbol activity happens either (along w/ other
debug symbol stuff)

- test packaging
- nothing built with debug symbols
- no debug package present
- no .gnu_debuglink section at all
- (no regressions)


Test packaging, debug symbols disabled at all (skipdbg=true).

The dkms-build script doesn't do any debug symbol work at all.

II: dkms-build installing zfs into 
/home/ubuntu/dbgsym/unstable/debian/linux-modules-5.3.0-8-generic/lib/modules/5.3.0-8-generic/kernel/zfs
signing zavl.ko
signing znvpair.ko
signing zunicode.ko
signing zcommon.ko
signing zfs.ko
signing icp.ko
signing zlua.ko
signing spl.ko
II: dkms-build build zfs complete

No debug sections are present in ZFS modules (as expected):

$ objdump -h deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zfs.ko 
| grep debug
$

And the check for modules without debug symbols is not exercised (as
expected):

$ grep WARNING build.log
$

$ find deb-modules/ -name '*.ko' | wc -l
1000

$ find deb-modules/ -name '*.ko' | while read ko; do objdump -h -j 
.gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link '$ko'"; 
done | wc -l
1000

$ find deb-modules-extra/ -name '*.ko' | wc -l
4508

$ find deb-modules-extra/ -name '*.ko' | while read ko; do objdump -h -j 
.gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link '$ko'"; 
done | wc -l
4508


** Description changed:

  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.
  
  Patches are required in:
  
  1) linux kernel packaging, to add infrastructure to
     enable/build/strip/package debug symbols on DKMS.
     (this is sufficient with zfs-linux now in Eoan.)
  
  2) zfs-linux and spl-linux, for the stable releases,
-    which need a few patches to enable debug symbols.
+    which need a few patches to enable debug symbols
+(add option './configure --enable-debuginfo' and
+'(ZFS|SPL)_DKMS_ENABLE_DEBUGINFO' to dkms.conf.)
  
  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.
  
  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

Title:
  ZFS kernel modules lack debug symbols

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.

  Patches are required in:

  1) linux kernel packaging, to add infrastructure to
     enable/build/strip/package debug symbols on DKMS.
     (this is sufficient with zfs-linux now in Eoan.)

  2) zfs-linux and spl-linux, for the stable releases,
     which need a few patches to enable debug symbols
 (add option './configure --enable-debuginfo' and
 '(ZFS|SPL)_DKMS_ENABLE_DEBUGINFO' to dkms.conf.)

  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.

  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

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

[Kernel-packages] [Bug 1840704] Re: ZFS kernel modules lack debug symbols

Test Build 2) New behavior if ZFS modules are *not* built with debug
symbols

goal: show failsafe/backwards compatible behavior if zfs-dksm doesn't 
support/build debug symbols
  and kernel build log reports missing debug symbols, and extra modules 
have .gnu_debuglink.

- test packaging
- zfs not built with debug symbols (disabled manually in dkms-build if-check)
- zfs modules not present in debug package
- extra modules have .gnu_debuglink section
- (no regressions)

Test packaging, with debug symbols *not enabled* in zfs-dkms:

The debug symbols are not found (as expected), 
and this case is handled without problems:

II: dkms-build installing zfs into 
/home/ubuntu/dbgsym/unstable/debian/linux-image-unsigned-5.3.0-8-generic-dbgsym/usr/lib/debug/lib/modules/5.3.0-8-generic/kernel/zfs
 (debug symbols)
ignoring zavl.ko (missing debug symbols)
stripping zavl.ko
ignoring znvpair.ko (missing debug symbols)
stripping znvpair.ko
ignoring zunicode.ko (missing debug symbols)
stripping zunicode.ko
ignoring zcommon.ko (missing debug symbols)
stripping zcommon.ko
ignoring zfs.ko (missing debug symbols)
stripping zfs.ko
ignoring icp.ko (missing debug symbols)
stripping icp.ko
ignoring zlua.ko (missing debug symbols)
stripping zlua.ko
ignoring spl.ko (missing debug symbols)
stripping spl.ko
II: dkms-build installing zfs into 
/home/ubuntu/dbgsym/unstable/debian/linux-modules-5.3.0-8-generic/lib/modules/5.3.0-8-generic/kernel/zfs
signing zavl.ko
signing znvpair.ko
signing zunicode.ko
signing zcommon.ko
signing zfs.ko
signing icp.ko
signing zlua.ko
signing spl.ko
II: dkms-build build zfs complete

The debug package contains the ZFS directory, but it's empty:

$ dpkg-deb -x 
linux-image-unsigned-5.3.0-8-generic-dbgsym_5.3.0-8.9_amd64.ddeb 
ddeb-test-disabled
$ ls 
ddeb-test-disabled/usr/lib/debug/lib/modules/5.3.0-8-generic/kernel/zfs/
$

The kernel build log documents which modules do not have debug symbols,
now covering modules built with DKMS (zfs and vbox):

$ grep WARNING build.log 
echo "WARNING: Missing debug symbols for module 
'$module'."; \
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/zavl.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/znvpair.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/zunicode.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/zcommon.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/zfs.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/icp.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/zlua.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/zfs/spl.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxguest.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxsf.ko'.

The ZFS modules have no '.gnu_debuglink' section or any other debug
section (as expected):

$ dpkg-deb -x linux-modules-5.3.0-8-generic_5.3.0-8.9_amd64.deb
deb-modules

$ find deb-modules/ -name '*.ko' | while read ko; do objdump -h -j 
.gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link '$ko'"; 
done
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/icp.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/spl.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zavl.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zcommon.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zfs.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zlua.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/znvpair.ko'
Module without debug link 
'deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/zunicode.ko'

$ for ko in deb-modules/lib/modules/5.3.0-8-generic/kernel/zfs/*.ko; do 
objdump -h $ko | grep debug; done
$

But all modules in 'linux-modules-extra' now have '.gnu_debuglink' sections
(except virtualbox modules which are DKMS-built without debug symbols too.)

$ dpkg-deb -x linux-modules-
extra-5.3.0-8-generic_5.3.0-8.9_amd64.deb deb-modules-extra

$ find deb-modules-extra/ -name '*.ko' | while read ko; do objdump -h 
-j .

[Kernel-packages] [Bug 1840704] Re: ZFS kernel modules lack debug symbols

Test Build 3) New behavior if ZFS modules are built with debug symbols

goal: show zfs debug symbols are correctly built and packaged into non-
debug & debug packages.

- test packaging
- zfs built with debug symbols
- zfs modules present in debug package
- extra modules *have* .gnu_debuglink section

Test packaging, debug symbols *enabled* in zfs-dkms:

Modules are built with debug symbols, copied to debug package directory, 
and stripped before being copied into strip/non-debug package directory.

II: dkms-build installing zfs into 
/home/ubuntu/dbgsym/unstable/debian/linux-image-unsigned-5.3.0-8-generic-dbgsym/usr/lib/debug/lib/modules/5.3.0-8-generic/kernel/zfs
 (debug symbols)
copying zavl.ko
stripping zavl.ko
copying znvpair.ko
stripping znvpair.ko
copying zunicode.ko
stripping zunicode.ko
copying zcommon.ko
stripping zcommon.ko
copying zfs.ko
stripping zfs.ko
copying icp.ko
stripping icp.ko
copying zlua.ko
stripping zlua.ko
copying spl.ko
stripping spl.ko
II: dkms-build installing zfs into 
/home/ubuntu/dbgsym/unstable/debian/linux-modules-5.3.0-8-generic/lib/modules/5.3.0-8-generic/kernel/zfs
signing zavl.ko
signing znvpair.ko
signing zunicode.ko
signing zcommon.ko
signing zfs.ko
signing icp.ko
signing zlua.ko
signing spl.ko
II: dkms-build build zfs complete

The ZFS modules are now present in the debug package:

$ dpkg-deb -x linux-image-unsigned-5.3.0-8-generic-
dbgsym_5.3.0-8.9_amd64.ddeb ddeb-test-enabled

$ ls -1 
ddeb-test-enabled/usr/lib/debug/lib/modules/5.3.0-8-generic/kernel/zfs/
icp.ko
spl.ko
zavl.ko
zcommon.ko
zfs.ko
zlua.ko
znvpair.ko
zunicode.ko

And now all modules in 'linux-modules' have the '.gnu_debuglink'
section:

$ dpkg-deb -x linux-modules-5.3.0-8-generic_5.3.0-8.9_amd64.deb 
deb-modules
$ find deb-modules/ -name '*.ko' | while read ko; do objdump -h -j 
.gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link '$ko'"; 
done
$


The build log no longer shows ZFS modules as missing debug symbols:

$ grep WARNING build.log 
echo "WARNING: Missing debug symbols for module 
'$module'."; \
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxguest.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxsf.ko'.
$ 

The only modules in 'linux-modules-extra' without that continue to be
virtualbox modules:

$ dpkg-deb -x linux-modules-extra-5.3.0-8-generic_5.3.0-8.9_amd64.deb 
deb-modules-extra
$ find deb-modules-extra/ -name '*.ko' | while read ko; do objdump -h 
-j .gnu_debuglink $ko >/dev/null 2>&1 || echo "Module without debug link 
'$ko'"; done
Module without debug link 
'deb-modules-extra/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxguest.ko'
Module without debug link 
'deb-modules-extra/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxsf.ko'
$

As reflected in the kernel build log.

$ grep WARNING build.log 
echo "WARNING: Missing debug symbols for module 
'$module'."; \
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxguest.ko'.
WARNING: Missing debug symbols for module 
'/lib/modules/5.3.0-8-generic/kernel/virtualbox-guest/vboxsf.ko'.

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

Title:
  ZFS kernel modules lack debug symbols

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.

  Patches are required in:

  1) linux kernel packaging, to add infrastructure to
     enable/build/strip/package debug symbols on DKMS.
     (this is sufficient with zfs-linux now in Eoan.)

  2) zfs-linux and spl-linux, for the stable releases,
     which need a few patches to enable debug symbols
 (add option './configure --enable-debuginfo' and
 '(ZFS|SPL)_DKMS_ENABLE_DEBUGINFO' to dkms.conf.)

  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.

  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 08:50 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 12:21 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:25 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:25 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1

2019-08-28 Thread Gerrit Gogel

I'm also experiencing this issue and I'm trying to fix this for days
now. The send speed caps out at about 700 Mbps. I'm not seeing any hangs
or connection losses though. I'm eager to find a solution for this, as I
have to move 50 TB over that server.

What I've tried:
- Kernels:  4.15.58, 4.15.60 from bionic-proposed, 5.3rc6 
- ethtool:
"ethool -K enp0s31f6 tso off gso off" doesn't do anything
ethtool doens't even have an option for tso, because  "ethtool -k enp0s31f6 | 
grep tso " doesn't return anything
"ethtool -k enp0s31f6 | grep gso" returns
tx-gso-robust: off [fixed]
tx-gso-partial: off [fixed]
tso is probably already off?
- installed latest driver from intel: no change

I would be really thankful I've anyone has a solution for 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/1802691

Title:
  Slow send speed with Intel I219-V on Ubuntu 18.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing with iperf3 send speed is only 750mbps while receive speed is
  normal - 940mbps.

  Ubuntu 18.04.1
  Msi b250m mortar
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  django 1016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A69
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M MORTAR ARCTIC (MS-7A69)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A69
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 12:21 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 12:25 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:25 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:01 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 12:31 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:31 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

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

[Kernel-packages] [Bug 1841070] Re: S3 sleep/suspend fails with Linux 4.15.0-58-generic

2019-08-28 Thread Patrick Wigmore

4.15.0-57 and 4.15.0-56 are both affected.

(They also have graphical glitches and no WiFi.)

Contrary to comment #23, I found -57 at
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/17349453

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

Title:
  S3 sleep/suspend fails with Linux 4.15.0-58-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression: My laptop has become unable to enter S3 sleep/suspend.
  (A.K.A. Suspend to RAM) It seems to go through all the motions,
  including shutting down network interfaces and stopping the hard disk,
  but fails at the last moment and immediately starts back up again,
  showing the lock screen.

  4.15.0-58-generic is affected.
  4.15.0-55-generic is NOT affected.

  In /var/log/syslog, it seems that the cause might be that a USB device
  fails to suspend. (Log excerpt attached.)

  The bug occurs both with and without external USB devices connected.
  There are USB devices integral to the laptop, which are always
  present.

  Laptop model: CLEVO N350DW
  Processor: 4x Intel(R) Core(TM) i5-6600T CPU
  BIOS date: 05/26/2016
  BIOS version: 5.11

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.15.0.58.79
  ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Aug 22 15:05:09 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-16 (1069 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick1845 F pulseaudio
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64
  InstallationDate: Installed on 2016-09-16 (1069 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: PC Specialist Limited N350DW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-58-generic N/A
   linux-backports-modules-4.15.0-58-generic  N/A
   linux-firmware 1.157.22
  Tags:  xenial xenial
  Uname: Linux 4.15.0-58-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: False
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Kernel-packages] [Bug 1840704] Re: ZFS kernel modules lack debug symbols

[Unstable][PATCH 0/6] Add support for ZFS debug symbols
https://lists.ubuntu.com/archives/kernel-team/2019-August/103425.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/1840704

Title:
  ZFS kernel modules lack debug symbols

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The ZFS kernel modules aren't built with debug symbols,
  which introduces problems/issues for debugging/support.

  Patches are required in:

  1) linux kernel packaging, to add infrastructure to
     enable/build/strip/package debug symbols on DKMS.
     (this is sufficient with zfs-linux now in Eoan.)

  2) zfs-linux and spl-linux, for the stable releases,
     which need a few patches to enable debug symbols
 (add option './configure --enable-debuginfo' and
 '(ZFS|SPL)_DKMS_ENABLE_DEBUGINFO' to dkms.conf.)

  Initially submitting the kernel patchset for Unstable,
  for review/feedback.  It backports nicely into B/D/E,
  should it be accepted; for X (doesn't use DKMS builds)
  a simpler patch for the moment (until it does) works.

  The zfs/spl-linux patches are ready, to be submitted
  once the approach used by the kernel package settles.

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

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

[Kernel-packages] [Bug 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:31 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

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

[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Promote to Proposed
  phase-changed: Thursday, 22. August 2019 15:47 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

Title:
  xenial/linux-deeplens: 4.15.0-1006.6 -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 promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Promote to Proposed
  phase-changed: Thursday, 22. August 2019 15:47 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:25 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:25 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1841148] Re: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver

Hi Martijn,

Thanks for testing bionic-proposed!
So it will be resolved for bionic kernels shortly, when it hit bionic-updates.

Disco/19.04 will get this patch via stable updates in the near future
[1].

Eoan has it applied (LP: #1837725).

So this is all good.

Thanks again,
Mauricio

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

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

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

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

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

Title:
  Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and
  82579V using e1000e driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Released

Bug description:
  Since linux-image-4.15.0-58-generic my ethernet connection fails to
  get a connection.

  The network connection constantly goes up and down. The issue has been
  reported by another user:

  https://bugzilla.kernel.org/show_bug.cgi?id=204591

  Snippet from kern.log showing that the connection constantly goes up
  and down:

  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open 
called by PID 5847 (vmnet-bridge)
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 
does not exist, allocating memory.
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port 
on hub 0 successfully opened
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: 
up
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: 
attached
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent 
link down event.
  Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent 
link up event.
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: 
disabling the bridge on dev down
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: 
down
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: 
detached
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent 
link down event.
  Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent 
link up event.
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open 
called by PID 5847 (vmnet-bridge)
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 
does not exist, allocating memory.
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port 
on hub 0 successfully opened
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: 
up
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: 
attached
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent 
link down event.
  Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent 
link up event.
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: 
disabling the bridge on dev down
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: 
down
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: 
detached
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent 
link down event.
  Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent 
link up event.
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open 
called by PID 5847 (vmnet-bridge)
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 
does not exist, allocating memory.
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port 
on hub 0 successfully opened
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: 
up
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: 
attached
  Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent 
link down event.
  Aug 20 10:06:

[Kernel-packages] [Bug 1841288] Re: does not create compressed dump on 5.0 or later kernels

2019-08-28 Thread Thadeu Lima de Souza Cascardo

** Patch removed: "debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+attachment/5284280/+files/makedumpfile_1.6.5-1ubuntu1.1~18.04.2.debdiff

** Patch added: "new debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+attachment/5285380/+files/makedumpfile_1.6.5-1ubuntu1~18.04.2.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/1841288

Title:
  does not create compressed dump on 5.0 or later kernels

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Disco:
  In Progress

Bug description:
  [Impact]
  On ppc64el, makedumpfile won't create compressed dumps, causing them to be 
very large. This affects any kernel later than 4.19 actually.

  [Test case]
  Crash a system with kdump-tools installed and enabled, by using the following 
sequence. Verify the created dumps are compressed by using file. This is the 
same test as the autopkgtest for makedumpfile.

  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  [Regression potential]
  This is a small fix and should only impact ppc64el. Older kernels should 
still work, and should be tested.

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

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

[Kernel-packages] [Bug 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)

2019-08-28 Thread bugproxy

--- Comment From anjutsudha...@in.ibm.com 2019-07-16 01:49 EDT---
>
> Anju - we missing something else?

Hi Michael,

This seems to be a different issue. Not related to thread-imc. Similar perf 
fuzzer issues are reported in
https://bugzilla.linux.ibm.com/show_bug.cgi?id=161854
https://bugzilla.linux.ibm.com/show_bug.cgi?id=162507

See this comment:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=162507#c37

One workaround can be: try with these patches as well:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3202e35ec1c8fc19cea24253ff83edf702a60a02

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

Above patches fixes two issues. But there are still cases where lockup
can still happen.

Thanks,
Anju

** Bug watch added: bugzilla.linux.ibm.com/ #161854
   https://bugzilla.linux.ibm.com/show_bug.cgi?id=161854

** Bug watch added: bugzilla.linux.ibm.com/ #162507
   https://bugzilla.linux.ibm.com/show_bug.cgi?id=162507

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

Title:
  [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is
  seen while running perf fuzzer (perf:)

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-02-02 
01:21:36 ==
  Problem Description :
  =

  Warn on message is seen while running perf fuzzer tests.

  Machine details :
  ==
  Hardware : Witherspoon (wsp12) + DD2.1
  OS : Ubuntu 1804
  uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 )

  
  Steps to reproduce :
  
  Build Kernel :
  
  To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in 
the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

  
  Call trace :
  ===
  [  329.228031] [ cut here ]
  [  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
  [  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
  [  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
  [  329.228070] task: c03f776ac900 task.stack: c03f77728000
  [  329.228071] NIP: c0299b70 LR: c02a4534 CTR: 
c029bb80
  [  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
  [  329.228073] MSR: 9282b033 
  [  329.228079]   CR: 24008822  XER: 
  [  329.228080] CFAR: c0299a70 SOFTE: 0 
 GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
 GPR04: c03f776ac900 0001  
003fee73 
 GPR08:   c11220d8 
0002 
 GPR12: c029bb80 c7a3d900  
 
 GPR16:    
 
 GPR20:   c03f776ad090 
c0c71354 
 GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
 GPR28: c11220d8 0001 c14c6108 
c03fef858900 
  [  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
  [  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
  [  329.228101] Call Trace:
  [  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
  [  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
  [  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
  [  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
  [  329.2

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

2019-08-28 Thread Thadeu Lima de Souza Cascardo

** Patch added: "backport to xenial"
   
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828596/+attachment/5285400/+files/makedumpfile_1.6.3-2~16.04.2.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/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Triaged
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  In Progress
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  In Progress
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

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

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

[Kernel-packages] [Bug 1841533] Re: xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-aws: 4.4.0-1092.103 -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 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 verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:20 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

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

[Kernel-packages] [Bug 1841534] Re: xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-kvm: 4.4.0-1056.63 -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 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 verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841533] Re: xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:02 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 13:20 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1092.103 -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 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 verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:20 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

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

[Kernel-packages] [Bug 1841534] Re: xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:02 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 13:32 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  xenial/linux-kvm: 4.4.0-1056.63 -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 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 verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841533] Re: xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:20 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1092.103 -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 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 verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:20 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

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

[Kernel-packages] [Bug 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:31 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 12:31 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

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

[Kernel-packages] [Bug 1841288] Re: does not create compressed dump on 5.0 or later kernels

Hello Thadeu, or anyone else affected,

Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.1 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-disco

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

Title:
  does not create compressed dump on 5.0 or later kernels

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  On ppc64el, makedumpfile won't create compressed dumps, causing them to be 
very large. This affects any kernel later than 4.19 actually.

  [Test case]
  Crash a system with kdump-tools installed and enabled, by using the following 
sequence. Verify the created dumps are compressed by using file. This is the 
same test as the autopkgtest for makedumpfile.

  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  [Regression potential]
  This is a small fix and should only impact ppc64el. Older kernels should 
still work, and should be tested.

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

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

[Kernel-packages] [Bug 1841536] Re: xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:03 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 13:40 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:40 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

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

[Kernel-packages] [Bug 1841536] Re: xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:40 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:46 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841539] Re: xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:45 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

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

[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.1 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-disco

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

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Disco:
  Fix Committed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-08 
01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right 
place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR  - 2018-01-08 03:05:05 
==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical 
Launchpad1676884 )

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

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

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.1 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: makedumpfile (Ubuntu Disco)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in kexec-tools source package in Cosmic:
  Invalid
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Confirmed
Status in makedumpfile source package in Disco:
  Fix Committed
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The kdump kernel will crash during its boot if booted on a CPU other than 0.

  [Test case]
  Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. 
Check that the dump is successful.

  echo c | sudo taskset -c 1 tee /proc/sysrq-trigger

  [Regression potential]
  This will cause more memory to be used by the dump kernel, which may cause 
OOMs during the dump. The fix is restricted to ppc64el.

  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.1 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-disco

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Committed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.1 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-disco

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Triaged
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  Fix Committed
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

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

[Kernel-packages] [Bug 1841288] Re: does not create compressed dump on 5.0 or later kernels

Hello Thadeu, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  does not create compressed dump on 5.0 or later kernels

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  On ppc64el, makedumpfile won't create compressed dumps, causing them to be 
very large. This affects any kernel later than 4.19 actually.

  [Test case]
  Crash a system with kdump-tools installed and enabled, by using the following 
sequence. Verify the created dumps are compressed by using file. This is the 
same test as the autopkgtest for makedumpfile.

  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  [Regression potential]
  This is a small fix and should only impact ppc64el. Older kernels should 
still work, and should be tested.

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

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

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in kexec-tools source package in Cosmic:
  Invalid
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Confirmed
Status in makedumpfile source package in Disco:
  Fix Committed
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The kdump kernel will crash during its boot if booted on a CPU other than 0.

  [Test case]
  Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. 
Check that the dump is successful.

  echo c | sudo taskset -c 1 tee /proc/sysrq-trigger

  [Regression potential]
  This will cause more memory to be used by the dump kernel, which may cause 
OOMs during the dump. The fix is restricted to ppc64el.

  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Triaged
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  Fix Committed
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

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

[Kernel-packages] [Bug 1841539] Re: xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:03 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 13:45 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:45 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:41 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 13:46 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:46 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841536] Re: xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:40 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:40 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1841535
  variant: debs

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

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

[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Disco:
  Fix Committed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-08 
01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right 
place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR  - 2018-01-08 03:05:05 
==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical 
Launchpad1676884 )

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

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

Hello bugproxy, or anyone else affected,

Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Committed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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

[Kernel-packages] [Bug 1806323] Re: libfu_plugin_dell.so w/dell TB16 Dock blanks the display

2019-08-28 Thread Mario Limonciello

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

** This bug has been marked a duplicate of bug 1793965
   Firmware update daemon resets displays connected to Dell TB16 dock soon 
after every first login

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

Title:
  libfu_plugin_dell.so w/dell TB16 Dock blanks the display

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

Bug description:
  Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15
  laptop and a Dell TB16 dock.

  A few seconds after logging into the Gnome 3 UI, something in the UI
  starts the fwupd.service. About 2 seconds later, the display goes
  blank and does not come back. There is no obvious recovery short of
  killing all the user's processes, and then logging back in.  A second
  login does not reproduce the problem, since the fwupd service is now
  running, and does not restart. However manually restarting the fwupd
  service causes the problem to recur.

  The problem does not occur if the "dell" module is blacklisted in
  /etc/fwupd/daemon.conf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: fwupd 1.0.6-2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:02:31 2018
  InstallationDate: Installed on 2018-11-19 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: fwupd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (197 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-19 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702

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

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

[Kernel-packages] [Bug 1841541] Re: trusty/linux-aws: 4.4.0-1052.56 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 11:04 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 14:01 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1052.56 -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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 14:01 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841541] Re: trusty/linux-aws: 4.4.0-1052.56 -proposed tracker

** 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) => Andy 
Whitcroft (apw)

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

Title:
  trusty/linux-aws: 4.4.0-1052.56 -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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 14:01 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841539] Re: xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:45 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1124.130 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:45 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1841537
  variant: debs

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

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

2019-08-28 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   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/1681909

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Committed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:46 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:46 UTC
  reason:
promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
  variant: debs

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

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

[Kernel-packages] [Bug 1841534] Re: xenial/linux-kvm: 4.4.0-1056.63 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

Title:
  xenial/linux-kvm: 4.4.0-1056.63 -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 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 verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 13:32 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1841658] Re: bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker

** 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/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
- phase: Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 12:25 UTC
+ phase: Ready for Testing
+ phase-changed: Wednesday, 28. August 2019 14:10 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-ibm-gt: 4.15.0-1034.36 -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 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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841086
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Testing
  phase-changed: Wednesday, 28. August 2019 14:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841704] Re: Test 391/u and 391/p from ubuntu_bpf failed on B

2019-08-28 Thread Kleber Sacilotto de Souza

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

Title:
  Test 391/u and 391/p from ubuntu_bpf failed on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed

Bug description:
  #391/u bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x0
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    R1 has unknown scalar with mixed signed bounds, pointer arithmetic with it 
prohibited for !root

  
    #391/p bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x9391367ba400
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    math between map_value pointer and register with unbounded min value is not 
allowed

  Test result with older kernel:
    #391/u bounds checks mixing signed and unsigned, variant 15 OK
    #391/p bounds checks mixing signed and unsigned, variant 15 OK

  The test has passed but the variant number is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Wed Aug 28 02:58:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   li

[Kernel-packages] [Bug 1841707] Re: Test 491/u and 491/p from ubuntu_bpf failed on B

2019-08-28 Thread Kleber Sacilotto de Souza

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

Title:
  Test 491/u and 491/p from ubuntu_bpf failed on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed

Bug description:
#491/u check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0

#491/p check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0

  Test result from 4.15.0-58:
#491/u check deducing bounds from const, 6 OK
#491/p check deducing bounds from const, 6 OK

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [  540.701915] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [  540.708360] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Aug 28 03:14:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-60-generic N/A
   linux-backports-modules-4.15.0-60-generic  N/A
   linux-firmware 1.173.10
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1841704] Re: Test 391/u and 391/p from ubuntu_bpf failed on B

2019-08-28 Thread Kleber Sacilotto de Souza

The bug was introduced by the following commit backported from the upstream 
stable 4.19.y:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-next&id=c779b6c6b215bc3b3b7fcb39ab62f816bd6dfb75

The mainline commit changes also test_verifier.c from bpf self_tests:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f7b3e82589e0de723780198ec7983e427144c0a

However, changing the expected error message for test #391 seems to be
not enough, since 391/u failed with a different error message (R1 has
unknown scalar with mixed signed bounds, pointer arithmetic with it
prohibited for !root).

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

Title:
  Test 391/u and 391/p from ubuntu_bpf failed on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed

Bug description:
  #391/u bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x0
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    R1 has unknown scalar with mixed signed bounds, pointer arithmetic with it 
prohibited for !root

  
    #391/p bounds checks mixing signed and unsigned, variant 14 FAIL
    Unexpected error message!
    0: (61) r9 = *(u32 *)(r1 +8)
    1: (7a) *(u64 *)(r10 -8) = 0
    2: (bf) r2 = r10
    3: (07) r2 += -8
    4: (18) r1 = 0x9391367ba400
    6: (85) call bpf_map_lookup_elem#1
    7: (15) if r0 == 0x0 goto pc+8
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    8: (7a) *(u64 *)(r10 -16) = -8
    9: (79) r1 = *(u64 *)(r10 -16)
    10: (b7) r2 = -1
    11: (b7) r8 = 2
    12: (15) if r9 == 0x2a goto pc+6
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    13: (6d) if r8 s> r1 goto pc+3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) 
R1=inv(id=0,umin_value=2,umax_value=9223372036854775807,var_off=(0x0; 
0x7fff)) R2=inv-1 R8=inv2 
R9=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) R10=fp0
    14: (65) if r1 s> 0x1 goto pc+2
    17: (b7) r0 = 0
    18: (95) exit

    from 13 to 17: safe

    from 12 to 19: R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    19: (2d) if r1 > r2 goto pc-3
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0) R2=inv-1 R8=inv2 
R9=inv42 R10=fp0
    20: (05) goto pc-7
    14: (65) if r1 s> 0x1 goto pc+2
     R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R1=inv(id=0,smax_value=1) 
R2=inv-1 R8=inv2 R9=inv42 R10=fp0
    15: (0f) r0 += r1
    math between map_value pointer and register with unbounded min value is not 
allowed

  Test result with older kernel:
    #391/u bounds checks mixing signed and unsigned, variant 15 OK
    #391/p bounds checks mixing signed and unsigned, variant 15 OK

  The test has passed but the variant number is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: User Name 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 02:49 seq
   crw-rw 1 root audio 116, 33 Aug 28 02:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory

[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker

** 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/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Promote to Proposed
- phase-changed: Thursday, 22. August 2019 15:47 UTC
+ phase: Ready for Testing
+ phase-changed: Wednesday, 28. August 2019 14:16 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  xenial/linux-deeplens: 4.15.0-1006.6 -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 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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841085
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Testing
  phase-changed: Wednesday, 28. August 2019 14:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space

2019-08-28 Thread Juerg Haefliger

Is this easily reproducible? Can you retry with the latest released
kernel 4.15.0-58.64? I haven't been able to reproduce the problem
locally so far. It would help if you could share the container and
workload, if that's possible at all. I'm still looking through the
dumpfiles but haven't made much progress yet towards finding the root
cause.

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

Title:
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in
  kernel virtual address space

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Robert J. Brenneman  - 2019-05-30 
11:16:45 ==
  ---Problem Description---
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual 
kernel address space

  Contact Information = rjbr...@us.ibm.com

  ---uname output---
  Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 
s390x s390x s390x GNU/Linux

  Machine Type = z13   2964 NE1

  ---System Hang---
   z/VM took a VMDUMP and reIPLed
  (the attached and available dumps are Linux dumps)

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   boot system, start jenkins, let it run a couple days

  Stack trace output:
   05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8
  05/29/19 13:24:06   ?<008e87f0>? ext_int_handler+0x134/0x138
  05/29/19 13:24:06   ?<00102cee>? enabled_wait+0x4e/0xe0
  05/29/19 13:24:06  (?<1201>? 0x1201)
  05/29/19 13:24:06   ?<0010303a>? arch_cpu_idle+0x32/0x48
  05/29/19 13:24:06   ?<001c5ae8>? do_idle+0xe8/0x1a8

  Oops output:
   05/29/19 13:24:06  User process fault: interruption code 003b ilc:3 in 
libc-2.23.so?3ffaca0+185000?
  05/29/19 13:24:06  Failing address:  TEID: 0800
  05/29/19 13:24:06  Fault in primary space mode while using user ASCE.
  05/29/19 13:24:06  AS:000710b241c7 R3:0024
  05/29/19 13:24:06  Unable to handle kernel pointer dereference in virtual 
kernel address space
  05/29/19 13:24:06  Failing address: 03dbe000 TEID: 03dbe403
  05/29/19 13:24:06  Fault in home space mode while using kernel ASCE.
  05/29/19 13:24:06  AS:00ea8007 R3:0024
  05/29/19 13:24:06  Oops: 003b ilc:3 ?#1? SMP
  05/29/19 13:24:06  Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_con
  05/29/19 13:24:06   ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 
sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod
  05/29/19 13:24:06  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 
4.15.0-50-generic #54-Ubuntu
  05/29/19 13:24:06  Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0)
  05/29/19 13:24:06  Krnl PSW : dcb002be 72762961 
(__tlb_remove_table+0x56/0xd0)
  05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 
PM:0 RI:0 EA:3
  05/29/19 13:24:06  Krnl GPRS: ffba 02b8 
02b80003 00eacac8
  05/29/19 13:24:06 ffba 00b9 
0700 000a
  05/29/19 13:24:06 0404c001 0007d2fb5c38 
0007cf71fdf0 03dbe000
  05/29/19 13:24:06 03dbe018 008fe740 
0007cf71fd08 0007cf71fcd8
  05/29/19 13:24:06  Krnl Code: 0012b956: ec2c002a027f   clij
%r2,2,12,12b9aa
  05/29/19 13:24:06 0012b95c: ec26001d037e   cij 
%r2,3,6,12b996
  05/29/19 13:24:06#0012b962: 41c0b018   la  
%r12,24(%r11)
  05/29/19 13:24:06>0012b966: e548b008   mvghi   
8(%r11),0
  05/29/19 13:24:06 0012b96c: a7390008   lghi
%r3,8
  05/29/19 13:24:06 0012b970: b904002b   lgr 
%r2,%r11
  05/29/19 13:24:06 0012b974: c0e5000e8f8a   brasl   
%r14,2fd888
  05/29/19 13:24:06 0012b97a: a718   lhi 
%r1,-1
  05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callba

[Kernel-packages] [Bug 1805631] Re: Freeze when usb-data-collision with usb-mouse

2019-08-28 Thread Patrik Nilsson

I haven't had a single crash with the v5.0 kernel although I really
tried. I mark this bug as invalid.

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

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Invalid

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

2019-08-28 Thread André

It's been over a year that I have this Dell XPS 13 9360. And this touchpad 
`DLL075B:01 06CB:76AF` with the same issue. I had this issue with both 
touchscreen enabled and disabled in the BIOS.
I'm currently on 18.04 and kernel 5.0.0-25-generic.
For my case this issue happens most often soon after unplugging the laptop from 
power supply. Usually closing the laptop lid and reopening helps to peace the 
issue slightly when coming back to suspend. Another thing that helps is nuking 
the touchpad specially right click. I wish modprobing would help too.
Also both scroll lock and mouse jumping around issues happens.

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

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Invalid
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

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

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

[Kernel-packages] [Bug 1841541] Re: trusty/linux-aws: 4.4.0-1052.56 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 14:01 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  trusty/linux-aws: 4.4.0-1052.56 -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 promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 14:01 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1841544] Re: xenial/linux: 4.4.0-161.189 -proposed tracker

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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
+ bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 12:31 UTC
+ phase: Testing
+ phase-changed: Wednesday, 28. August 2019 15:11 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

Title:
  xenial/linux: 4.4.0-161.189 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 28. August 2019 15:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1841541
trusty/linux-lts-xenial: bug 1841543
xenial/linux-aws: bug 1841533
xenial/linux-fips: bug 1841540
xenial/linux-kvm: bug 1841534
xenial/linux-raspi2: bug 1841536
xenial/linux-snapdragon: bug 1841539
xenial/linux/pc-kernel: bug 1841531
  variant: debs

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

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

[Kernel-packages] [Bug 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840826 (bionic/linux-oracle-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
-   promote-to-proposed: Stalled -- packages no longer available
+   promote-to-proposed: Stalled -- review FAILED
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -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:
  Incomplete
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 verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
promote-to-proposed: Stalled -- review FAILED
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

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

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

[Kernel-packages] [Bug 1841540] Re: xenial/linux-fips: 4.4.0-1019.24 -proposed tracker

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 13:46 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 28. August 2019 15:14 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
+   promote-signing-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1019.24 -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-signing-to-proposed series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 15:14 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1841533] Re: xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Proposed
- phase-changed: Wednesday, 28. August 2019 13:20 UTC
+ phase: Testing
+ phase-changed: Wednesday, 28. August 2019 15:12 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1092.103 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1841544
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 28. August 2019 15:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1841532
  variant: debs

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

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

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

2019-08-28 Thread Paul Menzel

@andre-miras, we do not experience the problem with Ubuntu 18.10(?) and
19.04 anymore. Please try to update, or test these releases. No idea,
what the cause and solution was in the end.

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

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Invalid
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

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

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

[Kernel-packages] [Bug 1841669] [NEW] SR-IOV interface goes down when testing network performance

2019-08-28 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Hello,

We are testing network performance with SR-IOV on ubuntu and security
onion in Rhev Hypervisor. We are using a SuperMicro box running T-rex
traffic generator on CentOS which is connected to a gigamon to push
traffic to the Ubuntu/Security Onion VMs.

The ubuntu 16.04 vm is running on a RHVH host node and is running SR-
IOV. We have ensured that SR-IOV is enabled in the BIOS. We are finding
that packets stop coming into the interface after a few seconds. This is
because the interface is going down after a few seconds of receiving
traffic. We are running promiscuous mode and it is required for our use
case of measuring network traffic.

As a troubleshooting measure, 5.3.0-rc3 was built using the 3.2.3 iavf
SR-IOV driver. Note that the i40evf driver was renamed to iavf, which is
why the name discrepancy exists. After updating the Kernel we stopped
seeing this issue.

Non-working default security onion kernel information
root@ubuntu:~# uname -r
3.10.0-957.21.3.el7.x86_64
root@ubuntu:~# ethtool -i ens7
driver: iavf
version: 3.0.1-k
firmware-version: N/A
expansion-rom-version:
bus-info: :00:07.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

Working modified security onion kernel information
root@ubuntu:~# uname -r
5.3.0-rc3-custom
root@ubuntu:~# ethtool -i ens7
driver: i40evf
version: 3.2.3-k
firmware-version: N/A
expansion-rom-version:
bus-info: :00:07.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

We were able to perform testing using the 5.3.0 kernel, but long term a
better solution is needed as this would require supporting a modified
Linux kernel with updates, testing, etc.

>From the hypervisor in /var/log/messages:

Aug 27 09:05:00 localhost libvirtd: 2019-08-27 13:05:00.522+: 10748: error 
:  qemuDomainAgentAvailable:9133 : Guest agent is not responding: 
QEMU guest agent  is not connected
Aug 27 09:05:07 localhost goferd: [ERROR][worker-0] 
gofer.messaging.adapter.conn ect:33 - connect: 
proton+amqps://subscription.rhsm.redhat.com:5647, failed: Conn 
ection amqps://subscription.rhsm.redhat.com:5647disconnected: Condition('amqp:r 
esource-limit-exceeded', 'local-idle-timeout expired')
Aug 27 09:05:07 localhost goferd: [INFO][worker-0] 
gofer.messaging.adapter.conne ct:35 - retry in 106 seconds
Aug 27 09:05:22 localhost kernel: i40e :b5:00.3: Unable to send the message 
 to VF 0 aq_err 12
Aug 27 09:05:22 localhost kernel: i40e :b5:00.3: Unable to send the message 
 to VF 0 aq_err 12

>From the VM, journalctl -xe gives:

-- The start-up result is done.
Aug 27 14:35:02 ubuntu kernel: i40evf :00:04.0: PF reset warning received
Aug 27 14:35:02 ubuntu kernel: i40evf :00:04.0: Scheduling reset task
Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
Aug 27 14:35:08 ubuntu systemd-logind[1251]: Removed session 16.
-- Subject: Session 16 has been terminated
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat

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


** Tags: bot-comment
-- 
SR-IOV interface goes down when testing network performance
https://bugs.launchpad.net/bugs/1841669
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 1841669] Re: SR-IOV interface goes down when testing network performance

2019-08-28 Thread Brian Murray

** Package changed: kernel-package (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/1841669

Title:
  SR-IOV interface goes down when testing network performance

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  We are testing network performance with SR-IOV on ubuntu and security
  onion in Rhev Hypervisor. We are using a SuperMicro box running T-rex
  traffic generator on CentOS which is connected to a gigamon to push
  traffic to the Ubuntu/Security Onion VMs.

  The ubuntu 16.04 vm is running on a RHVH host node and is running SR-
  IOV. We have ensured that SR-IOV is enabled in the BIOS. We are
  finding that packets stop coming into the interface after a few
  seconds. This is because the interface is going down after a few
  seconds of receiving traffic. We are running promiscuous mode and it
  is required for our use case of measuring network traffic.

  As a troubleshooting measure, 5.3.0-rc3 was built using the 3.2.3 iavf
  SR-IOV driver. Note that the i40evf driver was renamed to iavf, which
  is why the name discrepancy exists. After updating the Kernel we
  stopped seeing this issue.

  Non-working default security onion kernel information
  root@ubuntu:~# uname -r
  3.10.0-957.21.3.el7.x86_64
  root@ubuntu:~# ethtool -i ens7
  driver: iavf
  version: 3.0.1-k
  firmware-version: N/A
  expansion-rom-version:
  bus-info: :00:07.0
  supports-statistics: yes
  supports-test: no
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: yes

  Working modified security onion kernel information
  root@ubuntu:~# uname -r
  5.3.0-rc3-custom
  root@ubuntu:~# ethtool -i ens7
  driver: i40evf
  version: 3.2.3-k
  firmware-version: N/A
  expansion-rom-version:
  bus-info: :00:07.0
  supports-statistics: yes
  supports-test: no
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: yes

  We were able to perform testing using the 5.3.0 kernel, but long term
  a better solution is needed as this would require supporting a
  modified Linux kernel with updates, testing, etc.

  From the hypervisor in /var/log/messages:

  Aug 27 09:05:00 localhost libvirtd: 2019-08-27 13:05:00.522+: 10748: 
error :  qemuDomainAgentAvailable:9133 : Guest agent is not 
responding: QEMU guest agent  is not connected
  Aug 27 09:05:07 localhost goferd: [ERROR][worker-0] 
gofer.messaging.adapter.conn ect:33 - connect: 
proton+amqps://subscription.rhsm.redhat.com:5647, failed: Conn 
ection amqps://subscription.rhsm.redhat.com:5647disconnected: Condition('amqp:r 
esource-limit-exceeded', 'local-idle-timeout expired')
  Aug 27 09:05:07 localhost goferd: [INFO][worker-0] 
gofer.messaging.adapter.conne ct:35 - retry in 106 seconds
  Aug 27 09:05:22 localhost kernel: i40e :b5:00.3: Unable to send the 
message  to VF 0 aq_err 12
  Aug 27 09:05:22 localhost kernel: i40e :b5:00.3: Unable to send the 
message  to VF 0 aq_err 12

  From the VM, journalctl -xe gives:

  -- The start-up result is done.
  Aug 27 14:35:02 ubuntu kernel: i40evf :00:04.0: PF reset warning received
  Aug 27 14:35:02 ubuntu kernel: i40evf :00:04.0: Scheduling reset task
  Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
  Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
  Aug 27 14:35:03 ubuntu kernel: i40evf :00:04.0: Hardware reset detected
  Aug 27 14:35:08 ubuntu systemd-logind[1251]: Removed session 16.
  -- Subject: Session 16 has been terminated
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat

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

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

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