[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap

[Po-Hsu Lin]

Can be reproduced easily with Cosmic kernel, patch works as expected. A
test kernel could be found here:
http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-
zswap/Cosmic/

Will try this on Bionic next.

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

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

Title:
  NULL pointer dereference when using z3fold and zswap

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  New

Bug description:
  Under memory pressure, my VM locks up. This has been reported upstream
  though I don't know how far any solution has progressed.

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

  Feb  6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0
  Feb  6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle 
kernel NULL pointer dereference at 0008

  The little bit of log I managed to salvage is attached.

  This has happened to two identical VMs. Unusually it has not occurred
  on a third VM which is configured the same but has less RAM (fingers
  crossed it won't).

  Irrelevant information:
  I thought the lock-ups were due to me using a BTRFS filesystem, however I 
swapped over to NILFS2 and this still occurs. The only difference seems to be 
that I am now able to grab some of the kernel output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:55:05 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Joe Barnett]

Saw same thing with the btmgr commands added to system-sleep script,
attaching kernel log from that boot

** Attachment added: "kernel log with btmgr privacy set during system-sleep 
script"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5255096/+files/kern-btprivacy.log

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Michael J]

The battery in these are weak; only 2 cell (7.7v) @ 4600mah. 6hrs is a
pipe dream; perhaps with the screen being off and no apps running, maybe
5hrs. 3hrs or so seem realistic to me, especially watching video. Budget
laptop, budget battery.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1824374] Re: linux-raspi2: 5.0.0-1006.6 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1824383
- phase: Promote to Proposed
- phase-changed: Friday, 12. April 2019 01:39 UTC
+ phase: Testing
+ phase-changed: Friday, 12. April 2019 03:10 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 5.0.0-1006.6 -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:
  New
Status in linux-raspi2 source package in Disco:
  New

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: 1824383
  phase: Testing
  phase-changed: Friday, 12. April 2019 03:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824375] Re: linux-aws: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1824383
- phase: Promote to Proposed
- phase-changed: Friday, 12. April 2019 01:40 UTC
+ phase: Testing
+ phase-changed: Friday, 12. April 2019 03:10 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 5.0.0-1003.3 -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:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New

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: 1824383
  phase: Testing
  phase-changed: Friday, 12. April 2019 03:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

[Kai-Heng Feng]

So the patched kernel reduce the fail rate, but not completely?

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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

[Kernel-packages] [Bug 1812153] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

[Po-Hsu Lin]

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

Title:
  CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released
Status in linux-kvm source package in Cosmic:
  Fix Released
Status in linux-kvm source package in Disco:
  Fix Released

Bug description:
  The test_081_config_security_selinux_disable test failed on the Bionic
  KVM kernel

FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be 
unset in the kernel config

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 04:31:59 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

[Po-Hsu Lin]

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

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a later kernel
  (please see got log without --oneline for stable@ details)

  However both bionic and xenial/hwe has much less fuse patches applied:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: 

[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Tags added: block-proposed-disco

** 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 --
  kernel-stable-master-bug: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux-gcp: 5.0.0-1003.3 -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:
  In Progress
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-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

[Kernel-packages] [Bug 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-disco

** 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: 1824383
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 11. April 2019 22:10 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 12. April 2019 02:10 UTC
  reason:
-   promote-to-proposed: Holding -- master bug not ready for proposed
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-kvm: 5.0.0-1003.3 -proposed tracker

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

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: 1824383
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 12. April 2019 02:10 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1824382] Re: linux-oem-osp1: -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: 1824383
- phase: Holding before Packaging
- phase-changed: Thursday, 11. April 2019 15:42 UTC
+ phase: Ready for Packaging
+ phase-changed: Friday, 12. April 2019 02:11 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-oem-osp1:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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 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 --
  kernel-stable-master-bug: 1824383
  phase: Ready for Packaging
  phase-changed: Friday, 12. April 2019 02:11 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1824376] Re: linux-azure: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Tags added: block-proposed-disco

** 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 --
  kernel-stable-master-bug: 1824383
- phase: Packaging
- phase-changed: Thursday, 11. April 2019 17:40 UTC
+ phase: Promote to Proposed
+ phase-changed: Friday, 12. April 2019 02:10 UTC
  reason:
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux-azure: 5.0.0-1003.3 -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 Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

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: 1824383
  phase: Promote to Proposed
  phase-changed: Friday, 12. April 2019 02:10 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

[Kernel-packages] [Bug 1824383] Re: linux: 5.0.0-11.12 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Tags added: block-proposed-disco

** 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
  
  backports: bug 1824381 (bionic/linux-hwe-edge), bug 1824382 
(bionic/linux-oem-osp1)
  derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 
(linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 
(linux-snapdragon)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 15:43 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
+   prepare-package-meta: Pending -- package tag not yet published
+   prepare-package-signed: Pending -- package tag not yet published
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux: 5.0.0-11.12 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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 package in Ubuntu:
  New
Status in linux source package in Disco:
  New

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

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

  backports: bug 1824381 (bionic/linux-hwe-edge), bug 1824382 
(bionic/linux-oem-osp1)
  derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 
(linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 
(linux-snapdragon)

  -- swm properties --
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 15:43 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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

[Kernel-packages] [Bug 1823216] Re: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG:

[Liz Fong-Jones]

Canarying both 4.4.0-1040-aws #43-Ubuntu and 4.4.0-144-generic
#170~14.04.1-Ubuntu in parallel to see whether the bug trips in either
of these. Should have results by Monday -- it was tripping every ~24h
with 3.13.0-167-generic so if there's no failures by Monday I'll
consider it resolved with the newer kernel train.

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

Title:
  [trusty] 3.13.0-167-generic repeatedly trips kernel paging request
  BUG:

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  While trying to diagnose a problem with getting a kernel BUG: Bad page
  map in process retriever (retriever is the name of our serving
  binary), causing the serving binary to crash, we tried upgrading from
  3.13.0-121-generic to 3.13.0-167-generic and instead started more
  regularly tripping a different bug that hardlocks the system when we
  attempt to stop & restart the affected process.

  We are running Trusty on AWS in i3.xlarge instances.

  BUG: unable to handle kernel paging request at eaf0
  [89149.537277] IP: [] _raw_spin_lock+0xe/0x50
  [89149.543462] PGD 0
  [89149.545919] Oops: 0002 [#1] SMP
  [89149.549887] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [89149.574925] CPU: 3 PID: 21681 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [89149.583168] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [89149.589649] task: 8807f2f7e000 ti: 88015b674000 task.ti: 
88015b674000
  [89149.597338] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [89149.605845] RSP: :88015b675d88  EFLAGS: 00010206
  [89149.611431] RAX: 0002 RBX: 00c0dee00020 RCX: 
f000cf53
  [89149.618873] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [89149.626336] RBP: 88015b675d88 R08: 3fe0 R09: 
00a9
  [89149.633705] R10:  R11: f000ff53f000ff53 R12: 
880037471900
  [89149.641019] R13: 8807f49c57b8 R14: 8807f2eb2680 R15: 
eaf0
  [89149.648287] FS:  7f92262dd700() GS:88081fc6() 
knlGS:
  [89149.657764] CS:  0010 DS:  ES:  CR0: 80050033
  [89149.664294] CR2: eaf0 CR3: 0007f438 CR4: 
00160670
  [89149.672158] DR0:  DR1:  DR2: 

  [89149.680246] DR3:  DR6: fffe0ff0 DR7: 
0400
  [89149.688126] Stack:
  [89149.690903]  88015b675e20 811831fe 81e85225 
8807f2eb2680
  [89149.700310]  88015b675f20 88015b675e10 0007 
f000cf53
  [89149.709739]  00a9 f000ff53f000ff53 8800 
8003
  [89149.719331] Call Trace:
  [89149.722581]  [] handle_mm_fault+0x27e/0xfb0
  [89149.729984]  [] __do_page_fault+0x183/0x570
  [89149.737506]  [] ? do_futex+0x10a/0x760
  [89149.744529]  [] ? set_next_entity+0x95/0xb0
  [89149.752059]  [] ? pick_next_task_fair+0x5f/0x1b0
  [89149.76]  [] ? sched_clock_cpu+0xb5/0x100
  [89149.767489]  [] do_page_fault+0x1a/0x70
  [89149.774460]  [] page_fault+0x28/0x30
  [89149.781134] Code: 00 00 55 48 89 e5 f0 81 07 00 00 10 00 48 89 f7 57 9d 0f 
1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00  0f 
c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7
  [89149.820963] RIP  [] _raw_spin_lock+0xe/0x50
  [89149.828646]  RSP 
  [89149.833460] CR2: eaf0
  [89149.843886] ---[ end trace 5e5ae13dbb1d0f6e ]---

  BUG: unable to handle kernel paging request at eaf0
  [66384.498399] IP: [] _raw_spin_lock+0xe/0x50
  [66384.502611] PGD 0
  [66384.504586] Oops: 0002 [#1] SMP
  [66384.507578] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [66384.525392] CPU: 1 PID: 21144 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [66384.531418] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [66384.535812] task: 88074a9a9800 ti: 8807f411e000 task.ti: 
8807f411e000
  [66384.542092] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [66384.548699] RSP: :8807f411fd88  EFLAGS: 00010206
  [66384.552560] RAX: 0002 RBX: 00c2b0c0 RCX: 
f000cf53
  [66384.557499] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [66384.562419] RBP: 8807f411fd88 R08: 3fe0 R09: 
00a9
  [66384.567450] R10:  R11: f000ff53f000ff53 R12: 
8807f4af9f00
  [66384.572935] R13: 8807f2ed9c30 R14: 

[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package tag not yet published
prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-gcp: 5.0.0-1003.3 -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:
  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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1824374] Re: linux-raspi2: 5.0.0-1006.6 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

** Tags added: block-proposed-disco

** 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 --
  kernel-stable-master-bug: 1824383
- phase: Packaging
- phase-changed: Thursday, 11. April 2019 17:40 UTC
+ phase: Promote to Proposed
+ phase-changed: Friday, 12. April 2019 01:39 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-raspi2: 5.0.0-1006.6 -proposed tracker

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

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: 1824383
  phase: Promote to Proposed
  phase-changed: Friday, 12. April 2019 01:39 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1824375] Re: linux-aws: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

** Tags added: block-proposed-disco

** 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 --
  kernel-stable-master-bug: 1824383
- phase: Packaging
- phase-changed: Thursday, 11. April 2019 15:42 UTC
+ phase: Promote to Proposed
+ phase-changed: Friday, 12. April 2019 01:40 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-aws: 5.0.0-1003.3 -proposed tracker

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

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: 1824383
  phase: Promote to Proposed
  phase-changed: Friday, 12. April 2019 01:40 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1824376] Re: linux-azure: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   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 --
  kernel-stable-master-bug: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 17:40 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

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

Title:
  linux-azure: 5.0.0-1003.3 -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:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 17:40 UTC
  reason:
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1785912] Re: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV

[Daniel van Vugt]

** Summary changed:

- Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV 
+ Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 
13IKB 81BV

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=108132
   Importance: Unknown
   Status: Unknown

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

Title:
  Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo
  Ideapad 720s 13IKB 81BV

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

Bug description:
  Horrible screen flicker from login screen and after login.  18.04.1 LTS.
  I have two similar laptops, both Lenovo Ideapad 720s 13IKB,
  model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine.
  model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen 
flashing.

  Neither have the problem in Windows (ie hardware fine)

  I installed the standard Ubuntu 18.04 on each of them (same USB Key,
  few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the
  problem.

  Flickering visible on video here:
  https://photos.app.goo.gl/HCN73q1nQfgstgVBA

  I've used ubuntu-bug so I believe you have all the details of the
  machine.  The install came straight from your standard 18.04 download.
  Any changes are due to me trying to fix this (not much prev exp of
  kernel params etc)

  Things tried but which didn't work were:
  - enable huc/guc (got it to load - it's now visible in the attached dmesg - 
but didn't help.)
  - enable_rc6=0 (just stopped sleep / resume working)
  - edp_vswing=2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Aug  7 23:09:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:39af]
  InstallationDate: Installed on 2018-08-06 (1 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 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 003: ID 5986:210d Acer, Inc
   Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81BV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 
i915.enable_guc_loading=1
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
  dmi.product.family: ideapad 720S-13IKB
  dmi.product.name: 81BV
  dmi.product.version: Lenovo ideapad 720S-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => 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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822807 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Promote to Proposed
- phase-changed: Thursday, 11. April 2019 07:35 UTC
+ phase: Testing
+ phase-changed: Friday, 12. April 2019 01:06 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: 'Pending -- snap gcp-kernel not in expected 
channel(s): arch=amd64:channel=18/beta'
+   snap-release-to-edge: 'Pending -- snap gcp-kernel not in expected 
channel(s): arch=amd64:channel=18/edge'
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1030.32 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

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

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

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 12. April 2019 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap gcp-kernel not in expected 
channel(s): arch=amd64:channel=18/beta'
snap-release-to-edge: 'Pending -- snap gcp-kernel not in expected 
channel(s): arch=amd64:channel=18/edge'
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822817
- phase: Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 15:42 UTC
+ phase: Testing
+ phase-changed: Friday, 12. April 2019 01:13 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1042.46~14.04.1 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  New

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: 1822817
  phase: Testing
  phase-changed: Friday, 12. April 2019 01:13 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: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

[Manoj Iyer]

Michael,

I backported that patch and built a new kernel for you to test in this
PPA:

https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1822870

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

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

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

[Kernel-packages] [Bug 1821395] Re: fscache: jobs might hang when fscache disk is full

[Mauricio Faria de Oliveira]

The verification for bionic/cosmic -proposed is expected to finish by
tomorrow (Apr 12).

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

Title:
  fscache: jobs might hang when fscache disk is full

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * fscache issue where jobs get hung when fscache disk is full.

   * trivial upstream fix; already applied in X/D, required in B/C:
     commit c5a94f434c82 ("fscache: fix race between enablement and
     dropping of object").

  [Test Case]

   * Test kernel verified / regression-tested by reporter.

   * Apparently there's no simple test case,
     but these are the conditions to hit the problem:

     1) The active dataset size is equal to the cache disk size.
    The application reads the data over and over again.
     2) Disk is near full (90%+)
     3) cachefilesd in userspace is trying to cull the old objects
    while new objects are being looked up.
     4) new cachefiles are created and some fail with no disk space.
     5) race in dropping object state machine and
    deferred lookup state machine causes the hang.
     6) HUNG in fscache_wait_for_deferred_lookup for
    clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

  [Regression Potential]

   * Low; contained in fscache; no further fixes applied upstream.

   * This patch is applied in a stable tree (linux-4.4.y).

  [Original Description]

  An user reported an fscache issue where jobs get hung when the fscache
  disk is full.

  After investigation, it's been found to be an issue already reported/fixed 
