[Kernel-packages] [Bug 1865431] Re: bionic/linux-gcp: 5.0.0-1033.34 -proposed tracker

[Łukasz Zemczak]

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

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

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

Title:
  bionic/linux-gcp: 5.0.0-1033.34 -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-lrm 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Proposed
  phase-changed: Thursday, 05. March 2020 07:51 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

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

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

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

[Eugene Crosser]

Could the culprit be enabled "wake on LAN" functionality of e1000e, that
was not enabled in 5.3?

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

Title:
  suspend only works once on ThinkPad X1 Carbon gen 7

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
  once* after boot. On subsequent attempts, when the lid it closed,
  backlight and wifi are turned off, but system does not suspend.

  First successful suspend:
  [ 147.413295] PM: suspend entry (s2idle)
  [ 147.416601] Filesystems sync: 0.003 seconds
  [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 147.421210] OOM killer disabled.
  [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 147.527810] e1000e: EEE TX LPI TIMER: 0011
  [ 150.246317] ACPI: EC: interrupt blocked
  [ 881.134544] ACPI: EC: interrupt unblocked
  [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
  [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [ 888.016931] OOM killer enabled.
  [ 888.016932] Restarting tasks ... done.
  [ 888.060613] PM: suspend exit

  Second unsuccessful suspend:
  [ 907.584802] PM: suspend entry (s2idle)
  [ 907.589779] Filesystems sync: 0.004 seconds
  [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [ 907.593518] OOM killer disabled.
  [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) 
done.
  [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 908.024438] e1000e: EEE TX LPI TIMER: 0011
  [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
  [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
  [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2
  [ 911.183052] PM: Some devices failed to suspend, or early wake event detected
  [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 911.413624] OOM killer enabled.
  [ 911.413625] Restarting tasks ... done.
  [ 911.462021] PM: suspend exit

  It looks like Ethernet driver prevents suspend. Ethernet is not
  connected (I do not have the adaptor).

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

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

[Kernel-packages] [Bug 1866162] s390/pci: Fix unexpected write combine on resource

[bugproxy]

Default Comment by Bridge

** Attachment added: "s390/pci: Fix unexpected write combine on resource"
   
https://bugs.launchpad.net/bugs/1866162/+attachment/5333738/+files/0001-s390-pci-Fix-unexpected-write-combine-on-resource.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: 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/1866162

Title:
  [UBUNTU 20.04] ZPCI used write back addresses by default but should
  use write through

Status in linux package in Ubuntu:
  New

Bug description:
  In the initial MIO support introduced in

  commit 71ba41c9b1d9 ("s390/pci: provide support for MIO instructions")

  setting up the PCI BAR resources defaults to using the
  mio_wb address as the resource's start address. 

  This means users of the mapping, which includes most drivers, will get
  write combining on PCI Stores.

  his may lead to problems when drivers expect write through
  behavior when not using an explicit ioremap_wc() which is the default
  behavior on other platforms.

  The attached patch changes the default to write through.
  It has already been reviewed and is currently queued to be send for
  Linux 5.6-rc5 with a CC stable tag.

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

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

[Kernel-packages] [Bug 1866162] [NEW] [UBUNTU 20.04] ZPCI used write back addresses by default but should use write through

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In the initial MIO support introduced in

commit 71ba41c9b1d9 ("s390/pci: provide support for MIO instructions")

setting up the PCI BAR resources defaults to using the
mio_wb address as the resource's start address. 

This means users of the mapping, which includes most drivers, will get
write combining on PCI Stores.

his may lead to problems when drivers expect write through
behavior when not using an explicit ioremap_wc() which is the default
behavior on other platforms.

The attached patch changes the default to write through.
It has already been reviewed and is currently queued to be send for
Linux 5.6-rc5 with a CC stable tag.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-184193 severity-high 
targetmilestone-inin2004
-- 
[UBUNTU 20.04] ZPCI used write back addresses by default but should use write 
through
https://bugs.launchpad.net/bugs/1866162
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 1862313] Re: Support Headset Mic on HP cPC

[Anthony Wong]

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

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

Title:
  Support Headset Mic on HP cPC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-oem source package in Focal:
  Won't Fix
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  Two HP workstations can't detect headset microphone.

  [Fix]
  Apply vendor-specific coefficient to enable headset mic detection.

  [Test]
  Plug headset and see if the mic gets detected.
  Headset mic gets detected correctly after applying the patch.

  [Regression Potential]
  Low. The fix matches to very specific machines, so all other systems are 
unaffected.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

[Kernel-packages] [Bug 1863334] Re: trusty/linux-aws: 4.4.0-1063.67 -proposed tracker

[Ubuntu Kernel Bot]

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

** This bug has been marked a duplicate of bug 1865246
   trusty/linux-aws: 4.4.0-1064.68 -proposed tracker

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

Title:
  trusty/linux-aws: 4.4.0-1063.67 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 20. February 2020 18:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1866156] Re: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.

[Che Cheng]

** Tags added: originate-from-1805928

** Changed in: oem-priority
   Status: New => Triaged

** Changed in: oem-priority
   Importance: Undecided => Medium

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

[Kernel-packages] [Bug 1865246] Re: trusty/linux-aws: 4.4.0-1064.68 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 05. March 2020 05:32 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 07:21 UTC
  reason:
-   build-packages-ppa: Ongoing -- building in ppa main:building
- replaces: bug 1863334
+   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/1865246

Title:
  trusty/linux-aws: 4.4.0-1064.68 -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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 05. March 2020 07:21 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/1865246/+subscriptions

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

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

[Eugene Crosser]

5.6.0-050600rc4-generic
Same behaviour:

First time works:
[  122.113542] PM: suspend entry (s2idle)
[  122.118823] Filesystems sync: 0.005 seconds
[  122.120954] Freezing user space processes ... (elapsed 0.002 seconds) done.
[  122.12] OOM killer disabled.
[  122.123334] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  122.124606] printk: Suspending console(s) (use no_console_suspend to debug)
[  122.125072] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
[  122.230038] e1000e: EEE TX LPI TIMER: 0011
[  122.345108] ACPI: EC: interrupt blocked
[  138.117673] ACPI: EC: interrupt unblocked
[  140.917449] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[  141.031854] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[  141.096775] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[  143.796468] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
[  144.466557] e1000e :00:1f.6 enp0s31f6: Hardware Error
[  145.195597] OOM killer enabled.
[  145.195597] Restarting tasks ... done.
[  145.213016] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
[  145.239043] PM: suspend exit

Second time fails to suspend:
[  169.696561] PM: suspend entry (s2idle)
[  169.734111] Filesystems sync: 0.037 seconds
[  169.734688] Freezing user space processes ... (elapsed 0.002 seconds) done.
[  169.736790] OOM killer disabled.
[  169.736791] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  169.738032] printk: Suspending console(s) (use no_console_suspend to debug)
[  169.738318] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
[  169.839564] e1000e: EEE TX LPI TIMER: 0011
[  171.730682] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
[  171.730685] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -2
[  171.730687] PM: Device :00:1f.6 failed to suspend async: error -2
[  172.997917] PM: Some devices failed to suspend, or early wake event detected
[  173.010160] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[  173.126554] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[  173.193691] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[  173.222986] OOM killer enabled.
[  173.222987] Restarting tasks ... 
[  173.235209] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
[  173.235267] done.
[  173.266890] PM: suspend exit

Suspend works with eoan's 5.3.0-18-generic (same system, just booted
into the old kernel):

First time successful:
[   66.725822] PM: suspend entry (s2idle)
[   66.731748] Filesystems sync: 0.005 seconds
[   66.732769] Freezing user space processes ... (elapsed 0.002 seconds) done.
[   66.735102] OOM killer disabled.
[   66.735103] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[   66.736358] printk: Suspending console(s) (use no_console_suspend to debug)
[   66.737562] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
[   66.842558] pcieport :06:04.0: pciehp: pcie_do_write_cmd: no response 
from device
[   66.842582] pcieport :06:01.0: pciehp: pcie_do_write_cmd: no response 
from device
[   66.843126] e1000e: EEE TX LPI TIMER: 0011
[   81.464128] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[   81.582688] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[   81.650014] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[   82.278399] OOM killer enabled.
[   82.278399] Restarting tasks ... done.
[   82.329029] PM: suspend exit

Second time successful too:
[  110.896082] PM: suspend entry (s2idle)
[  110.903315] Filesystems sync: 0.007 seconds
[  110.904398] Freezing user space processes ... (elapsed 0.002 seconds) done.
[  110.906958] OOM killer disabled.
[  110.906958] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  110.908232] printk: Suspending console(s) (use no_console_suspend to debug)
[  110.909122] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
[  111.010349] pcieport :06:04.0: pciehp: pcie_do_write_cmd: no response 
from device
[  111.010410] pcieport :06:01.0: pciehp: pcie_do_write_cmd: no response 
from device
[  111.010499] e1000e: EEE TX LPI TIMER: 0011
[  137.062899] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[  137.180784] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[  137.248212] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[  137.880444] OOM killer enabled.
[  137.880444] Restarting tasks ... done.
[  137.927342] PM: suspend exit

-- 
You received this bug notification because you are a member of Kernel
Packages, 

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:52 UTC
  reason:
-   build-packages-ppa: Ongoing -- building in ppa main:building
+   build-packages-ppa: Ongoing -- building in ppa signed:depwait
  replaces: bug 1864744
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

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

Bug description:
  This bug 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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:52 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa signed:depwait
  replaces: bug 1864744
  variant: debs

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

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel

[Po-Hsu Lin]

Didn't see this issue with Eoan 5.3 on node rizzo

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

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  Test failed becuase:
 ./ip_defrag: sendto overlap: 1400: Operation not permitted

  
   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

[Kernel-packages] [Bug 1865199] Re: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865106
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:31 UTC
  reason:
-   build-packages-ppa: Ongoing -- building in ppa main:building
+   build-packages-ppa: Ongoing -- building in ppa meta:depwait
+ signed:depwait
  replaces: bug 1863331
  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/1865199

Title:
  xenial/linux-fips: 4.4.0-1031.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 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: 1865106
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:31 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa meta:depwait
  signed:depwait
  replaces: bug 1863331
  variant: debs

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

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