upstream,
  by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").

  This patch is required in Bionic and Cosmic, and it's applied in
  Xenial (via stable) and Disco.

  Apparently there's no simple test case, but these are the conditions
  to hit the problem:

  1) The active dataset size is equal to the cache disk size.
     The application reads the data over and over again.
  2) Disk is near full (90%+)
  3) cachefilesd in userspace is trying to cull the old objects
     while new objects are being looked up.
  4) new cachefiles are created and some fail with no disk space.
  5) race in dropping object state machine and
     deferred lookup state machine causes the hang.
  6) HUNG in fscache_wait_for_deferred_lookup for
     clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

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

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

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -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
  
  backports: bug 1822807 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Thursday, 11. April 2019 07:35 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030

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

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
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:
  New

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

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

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Thursday, 11. April 2019 07:35 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030

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

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

[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~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: 1822817
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 15:42 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

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

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: 1822817
  phase: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 15:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

For better battery time in linux set the cpufreq governor to "powersave"
and check powertop options.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   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: 1824383
- phase: Packaging
- phase-changed: Thursday, 11. April 2019 18:40 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 11. April 2019 22:10 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Holding -- master bug not ready for proposed

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

Title:
  linux-kvm: 5.0.0-1003.3 -proposed tracker

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

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: 1824383
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 11. April 2019 22:10 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed

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

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

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

[bugproxy]

--- Comment From gcwil...@us.ibm.com 2019-04-11 17:25 EDT---
Closing on our side as fixed.

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

Title:
  Please disable unnecessary config options in the Ubuntu 17.04 kernel
  config

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Some krnel config options for IMA should not be enabled in the Ubuntu 17.04 
kernel as they are at best experimental and at worst dangerous:

CONFIG_IMA_APPRAISE_SIGNED_INIT
CONFIG_IMA_BLACKLIST_KEYRING
CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY
CONFIG_IIMA_READ_POLICY
CONFIG_IIMA_WRITE_POLICY

  Please disable these config options in the Ubuntu 17.04 kernel config.
   
  ---uname output---
  Linux briggs-rtp-2 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = S822LC 8001-22C

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

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

[Kernel-packages] [Bug 1776563]

[pofavuyo]

If you check the manufacturer specifications, at least for my model it
says "Maximum Battery Run Time 6 Hour" ofc this is not realistic, but 5h
is. I'm not saying that different OS's should have the same energy
behaviour but going from 6h -> 5h -> 3h and less as the battery material
degrades is not good. I'm not expert in linux internals but I kept open
the CPU usage graph in both windows and linux, and while the percentages
were very close with same usage the draining was faster. I didn't put a
CPU frequency graph though and I suspect the problem is there, that
linux doesnt put it in the lowest needed freq scale when not needed.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

[pofavuyo]

Erik you'd be surpised to know that many people don't use vanilla kernels or 
don't have special knowledge on linux. It's OK to give details and github 
patches but it gives the false impression to people who just search their 
problem, that their 
touchpad won't work out of the box.

Ubuntu is not "my distro" is one of the top distros and many projects
use it as a proposed base to build like AOSP , Chrome browser etc. It
wasn't hostility against you so your defensive stance is unreasonable.

To the battery draining part, I get almost 5 hours with Windows 10
testing and many people commented that this the ultimate goal :) Because
you asked about my drain I got 2h40m max watching youtube and IRC
talking as I remember.

A fix is prepared so it means THERE IS a problem. Cheers mate.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

[eutychios23]

I dont know what you people are talking about 5hrs of battery life on
windows, but on all my budget laptops that run linux i get a max of
3hrs.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Joe Barnett]

yes, all packages are up to date, and specifically the gnome-bluetooth
package at 3.32.1-1 since april 3rd.

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep)
  Apr 02 13:39:59 taplop kernel: PM: Syncing 

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

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

** This bug has been marked a duplicate of bug 1821820
   Cannot boot or install - have to use nomodeset

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => 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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 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
-   snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
- arch=amd64:channel=latest/candidate:rev=66'
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.4.0-1080.90 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 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

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

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

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Question for everybody, I noticed that linux-5.0.0-10.11 which is
currently in proposed for cosmic has an explicit fix for this bug
(mentioned in the changelog).  Will this kernel make it into the
official 19.04 release - or will the release use linux-5.0.0-8.9?

If the official release doesn't use linux-5.0.0-10.11 (or something
greater) then many Dell laptop users will be unable to install using the
release ISO, which would be very unfortunate.

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

[Andrea Righi]

@navytux yes, a few of them require minimal changes, but most of them
can be applied cleanly to 4.15.

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a later kernel
  (please see got log without --oneline for stable@ details)

  However both bionic and xenial/hwe has much less fuse patches applied:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts
  

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

[Ubuntu Kernel Bot]

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

apport-collect 1824407

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: disco

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

Title:
   why does booting any livefs squashfs has kernel complaining about
  unable to read metadata something rather

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6ff3660032757063
  Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff3660032757063]
  Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6261746d79732e
  Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6261746d79732e]
  Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6ff366df00333a37
  Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff366df00333a37]

  Happens when booting e.g. subiquity disco image. v5.0.0-8-generic
  kernel

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

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

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

[Kirill Smelkov]

Thanks. If I understood correctly, the patches should be more or less
directly applicable to 4.15.y

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a later kernel
  (please see got log without --oneline for stable@ details)

  However both bionic and xenial/hwe has much less fuse patches applied:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts
  

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

[Andrea Righi]

I'll take a look at the other patches, I think they can be easily
applied to 4.15 if they don't require too much backporting work.

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a later kernel
  (please see got log without --oneline for stable@ details)

  However both bionic and xenial/hwe has much less fuse patches applied:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: 

[Kernel-packages] [Bug 1776563]

[erikjohansson]

Maybe it worked with kernel 4.19 with your distribution but touchpad didn't 
work for me since i only use vanilla kernels without patches.
Ubuntu patches i2c-amd-mp2 support, in older kernel series there was an older 
version that didn't work for many laptop users that needed to recompile the 
kernel without that module built in and add the support later, but maybe it 
works with A315-41 laptops.
In later ubuntu kernels series the i2c-amd-mp2 support is built as a module =m 
instead so it can stopped from loading, in 4.19 it's still compiled into the 
kernel =y for both x86_64 and i386 in the kernel config but in 5.0 it's 
compiled as a module =m for x86_64 but not at all for i386 (source 
https://kernel.ubuntu.com/~kernel-ppa/mainline).
If that patched support makes your touchpad work good with ubuntu then good for 
you but not everyone is a ubuntu user.
For vanilla kernels the touchpad support is supposed to land in mainline in 
kernel 5.2.

It's very easy for people using certain distributions to think that because 
something works that it's works for everyone, not taking into account the 
distributions extensive patching and fixes everywhere but also hardware 
variations.
I use vanilla kernels not patched ones.
I just tried a non patched 4.19 kernel with those options and it did boot, i 
was also able to get touchpad working with dkms i2c-amd-mp2, so things seems to 
work with 4.19 as well.
If your distribution use patched kernels you might have had some support with 
earlier kernels, not because of the linux kernel but rather your distributions 
patches, so kernel updates might be different with different distributions or 
if you use a vanilla kernel.

Battery draining, i don't have any drainage battery problems that i am aware 
of, yesterday i used my laptop for 3 hours on battery, working, looking some 
youtube, some video from hdd and 25-30minutes of compiling.
I think that the battery uptime is acceptable and i got almost 3h with 4.19 as 
well but then i didn't compile anything.
I got no idea how long the battery should last but 3h seems ok to me.
How fast do your battery drain?

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1747463]

[nickel]

(In reply to Alex Deucher from comment #25)
> Does booting with amdgpu.runpm=0 on the kernel command line help?

Yes it does. System is able to boot and no filesystem corruption occurs
either.

So which solution is preferable in such case then?

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-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/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1747463]

[nickel]

Created attachment 282309
dmesg for HP laptop 17-ak041ur with amdgpu.runpm=0 kernel parameter

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-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/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1824407] [NEW] why does booting any livefs squashfs has kernel complaining about unable to read metadata something rather

[Dimitri John Ledkov]

Public bug reported:

Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: squashfs_read_data failed 
to read block 0x6ff3660032757063
Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff3660032757063]
Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: squashfs_read_data failed 
to read block 0x6261746d79732e
Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6261746d79732e]
Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: squashfs_read_data failed 
to read block 0x6ff366df00333a37
Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff366df00333a37]

Happens when booting e.g. subiquity disco image. v5.0.0-8-generic kernel

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

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

Title:
   why does booting any livefs squashfs has kernel complaining about
  unable to read metadata something rather

Status in linux package in Ubuntu:
  New

Bug description:
  Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6ff3660032757063
  Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff3660032757063]
  Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6261746d79732e
  Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6261746d79732e]
  Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6ff366df00333a37
  Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff366df00333a37]

  Happens when booting e.g. subiquity disco image. v5.0.0-8-generic
  kernel

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

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

[Kernel-packages] [Bug 1824378] Re: linux-kvm: 5.0.0-1003.3 -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: 1824383
- phase: Holding before Packaging
- phase-changed: Thursday, 11. April 2019 15:42 UTC
+ phase: Packaging
+ phase-changed: Thursday, 11. April 2019 18:40 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

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

Title:
  linux-kvm: 5.0.0-1003.3 -proposed tracker

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

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:40 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs

[Server Team CI bot]

This bug is fixed with commit 08bf6ff7 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=08bf6ff7


** Changed in: curtin
   Status: Confirmed => Fix Committed

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

Title:
  symlinks managed by kernel postinst are different from zipl-installer
  and livefs-rootfs

Status in curtin:
  Fix Committed
Status in subiquity:
  Confirmed
Status in base-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in zipl-installer package in Ubuntu:
  Fix Released

Bug description:
  
  On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the 
"installer". It is currently done by base-installer/live-installer/ubiquity but 
not curtin, but it should be. At the moment we require kernel-img.conf and we 
do not have the correct per-arch built-in defaults for its settings in all of 
our kernels. It is not a config file, nor is it created by livecd-rootfs (after 
all our squashfs might be containers, and never live to install kernels and 
bootloaders).

  One day we might fix our kernels to not require kernel-img.conf, but
  until then curtin should be generating the right one. Making a merge
  proposal to fix this in curtin by mimicking what base-installer did.

  ==

  Symlinks are not managed correctly.

  Last installed and configured kernel, prior to purging -5- was -6-,
  yet symlinks were not updated to -6- when that happened.

  root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5 