[Kernel-packages] [Bug 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan

[Po-Hsu Lin]

Passed with Xenial 4.4.0-176-generic

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

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  pty03 from pty in ubuntu_ltp failed on Eoan

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

Bug description:
  == Justification ==
  The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL
  pointer dereference:

  [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020
  [ 951.309960] #PF: supervisor write access in kernel mode
  [ 951.312130] #PF: error_code(0x0002) - not-present page
  [ 951.314227] PGD 0 P4D 0
  [ 951.315278] Oops: 0002 [#1] SMP PTI
  [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic 
#15-Ubuntu
  [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50

  [ 951.352494] Call Trace:
  [ 951.353244] slip_write_wakeup+0x25/0x30 [slip]
  [ 951.354600] tty_wakeup+0x5b/0x70
  [ 951.355539] pty_unthrottle+0x19/0x30
  [ 951.356560] tty_unthrottle+0x42/0x60
  [ 951.357566] __tty_perform_flush+0x87/0x90
  [ 951.358768] n_tty_ioctl_helper+0xcc/0x150
  [ 951.359955] n_tty_ioctl+0x2d/0x100
  [ 951.360930] tty_ioctl+0x3c0/0x8e0
  [ 951.361882] ? __switch_to_asm+0x34/0x70
  [ 951.363049] ? __switch_to_asm+0x40/0x70
  [ 951.364191] ? __switch_to_asm+0x34/0x70
  [ 951.365261] ? __switch_to_asm+0x40/0x70
  [ 951.366382] ? __switch_to_asm+0x34/0x70
  [ 951.367452] ? __switch_to_asm+0x40/0x70
  [ 951.368523] ? __switch_to_asm+0x34/0x70
  [ 951.369693] ? __switch_to_asm+0x40/0x70
  [ 951.370829] ? __switch_to_asm+0x34/0x70
  [ 951.371923] ? __switch_to_asm+0x40/0x70
  [ 951.372998] ? __switch_to_asm+0x34/0x70
  [ 951.374097] ? __switch_to_asm+0x40/0x70
  [ 951.375183] ? __switch_to_asm+0x34/0x70
  [ 951.376288] ? __switch_to_asm+0x40/0x70
  [ 951.377390] ? __switch_to+0x110/0x470
  [ 951.378863] do_vfs_ioctl+0x407/0x670
  [ 951.380269] ? __schedule+0x2eb/0x740
  [ 951.381761] ksys_ioctl+0x67/0x90
  [ 951.383076] __x64_sys_ioctl+0x1a/0x20
  [ 951.384510] do_syscall_64+0x57/0x190
  [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9

  == Fixes ==
  Indicated by the test case, this issue can be fixed by:
  * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and
  close with RCU)

  This patch can be cherry-picked into all of our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/

  Tested on KVM nodes and the patched kernels work as expected, there
  will be no more kernel null pointer dereference issue, and the test
  can finish properly.

  == Regression potential ==
  Low, changes limited to two specific drivers for serial line TTY. This
  issue can be reproduced quite easily and the patched kernels show
  positive results.


  == Original Bug Report ==
  startup='Thu Feb  6 02:45:23 2020'
   tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s
   pty03.c:101: INFO: Creating PTY with SLIP line discipline
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0

  This is a new test case, so it's not a regression.

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

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

[Kernel-packages] [Bug 1866156] RfKill.txt

[Che Cheng]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1866156/+attachment/5333711/+files/RfKill.txt

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1866156/+attachment/5333707/+files/ProcCpuinfoMinimal.txt

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

[Kernel-packages] [Bug 1866156] Re: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.

[Che Cheng]

apport information

** Tags added: apport-collected bionic

** Description changed:

  Dell laptops have an option for power management in the BIOS setting to
  control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected wireless
  radios (WLAN and/or WWAN). Upon disconnection from the wired network,
  the selected wireless radios will be re-enabled.
  
- When Dell docking station (the ethernet is Realtek r8153 USB
- controller), with runtime PM enabled, is the wired network, WLAN radio
- won't be re-enabled after unplugging ethernet cable. By checking rfkill,
- the radio is hard blocked. Disable runtime PM of the r8153 USB device
- can work around this issue.
+ When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.9
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  2160 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ 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-highsparrow+X32
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-01-10 (54 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
+ MachineType: Dell Inc. Latitude 9510
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
+  linux-backports-modules-5.0.0-1040-oem-osp1  N/A
+  linux-firmware   1.173.14
+ Tags:  bionic
+ Uname: Linux 5.0.0-1040-oem-osp1 x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/24/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 0.2.6
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 9510
+ dmi.product.sku: 0983
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

[Kernel-packages] [Bug 1866156] CRDA.txt

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1866156/+attachment/5333703/+files/IwConfig.txt

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

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

[Che Cheng]

apport information

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

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1866156/+subscriptions

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

[Kernel-packages] [Bug 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan

[Po-Hsu Lin]

Passed with Eoan 5.3.0-42.34
 pty03.c:127: PASS: Did not crash with GSM TTY discipline

 Summary:
 passed 9
 failed 0
 skipped 0
 warnings 0
 tag=pty03 stime=1583154902 dur=186 exit=exited stat=0 core=no cu=19624 cs=7948

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

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

Title:
  pty03 from pty in ubuntu_ltp failed on Eoan

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  == Justification ==
  The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL
  pointer dereference:

  [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020
  [ 951.309960] #PF: supervisor write access in kernel mode
  [ 951.312130] #PF: error_code(0x0002) - not-present page
  [ 951.314227] PGD 0 P4D 0
  [ 951.315278] Oops: 0002 [#1] SMP PTI
  [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic 
#15-Ubuntu
  [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50

  [ 951.352494] Call Trace:
  [ 951.353244] slip_write_wakeup+0x25/0x30 [slip]
  [ 951.354600] tty_wakeup+0x5b/0x70
  [ 951.355539] pty_unthrottle+0x19/0x30
  [ 951.356560] tty_unthrottle+0x42/0x60
  [ 951.357566] __tty_perform_flush+0x87/0x90
  [ 951.358768] n_tty_ioctl_helper+0xcc/0x150
  [ 951.359955] n_tty_ioctl+0x2d/0x100
  [ 951.360930] tty_ioctl+0x3c0/0x8e0
  [ 951.361882] ? __switch_to_asm+0x34/0x70
  [ 951.363049] ? __switch_to_asm+0x40/0x70
  [ 951.364191] ? __switch_to_asm+0x34/0x70
  [ 951.365261] ? __switch_to_asm+0x40/0x70
  [ 951.366382] ? __switch_to_asm+0x34/0x70
  [ 951.367452] ? __switch_to_asm+0x40/0x70
  [ 951.368523] ? __switch_to_asm+0x34/0x70
  [ 951.369693] ? __switch_to_asm+0x40/0x70
  [ 951.370829] ? __switch_to_asm+0x34/0x70
  [ 951.371923] ? __switch_to_asm+0x40/0x70
  [ 951.372998] ? __switch_to_asm+0x34/0x70
  [ 951.374097] ? __switch_to_asm+0x40/0x70
  [ 951.375183] ? __switch_to_asm+0x34/0x70
  [ 951.376288] ? __switch_to_asm+0x40/0x70
  [ 951.377390] ? __switch_to+0x110/0x470
  [ 951.378863] do_vfs_ioctl+0x407/0x670
  [ 951.380269] ? __schedule+0x2eb/0x740
  [ 951.381761] ksys_ioctl+0x67/0x90
  [ 951.383076] __x64_sys_ioctl+0x1a/0x20
  [ 951.384510] do_syscall_64+0x57/0x190
  [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9

  == Fixes ==
  Indicated by the test case, this issue can be fixed by:
  * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and
  close with RCU)

  This patch can be cherry-picked into all of our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/

  Tested on KVM nodes and the patched kernels work as expected, there
  will be no more kernel null pointer dereference issue, and the test
  can finish properly.

  == Regression potential ==
  Low, changes limited to two specific drivers for serial line TTY. This
  issue can be reproduced quite easily and the patched kernels show
  positive results.


  == Original Bug Report ==
  startup='Thu Feb  6 02:45:23 2020'
   tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s
   pty03.c:101: INFO: Creating PTY with SLIP line discipline
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Test timeouted, sending SIGKILL!
   Cannot kill test processes!
   Congratulation, likely test hit a kernel bug.
   Exitting uncleanly...
   tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0

  This is a new test case, so it's not a regression.

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

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

[Kernel-packages] [Bug 1866156] [NEW] Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.

[Che Cheng]

Public bug reported:

Dell laptops have an option for power management in the BIOS setting to
control WLAN radio. If enabled, it will sense the connection of the
system to a wired network and subsequently disable the selected wireless
radios (WLAN and/or WWAN). Upon disconnection from the wired network,
the selected wireless radios will be re-enabled.

When Dell docking station (the ethernet is Realtek r8153 USB controller), with 
runtime PM enabled, is the wired network, WLAN radio won't be re-enabled after 
unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  2160 F pulseaudio
CurrentDesktop: ubuntu:GNOME
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-highsparrow+X32
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-01-10 (54 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
MachineType: Dell Inc. Latitude 9510
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
 linux-backports-modules-5.0.0-1040-oem-osp1  N/A
 linux-firmware   1.173.14
Tags:  bionic
Uname: Linux 5.0.0-1040-oem-osp1 x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/24/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.6
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 9510
dmi.product.sku: 0983
dmi.sys.vendor: Dell Inc.

** Affects: oem-priority
 Importance: Undecided
 Assignee: Che Cheng (cktenn)
 Status: New

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


** Tags: apport-collected bionic ihv-realtek

** Attachment added: "Ubuntu 18.04 + Docking + WLAN Radio Issue.mp4"
   
https://bugs.launchpad.net/bugs/1866156/+attachment/5333692/+files/Ubuntu%2018.04%20+%20Docking%20+%20WLAN%20Radio%20Issue.mp4

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Che Cheng (cktenn)

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker

[Ubuntu Kernel Bot]

** 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-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   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: 1865109
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Packaging
- phase-changed: Thursday, 05. March 2020 06:12 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 06:51 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   build-packages-ppa: Ongoing -- building in ppa main:building
  trackers:
xenial/linux-oracle: bug 1865479
  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/1865480

Title:
  bionic/linux-oracle: 4.15.0-1035.38 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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 --
  kernel-stable-master-bug: 1865109
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 06:51 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  trackers:
xenial/linux-oracle: bug 1865479
  variant: debs

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

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

[Kernel-packages] [Bug 1865479] Re: xenial/linux-oracle: -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1865480
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Holding before Packaging
- phase-changed: Monday, 02. March 2020 12:44 UTC
+ phase: Ready for Packaging
+ phase-changed: Thursday, 05. March 2020 06:52 UTC
  reason:
-   prepare-package: Holding -- waiting for master bug
+   prepare-package: Pending -- version not specified
  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/1865479

Title:
  xenial/linux-oracle:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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 --
  kernel-stable-master-bug: 1865480
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Ready for Packaging
  phase-changed: Thursday, 05. March 2020 06:52 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1865190] Re: eoan/linux-azure: 5.3.0-1015.16 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-azure-5.3: bug 1865189
+   bionic/linux-azure-5.3: bug 1863273, bug 1865189
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1015.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 18:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1863273, bug 1865189
  variant: debs

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

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

[Kernel-packages] [Bug 1865106] Re: xenial/linux: 4.4.0-176.206 -proposed tracker

[Ubuntu Kernel Bot]

** 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: Testing
  phase-changed: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-aws: bug 1865246
+   trusty/linux-aws: bug 1863334, bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
-   xenial/linux-fips: bug 1865199
+   xenial/linux-fips: bug 1863331, bug 1865199
xenial/linux-kvm: bug 1865243
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  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/1865106

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: Friday, 28. February 2020 19:21 UTC
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1863334, bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331, bug 1865199
xenial/linux-kvm: bug 1865243
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
  variant: debs

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

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

[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 05. March 2020 03:59 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 06:41 UTC
  reason:
-   build-packages-ppa: Ongoing -- building in ppa lrm:depwait
- meta:depwait signed:depwait
+   promote-to-proposed: Pending -- ready for review
  replaces: bug 1864732
  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/1865419

Title:
  bionic/linux-aws-fips: 4.15.0-2012.12 -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-lrm 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 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 05. March 2020 06:41 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  replaces: bug 1864732
  variant: debs

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

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:52 UTC
  reason:
-   build-packages-ppa: Pending -- building in ppa main:building
- meta:queued
+   build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1864744
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

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

Bug description:
  This bug 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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:52 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1864744
  variant: debs

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

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

[Kernel-packages] [Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865109
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Ready for Packaging
- phase-changed: Monday, 02. March 2020 12:45 UTC
+ phase: Packaging
+ phase-changed: Thursday, 05. March 2020 06:12 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux-oracle: bug 1865479
  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/1865480

Title:
  bionic/linux-oracle: 4.15.0-1035.38 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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 --
  kernel-stable-master-bug: 1865109
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Packaging
  phase-changed: Thursday, 05. March 2020 06:12 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux-oracle: bug 1865479
  variant: debs

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

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

[Kernel-packages] [Bug 1864188] Re: After the upgrade of 19.10 on 2020-02-18, wifi does not exist

[Jeremie Lemieux]

Affected user here

Lenovo Ideapad S 530.

NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"

Solving the problem temporarily by booting under
5.3.0-28-generic, 

Until 5.3.0-40 will have a patch released.

Let me know if I can provide logs to help with the process, or if there
is a better fix available.

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

Title:
  After the upgrade of 19.10 on 2020-02-18, wifi does not exist

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsmod shows the the modules are on, but no wifi hardware seems available.
  That happened just after the kernel update I did on 18th of Feb. 2020, on 
Ubuntu 19.10. No other change.
  System is Dell Vostro 5490/i7 .

  mgrivas@Vostro:~$ lsmod | grep iwl
  iwlmvm401408  0
  mac80211  851968  1 iwlmvm
  iwlwifi   348160  1 iwlmvm
  cfg80211  712704  3 iwlmvm,iwlwifi,mac80211

  mgrivas@Vostro:~$ iwconfig 
  no wireless extensions.
  - The wlan device does not appear.

  mgrivas@Vostro:~$ lspci | grep -i net
  00:14.3 Network controller: Intel Corporation Device 02f0
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

  mgrivas@Vostro:~$ cat /proc//version_signature 
  Ubuntu 5.3.0-40.32-generic 5.3.18

  mgrivas@Vostro:~$ lspci -vnvns 00:14.3
  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
Subsystem: Intel Corporation Device [8086:42a4]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mgrivas3042 F pulseaudio
   /dev/snd/controlC0:  mgrivas3042 F pulseaudio
   /dev/snd/controlC2:  mgrivas3042 F pulseaudio
  Date: Fri Feb 21 11:36:58 2020
  InstallationDate: Installed on 2019-12-23 (60 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Vostro 5490
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=UUID=5107e080-d818-4651-b256-cbd6c7047a2f ro
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0YR1P7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0YR1P7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5490
  dmi.product.sku: 0959
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker

[Khaled El Mously]

** Summary changed:

- bionic/linux-oracle:  -proposed tracker
+ bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  bionic/linux-oracle: 4.15.0-1035.38 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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 --
  kernel-stable-master-bug: 1865109
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Packaging
  phase-changed: Thursday, 05. March 2020 06:12 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
xenial/linux-oracle: bug 1865479
  variant: debs

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

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

[Kernel-packages] [Bug 1865110] Re: disco/linux: 5.0.0-43.47 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-5.0: bug 1865434, bug 1863281
+   bionic/linux-aws-5.0: bug 1865434
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
-   bionic/linux-gcp: bug 1865431, bug 1863289
+   bionic/linux-gcp: bug 1865431
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
-   bionic/linux-oracle-5.0: bug 1863296, bug 1865422
+   bionic/linux-oracle-5.0: bug 1865422
  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/1865110

Title:
  disco/linux: 5.0.0-43.47 -proposed tracker

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1865434
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1865431
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
bionic/linux-oracle-5.0: bug 1865422
  variant: debs

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

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Packaging
- phase-changed: Wednesday, 04. March 2020 03:51 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 05:52 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   build-packages-ppa: Pending -- building in ppa main:building
+ meta:queued
  replaces: bug 1864744
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

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

Bug description:
  This bug 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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:52 UTC
  reason:
build-packages-ppa: Pending -- building in ppa main:building
  meta:queued
  replaces: bug 1864744
  variant: debs

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

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

[Kernel-packages] [Bug 1864744] Re: trusty/linux-azure: 4.15.0-1073.78~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1864745
+ kernel-stable-master-bug: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 27. February 2020 21:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Stalled -- waiting for signoff
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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1864744

Title:
  trusty/linux-azure: 4.15.0-1073.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed 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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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: 1865198
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 27. February 2020 21:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1866149] [NEW] CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl

[David Monro]

Public bug reported:

I'm not completely sure which package to log this against.

I'm running the kvm focal minimal cloud image from 20200302. I noticed
on boot that there was an error complaining that systemd-systemctl
couldn't update pid_max to the value it wanted:

systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max':
Invalid argument

Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf:
# Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default
# of 2^16), to make PID collisions less likely.
kernel.pid_max = 4194304

However, the linux-image-kvm kernel is compiled with
CONFIG_BASE_SMALL=1

and this triggers the following code in include/linux/threads.h

#define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \
(sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT))

which means that if CONFIG_BASE_SMALL is set we get a maximum limit of
PAGE_SIZE * 8, which on x86 would be 32768.

As a workaround I can override it with a file in /etc/sysctl.d/ but this
shouldn't be needed.

I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud
images, they really aren't small machines in the scheme of things!

Cheers

David

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

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

Title:
  CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd
  default sysctl

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  I'm not completely sure which package to log this against.

  I'm running the kvm focal minimal cloud image from 20200302. I noticed
  on boot that there was an error complaining that systemd-systemctl
  couldn't update pid_max to the value it wanted:

  systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max':
  Invalid argument

  Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf:
  # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel 
default
  # of 2^16), to make PID collisions less likely.
  kernel.pid_max = 4194304

  However, the linux-image-kvm kernel is compiled with
  CONFIG_BASE_SMALL=1

  and this triggers the following code in include/linux/threads.h

  #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \
(sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT))

  which means that if CONFIG_BASE_SMALL is set we get a maximum limit of
  PAGE_SIZE * 8, which on x86 would be 32768.

  As a workaround I can override it with a file in /etc/sysctl.d/ but
  this shouldn't be needed.

  I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud
  images, they really aren't small machines in the scheme of things!

  Cheers

  David

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

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

[Kernel-packages] [Bug 1865246] Re: trusty/linux-aws: 4.4.0-1064.68 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Packaging
- phase-changed: Tuesday, 03. March 2020 18:01 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 05:32 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1863334
  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/1865246

Title:
  trusty/linux-aws: 4.4.0-1064.68 -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:
  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-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 --
  kernel-stable-master-bug: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:32 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1863334
  variant: debs

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

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

[Kernel-packages] [Bug 1865199] Re: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   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: 1865106
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Packaging
- phase-changed: Tuesday, 03. March 2020 02:46 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 05:31 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1863331
  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/1865199

Title:
  xenial/linux-fips: 4.4.0-1031.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 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: 1865106
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 05:31 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1863331
  variant: debs

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

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

[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 03:59 UTC
  reason:
-   build-packages-ppa: Ongoing -- building in ppa main:building
+   build-packages-ppa: Ongoing -- building in ppa lrm:depwait
+ meta:depwait signed:depwait
  replaces: bug 1864732
  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/1865419

Title:
  bionic/linux-aws-fips: 4.15.0-2012.12 -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-lrm 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 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 03:59 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa lrm:depwait
  meta:depwait signed:depwait
  replaces: bug 1864732
  variant: debs

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

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

[Kernel-packages] [Bug 1863334] Re: trusty/linux-aws: 4.4.0-1063.67 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1863338
+ kernel-stable-master-bug: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 20. February 2020 18:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1863334

Title:
  trusty/linux-aws: 4.4.0-1063.67 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1865106
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 20. February 2020 18:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1863331] Re: xenial/linux-fips: 4.4.0-1030.35 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1863338
+ kernel-stable-master-bug: 1865106
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1863331

Title:
  xenial/linux-fips: 4.4.0-1030.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed 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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1865106
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Testing
  phase-changed: Thursday, 20. February 2020 17:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1864897] Re: booting 5.3.0-40 with encrypted disk fails

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc4/

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

Title:
  booting 5.3.0-40 with encrypted disk fails

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up
  in a blank screen. Selecting 5.3.0-29 in the grub menu instead works,
  i. e., "please unlock disk" is displayed and after doing so xubuntu
  19.10 is started. The installation is encrypted as provided by the
  installer. Is some different but might be related to bug #1863759.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Wed Feb 26 18:11:45 2020
  InstallationDate: Installed on 2019-10-17 (131 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-02-24 17:34:11.828555
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   None
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1309 F pulseaudio
   /dev/snd/controlC0:  al 1309 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-17 (137 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc4/

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

Title:
  suspend only works once on ThinkPad X1 Carbon gen 7

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
  once* after boot. On subsequent attempts, when the lid it closed,
  backlight and wifi are turned off, but system does not suspend.

  First successful suspend:
  [ 147.413295] PM: suspend entry (s2idle)
  [ 147.416601] Filesystems sync: 0.003 seconds
  [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 147.421210] OOM killer disabled.
  [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 147.527810] e1000e: EEE TX LPI TIMER: 0011
  [ 150.246317] ACPI: EC: interrupt blocked
  [ 881.134544] ACPI: EC: interrupt unblocked
  [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
  [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error
  [ 888.016931] OOM killer enabled.
  [ 888.016932] Restarting tasks ... done.
  [ 888.060613] PM: suspend exit

  Second unsuccessful suspend:
  [ 907.584802] PM: suspend entry (s2idle)
  [ 907.589779] Filesystems sync: 0.004 seconds
  [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [ 907.593518] OOM killer disabled.
  [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) 
done.
  [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 908.024438] e1000e: EEE TX LPI TIMER: 0011
  [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] 
returns -2
  [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
  [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2
  [ 911.183052] PM: Some devices failed to suspend, or early wake event detected
  [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring
  [ 911.413624] OOM killer enabled.
  [ 911.413625] Restarting tasks ... done.
  [ 911.462021] PM: suspend exit

  It looks like Ethernet driver prevents suspend. Ethernet is not
  connected (I do not have the adaptor).

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

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

[Kernel-packages] [Bug 1865022] Re: focal/linux-gcp: 5.4.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => 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: 1865025
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. March 2020 06:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1865022

Title:
  focal/linux-gcp: 5.4.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Focal:
  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: 1865025
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. March 2020 06:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1866147] Re: WiFi card fails to activate on 5.3.0-40-generic

[AceLan Kao]

Here is the test kernel which should fix this issue
http://people.canonical.com/~acelan/bugs/lp1865829

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

Title:
  WiFi card fails to activate on 5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My WiFi card works fine with kernel 5.3.0-18-generic, but when I try
  to use 5.3.0-40-generic it fails to activate (and doesn't show up in
  `ip link`). `dmesg | grep iwlwifi` shows the following debug
  information:

  [   12.292292] iwlwifi :00:14.3: enabling device ( -> 0002)
  [   12.346746] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.347045] iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.502729] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x354
  [   13.518078] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [   13.518162] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [   13.518165] iwlwifi :00:14.3: Status: 0x, count: -871717974
  [   13.518167] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [   13.518169] iwlwifi :00:14.3: 0xABD222C6 | ADVANCED_SYSASSERT
  [   13.518170] iwlwifi :00:14.3: 0xA43D5A29 | trm_hw_status0
  [   13.518172] iwlwifi :00:14.3: 0x6642BD97 | trm_hw_status1
  [   13.518173] iwlwifi :00:14.3: 0x8FE44EA9 | branchlink2
  [   13.518174] iwlwifi :00:14.3: 0x1C54C232 | interruptlink1
  [   13.518176] iwlwifi :00:14.3: 0xA7D409CD | interruptlink2
  [   13.518177] iwlwifi :00:14.3: 0x8A0C7875 | data1
  [   13.518178] iwlwifi :00:14.3: 0x99E03556 | data2
  [   13.518179] iwlwifi :00:14.3: 0x137C675B | data3
  [   13.518181] iwlwifi :00:14.3: 0xAB1BDD6D | beacon time
  [   13.518182] iwlwifi :00:14.3: 0x5608950B | tsf low
  [   13.518183] iwlwifi :00:14.3: 0x821A4BFA | tsf hi
  [   13.518185] iwlwifi :00:14.3: 0xD3F9F35B | time gp1
  [   13.518186] iwlwifi :00:14.3: 0xF0044C16 | time gp2
  [   13.518187] iwlwifi :00:14.3: 0xD50101E2 | uCode revision type
  [   13.518188] iwlwifi :00:14.3: 0x91B27A5E | uCode version major
  [   13.518190] iwlwifi :00:14.3: 0x5487A879 | uCode version minor
  [   13.518191] iwlwifi :00:14.3: 0x21B8EEAC | hw version
  [   13.518192] iwlwifi :00:14.3: 0x359EC8C9 | board version
  [   13.518193] iwlwifi :00:14.3: 0xE3137EBB | hcmd
  [   13.518195] iwlwifi :00:14.3: 0x09BBC532 | isr0
  [   13.518196] iwlwifi :00:14.3: 0x2716EDB8 | isr1
  [   13.518197] iwlwifi :00:14.3: 0x6C0451A5 | isr2
  [   13.518198] iwlwifi :00:14.3: 0x721A5CD0 | isr3
  [   13.518200] iwlwifi :00:14.3: 0x49ADC2D3 | isr4
  [   13.518201] iwlwifi :00:14.3: 0x183C47FC | last cmd Id
  [   13.518202] iwlwifi :00:14.3: 0x57F5E136 | wait_event
  [   13.518203] iwlwifi :00:14.3: 0x136FEC9F | l2p_control
  [   13.518205] iwlwifi :00:14.3: 0xD0DC1B77 | l2p_duration
  [   13.518206] iwlwifi :00:14.3: 0x2CD5FAD6 | l2p_mhvalid
  [   13.518207] iwlwifi :00:14.3: 0x36FBF34E | l2p_addr_match
  [   13.518209] iwlwifi :00:14.3: 0x76814124 | lmpm_pmg_sel
  [   13.518210] iwlwifi :00:14.3: 0x7350416A | timestamp
  [   13.518211] iwlwifi :00:14.3: 0x905B98D6 | flow_handler
  [   13.518244] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [   13.518246] iwlwifi :00:14.3: Status: 0x, count: 7
  [   13.518247] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
  [   13.518248] iwlwifi :00:14.3: 0x | umac branchlink1
  [   13.518250] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2
  [   13.518251] iwlwifi :00:14.3: 0x | umac interruptlink1
  [   13.518252] iwlwifi :00:14.3: 0x | umac interruptlink2
  [   13.518254] iwlwifi :00:14.3: 0x0003 | umac data1
  [   13.518255] iwlwifi :00:14.3: 0x2302 | umac data2
  [   13.518256] iwlwifi :00:14.3: 0x01300202 | umac data3
  [   13.518257] iwlwifi :00:14.3: 0x0030 | umac major
  [   13.518258] iwlwifi :00:14.3: 0x4FA0041F | umac minor
  [   13.518260] iwlwifi :00:14.3: 0x5CAB | frame pointer
  [   13.518261] iwlwifi :00:14.3: 0xC0887F58 | stack pointer
  [   13.518263] iwlwifi :00:14.3: 0x | last host cmd
  [   13.518264] iwlwifi :00:14.3: 0x | isr status reg
  [   13.518280] iwlwifi :00:14.3: Fseq Registers:
  [   13.518283] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE
  [   13.518286] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   13.518288] iwlwifi :00:14.3: 0xD787F0D4 | FSEQ_CNVIO_INIT_VERSION
  [   13.518291] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   13.518294] iwlwifi :00:14.3: 0x8E6A94AA | FSEQ_TOP_CONTENT_VERSION
  [   13.518297] iwlwifi :00:14.3: 0xC24B2F1A | FSEQ_ALIVE_TOKEN
  [   13.518300] iwlwifi :00:14.3: 

[Kernel-packages] [Bug 1865021] Re: focal/linux-azure: 5.4.0-1005.5 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => 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: 1865025
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 29. February 2020 02:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

Title:
  focal/linux-azure: 5.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Focal:
  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: 1865025
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 29. February 2020 02:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  WiFi card fails to activate on 5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My WiFi card works fine with kernel 5.3.0-18-generic, but when I try
  to use 5.3.0-40-generic it fails to activate (and doesn't show up in
  `ip link`). `dmesg | grep iwlwifi` shows the following debug
  information:

  [   12.292292] iwlwifi :00:14.3: enabling device ( -> 0002)
  [   12.346746] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.347045] iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.502729] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x354
  [   13.518078] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [   13.518162] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [   13.518165] iwlwifi :00:14.3: Status: 0x, count: -871717974
  [   13.518167] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [   13.518169] iwlwifi :00:14.3: 0xABD222C6 | ADVANCED_SYSASSERT
  [   13.518170] iwlwifi :00:14.3: 0xA43D5A29 | trm_hw_status0
  [   13.518172] iwlwifi :00:14.3: 0x6642BD97 | trm_hw_status1
  [   13.518173] iwlwifi :00:14.3: 0x8FE44EA9 | branchlink2
  [   13.518174] iwlwifi :00:14.3: 0x1C54C232 | interruptlink1
  [   13.518176] iwlwifi :00:14.3: 0xA7D409CD | interruptlink2
  [   13.518177] iwlwifi :00:14.3: 0x8A0C7875 | data1
  [   13.518178] iwlwifi :00:14.3: 0x99E03556 | data2
  [   13.518179] iwlwifi :00:14.3: 0x137C675B | data3
  [   13.518181] iwlwifi :00:14.3: 0xAB1BDD6D | beacon time
  [   13.518182] iwlwifi :00:14.3: 0x5608950B | tsf low
  [   13.518183] iwlwifi :00:14.3: 0x821A4BFA | tsf hi
  [   13.518185] iwlwifi :00:14.3: 0xD3F9F35B | time gp1
  [   13.518186] iwlwifi :00:14.3: 0xF0044C16 | time gp2
  [   13.518187] iwlwifi :00:14.3: 0xD50101E2 | uCode revision type
  [   13.518188] iwlwifi :00:14.3: 0x91B27A5E | uCode version major
  [   13.518190] iwlwifi :00:14.3: 0x5487A879 | uCode version minor
  [   13.518191] iwlwifi :00:14.3: 0x21B8EEAC | hw version
  [   13.518192] iwlwifi :00:14.3: 0x359EC8C9 | board version
  [   13.518193] iwlwifi :00:14.3: 0xE3137EBB | hcmd
  [   13.518195] iwlwifi :00:14.3: 0x09BBC532 | isr0
  [   13.518196] iwlwifi :00:14.3: 0x2716EDB8 | isr1
  [   13.518197] iwlwifi :00:14.3: 0x6C0451A5 | isr2
  [   13.518198] iwlwifi :00:14.3: 0x721A5CD0 | isr3
  [   13.518200] iwlwifi :00:14.3: 0x49ADC2D3 | isr4
  [   13.518201] iwlwifi :00:14.3: 0x183C47FC | last cmd Id
  [   13.518202] iwlwifi :00:14.3: 0x57F5E136 | wait_event
  [   13.518203] iwlwifi :00:14.3: 0x136FEC9F | l2p_control
  [   13.518205] iwlwifi :00:14.3: 0xD0DC1B77 | l2p_duration
  [   13.518206] iwlwifi :00:14.3: 0x2CD5FAD6 | l2p_mhvalid
  [   13.518207] iwlwifi :00:14.3: 0x36FBF34E | l2p_addr_match
  [   13.518209] iwlwifi :00:14.3: 0x76814124 | lmpm_pmg_sel
  [   13.518210] iwlwifi :00:14.3: 0x7350416A | timestamp
  [   13.518211] iwlwifi :00:14.3: 0x905B98D6 | flow_handler
  [   13.518244] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [   13.518246] iwlwifi :00:14.3: Status: 0x, count: 7
  [   13.518247] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
  [   13.518248] iwlwifi :00:14.3: 0x | umac branchlink1
  [   13.518250] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2
  [   13.518251] iwlwifi :00:14.3: 0x | umac interruptlink1
  [   13.518252] iwlwifi :00:14.3: 0x | umac interruptlink2
  [   13.518254] iwlwifi :00:14.3: 0x0003 | umac data1
  [   13.518255] iwlwifi :00:14.3: 0x2302 | umac data2
  [   13.518256] iwlwifi :00:14.3: 0x01300202 | umac data3
  [   13.518257] iwlwifi :00:14.3: 0x0030 | umac major
  [   13.518258] iwlwifi :00:14.3: 0x4FA0041F | umac minor
  [   13.518260] iwlwifi :00:14.3: 0x5CAB | frame pointer
  [   13.518261] iwlwifi :00:14.3: 0xC0887F58 | stack pointer
  [   13.518263] iwlwifi :00:14.3: 0x | last host cmd
  [   13.518264] iwlwifi :00:14.3: 0x | isr status reg
  [   13.518280] iwlwifi :00:14.3: Fseq Registers:
  [   13.518283] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE
  [   13.518286] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   13.518288] iwlwifi :00:14.3: 0xD787F0D4 | FSEQ_CNVIO_INIT_VERSION
  [   13.518291] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   13.518294] iwlwifi :00:14.3: 0x8E6A94AA | FSEQ_TOP_CONTENT_VERSION
  [   13.518297] iwlwifi :00:14.3: 0xC24B2F1A | FSEQ_ALIVE_TOKEN
  [   13.518300] iwlwifi :00:14.3: 0x3DA36A92 | 

[Kernel-packages] [Bug 1866147] [NEW] WiFi card fails to activate on 5.3.0-40-generic

[Emanuel Evans]

Public bug reported:

My WiFi card works fine with kernel 5.3.0-18-generic, but when I try to
use 5.3.0-40-generic it fails to activate (and doesn't show up in `ip
link`). `dmesg | grep iwlwifi` shows the following debug information:

[   12.292292] iwlwifi :00:14.3: enabling device ( -> 0002)
[   12.346746] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
[   12.347045] iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
[   12.502729] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, 
REV=0x354
[   13.518078] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
[   13.518162] iwlwifi :00:14.3: Start IWL Error Log Dump:
[   13.518165] iwlwifi :00:14.3: Status: 0x, count: -871717974
[   13.518167] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
[   13.518169] iwlwifi :00:14.3: 0xABD222C6 | ADVANCED_SYSASSERT
[   13.518170] iwlwifi :00:14.3: 0xA43D5A29 | trm_hw_status0
[   13.518172] iwlwifi :00:14.3: 0x6642BD97 | trm_hw_status1
[   13.518173] iwlwifi :00:14.3: 0x8FE44EA9 | branchlink2
[   13.518174] iwlwifi :00:14.3: 0x1C54C232 | interruptlink1
[   13.518176] iwlwifi :00:14.3: 0xA7D409CD | interruptlink2
[   13.518177] iwlwifi :00:14.3: 0x8A0C7875 | data1
[   13.518178] iwlwifi :00:14.3: 0x99E03556 | data2
[   13.518179] iwlwifi :00:14.3: 0x137C675B | data3
[   13.518181] iwlwifi :00:14.3: 0xAB1BDD6D | beacon time
[   13.518182] iwlwifi :00:14.3: 0x5608950B | tsf low
[   13.518183] iwlwifi :00:14.3: 0x821A4BFA | tsf hi
[   13.518185] iwlwifi :00:14.3: 0xD3F9F35B | time gp1
[   13.518186] iwlwifi :00:14.3: 0xF0044C16 | time gp2
[   13.518187] iwlwifi :00:14.3: 0xD50101E2 | uCode revision type
[   13.518188] iwlwifi :00:14.3: 0x91B27A5E | uCode version major
[   13.518190] iwlwifi :00:14.3: 0x5487A879 | uCode version minor
[   13.518191] iwlwifi :00:14.3: 0x21B8EEAC | hw version
[   13.518192] iwlwifi :00:14.3: 0x359EC8C9 | board version
[   13.518193] iwlwifi :00:14.3: 0xE3137EBB | hcmd
[   13.518195] iwlwifi :00:14.3: 0x09BBC532 | isr0
[   13.518196] iwlwifi :00:14.3: 0x2716EDB8 | isr1
[   13.518197] iwlwifi :00:14.3: 0x6C0451A5 | isr2
[   13.518198] iwlwifi :00:14.3: 0x721A5CD0 | isr3
[   13.518200] iwlwifi :00:14.3: 0x49ADC2D3 | isr4
[   13.518201] iwlwifi :00:14.3: 0x183C47FC | last cmd Id
[   13.518202] iwlwifi :00:14.3: 0x57F5E136 | wait_event
[   13.518203] iwlwifi :00:14.3: 0x136FEC9F | l2p_control
[   13.518205] iwlwifi :00:14.3: 0xD0DC1B77 | l2p_duration
[   13.518206] iwlwifi :00:14.3: 0x2CD5FAD6 | l2p_mhvalid
[   13.518207] iwlwifi :00:14.3: 0x36FBF34E | l2p_addr_match
[   13.518209] iwlwifi :00:14.3: 0x76814124 | lmpm_pmg_sel
[   13.518210] iwlwifi :00:14.3: 0x7350416A | timestamp
[   13.518211] iwlwifi :00:14.3: 0x905B98D6 | flow_handler
[   13.518244] iwlwifi :00:14.3: Start IWL Error Log Dump:
[   13.518246] iwlwifi :00:14.3: Status: 0x, count: 7
[   13.518247] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
[   13.518248] iwlwifi :00:14.3: 0x | umac branchlink1
[   13.518250] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2
[   13.518251] iwlwifi :00:14.3: 0x | umac interruptlink1
[   13.518252] iwlwifi :00:14.3: 0x | umac interruptlink2
[   13.518254] iwlwifi :00:14.3: 0x0003 | umac data1
[   13.518255] iwlwifi :00:14.3: 0x2302 | umac data2
[   13.518256] iwlwifi :00:14.3: 0x01300202 | umac data3
[   13.518257] iwlwifi :00:14.3: 0x0030 | umac major
[   13.518258] iwlwifi :00:14.3: 0x4FA0041F | umac minor
[   13.518260] iwlwifi :00:14.3: 0x5CAB | frame pointer
[   13.518261] iwlwifi :00:14.3: 0xC0887F58 | stack pointer
[   13.518263] iwlwifi :00:14.3: 0x | last host cmd
[   13.518264] iwlwifi :00:14.3: 0x | isr status reg
[   13.518280] iwlwifi :00:14.3: Fseq Registers:
[   13.518283] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE
[   13.518286] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[   13.518288] iwlwifi :00:14.3: 0xD787F0D4 | FSEQ_CNVIO_INIT_VERSION
[   13.518291] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[   13.518294] iwlwifi :00:14.3: 0x8E6A94AA | FSEQ_TOP_CONTENT_VERSION
[   13.518297] iwlwifi :00:14.3: 0xC24B2F1A | FSEQ_ALIVE_TOKEN
[   13.518300] iwlwifi :00:14.3: 0x3DA36A92 | FSEQ_CNVI_ID
[   13.518303] iwlwifi :00:14.3: 0xF19AF84B | FSEQ_CNVR_ID
[   13.518306] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP
[   13.518311] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
[   13.518316] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   13.518351] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   13.518385] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c1d, CPU2 Status: 
0x3
[   13.518386] iwlwifi 

[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-fips: bug 1864732, bug 1865419
+   bionic/linux-aws-fips: bug 1865419, bug 1864732
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  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/1865269

Title:
  bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1865419, bug 1864732
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

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

[Kernel-packages] [Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1865480, bug 1863339
+   bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

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

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

[Kernel-packages] [Bug 1858254] Re: thermald: [ERR]THD engine start failed

[Launchpad Bug Tracker]

[Expired for thermald (Ubuntu) because there has been no activity for 60
days.]

** Changed in: thermald (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  thermald: [ERR]THD engine start failed

Status in thermald package in Ubuntu:
  Expired

Bug description:
  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.

  Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
  Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

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

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

[Kernel-packages] [Bug 1863289] Re: bionic/linux-gcp: 5.0.0-1032.33 -proposed tracker

[Ubuntu Kernel Bot]

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

** This bug has been marked a duplicate of bug 1865431
   bionic/linux-gcp: 5.0.0-1033.34 -proposed tracker

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

Title:
  bionic/linux-gcp: 5.0.0-1032.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 19. February 2020 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1863287
  variant: debs

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

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

[Kernel-packages] [Bug 1865431] Re: bionic/linux-gcp: 5.0.0-1033.34 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 05. March 2020 03:42 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 03:58 UTC
  reason:
-   build-packages-ppa: Ongoing -- building in ppa lrm:building
- replaces: bug 1863289
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1033.34 -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-lrm 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 05. March 2020 03:58 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

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

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

[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker

[Ubuntu Kernel Bot]

** 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-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Packaging
- phase-changed: Wednesday, 04. March 2020 22:46 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 03:59 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1864732
  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/1865419

Title:
  bionic/linux-aws-fips: 4.15.0-2012.12 -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-lrm 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 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 03:59 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  replaces: bug 1864732
  variant: debs

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

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

[Kernel-packages] [Bug 1865431] Re: bionic/linux-gcp: 5.0.0-1033.34 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-lrm
   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: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Packaging
- phase-changed: Monday, 02. March 2020 20:06 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 05. March 2020 03:42 UTC
  reason:
-   prepare-package-lrm: Pending -- package not yet uploaded
+   build-packages-ppa: Ongoing -- building in ppa lrm:building
  replaces: bug 1863289
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1033.34 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1865110
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 05. March 2020 03:42 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa lrm:building
  replaces: bug 1863289
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
  variant: debs

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

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

[Kernel-packages] [Bug 1856163] Re: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR

[Po-Hsu Lin]

The test didn't manage to pass with the second attempt (run #11).

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

Title:
  test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR

Status in ubuntu-kernel-tests:
  Triaged
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  This issue can be reproduced with 5.3.0-24, so this is not a
  regression in this cycle.

  Reproduce rate: 3/3

  On the s390x LPAR (s2lp4), the test_maps test from ubuntu_bpf will
  cause OOM and the following tests will be aborted.

  [  591.755446] test_maps invoked oom-killer: 
gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
  [  591.755451] CPU: 1 PID: 19054 Comm: test_maps Tainted: PW  O  
5.3.0-25-generic #27-Ubuntu
  [  591.755452] Hardware name: IBM 2964 N63 400 (LPAR)
  [  591.755453] Call Trace:
  [  591.755460] ([<00023d11b98e>] show_stack+0x8e/0xd0)
  [  591.755464]  [<00023d995f6a>] dump_stack+0x8a/0xb8
  [  591.755469]  [<00023d30e082>] dump_header+0x62/0x250
  [  591.755470]  [<00023d30d152>] oom_kill_process+0x172/0x178
  [  591.755472]  [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0
  [  591.755473]  [<00023d30df1e>] out_of_memory+0x6e/0xf8
  [  591.755477]  [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0
  [  591.755478]  [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318
  [  591.755481]  [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8
  [  591.755482]  [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268
  [  591.755483]  [<00023d372daa>] read_swap_cache_async+0x2a/0x60
  [  591.755485]  [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8
  [  591.755486]  [<00023d3734f8>] swapin_readahead+0x2d0/0x408
  [  591.755488]  [<00023d34a14c>] do_swap_page+0x1f4/0x880
  [  591.755489]  [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910
  [  591.755491]  [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0
  [  591.755492]  [<00023d12c2bc>] do_exception+0x12c/0x3e0
  [  591.755494]  [<00023d12d122>] do_dat_exception+0x2a/0x58
  [  591.755497]  [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220
  [  591.755497] Mem-Info:
  [  591.755501] active_anon:0 inactive_anon:33 isolated_anon:6
  active_file:59 inactive_file:93 isolated_file:3
  unevictable:6786 dirty:0 writeback:2 unstable:0
  slab_reclaimable:27072 slab_unreclaimable:44918
  mapped:3670 shmem:0 pagetables:12555 bounce:0
  free:19327 free_pcp:356 free_cma:0
  [  591.755505] Node 0 active_anon:0kB inactive_anon:132kB active_file:236kB 
inactive_file:372kB unevictable:27144kB isolated(anon):24kB isolated(file):12kB 
mapped:14680kB dirty:0kB writeback:8kB shmem:0kB shmem_thp: 0kB 
shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB 
all_unreclaimable? no
  [  591.755505] Node 0 DMA free:57800kB min:2876kB low:4944kB high:7012kB 
active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:2097152kB managed:2097056kB 
mlocked:0kB kernel_stack:496kB pagetables:4964kB bounce:0kB free_pcp:620kB 
local_pcp:248kB free_cma:0kB
  [  591.755509] lowmem_reserve[]: 0 13806 13806
  [  591.755511] Node 0 Normal free:19508kB min:19648kB low:33784kB 
high:47920kB active_anon:0kB inactive_anon:132kB active_file:0kB 
inactive_file:576kB unevictable:27144kB writepending:8kB present:14680064kB 
managed:14141200kB mlocked:27144kB kernel_stack:25040kB pagetables:45256kB 
bounce:0kB free_pcp:804kB local_pcp:120kB free_cma:0kB
  [  591.755515] lowmem_reserve[]: 0 0 0
  [  591.755516] Node 0 DMA: 1*4kB (M) 5*8kB (UME) 6*16kB (UME) 2*32kB (M) 
4*64kB (UME) 4*128kB (ME) 5*256kB (UME) 4*512kB (ME) 52*1024kB (UM) = 57548kB
  [  591.755525] Node 0 Normal: 244*4kB (UME) 198*8kB (UMEH) 94*16kB (UMEH) 
149*32kB (MEH) 31*64kB (UME) 10*128kB (UMEH) 2*256kB (MH) 2*512kB (MH) 5*1024kB 
(UM) = 18752kB
  [  591.755534] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=1024kB
  [  591.755535] 3724 total pagecache pages
  [  591.755536] 74 pages in swap cache
  [  591.755537] Swap cache stats: add 98390, delete 98316, find 11531/42289
  [  591.755538] Free swap  = 935816kB
  [  591.755538] Total swap = 1001096kB
  [  591.755539] 4194304 pages RAM
  [  591.755540] 0 pages HighMem/MovableOnly
  [  591.755540] 134740 pages reserved
  [  591.755541] 0 pages cma reserved
  [  591.755542] Unreclaimable slab info:
  [  591.755542] Name  Used  Total
  [  591.755614] nf_conntrack 128KB128KB
  [  591.755680] abd_t  3KB  3KB
  [  591.755682] zio_data_buf_16384 64KB 64KB
  [  591.755683] zio_buf_16384 32KB 32KB
  [  

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Kai-Heng Feng]

Can you please attach dmesg after rolling back linux-firmware?

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: 

Re: [Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0

[Seth Forshee]

On Wed, Mar 04, 2020 at 10:51:34PM -, DooMMasteR wrote:
> I can reproduce to get the driver/gpu hanging by playing back 4k h.264
> video in celluloid/mpv.
> 
> [  324.680024] i915 :00:02.0: GPU HANG: ecode 9:5:0x, hang on 
> rcs0, vcs0
> [  324.681031] i915 :00:02.0: Resetting rcs0 for hang on rcs0, vcs0
> [  324.681065] i915 :00:02.0: Resetting vcs0 for hang on rcs0, vcs0
> 
> the system becomes nearly unresponsive after a short time (2-3 seconds
> after the first crash
> 
> my CPU is an Intel(R) Core(TM) i5-6300U, no external GPU, 16 GB RAM in
> an HP Elitebook 820 G3, the iGPU has 512MB memory allocated.

Which kernel version are you running when you see 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/1861395

Title:
  system hang: i915 Resetting rcs0 for hang on rcs0

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Incomplete

Bug description:
  System hangs, unknown cause, When this happens, the mouse pointer
  still moves, but I can't do anything else with the keys or clicking in
  the UI.  Only recover I have found is a hard power-off

  Last bit of kern.log below:

  Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: 
ecode 9:1:0x, hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
  Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
  Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required 
to analyze GPU hangs, so please always attach it.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting 
chip for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks 
suppressed
  Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
  Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 
01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 
7d 8f 00
  Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 12:51:24 2020
  InstallationDate: Installed on 2018-06-18 (591 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
  

[Kernel-packages] [Bug 1865110] Re: disco/linux: 5.0.0-43.47 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-5.0: bug 1863281, bug 1865434
+   bionic/linux-aws-5.0: bug 1865434, bug 1863281
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
-   bionic/linux-gcp: bug 1863289, bug 1865431
+   bionic/linux-gcp: bug 1865431, bug 1863289
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
-   bionic/linux-oracle-5.0: bug 1865422, bug 1863296
+   bionic/linux-oracle-5.0: bug 1863296, bug 1865422
  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/1865110

Title:
  disco/linux: 5.0.0-43.47 -proposed tracker

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1865434, bug 1863281
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1865431, bug 1863289
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
bionic/linux-oracle-5.0: bug 1863296, bug 1865422
  variant: debs

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

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

[Kernel-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[robert knox]

I see this as well. It seems to happen every 2 or 3 days as a result a some 
combination of random keystrokes. i reboot fixes the issue, but it is very 
annoying.

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+subscriptions

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

[Kernel-packages] [Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
-   bionic/linux-kvm: bug 1864737, bug 1865247
+   bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1863339, bug 1865480
+   bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1865247, bug 1864737
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1865480, bug 1863339
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

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

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

[Kernel-packages] [Bug 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 00:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  variant: debs

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

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

[Kernel-packages] [Bug 1865280] Re: unbinding igb driver causes general protection fault

[Launchpad Bug Tracker]

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

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

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

Title:
  unbinding igb driver causes general protection fault

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  I have a pci passthrough setup. I want to passthrough an Intel I210
  Gigabit controller (igb driver) to a VM.

  I got general protection fault after issuing the following command:
  echo :06:00.0 > /sys/bus/pci/devices/:06:00.0/driver/unbind

  It works with 4.15.0-76-generic kernel and it does not work with
  4.15.0-88-generic kernel.

  # lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  # uname -r
  4.15.0-88-generic

  # lspci
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.1 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
  00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #5 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation C226 Series Chipset Family Server 
Advanced SKU LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Oland PRO [Radeon R7 240/340]
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape 
Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
  03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge 
(rev 04)
  04:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] 
IEEE 1394 OHCI Controller (rev c0)
  05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
  06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network 
Connection (rev 03)
  07:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter 
(rev 01)

  kernel log:
  [   41.772488] general protection fault:  [#1] SMP PTI
  [   41.778675] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter 8021q 
garp mrp bridge stp llc btrfs zstd_compress intel_rapl btusb btrtl btbcm 
btintel bluetooth x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc aesni_intel ecdh_generic joydev 
input_leds aes_x86_64 snd_hda_intel crypto_simd glue_helper cryptd wmi_bmof 
intel_cstate intel_rapl_perf eeepc_wmi snd_hda_codec asus_wmi sparse_keymap 
snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm 
snd_seq snd_seq_device snd_timer mei_me snd mei soundcore lpc_ich
  [   41.853566]  shpchp mac_hid sch_fq_codel coretemp nct6775 hwmon_vid 
kvm_intel kvm vfio_pci vfio_virqfd irqbypass vfio_iommu_type1 vfio sunrpc 
ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor
  async_tx xor raid6_pq libcrc32c raid0 multipath linear pci_stub raid1 
hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid chash i915 igb ttm 
mxm_wmi drm_kms_helper dca syscopyarea firewire_ohci i2c_algo_bit sysfillrect 
ahci ptp sysimgblt libahci fb_sys_fops pps_core firewire_core drm crc_itu_t 
video wmi
  [   41.904435] CPU: 3 PID: 2790 Comm: poseidon.sh Not tainted 

[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0

[DooMMasteR]

I disabled secure-boot and booted kernel 5.5.7 (mainline ppa) which does
not exhibit the behavior…

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

Title:
  system hang: i915 Resetting rcs0 for hang on rcs0

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Incomplete

Bug description:
  System hangs, unknown cause, When this happens, the mouse pointer
  still moves, but I can't do anything else with the keys or clicking in
  the UI.  Only recover I have found is a hard power-off

  Last bit of kern.log below:

  Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: 
ecode 9:1:0x, hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
  Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
  Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required 
to analyze GPU hangs, so please always attach it.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting 
chip for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks 
suppressed
  Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
  Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 
01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 
7d 8f 00
  Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 12:51:24 2020
  InstallationDate: Installed on 2018-06-18 (591 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpb   115653 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-06-18 (604 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 

[Kernel-packages] [Bug 1863314] Re: xenial/linux-cascade: 4.4.0-1015.17 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865106
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 11:42 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1863313
  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/1863314

Title:
  xenial/linux-cascade: 4.4.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  Invalid
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: 1865106
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 11:42 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1863313
  variant: debs

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

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

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[yahia farghaly]

Rolling back to linux-firmware=1.173.12 doesn't solve the problem for me

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro
  SourcePackage: xorg
  Symptom: display
  

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to
  install/upgrade: installed linux-image-5.3.0-40-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lost settings for display. The real resolution is not listed

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: hid_logitech_hidpp hid_logitech_dj i2c_i801 pata_acpi 
lpc_ich
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Feb 19 19:31:32 2020
  DuplicateSignature:
   package:linux-image-5.3.0-40-generic:5.3.0-40.32
   Removing linux-image-5.3.0-40-generic (5.3.0-40.32) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-5.3.0-40-generic (--remove):
installed linux-image-5.3.0-40-generic package pre-removal script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-5.3.0-40-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2019-11-03 (122 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 790
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3d85aa37-300e-4ace-b795-b854262f165c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to 
install/upgrade: installed linux-image-5.3.0-40-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0D28YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd04/02/2012:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0D28YY:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0

[DooMMasteR]

I can reproduce to get the driver/gpu hanging by playing back 4k h.264
video in celluloid/mpv.

[  324.680024] i915 :00:02.0: GPU HANG: ecode 9:5:0x, hang on rcs0, 
vcs0
[  324.681031] i915 :00:02.0: Resetting rcs0 for hang on rcs0, vcs0
[  324.681065] i915 :00:02.0: Resetting vcs0 for hang on rcs0, vcs0

the system becomes nearly unresponsive after a short time (2-3 seconds
after the first crash

my CPU is an Intel(R) Core(TM) i5-6300U, no external GPU, 16 GB RAM in
an HP Elitebook 820 G3, the iGPU has 512MB memory allocated.

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

Title:
  system hang: i915 Resetting rcs0 for hang on rcs0

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Incomplete

Bug description:
  System hangs, unknown cause, When this happens, the mouse pointer
  still moves, but I can't do anything else with the keys or clicking in
  the UI.  Only recover I have found is a hard power-off

  Last bit of kern.log below:

  Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: 
ecode 9:1:0x, hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug 
anywhere in the entire gfx stack, including userspace.
  Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report 
on bugs.freedesktop.org against DRI -> DRM/Intel
  Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then 
reassign to the right component if it's not a kernel issue.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required 
to analyze GPU hangs, so please always attach it.
  Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting 
chip for hang on rcs0
  Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] 
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
  Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks 
suppressed
  Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
  Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 
01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 
7d 8f 00
  Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 12:51:24 2020
  InstallationDate: Installed on 2018-06-18 (591 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpb   115653 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: 

[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

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

** 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Ready for Packaging
- phase-changed: Tuesday, 03. March 2020 07:47 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 04. March 2020 22:46 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1864732
  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/1865419

Title:
  bionic/linux-aws-fips: 4.15.0-2012.12 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Wednesday, 04. March 2020 22:46 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1864732
  variant: debs

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

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

[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker

[Manoj Iyer]

** Summary changed:

- bionic/linux-aws-fips:  -proposed tracker
+ bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker

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

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

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

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

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

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

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

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

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

Title:
  bionic/linux-aws-fips: 4.15.0-2012.12 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 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: 1865269
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Wednesday, 04. March 2020 22:46 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1864732
  variant: debs

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

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

[Kernel-packages] [Bug 1866131] Re: package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to install/upgrade: installed linux-image-5.3.0-40-generic package pre-removal script subprocess returned er

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to
  install/upgrade: installed linux-image-5.3.0-40-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Lost settings for display. The real resolution is not listed

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: hid_logitech_hidpp hid_logitech_dj i2c_i801 pata_acpi 
lpc_ich
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Feb 19 19:31:32 2020
  DuplicateSignature:
   package:linux-image-5.3.0-40-generic:5.3.0-40.32
   Removing linux-image-5.3.0-40-generic (5.3.0-40.32) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-5.3.0-40-generic (--remove):
installed linux-image-5.3.0-40-generic package pre-removal script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-5.3.0-40-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2019-11-03 (122 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 790
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3d85aa37-300e-4ace-b795-b854262f165c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to 
install/upgrade: installed linux-image-5.3.0-40-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0D28YY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd04/02/2012:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0D28YY:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1866131] [NEW] package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to install/upgrade: installed linux-image-5.3.0-40-generic package pre-removal script subprocess returned

[Reynaldo A ROSAS-HIJAR]

Public bug reported:

Lost settings for display. The real resolution is not listed

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-40-generic 5.3.0-40.32
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: hid_logitech_hidpp hid_logitech_dj i2c_i801 pata_acpi 
lpc_ich
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Wed Feb 19 19:31:32 2020
DuplicateSignature:
 package:linux-image-5.3.0-40-generic:5.3.0-40.32
 Removing linux-image-5.3.0-40-generic (5.3.0-40.32) ...
 E: Aborting removal of the running kernel
 dpkg: error processing package linux-image-5.3.0-40-generic (--remove):
  installed linux-image-5.3.0-40-generic package pre-removal script subprocess 
returned error exit status 1
ErrorMessage: installed linux-image-5.3.0-40-generic package pre-removal script 
subprocess returned error exit status 1
InstallationDate: Installed on 2019-11-03 (122 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 eno1  no wireless extensions.
 
 lono wireless extensions.
MachineType: Dell Inc. OptiPlex 790
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3d85aa37-300e-4ace-b795-b854262f165c ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
RfKill:
 
SourcePackage: linux
Title: package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to 
install/upgrade: installed linux-image-5.3.0-40-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0D28YY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd04/02/2012:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0D28YY:rvrA03:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package eoan

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

Title:
  package linux-image-5.3.0-40-generic 5.3.0-40.32 failed to
  install/upgrade: installed linux-image-5.3.0-40-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Lost settings for display. The real resolution is not listed

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: hid_logitech_hidpp hid_logitech_dj i2c_i801 pata_acpi 
lpc_ich
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Feb 19 19:31:32 2020
  DuplicateSignature:
   package:linux-image-5.3.0-40-generic:5.3.0-40.32
   Removing linux-image-5.3.0-40-generic (5.3.0-40.32) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-5.3.0-40-generic (--remove):
installed linux-image-5.3.0-40-generic package pre-removal script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-5.3.0-40-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2019-11-03 (122 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 790
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3d85aa37-300e-4ace-b795-b854262f165c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
  RfKill:
   
 

[Kernel-packages] [Bug 1865110] Re: disco/linux: 5.0.0-43.47 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-5.0: bug 1865434, bug 1863281
+   bionic/linux-aws-5.0: bug 1863281, bug 1865434
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
-   bionic/linux-gcp: bug 1865431, bug 1863289
+   bionic/linux-gcp: bug 1863289, bug 1865431
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
bionic/linux-oracle-5.0: bug 1865422, bug 1863296
  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/1865110

Title:
  disco/linux: 5.0.0-43.47 -proposed tracker

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1863281, bug 1865434
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1863289, bug 1865431
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
bionic/linux-oracle-5.0: bug 1865422, bug 1863296
  variant: debs

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

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

[Kernel-packages] [Bug 1865495] Re: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865142
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 09:11 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- 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/1865495

Title:
  xenial/linux-deeplens: 4.15.0-1019.19 -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:
  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:
  Invalid
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:
  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: 1865142
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 09:11 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-fips: bug 1865419, bug 1864732
+   bionic/linux-aws-fips: bug 1864732, bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  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/1865269

Title:
  bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1864732, bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

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

[Kernel-packages] [Bug 1852119] Re: Please add zfs modules to linux-raspi2

[satmandu]

Thanks for the policy clarification. But as I understand it "4 GiB of
memory is recommended for normal performance in basic workloads"
referred to 4Gb of memory in total, not 4gb of free memory.

I'll ask again once there is a device with more than 4Gb of RAM, but
FYI, since the raspberry pi may often be used for single tasks, a 4Gb
ram machine might be just fine with that zfs overhead.

(I haven't seen any memory pressure issues with multiple headless 4Gb
Pi4 machines running with ubuntu on zfs.)

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

Title:
  Please add zfs modules to linux-raspi2

Status in linux-raspi2 package in Ubuntu:
  Won't Fix

Bug description:
  The 4gb RPI4 is more than capable of handling zfs.
  ( Even zfs root can be enabled manually with arm64 eoan builds using a 
variant of the steps at 
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . )

  Currently one has to install zfs-dkms for zfs support, but ideally one
  would have zfs modules come with the standard arm64 kernel so that one
  does not have to recompile zfs on the pi.

  Example:

  uname -a
  Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 
aarch64 aarch64 aarch64 GNU/Linux
  @rpi4:~$ zpool status
pool: bpool
   state: ONLINE
  status: Some supported features are not enabled on the pool. The pool can
  still be used, but some features are unavailable.
  action: Enable all features using 'zpool upgrade'. Once this is done,
  the pool may no longer be accessible by software that does not support
  the features. See zpool-features(5) for details.
scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 
13:50:14 2019
  config:

  NAME  STATE 
READ WRITE CKSUM
  bpool ONLINE  
 0 0 0
usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3  ONLINE  
 0 0 0

  errors: No known data errors

pool: rpool
   state: ONLINE
scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 
13:51:39 2019
  config:

  NAMESTATE READ WRITE CKSUM
  rpool   ONLINE   0 0 0
sda4  ONLINE   0 0 0

  errors: No known data errors

  dkms status
  zfs, 0.8.1, 5.3.0-1011-raspi2, aarch64: installed

  @rpi4:~$ cat /proc/cpuinfo 
  processor   : 0
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  processor   : 1
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  processor   : 2
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  processor   : 3
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  Hardware: BCM2835
  Revision: c03111
  Serial  : ---
  Model   : Raspberry Pi 4 Model B Rev 1.1
  @rpi4:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:   3791 8832612  18 295
2836
  Swap:  4095   04095

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

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

[Kernel-packages] [Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
-   bionic/linux-kvm: bug 1865247, bug 1864737
+   bionic/linux-kvm: bug 1864737, bug 1865247
bionic/linux-oem: bug 1865200
-   bionic/linux-oracle: bug 1865480, bug 1863339
+   bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  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/1865109

Title:
  bionic/linux: 4.15.0-91.92 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 29. February 2020 01:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1865269
bionic/linux-fips: bug 1865203
bionic/linux-gke-4.15: bug 1865255
bionic/linux-ibm-gt: bug 1865201
bionic/linux-kvm: bug 1864737, bug 1865247
bionic/linux-oem: bug 1865200
bionic/linux-oracle: bug 1863339, bug 1865480
bionic/linux-raspi2: bug 1864726
bionic/linux-snapdragon: bug 1864729
bionic/linux/pc-kernel: bug 1865107
bionic/linux/pc-lowlatency-kernel: bug 1865108
xenial/linux-azure: bug 1865198
xenial/linux-gcp: bug 1865251
xenial/linux-hwe: bug 1865142
  variant: debs

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

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

[Kernel-packages] [Bug 1865022] Re: focal/linux-gcp: 5.4.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865025
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. March 2020 06:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1865022

Title:
  focal/linux-gcp: 5.4.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Focal:
  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: 1865025
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. March 2020 06:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1865021] Re: focal/linux-azure: 5.4.0-1005.5 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865025
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 29. February 2020 02:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

Title:
  focal/linux-azure: 5.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Focal:
  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: 1865025
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 29. February 2020 02:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
  variant: debs

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

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

[Kernel-packages] [Bug 1865017] Re: focal/linux-raspi2: 5.4.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865025
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Monday, 02. March 2020 21:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
  trackers:
focal/linux-raspi2/pi-kernel: bug 1865031
  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/1865017

Title:
  focal/linux-raspi2: 5.4.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Focal:
  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: 1865025
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Monday, 02. March 2020 21:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  trackers:
focal/linux-raspi2/pi-kernel: bug 1865031
  variant: debs

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

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

[Kernel-packages] [Bug 1865020] Re: focal/linux-aws: 5.4.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1865025
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1865020

Title:
  focal/linux-aws: 5.4.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Focal:
  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: 1865025
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 28. February 2020 19:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

Fortunately, all of the failing ACPI methods are optional, and there are
good chances that Linux / Ubuntu will work without them. There are three
types of devices *might* be affected according to the error messages:

1. USB (\_SB.PCI0.XHC.RHUB...)- but USB ports and devices should just-
work without BIOS code, which are usually for OEM customization.

2. Touchpad (\_SB.PCI0.I2Cx...) - error messages are reported for i2c-2
and i2c-3, but it is likely the touchpad is connected to i2c-1. Please
check whether you are experience problems with your touchpad.

3. Switchable graphics (\_SB.PCI0.PEG0...)- but error messages are
"AE_ALREADY_EXISTS". lspci also shows no discrete VGA present on this
system, and nothing to worry about.


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

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

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI 

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

There are two types of ACPI errors observed: AE_ALREADY_EXISTS and
AE_NOT_FOUND

The former, AE_ALREADY_EXISTS, usually happens

1) when BIOS loads multiple SSDTs (in /sys/firmware/acpi/tables) that
contains the objects with the same names (and usually the same functions
too). Naming conflicts prevent kernel to load all of them correctly.

2) BIOS's ACPI methods are not serialized and multiple calls the same
methods occur.

I would guess we are seeing scenario 1 here. They are usually harmless
because a copy of working SSDT is loaded while duplicated ones are
discarded.

The later, AE_NOT_FOUND, is the opposite. This occurs when BIOS does NOT
load SSDTs and therefore kernel is not able to get information and
perform accordingly.

Neither types of error messages can be fixed without BIOS fixes.

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 

[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen

[Colton Donnelly]

Hi Andrea,

Results running in gnome session:
Test 1: (dmesg -w) See attached. No output after closing lid.
Test 2: (acpi_listen) `button/lid LID close`, `button/lid LID open`
Test 3: (echo mem > /sys/power/state) laptop froze for 20s, recovered by 
pressing power button. Terminal output: `echo write error: device or resource 
busy`.

Results running in separate TTY session:
Test 1: (dmesg -w) Same as previous results
Test 2: (acpi_listen) Same as previous results
Test 3: (echo mem > /sys/power/state) laptop froze, unable to recover. Had to 
do a hard reset. Output from before crash: `[time] PM: suspend entry 
(s2idle)\n[time] PM: Syncing filesystems ... done.`

For what it's worth, I'm now noticing my laptop hangs when I try to
power off via the ubuntu power menu. `sudo shutdown now` is also coin
toss as to whether the shutdown will succeed or not (although it does
succeed, unlike the ubuntu power menu). `sudo reboot` consistently
works, as with the power menu option.

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

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  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-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 

[Kernel-packages] [Bug 1864895] Re: dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

[Alex Hung]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  dmseg report multiple "ACPI Error" and "ACPI BIOS Error"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  'lsb_release -rd':
  Description:  Ubuntu 19.10
  Release:  19.10

  'cat /proc/version_signature > version.log':
  Ubuntu 5.3.0-40.32-generic 5.3.18

  'sudo lspci -vnvn > lspci-vnvn.log' as attachments.

  'dmesg | grep "Error"':
  [0.214136] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214145] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214196] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.214203] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.214205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216645] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216648] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.216652] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.216654] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219087] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219091] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.219094] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.219097] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221521] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221524] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.221527] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.221529] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.223957] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.223961] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226392] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.226399] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.226401] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.228826] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.228829] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.231260] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.231263] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233688] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233691] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.233694] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS09._PLD], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.233696] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.236125] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.236128] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20190703/psobject-220)
  [0.238559] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS11._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323)
  [0.238562] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Anshul Jethvani]

A temporary solution (disable module) that worked for me :

https://askubuntu.com/questions/1155263/new-install-desktop-ubuntu-19-04
-shows-error-message-ucsi-ccg-0-0008-failed-to

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

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

Bug description:
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.


  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit

  
  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
 +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 
Ti Mobile]
 |+-00.1  NVIDIA Corporation Device 1aeb
 |+-00.2  NVIDIA Corporation Device 1aec
 |\-00.3  NVIDIA Corporation Device 1aed
  ...

  Where the '1aed' device is detected as "NVIDIA USB Type-C Port Policy
  Controller" in Windows.

  I'm not sure if it's serving any useful purpose on this laptop, and it
  certainly doesn't seem to function properly:

  If I enable UCSI logging on startup (root's crontab):

  @reboot bash -c 'echo 1 >
  /sys/kernel/debug/tracing/events/ucsi/enable'

  ..the steps to 

[Kernel-packages] [Bug 793261] Re: CP210x not support CP2104 device

[Andrew]

Running PopOS 19.10

There seems to be no support for CP2104 in the default kernel!

This makes uploading to the new Adafruit feather arduino's difficult.

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

Title:
  CP210x not support CP2104 device

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying to use CP2104 (Silicon Labs), which should be support by CP210X 
driver and I am not able to get good baud rate or even to modify it. Bit time 
40nS which means really high speed. Using Ubuntu kernel driver for it.
  Is the kernel driver supposed to handle CP2104? May I have access to kernel 
CP210x driver so that I would "modify" it to support CP2104?
  What are the steps to reconfigure (re-compile) the driver?

  Thanks
  Nuno

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

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

[Kernel-packages] [Bug 1865110] Re: disco/linux: 5.0.0-43.47 -proposed tracker

[Ubuntu Kernel Bot]

** 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:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-aws-5.0: bug 1863281, bug 1865434
+   bionic/linux-aws-5.0: bug 1865434, bug 1863281
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1865431, bug 1863289
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
-   bionic/linux-oem-osp1: bug 1865205, bug 1863279
-   bionic/linux-oracle-5.0: bug 1863296, bug 1865422
+   bionic/linux-oem-osp1: bug 1865205
+   bionic/linux-oracle-5.0: bug 1865422, bug 1863296
  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/1865110

Title:
  disco/linux: 5.0.0-43.47 -proposed tracker

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 28. February 2020 17:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1865434, bug 1863281
bionic/linux-azure: bug 1865193
bionic/linux-bluefield: bug 1863295
bionic/linux-gcp: bug 1865431, bug 1863289
bionic/linux-gke-5.0: bug 1865429
bionic/linux-hwe-5.0: bug 1865140
bionic/linux-oem-osp1: bug 1865205
bionic/linux-oracle-5.0: bug 1865422, bug 1863296
  variant: debs

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

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

[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen

[Andrea Righi]

Thanks for reporting this.

The CurrentDmesg.txt that you posted doesn't seem to include the part
when you close the lid, am I correct?

In that case could you run `dmesg -w` on a console session, close the
lid and post what you get in dmesg?

Another interesting test could be to check if the ACPI events are
properly handled by the kernel and passed to user-space. For this you
can try to run `acpi_listen` (as root) in another console session, close
the lid, re-open it, and you should see something like:

 button/lid LID close
 button/lid LID open

Then, I'm not sure if you tried it already, but what happens if you try
to suspend manually via `echo mem > /sys/power/state`. Does it actually
suspend? Do you get any error in dmesg?

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

Title:
  lid close simply turns off laptop screen

Status in gnome-session package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1)
  ubuntu-session version: 3.28.1-0ubuntu3
  Expected behavior: On laptop screen close, system should suspend
  Actual behavior: On laptop screen close, laptop screen disabled

  Previously, I triggered 'suspend when laptop lid is closed' in gnome-
  tweaks. This worked fine until about 2-3 days ago, when I came back to
  work with a dead laptop (I don't charge overnight, usually, but I do
  use a dock at work). Now, whenever I close my laptop screen, it
  doesn't trigger sleep - instead, it simply disables the laptop screen,
  resulting in my external monitor being used as the only output screen.
  Once I re-open my laptop, the laptop screen is re-enabled as the
  primary monitor.

  This happens regardless of connection to my dock. I tested this by
  unplugging my laptop, closing it, letting it sit for 3 minutes, then
  re-opening it. While the laptop was closed, fans still ran. When I re-
  opened my laptop, the lock screen didn't appear.

  Links to attempted fixes that didn't work:

  - 
https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate
  - 
https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close
  - 
https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369
  - 
https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid

  Results of attempted fixes:
  - mem_sleep: no behavior change (files correctly modified)
  - pm-hibernate: first run, hangs until I kill the process. future runs result 
in exit code 1.
  - update bios: already on latest bios
  - logind.conf: no behavior change
  - gnome tweaks: no behavior change

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  Uname: Linux 4.15.0-1073-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 10:23:52 2020
  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-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  InstallationDate: Installed on 2020-01-08 (51 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colton 4205 F pulseaudio
   /dev/snd/controlC0:  colton 4205 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  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-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-08 (53 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem 
root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1073-oem N/A
   linux-backports-modules-4.15.0-1073-oem  N/A
   linux-firmware

[Kernel-packages] [Bug 1865251] Re: xenial/linux-gcp: 4.15.0-1058.62 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865109
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 02. March 2020 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1865249
xenial/linux-gcp/gke-kernel: bug 1865250
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1058.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1865109
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 02. March 2020 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1865249
xenial/linux-gcp/gke-kernel: bug 1865250
  variant: debs

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

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

[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend

[MARTIN]

** Description changed:

  Good morning.
  
  There many months than I use "suspend" (settings -> energy -> When the
  shutdown button...) on Ubuntu 18.04 or 19.10.
  
  But at each wake up from my computer, the USB 3.1 Gen 1 ports (only
  motherboard back panel) no work after (loose use of webcam,
  keyboard...).
  
- No problems with USB 3.1 Gen 1 and USB 2.0/1.1 front panel (from
- internal USB header).
+ No problems with USB 3.1 Gen 1 and USB 2.0/1.1 front panel (from internal USB 
header).
+ No problems with USB 2.0/1.1 ports (motherboard back panel).
  
  I think my motherboard is not at fault because I did not reproduce this bug 
on Windows 10.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  christophe   1648 F pulseaudio
-  /dev/snd/controlC2:  christophe   1648 F pulseaudio
-  /dev/snd/controlC0:  christophe   1648 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  christophe   1648 F pulseaudio
+  /dev/snd/controlC2:  christophe   1648 F pulseaudio
+  /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
-  lono wireless extensions.
-  
-  enp6s0no wireless extensions.
+  lono wireless extensions.
+ 
+  enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-40-generic N/A
-  linux-backports-modules-5.3.0-40-generic  N/A
-  linux-firmware1.173.15
+  linux-restricted-modules-5.3.0-40-generic N/A
+  linux-backports-modules-5.3.0-40-generic  N/A
+  linux-firmware1.173.15
  RfKill:
-  
+ 
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Good morning.

  There many months than I use "suspend" (settings -> energy -> When the
  shutdown button...) on Ubuntu 18.04 or 19.10.

  But at each wake up from my computer, the USB 3.1 Gen 1 ports (only
  motherboard back panel) no work after (loose use of webcam,
  keyboard...).

  No problems with USB 3.1 Gen 1 and USB 2.0/1.1 front panel (from internal USB 
header).
  No problems with USB 2.0/1.1 ports (motherboard back panel).

  I think my motherboard is not at fault because I did not reproduce this bug 
on Windows 10.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   

[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1865419, bug 1864732
bionic/linux-aws/aws-kernel: bug 1865268
-   xenial/linux-aws-hwe: bug 1865421, bug 1864733
+   xenial/linux-aws-hwe: bug 1865421
  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/1865269

Title:
  bionic/linux-aws: 4.15.0-1063.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1865109
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Tuesday, 03. March 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1865419, bug 1864732
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
  variant: debs

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

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

[Kernel-packages] [Bug 1865024] Re: focal/linux-oracle: 5.4.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** 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: 1865025
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 13:36 UTC
  reason:
-   build-packages-proposed: Ongoing -- building in Proposed
- signed:depwait
+   build-packages-proposed: Pending -- building in Proposed
+ signed:retry-needed
promote-to-proposed: Stalled -- packages copying to Proposed
  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/1865024

Title:
  focal/linux-oracle: 5.4.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Confirmed
Status in linux-oracle source package in Focal:
  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: 1865025
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Wednesday, 04. March 2020 13:36 UTC
  reason:
build-packages-proposed: Pending -- building in Proposed
  signed:retry-needed
promote-to-proposed: Stalled -- packages copying to Proposed
  variant: debs

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

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