linux-headers-4.3.0-5-generic linux-image-4.3.0-5-generic 
linux-image-extra-4.3.0-5-generic
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.3.0-5* linux-headers-4.3.0-5-generic* 
linux-image-4.3.0-5-generic*
    linux-image-extra-4.3.0-5-generic*
  0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
  After this operation, 131 MB disk space will be freed.
  Do you want to continue? [Y/n] Y
  (Reading database ... 92073 files and directories currently installed.)
  Removing linux-headers-4.3.0-5-generic (4.3.0-5.16) ...
  Removing linux-headers-4.3.0-5 (4.3.0-5.16) ...
  Removing linux-image-extra-4.3.0-5-generic (4.3.0-5.16) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-5-generic 
/boot/vmlinuz-4.3.0-5-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-5-generic 
/boot/vmlinuz-4.3.0-5-generic
  update-initramfs: Generating /boot/initrd.img-4.3.0-5-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot/'
  Building menu 'zipl-automatic-menu'
  Adding #1: IPL section 'ubuntu' (default)
  Preparing boot device: dasda (0200).
  Done.
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-5-generic 
/boot/vmlinuz-4.3.0-5-generic
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 4.3.0-5-generic 
/boot/vmlinuz-4.3.0-5-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot/'
  Building menu 'zipl-automatic-menu'
  Adding #1: IPL section 'ubuntu' (default)
  Preparing boot device: dasda (0200).
  Done.
  Purging configuration files for linux-image-extra-4.3.0-5-generic 
(4.3.0-5.16) ...
  Removing linux-image-4.3.0-5-generic (4.3.0-5.16) ...
  WARN: Proceeding with removing running kernel image.
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.3.0-5-generic 
/boot/vmlinuz-4.3.0-5-generic
  update-initramfs: Deleting /boot/initrd.img-4.3.0-5-generic
  run-parts: executing /etc/kernel/postrm.d/zz-zipl 4.3.0-5-generic 
/boot/vmlinuz-4.3.0-5-generic
  Using config file '/etc/zipl.conf'
  Error: Image file '/boot/vmlinuz' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/kernel/postrm.d/zz-zipl exited with return code 1
  Failed to process /etc/kernel/postrm.d at 
/var/lib/dpkg/info/linux-image-4.3.0-5-generic.postrm line 328.
  dpkg: error processing package linux-image-4.3.0-5-generic (--purge):
   subprocess installed post-removal script returned error exit status 1
  Errors were encountered while processing:
   linux-image-4.3.0-5-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@devac03:~# ls -latr /boot
  total 24208
  drwx--  2 root root16384 Dec  9 16:38 lost+found
  lrwxrwxrwx  1 root root   26 Jan  6 16:23 initrd.img -> 
initrd.img-4.3.0-5-generic
  lrwxrwxrwx  1 root root   23 Jan  6 16:24 vmlinuz -> 
vmlinuz-4.3.0-5-generic
  -rw---  1 root root 13026048 Jan 11 21:36 vmlinuz-4.3.0-6-generic
  -rw---  1 root root  2446124 Jan 11 21:36 System.map-4.3.0-6-generic
  -rw-r--r--  1 root root63422 Jan 11 21:36 config-4.3.0-6-generic
  -rw-r--r--  1 root root   517933 Jan 11 

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Kalin Stoyanov]

These work on 18.04 (suspend/resume etc.), and so far don't cause the
performance hit I get with ivrs. Will use the laptop some more tomorrow
and see how it goes.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Georgi Georgiev]

kmod (25-1ubuntu3) disco; urgency=medium

  * Drop i2c_i801 from the blacklist again, things work fine with
current kernels. (LP: #1786574)

 -- Timo Aaltonen   Thu, 04 Apr 2019 11:30:14 +0300

...

The above fixed it for me.

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

[Valentin Manea]

I think it's your kernel, I never shut it down after the upgrade and it
has this build date: 4.15.0-47-generic #50 SMP Mon Mar 25 15:56:04 CST
2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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

[Kernel-packages] [Bug 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 5.0.0-1003.3 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux-kvm: 5.0.0-1003.3 -proposed tracker

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

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: 1824383
  phase: Holding before Packaging
  phase-changed: Thursday, 11. April 2019 15:42 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

[Alexander Mikhalitsyn]

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

@paelzer,
>If anything it might be only (or more likely) showing up when the laptop is 
>docked - but I don#t see >how that would happen.
you are completely right!
After you comment I've made detailed experiments with that. And on my ASUS 
VivoBook Pro with Intel 8265 problem will appearing quickly after I've put 
something under my laptop (cooling dock, any another metal thing). As I think 
problem is in signal power settings in driver or something similar. Device is 
affected by interference of electromagnetic waves that radiated by themself...

Very interesting fact that in Windows 10 with standard drivers all works
fine in the same conditions...

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -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: 1824383
- phase: Holding before Packaging
- phase-changed: Thursday, 11. April 2019 15:42 UTC
+ phase: Packaging
+ phase-changed: Thursday, 11. April 2019 18:10 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-gcp: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 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

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

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

[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -proposed tracker

[Seth Forshee]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 5.0.0-1003.3 -proposed tracker

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

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

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-gcp: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 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

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

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

[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

[Kai-Heng Feng]

Does the system recently get update? My test kernel was -47 and it may
be replaced by official kernel, which also has -47 suffix.

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Aroiu Ovidiu]

Hello. New kernel parameters to try:

i8042.nopnp
acpi_osi=!
acpi_osi=\"Windows 2009\" (in grub cfg)
acpi_backlight=vendor

Tested on kdeneon and ubuntu 19.04.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.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
  
  derivatives: bug 1822789 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-candidate: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -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-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:
  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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => 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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 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
-   snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta'
-   snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge'
+   snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
+ arch=amd64:channel=latest/candidate:rev=66'
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.4.0-1080.90 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 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
snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
  arch=amd64:channel=latest/candidate:rev=66'
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823216] Re: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG:

[Liz Fong-Jones]

(our other option is going straight to 18.04 but that's a much larger
change to test...

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

Title:
  [trusty] 3.13.0-167-generic repeatedly trips kernel paging request
  BUG:

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  While trying to diagnose a problem with getting a kernel BUG: Bad page
  map in process retriever (retriever is the name of our serving
  binary), causing the serving binary to crash, we tried upgrading from
  3.13.0-121-generic to 3.13.0-167-generic and instead started more
  regularly tripping a different bug that hardlocks the system when we
  attempt to stop & restart the affected process.

  We are running Trusty on AWS in i3.xlarge instances.

  BUG: unable to handle kernel paging request at eaf0
  [89149.537277] IP: [] _raw_spin_lock+0xe/0x50
  [89149.543462] PGD 0
  [89149.545919] Oops: 0002 [#1] SMP
  [89149.549887] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [89149.574925] CPU: 3 PID: 21681 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [89149.583168] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [89149.589649] task: 8807f2f7e000 ti: 88015b674000 task.ti: 
88015b674000
  [89149.597338] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [89149.605845] RSP: :88015b675d88  EFLAGS: 00010206
  [89149.611431] RAX: 0002 RBX: 00c0dee00020 RCX: 
f000cf53
  [89149.618873] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [89149.626336] RBP: 88015b675d88 R08: 3fe0 R09: 
00a9
  [89149.633705] R10:  R11: f000ff53f000ff53 R12: 
880037471900
  [89149.641019] R13: 8807f49c57b8 R14: 8807f2eb2680 R15: 
eaf0
  [89149.648287] FS:  7f92262dd700() GS:88081fc6() 
knlGS:
  [89149.657764] CS:  0010 DS:  ES:  CR0: 80050033
  [89149.664294] CR2: eaf0 CR3: 0007f438 CR4: 
00160670
  [89149.672158] DR0:  DR1:  DR2: 

  [89149.680246] DR3:  DR6: fffe0ff0 DR7: 
0400
  [89149.688126] Stack:
  [89149.690903]  88015b675e20 811831fe 81e85225 
8807f2eb2680
  [89149.700310]  88015b675f20 88015b675e10 0007 
f000cf53
  [89149.709739]  00a9 f000ff53f000ff53 8800 
8003
  [89149.719331] Call Trace:
  [89149.722581]  [] handle_mm_fault+0x27e/0xfb0
  [89149.729984]  [] __do_page_fault+0x183/0x570
  [89149.737506]  [] ? do_futex+0x10a/0x760
  [89149.744529]  [] ? set_next_entity+0x95/0xb0
  [89149.752059]  [] ? pick_next_task_fair+0x5f/0x1b0
  [89149.76]  [] ? sched_clock_cpu+0xb5/0x100
  [89149.767489]  [] do_page_fault+0x1a/0x70
  [89149.774460]  [] page_fault+0x28/0x30
  [89149.781134] Code: 00 00 55 48 89 e5 f0 81 07 00 00 10 00 48 89 f7 57 9d 0f 
1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00  0f 
c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7
  [89149.820963] RIP  [] _raw_spin_lock+0xe/0x50
  [89149.828646]  RSP 
  [89149.833460] CR2: eaf0
  [89149.843886] ---[ end trace 5e5ae13dbb1d0f6e ]---

  BUG: unable to handle kernel paging request at eaf0
  [66384.498399] IP: [] _raw_spin_lock+0xe/0x50
  [66384.502611] PGD 0
  [66384.504586] Oops: 0002 [#1] SMP
  [66384.507578] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [66384.525392] CPU: 1 PID: 21144 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [66384.531418] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [66384.535812] task: 88074a9a9800 ti: 8807f411e000 task.ti: 
8807f411e000
  [66384.542092] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [66384.548699] RSP: :8807f411fd88  EFLAGS: 00010206
  [66384.552560] RAX: 0002 RBX: 00c2b0c0 RCX: 
f000cf53
  [66384.557499] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [66384.562419] RBP: 8807f411fd88 R08: 3fe0 R09: 
00a9
  [66384.567450] R10:  R11: f000ff53f000ff53 R12: 
8807f4af9f00
  [66384.572935] R13: 8807f2ed9c30 R14: 8807f3ee2680 R15: 
eaf0
  [66384.578165] FS:  7f9886ac4700() GS:88081fc2() 
knlGS:
  [66384.584224] CS:  0010 DS:  ES:  CR0: 80050033
  [66384.588318] CR2: eaf0 

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Kai-Heng Feng]

Is gnome-bluetooth up-to-date? See LP: #1822533.

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep)
  Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done.
  Apr 02 13:39:59 taplop kernel: Freezing 

[Kernel-packages] [Bug 1823216] Re: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG:

[Liz Fong-Jones]

Yup, I'm happy to try the HWE kernel. I'll do that and report back.

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

Title:
  [trusty] 3.13.0-167-generic repeatedly trips kernel paging request
  BUG:

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  While trying to diagnose a problem with getting a kernel BUG: Bad page
  map in process retriever (retriever is the name of our serving
  binary), causing the serving binary to crash, we tried upgrading from
  3.13.0-121-generic to 3.13.0-167-generic and instead started more
  regularly tripping a different bug that hardlocks the system when we
  attempt to stop & restart the affected process.

  We are running Trusty on AWS in i3.xlarge instances.

  BUG: unable to handle kernel paging request at eaf0
  [89149.537277] IP: [] _raw_spin_lock+0xe/0x50
  [89149.543462] PGD 0
  [89149.545919] Oops: 0002 [#1] SMP
  [89149.549887] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [89149.574925] CPU: 3 PID: 21681 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [89149.583168] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [89149.589649] task: 8807f2f7e000 ti: 88015b674000 task.ti: 
88015b674000
  [89149.597338] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [89149.605845] RSP: :88015b675d88  EFLAGS: 00010206
  [89149.611431] RAX: 0002 RBX: 00c0dee00020 RCX: 
f000cf53
  [89149.618873] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [89149.626336] RBP: 88015b675d88 R08: 3fe0 R09: 
00a9
  [89149.633705] R10:  R11: f000ff53f000ff53 R12: 
880037471900
  [89149.641019] R13: 8807f49c57b8 R14: 8807f2eb2680 R15: 
eaf0
  [89149.648287] FS:  7f92262dd700() GS:88081fc6() 
knlGS:
  [89149.657764] CS:  0010 DS:  ES:  CR0: 80050033
  [89149.664294] CR2: eaf0 CR3: 0007f438 CR4: 
00160670
  [89149.672158] DR0:  DR1:  DR2: 

  [89149.680246] DR3:  DR6: fffe0ff0 DR7: 
0400
  [89149.688126] Stack:
  [89149.690903]  88015b675e20 811831fe 81e85225 
8807f2eb2680
  [89149.700310]  88015b675f20 88015b675e10 0007 
f000cf53
  [89149.709739]  00a9 f000ff53f000ff53 8800 
8003
  [89149.719331] Call Trace:
  [89149.722581]  [] handle_mm_fault+0x27e/0xfb0
  [89149.729984]  [] __do_page_fault+0x183/0x570
  [89149.737506]  [] ? do_futex+0x10a/0x760
  [89149.744529]  [] ? set_next_entity+0x95/0xb0
  [89149.752059]  [] ? pick_next_task_fair+0x5f/0x1b0
  [89149.76]  [] ? sched_clock_cpu+0xb5/0x100
  [89149.767489]  [] do_page_fault+0x1a/0x70
  [89149.774460]  [] page_fault+0x28/0x30
  [89149.781134] Code: 00 00 55 48 89 e5 f0 81 07 00 00 10 00 48 89 f7 57 9d 0f 
1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00  0f 
c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7
  [89149.820963] RIP  [] _raw_spin_lock+0xe/0x50
  [89149.828646]  RSP 
  [89149.833460] CR2: eaf0
  [89149.843886] ---[ end trace 5e5ae13dbb1d0f6e ]---

  BUG: unable to handle kernel paging request at eaf0
  [66384.498399] IP: [] _raw_spin_lock+0xe/0x50
  [66384.502611] PGD 0
  [66384.504586] Oops: 0002 [#1] SMP
  [66384.507578] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [66384.525392] CPU: 1 PID: 21144 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [66384.531418] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [66384.535812] task: 88074a9a9800 ti: 8807f411e000 task.ti: 
8807f411e000
  [66384.542092] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [66384.548699] RSP: :8807f411fd88  EFLAGS: 00010206
  [66384.552560] RAX: 0002 RBX: 00c2b0c0 RCX: 
f000cf53
  [66384.557499] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [66384.562419] RBP: 8807f411fd88 R08: 3fe0 R09: 
00a9
  [66384.567450] R10:  R11: f000ff53f000ff53 R12: 
8807f4af9f00
  [66384.572935] R13: 8807f2ed9c30 R14: 8807f3ee2680 R15: 
eaf0
  [66384.578165] FS:  7f9886ac4700() GS:88081fc2() 
knlGS:
  [66384.584224] CS:  0010 DS:  ES:  CR0: 80050033
  [66384.588318] CR2: eaf0 CR3: 

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -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: 1822834
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 13:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1107.115 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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: 1822834
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 13:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824374] Re: linux-raspi2: 5.0.0-1006.6 -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: 1824383
- phase: Holding before Packaging
- phase-changed: Thursday, 11. April 2019 15:42 UTC
+ phase: Packaging
+ phase-changed: Thursday, 11. April 2019 17:40 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

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

Title:
  linux-raspi2: 5.0.0-1006.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 17:40 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.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
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 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
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-candidate: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1036.38 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 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

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-candidate: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -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
  
  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:08 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
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-candidate: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1042.46 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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

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

  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:08 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: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824376] Re: linux-azure: 5.0.0-1003.3 -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: 1824383
- phase: Holding before Packaging
- phase-changed: Thursday, 11. April 2019 15:42 UTC
+ phase: Packaging
+ phase-changed: Thursday, 11. April 2019 17:40 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-azure: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 17:40 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

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

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

[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -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
  
  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips), bug 1824204 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 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: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-candidate: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-48.51 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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

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

  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips), bug 1824204 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 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: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 15:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1822820
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 15:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -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
  
  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 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: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- Ready
-   snap-release-to-candidate: Pending -- Ready
-   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-146.172 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 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: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824374] Re: linux-raspi2: 5.0.0-1006.6 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux-raspi2:  -proposed tracker
+ linux-raspi2: 5.0.0-1006.6 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux-raspi2: 5.0.0-1006.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Disco:
  New

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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 17:40 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1824376] Re: linux-azure: 5.0.0-1003.3 -proposed tracker

[Seth Forshee]

** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 5.0.0-1003.3 -proposed tracker

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

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

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-azure: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

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: 1824383
  phase: Holding before Packaging
  phase-changed: Thursday, 11. April 2019 15:42 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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

[Kernel-packages] [Bug 1815214] Re: Lenovo T480: throttling CPU issue

[Srinivas Pandruvada]

You marked this for thermald bug.
Can you try this?
#systemctl disable thermald
reboot 
then try to reproduce.

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

Title:
  Lenovo T480: throttling CPU issue

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

Bug description:
  On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
  drastically CPU performance under load.

  Apparently many Lenovo laptops (certified for Ubuntu) are affected.
  The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  There is "hacky" workaround (not compatible with SecureBoot, a Python
  script writing MSR registers periodically) :
  https://github.com/erpalma/throttled

  There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
  /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
  Linux/td-p/4028489

  I confirm the issue affect my machine running the latest kernel
  (4.15.0-45-generic, although bug affects previous releases as well)
  and using the latest firmware from Lenovo (1.19).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   4050 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   4050 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb  8 17:14:17 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (309 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

[Kirill Smelkov]

Andrea, thanks.

What about other fs/fuse/ patches marked as @stable? We have more
problems reported on 4.15.x Ubuntu kernel (see e.g.
https://github.com/hanwen/go-fuse/issues/287) and that is unfortunate
when the fix/patch is known, marked as needed to be applied to stable
kernel, but Ubuntu is not picking those patches up, just because
upstream 4.15 kernel is not LTS release and stopped being updated long
ago, unlike e.g. upstream 4.4 and 4.14 stable releases which are updated
to this day and have all those stable patches I'm talking about.

** Bug watch added: github.com/hanwen/go-fuse/issues #287
   https://github.com/hanwen/go-fuse/issues/287

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

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

   * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
  race condition that leave fuse inode's mutex held, triggering a
  deadlock

   * The problem is that the lock and unlock paths are relying on
  get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to
  be acquired/released, but its value might be set in the lock path and
  unset in the unlock path (leaving the mutex held)

  [Test Case]

   * A test case that triggers the bug almost immediately can be found
  here https://github.com/hanwen/go-fuse/pull/288

  [Fix]

   * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
  fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
  locking path and pass a variable to fuse_unlock_inode() to determine
  if the mutex was acquired or not

  [Regression Potential]

   * Fix has been tested on the affected platform. It is an upstream fix
  that seems to affect only 4.7+ kernels, more exactly in our case only
  Bionic kernels (and derived) are affected. Cosmic and above already
  include this fix. So regression potential is minimal.

  [Original bug report]

  Hello up there,

  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:

  https://git.kernel.org/linus/63576c13bd

  Please see the following go-fuse issue for full details:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562

  The bug is potentially applicable to libfuse users too since libfuse
  by default enables parallel dirops whenever kernel claims support for
  it, which libfuse maintained confirmed:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381

  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:

  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969

  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.

  

  Here is a full list of FUSE patches marked to be needed in stable
  kernels starting from v4.15:

  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache

  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied
  to 4.15.x becuase they cure a problem introduced in a later kernel
  

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -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-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:
  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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration m

[Derk Willem te Bokkel]

okay a previous "fresh install that was crashing plymouth
screen/lightdm/xorg was fixed by copying a known working set of netplan
conf files into  /etc/netplan ..

the 01-netcfg.yaml from the "network install" uses networkd as the
renderer .. with a working network device config.. plus the  01-network-
manager-all.yaml file as well

proof enough?  of some weird interactions between services

now the minimal 01-network-manager-all.yaml on the new installs seems to be 
lacking something ..
although the documentation says it should work .. which it does if your 
graphics start properly .. Wayland (ubuntu install) or amd/ati cards probably 
nvidia too I have not tested

 but if using the current default netplan  and i915 as module NOT listed
in /etc/modules  .. it does not work it crashes and locks up and only a
powerswitch shutdown works .. no reset button on laptop .. no console
access is available either .. so it has taken a bit of time to determine
all this ..

Anybody know how to fix the netplan config in a "generic way" to cure
this issue?



 the only problem is no control over switching  networks .. NetworkManager does 
not seem to have control over the interface started by networkd ..

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
  netplan mis-configuration maybe underlying cause.

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 

[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

[Andrea Righi]

Sent an SRU fix to include 63576c13bd in Bionic.

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ 
+  * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
+ race condition that leave fuse inode's mutex held, triggering a deadlock
+ 
+  * The problem is that the lock and unlock paths are relying on
+ get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to be
+ acquired/released, but its value might be set in the lock path and unset
+ in the unlock path (leaving the mutex held)
+ 
+ [Test Case]
+ 
+  * A test case that triggers the bug almost immediately can be found
+ here https://github.com/hanwen/go-fuse/pull/288
+ 
+ [Fix]
+ 
+  * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
+ fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
+ locking path and pass a variable to fuse_unlock_inode() to determine if
+ the mutex was acquired or not
+ 
+ [Regression Potential]
+ 
+  * Fix has been tested on the affected platform. It is an upstream fix
+ that seems to affect only 4.7+ kernels, more exactly in our case only
+ Bionic kernels (and derived) are affected. Cosmic+ already include this
+ fix. So regression potential is minimal.
+ 
+ [Original bug report]
+ 
  Hello up there,
  
  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:
  
  https://git.kernel.org/linus/63576c13bd
  
  Please see the following go-fuse issue for full details:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562
  
  The bug is potentially applicable to libfuse users too since libfuse by
  default enables parallel dirops whenever kernel claims support for it,
  which libfuse maintained confirmed:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381
  
  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969
  
  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.
  
  
  
- 
- Here is a full list of FUSE patches marked to be needed in stable kernels 
starting from v4.15:
+ Here is a full list of FUSE patches marked to be needed in stable
+ kernels starting from v4.15:
  
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache
  
  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to
  4.15.x becuase they cure a problem introduced in a later kernel (please
  see got log without --oneline for stable@ details)
  
  However both bionic and xenial/hwe has much less fuse patches applied:
  
- 
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts
  1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the 
superblock's namespace or a descendant
  b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems 

[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

Title:
  linux-raspi2: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1822820
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 15:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

Title:
  linux-aws: 4.15.0-1036.38 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 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
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

[Ubuntu Kernel Bot]

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

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

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
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:
  New

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

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

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Thursday, 11. April 2019 07:35 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030

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

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

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

Title:
  linux-raspi2: 4.4.0-1107.115 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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: 1822834
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 13:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  linux-aws: 4.4.0-1080.90 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 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
snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge'
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

Title:
  linux: 4.15.0-48.51 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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

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

  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips), bug 1824204 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 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: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

Title:
  linux-azure: 4.15.0-1042.46 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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

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

  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:08 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
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

[Andy Whitcroft]

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

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

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

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

Title:
  linux-aws: 4.4.0-1080.90 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Wednesday, 10. April 2019 18:38 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
snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge'
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

Title:
  linux: 4.4.0-146.172 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 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: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Joe Barnett]

ok, have added those commands to a /lib/systemd/system-sleep script to
have that happen before suspend and will report back if it helps or not.

It appears that with privacy on, my bt mouse doesn't connect anymore, is
that expected?

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: 

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

Title:
  linux-raspi2: 4.4.0-1107.115 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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: 1822834
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 13:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

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

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -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-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:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => 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
  
  derivatives: bug 1822789 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: Pending -- Ready
+   snap-release-to-candidate: Pending -- Ready
+   snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -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-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:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

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

Title:
  linux-aws: 4.15.0-1036.38 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 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
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

Title:
  linux-raspi2: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1822820
  phase: Signoff
  phase-changed: Thursday, 11. April 2019 15:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable 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:
  New

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

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

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Thursday, 11. April 2019 07:35 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => 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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
+   snap-release-to-beta: Pending -- Ready
+   snap-release-to-candidate: Pending -- Ready
+   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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: 1822808
  phase: Testing
  phase-changed: Thursday, 11. April 2019 12:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
regression-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

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

Title:
  linux-azure: 4.15.0-1042.46 -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-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

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

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

  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:08 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
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

Title:
  linux: 4.4.0-146.172 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 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: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Fix Released => New

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

Title:
  linux: 4.15.0-48.51 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

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

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

  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips), bug 1824204 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 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: Pending -- waiting for signoff
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1820605] Re: linux-azure: 5.0.0-1001.1 -proposed tracker

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1824376
   linux-azure:  -proposed tracker

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

Title:
  linux-azure: 5.0.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
  phase: Ready for Signoff
  phase-changed: Monday, 01. April 2019 11:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => 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
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 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
+   snap-release-to-beta: Pending -- Ready
+   snap-release-to-candidate: Pending -- Ready
+   snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1036.38 -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 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 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
snap-release-to-beta: Pending -- Ready
snap-release-to-candidate: Pending -- Ready
snap-release-to-edge: Pending -- Ready
verification-testing: Ongoing -- testing in progress

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

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