[Kernel-packages] [Bug 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space

[Frank Heimes]

Thx Robert, worked now.
Downloaded and transferred them to Canonical server 'mombin', folder 
~fheimes/1831899

** Changed in: ubuntu-z-systems
   Status: Incomplete => Triaged

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

Title:
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in
  kernel virtual address space

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Robert J. Brenneman  - 2019-05-30 
11:16:45 ==
  ---Problem Description---
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual 
kernel address space
   
  Contact Information = rjbr...@us.ibm.com 
   
  ---uname output---
  Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13   2964 NE1 
   
  ---System Hang---
   z/VM took a VMDUMP and reIPLed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   boot system, start jenkins, let it run a couple days
   
  Stack trace output:
   05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358 
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0 
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8 
  05/29/19 13:24:06   ?<008e87f0>? ext_int_handler+0x134/0x138 
  05/29/19 13:24:06   ?<00102cee>? enabled_wait+0x4e/0xe0 
  05/29/19 13:24:06  (?<1201>? 0x1201)
  05/29/19 13:24:06   ?<0010303a>? arch_cpu_idle+0x32/0x48 
  05/29/19 13:24:06   ?<001c5ae8>? do_idle+0xe8/0x1a8 

   
  Oops output:
   05/29/19 13:24:06  User process fault: interruption code 003b ilc:3 in 
libc-2.23.so?3ffaca0+185000?
  05/29/19 13:24:06  Failing address:  TEID: 0800
  05/29/19 13:24:06  Fault in primary space mode while using user ASCE.
  05/29/19 13:24:06  AS:000710b241c7 R3:0024 
  05/29/19 13:24:06  Unable to handle kernel pointer dereference in virtual 
kernel address space
  05/29/19 13:24:06  Failing address: 03dbe000 TEID: 03dbe403
  05/29/19 13:24:06  Fault in home space mode while using kernel ASCE.
  05/29/19 13:24:06  AS:00ea8007 R3:0024 
  05/29/19 13:24:06  Oops: 003b ilc:3 ?#1? SMP 
  05/29/19 13:24:06  Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_con
  05/29/19 13:24:06   ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 
sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod
  05/29/19 13:24:06  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 
4.15.0-50-generic #54-Ubuntu
  05/29/19 13:24:06  Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0)
  05/29/19 13:24:06  Krnl PSW : dcb002be 72762961 
(__tlb_remove_table+0x56/0xd0)
  05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 
PM:0 RI:0 EA:3
  05/29/19 13:24:06  Krnl GPRS: ffba 02b8 
02b80003 00eacac8
  05/29/19 13:24:06 ffba 00b9 
0700 000a
  05/29/19 13:24:06 0404c001 0007d2fb5c38 
0007cf71fdf0 03dbe000
  05/29/19 13:24:06 03dbe018 008fe740 
0007cf71fd08 0007cf71fcd8
  05/29/19 13:24:06  Krnl Code: 0012b956: ec2c002a027f   clij
%r2,2,12,12b9aa
  05/29/19 13:24:06 0012b95c: ec26001d037e   cij 
%r2,3,6,12b996
  05/29/19 13:24:06#0012b962: 41c0b018   la  
%r12,24(%r11)
  05/29/19 13:24:06>0012b966: e548b008   mvghi   
8(%r11),0
  05/29/19 13:24:06 0012b96c: a7390008   lghi
%r3,8
  05/29/19 13:24:06 0012b970: b904002b   lgr 
%r2,%r11
  05/29/19 13:24:06 0012b974: c0e5000e8f8a   brasl   
%r14,2fd888
  05/29/19 13:24:06 0012b97a: a718   lhi 
%r1,-1
  05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70 
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570 
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358 
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0 
  05/29/19 13:24:06   

[Kernel-packages] [Bug 1824385] Re: Drain battery on lenovo ideapad 100 15ibd intel i5 4288u

[Launchpad Bug Tracker]

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

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

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

Title:
  Drain battery on lenovo ideapad 100 15ibd intel i5 4288u

Status in linux package in Ubuntu:
  Expired

Bug description:
  The battery in laptop lenovo is drain after 1.5 hour when i use only
  chromium and read the text from web on wifi linux mint 19.1 xfce

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

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

[Kernel-packages] [Bug 1832290] [NEW] Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle

[Georgi Georgiev]

Public bug reported:

$ uptime
 12:40:44 up 1 day, 10:56,  1 user,  load average: 4.00, 4.02, 4.00

The load is always reported as higher than 4 even on an idle system.

Seems to be this upstream:
https://github.com/raspberrypi/linux/issues/2881

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9
ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8
Uname: Linux 5.0.0-1009-raspi2 aarch64
ApportVersion: 2.20.10-0ubuntu27
Architecture: arm64
Date: Tue Jun 11 12:33:57 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-raspi2
UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago)

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


** Tags: apport-bug arm64 disco

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

Title:
  Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  $ uptime
   12:40:44 up 1 day, 10:56,  1 user,  load average: 4.00, 4.02, 4.00

  The load is always reported as higher than 4 even on an idle system.

  Seems to be this upstream:
  https://github.com/raspberrypi/linux/issues/2881

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9
  ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8
  Uname: Linux 5.0.0-1009-raspi2 aarch64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  Date: Tue Jun 11 12:33:57 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-raspi2
  UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago)

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

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

[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

[Khaled El Mously]

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

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

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

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Cosmic:
  Fix Committed
Status in linux-kvm source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
  This issue can be verified with test_410_config_lock_down_kernel
  test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, we already have this config enabled in the generic kernel.

  
  == Original bug report ==
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

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

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

[Kernel-packages] [Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog

[nycnikato]

Does anyone know which kernel DOES have this fix so I can upgrade ? This
is an annoyance.

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

Title:
  Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The trackpad is working, but syslog is full of kernel errors regarding
  "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id
  data (ff)" if the trackpad is touched.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlku   1269 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Sep 23 15:48:36 2018
  HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561
  InstallationDate: Installed on 2018-09-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80XR
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5RCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IAP
  dmi.modalias: 
dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP:
  dmi.product.family: ideapad 320-15IAP
  dmi.product.name: 80XR
  dmi.product.version: Lenovo ideapad 320-15IAP
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

Sorry, last comment was posted 3 timex due to bad wrapping and mix of
chars because of that. Fixed now, I've hidden 2 broken comments. Thanks

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Triaged

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

WORKING

This is a comment summarising a bit the statement of work in this bug:

Bellow are the commits (and the merge requests they came from) that I
could identify by the previous comments. Judging by the selected
commits, the intent is to allow MSR supportability to be queried by
guest through CPUID MSR query emulation <-> kvm ioctls interface.
Every feature to be reported has to have its MSR declared for the CPU
type to be used AND the kvm ioctl backend + kernel support (to query
the actual hardware).

(1)

Request is to allow the following features to be reported by QEMU/KVM:

CPUID.(EAX=7H,ECX=0):EDX[26] (Enable/Disable IBRS/IBPB feature flag):

Enumerates support for indirect branch restricted speculation
(IBRS) and the indirect branch predictor barrier (IBPB).
Processors that set this bit support the IA32_SPEC_CTRL MSR and
the IA32_PRED_CMD MSR. They allow software to set
IA32_SPEC_CTRL[0] (IBRS) and IA32_PRED_CMD[0] (IBPB).

and

CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)

   Enumerates support for the IA32_ARCH_CAPABILITIES MSR, allowing
   MSR index 10AH to be read:

   - (bit 0) RDCL_NO: not susceptible to rogue data cache bit 1)
   - (IBRS_ALL: processor supports IBRS bit 2) RSBA: processor
   - (supports RSB alternate (if retpoline off) bit 3)
   - (SKIP_L1DFL_VMENTRY: vm entry don't need to flush L1D on VM
   - (entry bit 4) SSB_NO: processor not susceptible to spec store
   - (bypass

(2)

There is *no current request* to allow following features to be
reported by EAX_7H_ECX_0_EDX QEMU/KVM right now:

* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.

OBS: I haven't checked patch dependencies yet, not sure if more
patches are needed yet, just realized that SSBD support flag wasn't
being asked to be backported (nor present in 2.11 version, Bionic
version which we are targetting this to). That explains the small
"statement of work" above.

For now the request was fully understood: I'll work tomorrow in a
backport attempt to check if big pieces in between 2.11 and something
around the v3.0.0-152-g8c80c99fcc .. v4.0.0-rc0-2-g014018e19b range
are missing that would require a major refactoring that would not be
possible to be done.

(3)

Possible points of pain:

- arch_capabilities unmigratable flag inside cpu data structure
  (while CPUID was being developed) turned later on into migratable
  later. 

- data structure changes to support MSR based features.

QEMU:

 MERGE REQUEST

21ee4787e53367590f284915bf4c30c684e65bdf
174a78a8a5c0cf421236fe14efc5559717f050df
bb4928c7cafe50ab2137a0034e350ef1bfa044d9
014018e19b3c54dd1bf5072bc912ceffea40abe8 +
485b1d256bcb0874bcde0223727c159b6837e6f8 +

commit 014018e19b3c54dd1bf5072bc912ceffea40abe8 (v4.0.0-rc0-2-g014018e19b)
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:06 2019

i386: Make arch_capabilities migratable

Now that kvm_arch_get_supported_cpuid() will only return
arch_capabilities if QEMU is able to initialize the MSR properly,
we know that the feature is safely migratable.

Signed-off-by: Eduardo Habkost 
Message-Id: <20190125220606.4864-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost 



commit 485b1d256bcb0874bcde0223727c159b6837e6f8 (v4.0.0-rc0-1-g485b1d256b)
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:05 2019

i386: kvm: Disable arch_capabilities if MSR can't be set

KVM has two bugs in the handling of MSR_IA32_ARCH_CAPABILITIES:

1) Linux commit commit 1eaafe91a0df ("kvm: x86: IA32_ARCH_CAPABILITIES
   is always supported") makes GET_SUPPORTED_CPUID return
   arch_capabilities even if running on SVM.  This makes "-cpu
   host,migratable=off" incorrectly expose arch_capabilities on CPUID on
   AMD hosts (where the MSR is not emulated by KVM).

2) KVM_GET_MSR_INDEX_LIST does not return MSR_IA32_ARCH_CAPABILITIES if
   the MSR is not supported by the host CPU.  This makes QEMU not
   initialize the MSR properly at kvm_put_msrs() on those hosts.

Work around both bugs on the QEMU side, by checking if the MSR
was returned by KVM_GET_MSR_INDEX_LIST before returning the
feature flag on kvm_arch_get_supported_cpuid().

This has the unfortunate side effect of making arch_capabilities
unavailable on hosts without hardware support for the MSR until bug #2
is fixed on KVM, but I can't see another way to work around bug #1
without that side effect.

Signed-off-by: Eduardo Habkost 
Message-Id: <20190125220606.4864-2-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost 



 possibly just one:

commit b0a1980384fc265d91de7e09aa5fe531a69e6288 (v3.1.0-1228-gb0a1980384)
Author: Tao Xu 
Date:   Thu Dec 27 00:43:03 2018

i386: Update stepping of Cascadelake-Server

Update the stepping from 5 to 6, in order that
the Cascadelake-Server CPU model can support 

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

WORKING

This is a comment summarising a bit the statement of work in this bug:

Bellow are the commits (and the merge requests they came from) that I
could identify by the previous comments. Judging by the selected
commits, the intent is to allow MSR supportability to be queried by
guest through CPUID MSR query emulation <-> kvm ioctls interface.
Every feature to be reported has to have its MSR declared for the CPU
type to be used AND the kvm ioctl backend + kernel support (to query
the actual hardware).

(1)

Request is to allow the following features to be reported by QEMU/KVM:

CPUID.(EAX=7H,ECX=0):EDX[26] (Enable/Disable IBRS/IBPB feature flag):

Enumerates support for indirect branch restricted speculation
(IBRS) and the indirect branch predictor barrier (IBPB).
Processors that set this bit support the IA32_SPEC_CTRL MSR and
the IA32_PRED_CMD MSR. They allow software to set
IA32_SPEC_CTRL[0] (IBRS) and IA32_PRED_CMD[0] (IBPB).

and

CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)

   Enumerates support for the IA32_ARCH_CAPABILITIES MSR, allowing
   MSR index 10AH to be read:

   - (bit 0) RDCL_NO: not susceptible to rogue data cache
   - (bit 1) IBRS_ALL: processor supports IBRS
   - (bit 2) RSBA: processor supports RSB alternate (retpol off)
   - (bit 3) SKIP_L1DFL_VMENTRY: vm entry don't flush L1D on VM entry
   - (bit 4) SSB_NO: processor not susceptible to spec store bypass

(2)

There is *no current request* to allow following features to be
reported by EAX_7H_ECX_0_EDX QEMU/KVM right now:

* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.

OBS: I haven't checked patch dependencies yet, not sure if more
patches are needed yet, just realized that SSBD support flag wasn't
being asked to be backported (nor present in 2.11 version, Bionic
version which we are targetting this to). That explains the small
"statement of work" above.

For now the request was fully understood: I'll work tomorrow in a
backport attempt to check if big pieces in between 2.11 and something
around the v3.0.0-152-g8c80c99fcc .. v4.0.0-rc0-2-g014018e19b range
are missing that would require a major refactoring that would not be
possible to be done.

(3)

Possible points of pain:

- arch_capabilities unmigratable flag inside cpu data structure
  (while CPUID was being developed) turned later on into migratable
  later. 

- data structure changes to support MSR based features.

QEMU:

 MERGE REQUEST

21ee4787e53367590f284915bf4c30c684e65bdf
174a78a8a5c0cf421236fe14efc5559717f050df
bb4928c7cafe50ab2137a0034e350ef1bfa044d9
014018e19b3c54dd1bf5072bc912ceffea40abe8 +
485b1d256bcb0874bcde0223727c159b6837e6f8 +

commit 014018e19b3c54dd1bf5072bc912ceffea40abe8 - v4.0.0-rc0-2-g014018e19b
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:06 2019

i386: Make arch_capabilities migratable

Now that kvm_arch_get_supported_cpuid() will only return
arch_capabilities if QEMU is able to initialize the MSR properly,
we know that the feature is safely migratable.

Signed-off-by: Eduardo Habkost 
Message-Id: <20190125220606.4864-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost 



commit 485b1d256bcb0874bcde0223727c159b6837e6f8 - v4.0.0-rc0-1-g485b1d256b
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:05 2019

i386: kvm: Disable arch_capabilities if MSR can't be set

KVM has two bugs in the handling of MSR_IA32_ARCH_CAPABILITIES:

1) Linux commit commit 1eaafe91a0df ("kvm: x86:
IA32_ARCH_CAPABILITIES is always supported") makes
GET_SUPPORTED_CPUID return arch_capabilities even if running on
SVM.  This makes "-cpu host,migratable=off" incorrectly expose
arch_capabilities on CPUID on AMD hosts (where the MSR is not
emulated by KVM).

2) KVM_GET_MSR_INDEX_LIST does not return
MSR_IA32_ARCH_CAPABILITIES if the MSR is not supported by the
host CPU.  This makes QEMU not initialize the MSR properly at
kvm_put_msrs() on those hosts.

Work around both bugs on the QEMU side, by checking if the MSR
was returned by KVM_GET_MSR_INDEX_LIST before returning the
feature flag on kvm_arch_get_supported_cpuid().

This has the unfortunate side effect of making arch_capabilities
unavailable on hosts without hardware support for the MSR until
bug #2 is fixed on KVM, but I can't see another way to work
around bug #1 without that side effect.

Signed-off-by: Eduardo Habkost 
Message-Id: <20190125220606.4864-2-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost 



 possibly just one:

commit b0a1980384fc265d91de7e09aa5fe531a69e6288 - v3.1.0-1228-gb0a1980384
Author: Tao Xu 
Date:   Thu Dec 27 00:43:03 2018

i386: Update stepping of Cascadelake-Server

Update the stepping from 5 to 6, in order that
the Cascadelake-Server CPU model can support AVX512VNNI
and MSR based 

[Kernel-packages] [Bug 1832184] Re: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel module failed to build

[Daniel van Vugt]

during RTL pass: cprop
/var/lib/dkms/nvidia/390.116/build/nvidia-uvm/uvm8_page_tree_test.c: In 
function ‘alloc_64k_memory_kepler’:
/var/lib/dkms/nvidia/390.116/build/nvidia-uvm/uvm8_page_tree_test.c:1112:1: 
internal compiler error: Naruszenie ochrony pamięci
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.


** Package changed: nvidia-graphics-drivers-390 (Ubuntu) => gcc-8 (Ubuntu)

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

Title:
  nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel
  module failed to build

Status in gcc-8 package in Ubuntu:
  New

Bug description:
  Bug showed up during normal upgrade process.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  DKMSKernelVersion: 4.18.0-16-generic
  Date: Mon Jun 10 10:21:53 2019
  Dependencies:
   
  InstallationDate: Installed on 2016-07-16 (1058 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageVersion: 390.116-0ubuntu0.18.10.1
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.5
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel 
module failed to build
  UpgradeStatus: Upgraded to cosmic on 2018-12-10 (182 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1832184/+subscriptions

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

This is a comment summarising a bit the statement of work in this bug:

Bellow are the commits (and the merge requests they came from) that I could
identify by the previous comments. Judging by the selected commits, the intent
is to allow MSR supportability to be queried by guest through CPUID MSR query
emulation <-> kvm ioctls interface. Every feature to be reported has to have
its MSR declared for the CPU type to be used AND the kvm ioctl backend +
kernel support (to query the actual hardware).

(1)

Request is to allow the following features to be reported by QEMU/KVM:

CPUID.(EAX=7H,ECX=0):EDX[26] (Enable/Disable IBRS/IBPB feature flag):

Enumerates support for indirect branch restricted speculation (IBRS) and
the indirect branch predictor barrier (IBPB). Processors that set this bit
support the IA32_SPEC_CTRL MSR and the IA32_PRED_CMD MSR. They allow
software to set IA32_SPEC_CTRL[0] (IBRS) and IA32_PRED_CMD[0] (IBPB).

and

CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)

   Enumerates support for the IA32_ARCH_CAPABILITIES MSR, allowing MSR index
   10AH to be read:

   - (bit 0) RDCL_NO: not susceptible to rogue data cache
   - (bit 1) IBRS_ALL: processor supports IBRS
   - (bit 2) RSBA: processor supports RSB alternate (if retpoline off)
   - (bit 3) SKIP_L1DFL_VMENTRY: vm entry don't need to flush L1D on VM entry
   - (bit 4) SSB_NO: processor not susceptible to spec store bypass

(2)

There is *no current request* to allow following features to be reported by
EAX_7H_ECX_0_EDX QEMU/KVM right now:

* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.

OBS: I haven't checked patch dependencies yet, not sure if more patches are
needed yet, just realized that SSBD support flag wasn't being asked to be
backported (nor present in 2.11 version, Bionic version which we are
targeting this to). That explains the small "statement of work" above.

For now the request was fully understood: I'll work tomorrow in a backport
attempt to check if big pieces in between 2.11 and something around the
v3.0.0-152-g8c80c99fcc..v4.0.0-rc0-2-g014018e19b range are missing that would
require a major refactoring that would not be possible to be done.

(3)

Possible points of pain:

- arch_capabilities non migratable flag inside cpu data structure
  (while CPUID was being developed) turned later on into migratable
  later. 

- data structure changes to support MSR based features.

QEMU:

 MERGE REQUEST

21ee4787e53367590f284915bf4c30c684e65bdf
174a78a8a5c0cf421236fe14efc5559717f050df
bb4928c7cafe50ab2137a0034e350ef1bfa044d9
014018e19b3c54dd1bf5072bc912ceffea40abe8 +
485b1d256bcb0874bcde0223727c159b6837e6f8 +

commit 014018e19b3c54dd1bf5072bc912ceffea40abe8 (v4.0.0-rc0-2-g014018e19b)
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:06 2019

i386: Make arch_capabilities migratable

Now that kvm_arch_get_supported_cpuid() will only return
arch_capabilities if QEMU is able to initialize the MSR properly,
we know that the feature is safely migratable.

Signed-off-by: Eduardo Habkost 
Message-Id: <20190125220606.4864-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost 



commit 485b1d256bcb0874bcde0223727c159b6837e6f8 (v4.0.0-rc0-1-g485b1d256b)
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:05 2019

i386: kvm: Disable arch_capabilities if MSR can't be set

KVM has two bugs in the handling of MSR_IA32_ARCH_CAPABILITIES:

1) Linux commit commit 1eaafe91a0df ("kvm: x86: IA32_ARCH_CAPABILITIES
   is always supported") makes GET_SUPPORTED_CPUID return
   arch_capabilities even if running on SVM.  This makes "-cpu
   host,migratable=off" incorrectly expose arch_capabilities on CPUID on
   AMD hosts (where the MSR is not emulated by KVM).

2) KVM_GET_MSR_INDEX_LIST does not return MSR_IA32_ARCH_CAPABILITIES if
   the MSR is not supported by the host CPU.  This makes QEMU not
   initialize the MSR properly at kvm_put_msrs() on those hosts.

Work around both bugs on the QEMU side, by checking if the MSR
was returned by KVM_GET_MSR_INDEX_LIST before returning the
feature flag on kvm_arch_get_supported_cpuid().

This has the unfortunate side effect of making arch_capabilities
unavailable on hosts without hardware support for the MSR until bug #2
is fixed on KVM, but I can't see another way to work around bug #1
without that side effect.

Signed-off-by: Eduardo Habkost 
Message-Id: <20190125220606.4864-2-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost 



 possibly just one:

commit b0a1980384fc265d91de7e09aa5fe531a69e6288 (v3.1.0-1228-gb0a1980384)
Author: Tao Xu 
Date:   Thu Dec 27 00:43:03 2018

i386: Update stepping of Cascadelake-Server

Update the stepping from 5 to 6, in order that
the Cascadelake-Server CPU model can support AVX512VNNI
and MSR 

[Kernel-packages] [Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04

[Daniel van Vugt]

Please reproduce the problem again and then immediately run this command
in a Terminal window:

  dmesg > dmesg.txt

That will create a new file called 'dmesg.txt'. We would like you to
then attach that new file to this bug in a new comment.

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

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Kernel-packages] [Bug 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

[Daniel van Vugt]

Thanks. If you could describe the keyboard problem in more detail then
it would help.

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

[VanVan]

Asus vivobook s15 s530uf has the same new BIOS 304 released, You need to test 
it before posting here
https://www.asus.com/za/Laptops/ASUS-VivoBook-S15-S530UF/HelpDesk_BIOS/

-- 
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 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  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.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  shouldn't be any, since this reverts to what was used on kernels before 5.0

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 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

[Muhammad Ruhul Amin]

can't even install Ubuntu 19.04 on Asus vivobook s15 s530uf. Black
screen, even the installer USB stops blinking. But I can install it
using the `safe graphics` option. But when I reboot it gets stuck at the
black screen. Frustrated.

-- 
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 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  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.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  shouldn't be any, since this reverts to what was used on kernels before 5.0

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 1752002] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mranw...@us.ibm.com 2019-06-10 17:45 EDT---
Anju - I tried this with both the 4.15.0-50 kernel (that has the first patch) 
and the test kernel in the above comment and I see the same behavior.  No call 
trace, but on both the test ends:
==
Starting fuzzing at 2019-06-10 16:35:58
==
Watchdog triggered; failed to progress for 60 seconds;  killing
Trying to shut ourselves down: 4986, last child 0

This is on a dd 2.3 witherspoon.  Any ideas?

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

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

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

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

  Warn on message is seen while running perf fuzzer tests.

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

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

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

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

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

[Kernel-packages] [Bug 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373

[Carlos Cesar Caballero Diaz]

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

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

Title:
  Ubuntu 19.04 suspend freeze on Dell inspiron 7373

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 19.04 in my Dell Inspiron 7373 and I am
  getting issues with suspend. When I lock the case or write the
  "systemctl suspend" command, the screen turn off, the system freeze
  and the laptop keeps turned on. I need to force the laptop turn off
  and on again. There are some cases when it suspends without issues,
  but most of the time it freezes.

  There are some workarounds for issues like this one but they are
  mostly for laptops using nvidia graphics.

  I am not sure how to provide debug information about this issue, but I
  can give it if someone tells me how to do it.

  "lsb_release -rd" output:
  Description:Ubuntu 19.04
  Release:19.04

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

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

[Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

[Jeremy]

Boot into Ubuntu 18.04, in terminal check>  mokutil --sb-state
as Secure Boot will need to be disabled
Then do in terminal
sudo apt install git build-essential dkms
git clone https://github.com/jeremyb31/mouse-4.18.git
sudo dkms add ./mouse-4.18
sudo dkms install mouse/1.0

Reboot

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

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  athena 1232 F pulseaudio
   /dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
   /dev/snd/controlC0:  athena 1232 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 81D2
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-21-generic N/A
   linux-backports-modules-4.18.0-21-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.18.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN46WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO

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

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

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  

[Kernel-packages] [Bug 1832101] ProcEnviron.txt

[Poloskey]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1832101/+attachment/5269979/+files/ProcEnviron.txt

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  Jun  8 

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  Jun  8 

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

[Poloskey]

apport information

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
 

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

[Poloskey]

apport information

** Tags added: apport-collected

** Description changed:

  Just installed a fresh installation of ubuntu 19 on our server and we're
  having a lot of carrier-lost erros.
  
  There is no really good indicaton why this is hapening.
  
  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.
  
  Description:Ubuntu 19.04
  Release:19.04
  
  
  Kernel Log
  
  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  Jun  8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 
00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 63 03 00 00 31 ff e8 ba 65 8d ff 
fb 66 0f 1f 44 00 00 <
  45> 85 ed 0f 88 8d 02 00 00 49 63 cd 48 8b 75 d0 48 2b 75 c8 48 8d
  Jun  8 12:11:17 mc2 kernel: [30304.199103] RSP: 0018:bd934635be60 EFLAGS: 
0246 

[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change

[Mike Ranweiler]

Opened issue 1423 on this - unfortunately the boston openpower is
closed.

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

Title:
  hwclock test failed on Power9 due to 0.x sec differences / time out
  waiting for time change

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The hwclock test will fail on the Power9 system "baltar" due to a
  <0.02 second difference.

  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in 
run_once
  raise error.TestFail("Failed to set hwclock back to Warthog's birthday. 
Output of hwclock is '%s'" % date)
  TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock 
is '2004-10-20 04:09:59.582146+'

  Didn't see this on Power8 boxes

  Sometimes it will fail because "time out waiting for time change" on the same 
node:
  $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
  hwclock: Timed out waiting for time change.

  Workaround for these is to add "sleep 1".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:45 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Thu Nov  8 06:03:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3544 00:17:582 0 EOF
   2: POSIX  ADVISORY  WRITE 1798 00:17:338 0 EOF
   3: POSIX  ADVISORY  WRITE 3603 00:17:576 0 EOF
   4: FLOCK  ADVISORY  WRITE 3535 00:17:564 0 EOF
   5: FLOCK  ADVISORY  WRITE 4081 00:17:481 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 1)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

  -- Firmware information on Baltar --
  pnor: P9DSU20190404_IBM_prod_sign.pnor
  bmc: SMT_P9_206.bin

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

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

[Kernel-packages] [Bug 1832238] Re: ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-utils dependencies

[Rafael David Tinoco]

Proposed fix:

https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ubuntu-fan/+git
/ubuntu-fan/+merge/368622

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

Title:
  ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-
  utils dependencies

Status in ubuntu-fan package in Ubuntu:
  In Progress

Bug description:
  
  Whenever running autopkgtests in ubuntu-fan you might hit issues on missing 
dependencies:

  

  Starting fanatic-test
  Remapping container filesystem
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  slave: detected primary route through eth0
  slave: DNS: systemd(250.0.1.1)
  test master: ping test (250.0.1.179) ...
  test slave: ping test (250.0.1.1) ...
  test master: ping test ... PASS
  test master: short data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: ping test ... PASS
  test slave: short data test (250.0.1.179 -> 250.0.1.1) ...
  test master: short data ... PASS
  test master: long data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: short data ... PASS
  test slave: long data test (250.0.1.179 -> 250.0.1.1) ...
  test slave: long data ... PASS
  test master: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  II: Undefining LXD profile for Fan Bridge...
  de-configuring LXD underlay:127.0.0.0/16 overlay:250.0.0.0/8
  Profile fan-250 deleted
  /tmp/autopkgtest.WLlVT9/build.Imn/src/debian/tests/lxd: line 57: ifconfig: 
command not found
  FAIL: No fan-250 left after disable-lxd
  autopkgtest [14:33:37]: test lxd: ---]
  autopkgtest [14:33:37]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd  FAIL non-zero exit status 1
  autopkgtest [14:33:37]:  summary
  docker   FAIL non-zero exit status 1
  lxd  FAIL non-zero exit status 1
  Exit request sent.

  

  autopkgtest [15:24:09]: test lxd: [---
  /tmp/autopkgtest.7u3mm8/build.s4D/src/debian/tests/lxd: line 3: route: 
command not found
  II: Test LXD...
  master: detected primary route through bridge0
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: systemd-resolve failure!
  local lxd test: prepare master failed!
  FAIL: Error on LXD test
  autopkgtest [15:24:40]: test lxd: ---]
  autopkgtest [15:24:40]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd  FAIL non-zero exit status 1

  

  That happens because tests don't explicitly declare bridge-utils and
  net-tools as its dependency and the building/autopkgtest environment
  might not have them installed by default.

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

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

[Kernel-packages] [Bug 1832238] Re: ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-utils dependencies

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ubuntu-fan/+git/ubuntu-fan/+merge/368622

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

Title:
  ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-
  utils dependencies

Status in ubuntu-fan package in Ubuntu:
  In Progress

Bug description:
  
  Whenever running autopkgtests in ubuntu-fan you might hit issues on missing 
dependencies:

  

  Starting fanatic-test
  Remapping container filesystem
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  slave: detected primary route through eth0
  slave: DNS: systemd(250.0.1.1)
  test master: ping test (250.0.1.179) ...
  test slave: ping test (250.0.1.1) ...
  test master: ping test ... PASS
  test master: short data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: ping test ... PASS
  test slave: short data test (250.0.1.179 -> 250.0.1.1) ...
  test master: short data ... PASS
  test master: long data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: short data ... PASS
  test slave: long data test (250.0.1.179 -> 250.0.1.1) ...
  test slave: long data ... PASS
  test master: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  II: Undefining LXD profile for Fan Bridge...
  de-configuring LXD underlay:127.0.0.0/16 overlay:250.0.0.0/8
  Profile fan-250 deleted
  /tmp/autopkgtest.WLlVT9/build.Imn/src/debian/tests/lxd: line 57: ifconfig: 
command not found
  FAIL: No fan-250 left after disable-lxd
  autopkgtest [14:33:37]: test lxd: ---]
  autopkgtest [14:33:37]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd  FAIL non-zero exit status 1
  autopkgtest [14:33:37]:  summary
  docker   FAIL non-zero exit status 1
  lxd  FAIL non-zero exit status 1
  Exit request sent.

  

  autopkgtest [15:24:09]: test lxd: [---
  /tmp/autopkgtest.7u3mm8/build.s4D/src/debian/tests/lxd: line 3: route: 
command not found
  II: Test LXD...
  master: detected primary route through bridge0
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: systemd-resolve failure!
  local lxd test: prepare master failed!
  FAIL: Error on LXD test
  autopkgtest [15:24:40]: test lxd: ---]
  autopkgtest [15:24:40]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd  FAIL non-zero exit status 1

  

  That happens because tests don't explicitly declare bridge-utils and
  net-tools as its dependency and the building/autopkgtest environment
  might not have them installed by default.

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

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

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: 

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

[Brian Murray]

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

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  Jun  8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 
00 74 17 9c 58 0f 1f 44 

[Kernel-packages] [Bug 1832101] [NEW] systemd-networkd: Lost carrier e1000

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Just installed a fresh installation of ubuntu 19 on our server and we're
having a lot of carrier-lost erros.

There is no really good indicaton why this is hapening.

Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
removed netplan, switched to systemd-networkd and added configurewithoutcarrier 
to true, the option ignorecarrierlost is not accepted by systemd.

Description:Ubuntu 19.04
Release:19.04


Kernel Log

Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here ]
Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
 nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel
Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef 
c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 
c2 e8 71 f1 79 ff
 <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
Jun  8 12:11:17 mc2 kernel: [30304.199088]  
Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
Jun  8 12:11:17 mc2 kernel: [30304.199099]  smp_apic_timer_interrupt+0x79/0x140
Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
Jun  8 12:11:17 mc2 kernel: [30304.199101]  
Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
Jun  8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 00 
74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 63 03 00 00 31 ff e8 ba 65 8d ff fb 
66 0f 1f 44 00 00 <
45> 85 ed 0f 88 8d 02 00 00 49 63 cd 48 8b 75 d0 48 2b 75 c8 48 8d
Jun  8 12:11:17 mc2 kernel: [30304.199103] RSP: 0018:bd934635be60 EFLAGS: 
0246 ORIG_RAX: ff13
Jun  8 12:11:17 mc2 kernel: [30304.199104] RAX: 93adff222d80 RBX: 
96153c80 RCX: 001f
Jun  8 12:11:17 

[Kernel-packages] [Bug 1826065] Re: Can't boot from usb live system to install disco dingo 19.04

[dualboot]

Hello,

 I just upgraded my BIOS to 304 version and now it's working as expected. I 
could upgrade the linux kernel
to the latest version provided by Fedora repository and reboot in a normal way.
 I have also tested with Ubuntu 19.04 live usb and now it is working as 
expected. So I have installed
again Ubuntu and could upgraded and worked with it. And Nvivia proprietary 
driver have been installed too and it works till now as expected with a low 
profile (internal Intel GPU, no over heat and fan noise).

  Regards,

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

Title:
  Can't boot from usb live system to install disco dingo 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot boot from a USB live system with Disco Dingo 19.04 to install
  Ubuntu. I tried several kernel command line options (nomodeset
  modprobe.blacklist=nouveau) but nothing seems to work.

  With acpi=off I can see some output. The boot sequence stops at
  "Freeing unused kernel image memory". Before, there are some UEFI
  error messages (Couldn't get UEFI db list, dbx list). I attached a
  photo of the output. I don't get these errors with 18.10.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  cosmic kernel (and above) provides two /dev/videoX device but there
  should be only one video device physically

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since cosmic kernel (4.18) and above, I am aware that there will be
  two /dev/videoX even there is only one device physically. This issue
  could be found in many hardware platforms[1]

  [Steps to Reproduce]

  1. Install Ubuntu desktop image (cosmic or above) on one of the platforms[1]
  2. Check /dev/video*

  [Expected Result]

  There is only /dev/video0 because there is only one video device (the
  default webcam).

  [Actual Result]

  Both of /dev/video0 and /dev/video1 are shown.

  [1] The platforms have this issue:
  Dell Vostro 5568
  Dell OptiPlex 3011 All In One
  Dell Computer Corporation XPS 15 9550
  Dell Latitude E5570
  Dell Vostro 3459
  Dell Vostro 3559
  Lenovo ThinkCentre Edge 62z All In One

  -

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1388 F pulseaudio
  Date: Mon Jun 10 11:20:43 2019
  InstallationDate: Installed on 2018-11-23 (199 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. Vostro 5568
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=89c301bf-b96d-44b3-890f-71987524c021 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-21-generic N/A
   linux-backports-modules-4.18.0-21-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd07/18/2016:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 5568
  dmi.product.sku: 0786
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing

[Dimitri John Ledkov]

tested s390-tools packages on dogfood which look correct.

** Changed in: s390-tools (Ubuntu)
   Status: New => In Progress

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

Title:
  Please add support for zipl signing

Status in Launchpad itself:
  Fix Committed
Status in linux-signed package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  In Progress

Bug description:
  Please add support for zipl ("z/ecureBoot") signing.

  It should be similar to opal signing, but using the new zipl signing
  key.

  I am expecting to sign s390-tools stage3.bin and kernel images using
  this key.

  s390-tools -> can be signed already
  kernels -> should only sign v5.2+

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

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

[Kernel-packages] [Bug 1832238] [NEW] ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-utils dependencies

[Rafael David Tinoco]

Public bug reported:


Whenever running autopkgtests in ubuntu-fan you might hit issues on missing 
dependencies:



Starting fanatic-test
Remapping container filesystem
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
slave: detected primary route through eth0
slave: DNS: systemd(250.0.1.1)
test master: ping test (250.0.1.179) ...
test slave: ping test (250.0.1.1) ...
test master: ping test ... PASS
test master: short data test (250.0.1.1 -> 250.0.1.179) ...
test slave: ping test ... PASS
test slave: short data test (250.0.1.179 -> 250.0.1.1) ...
test master: short data ... PASS
test master: long data test (250.0.1.1 -> 250.0.1.179) ...
test slave: short data ... PASS
test slave: long data test (250.0.1.179 -> 250.0.1.1) ...
test slave: long data ... PASS
test master: long data ... PASS
local lxd test: destroying test container ...
local lxd test: test complete PASS (master=0 slave=0)
II: Undefining LXD profile for Fan Bridge...
de-configuring LXD underlay:127.0.0.0/16 overlay:250.0.0.0/8
Profile fan-250 deleted
/tmp/autopkgtest.WLlVT9/build.Imn/src/debian/tests/lxd: line 57: ifconfig: 
command not found
FAIL: No fan-250 left after disable-lxd
autopkgtest [14:33:37]: test lxd: ---]
autopkgtest [14:33:37]: test lxd:  - - - - - - - - - - results - - - - - - - - 
- -
lxd  FAIL non-zero exit status 1
autopkgtest [14:33:37]:  summary
docker   FAIL non-zero exit status 1
lxd  FAIL non-zero exit status 1
Exit request sent.



autopkgtest [15:24:09]: test lxd: [---
/tmp/autopkgtest.7u3mm8/build.s4D/src/debian/tests/lxd: line 3: route: command 
not found
II: Test LXD...
master: detected primary route through bridge0
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: waiting for systemd resolver...
master: systemd-resolve failure!
local lxd test: prepare master failed!
FAIL: Error on LXD test
autopkgtest [15:24:40]: test lxd: ---]
autopkgtest [15:24:40]: test lxd:  - - - - - - - - - - results - - - - - - - - 
- -
lxd  FAIL non-zero exit status 1



That happens because tests don't explicitly declare bridge-utils and
net-tools as its dependency and the building/autopkgtest environment
might not have them installed by default.

** Affects: ubuntu-fan (Ubuntu)
 Importance: Medium
 Assignee: Rafael David Tinoco (rafaeldtinoco)
 Status: In Progress

** Changed in: ubuntu-fan (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-fan (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

** Changed in: ubuntu-fan (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-
  utils dependencies

Status in ubuntu-fan package in Ubuntu:
  In Progress

Bug description:
  
  Whenever running autopkgtests in ubuntu-fan you might hit issues on missing 
dependencies:

  

  Starting fanatic-test
  Remapping container filesystem
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  slave: detected primary route through eth0
  slave: DNS: systemd(250.0.1.1)
  test master: ping test (250.0.1.179) ...
  test slave: ping test (250.0.1.1) ...
  test master: ping test ... PASS
  test master: short data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: ping test ... PASS
  test slave: short data test (250.0.1.179 -> 250.0.1.1) ...
  test master: short data ... PASS
  test master: long data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: short data ... PASS
  test slave: long data test (250.0.1.179 -> 250.0.1.1) ...
  test slave: long data ... PASS
  test master: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  II: Undefining LXD profile for Fan Bridge...
  de-configuring LXD underlay:127.0.0.0/16 overlay:250.0.0.0/8
  Profile fan-250 deleted
  /tmp/autopkgtest.WLlVT9/build.Imn/src/debian/tests/lxd: 

[Kernel-packages] [Bug 1832239] [NEW] cosmic kernel (and above) provides two /dev/videoX device but there should be only one video device physically

[Taihsiang Ho]

Public bug reported:

Since cosmic kernel (4.18) and above, I am aware that there will be two
/dev/videoX even there is only one device physically. This issue could
be found in many hardware platforms[1]

[Steps to Reproduce]

1. Install Ubuntu desktop image (cosmic or above) on one of the platforms[1]
2. Check /dev/video*

[Expected Result]

There is only /dev/video0 because there is only one video device (the
default webcam).

[Actual Result]

Both of /dev/video0 and /dev/video1 are shown.

[1] The platforms have this issue:
Dell Vostro 5568
Dell OptiPlex 3011 All In One
Dell Computer Corporation XPS 15 9550
Dell Latitude E5570
Dell Vostro 3459
Dell Vostro 3559
Lenovo ThinkCentre Edge 62z All In One

-


ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-21-generic 4.18.0-21.22
ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1388 F pulseaudio
Date: Mon Jun 10 11:20:43 2019
InstallationDate: Installed on 2018-11-23 (199 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Dell Inc. Vostro 5568
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=89c301bf-b96d-44b3-890f-71987524c021 ro
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-21-generic N/A
 linux-backports-modules-4.18.0-21-generic  N/A
 linux-firmware 1.175
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd07/18/2016:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Vostro 5568
dmi.product.sku: 0786
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug cosmic taipei-lab uec-images

** Description changed:

  Since cosmic kernel (4.18) and above, I am aware that there will be two
  /dev/videoX even there is only one device physically. This issue could
  be found in many hardware platforms[1]
  
  [Steps to Reproduce]
  
  1. Install Ubuntu desktop image (cosmic or above) on one of the platforms[1]
  2. Check /dev/video*
  
  [Expected Result]
  
  There is only /dev/video0 because there is only one video device (the
  default webcam).
  
  [Actual Result]
  
  Both of /dev/video0 and /dev/video1 are shown.
  
- 
  [1] The platforms have this issue:
  Dell Vostro 5568
  Dell OptiPlex 3011 All In One
  Dell Computer Corporation XPS 15 9550
  Dell Latitude E5570
  Dell Vostro 3459
  Dell Vostro 3559
  Lenovo ThinkCentre Edge 62z All In One
  
+ -
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ubuntu 1388 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 1388 F pulseaudio
  Date: Mon Jun 10 11:20:43 2019
  InstallationDate: Installed on 2018-11-23 (199 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. Vostro 5568
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=89c301bf-b96d-44b3-890f-71987524c021 ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-21-generic N/A
-  linux-backports-modules-4.18.0-21-generic  N/A
-  linux-firmware 1.175
+  linux-restricted-modules-4.18.0-21-generic N/A
+  linux-backports-modules-4.18.0-21-generic  N/A
+  linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd07/18/2016:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 5568
  dmi.product.sku: 0786
  dmi.sys.vendor: Dell Inc.

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

Title:
  cosmic kernel (and above) provides two /dev/videoX device but there
  should be only one video device physically

Status in linux package in 

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

[Andrea Righi]

Thanks Chris, looking at journalct it seems that from the "Lid closed"
event and "Reached target Sleep" there's just 1s. So, the time between
these two events is also definitely fast, therefore the bottleneck is
not in the part of systemd that processes the "lid closed" event.

At this point I'm wondering if the bottleneck is in the part of systemd
that detects the "lid closed" event. For that we should run the same
loop in a bash session (while :; do echo `date` - `cat
/proc/acpi/button/lid/LID0/state`; sleep 1; done), close the lid and
compare the timestamps of the transition between "open" and "closed" (in
the bash session) with the timestamp of the "Lid closed" event in
journalctl. If they don't match the bottleneck is in systemd not being
able to detect the lid closed event fast enough.

Moreover, in the last comment (#10) you mentioned that things have been
improved. Do you have some numbers (i.e., how many second it needs to
actually go to sleep) or is it just a feeling? Thanks!

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

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

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

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

[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

[Steven Tang]

@cypressyew, I cannot have proof that the same issue occurred with v5.2 rc2 
from your link, as the kernel does not respond to earlyprintk=efi, but it died 
pretty much the same way, and no logs were produced.
As I mentioned earlier, the fix in efi.c is a clear indication of a bug in the 
kernel code. If that isn't sufficient, I'm not sure what is.

The same bug exists in the latest kernel source.
https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack/tree/drivers/firmware/efi/efi.c#n258

That being said, if you could provide me a kernel build that will have
proper logging I could capture, then I can try again. But please,
please, to save us some time, first take a quick look at the source, it
isn't too hard to see if it is a legitimate bug.

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

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

Title:
  kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 
1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can 
no longer boot with the 4.15.0-50 kernel installed with 1804.
  We tried various kernel flags without luck, and installed latest 4.18.0-20 
from HWE and got the same result.
  Unfortunately, no logs are created in /var/logs when the issue happens, and 
we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to 
get a backtrace in a photo.
  The issue happens consistently, i.e. the backtrace looks always the same just 
happens on different cores.
  Attached the boot-info output and the picture taken at the end of the kernel 
loading.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  steventang   2047 F pulseaudio
   /dev/snd/controlC0:  steventang   2047 F pulseaudio
   /dev/snd/controlC1:  steventang   2047 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870
  InstallationDate: Installed on 2019-05-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacPro5,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic 
root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-148-generic N/A
   linux-backports-modules-4.4.0-148-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.4.0-148-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP51.88Z.0084.B00.1708080528
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.name: MacPro5,1
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.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
  
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
-   promote-to-proposed: Pending -- packages copied to Proposed signed:building
+   promote-to-proposed: Pending -- packages copied to Proposed signed:queued

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
promote-to-proposed: Pending -- packages copied to Proposed signed:queued

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

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

[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

[Manoj Iyer]

The kernel propagates the error back if /sys/../uevent file fails to
write. /sys/bus/vio/devices/vio/uevent fails in this case because the
drivers associated with it are:

ubuntu@tiselius:~$ ls /sys/bus/vio/drivers/
hvc_console  tpm_ibmvtpm

On our power systems we do not have the devices associated with the
drive. Looks like these messages are expected, since this is the
expected behavior by the kernel I don't think this is a bug. Could IBM
please confirm that this is indeed the case?

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

Title:
  "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

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

Bug description:
  This bug is created from bug LP #1766201 which reported multiple
  errors in the kernel log on ppc64el. This bug is for tracking the
  issue of the error message "vio vio: uevent: failed to send synthetic
  uevent" (see the original bug, and
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12
  for more info)

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

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

[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2

[Łukasz Zemczak]

Thanks Paolo! We'll do that once we have everything in place. For now
Dave (the person responsible for Pi images) will do some tests to make
sure we're able to handle all the upgrade cases. But what we think will
have to happen is that we'd probably ask not to backport this change
into bionic and xenial. With snaps lacking dependency handling, it would
be too easy to actually cause machines to stop working - even if in our
gadget snaps we support loading of both compressed and uncompressed
kernels (with determining which case is currently needed), there's still
the case where someone could update only the kernel and leave an old
gadget snap. So we'd probably have to stick to uncompressed kernels for
core18, only switching to .gz in core20.

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

Title:
  vmlinuz is very large in arm64 -raspi2

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Triaged

Bug description:
  The debs are close to the same size:

  mwhudson@ringil:~/Downloads$ ls -l 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb 
  -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb
  mwhudson@ringil:~/Downloads$ ls -l 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb 
  -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 
linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb

  But the vmlinuz on arm64 is several times larger:

  $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb 
  -rw--- root/root   6633048 2018-12-07 06:38 
./boot/vmlinuz-4.15.0-1030-raspi2
  $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb 
  -rw--- root/root  23914504 2018-12-07 06:38 
./boot/vmlinuz-4.15.0-1030-raspi2

  This forced us to make the boot partition larger for the raspi3 b+
  arm64 image we made.

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

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

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.22

---
systemd (237-3ubuntu10.22) bionic; urgency=medium

  * d/p/resolved-rework-how-we-determine-which-scope-to-send.patch
- fix DNS leakage (LP: 1754671)
  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)
  * d/t/boot-smoke:
- Fix false negative checking for running jobs after boot
  (LP: #1825997)

 -- Dan Streetman   Wed, 24 Apr 2019 17:15:36
-0400

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 239-7ubuntu10.14

---
systemd (239-7ubuntu10.14) cosmic; urgency=medium

  * d/p/resolved-rework-how-we-determine-which-scope-to-send.patch
- fix DNS leakage (LP: 1754671)
  * d/t/boot-and-services:
- skip test_no_failed if gdm failed to start (LP: #1830484)
  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)
  * d/t/boot-smoke:
- Fix false negative checking for running jobs after boot
  (LP: #1825997)

 -- Dan Streetman   Wed, 24 Apr 2019 17:08:26
-0400

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Kernel-packages] [Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

[Raphael Mankin]

If I leave the machine for a while and the exit the shell it boots, but
with no swap.

I have  not discovered anything useful that I can do while in the
busybox shell.

I have dited /etc/initramfs-tools/conf.d/resume to read RESUME=none as
suggested in
https://www.reddit.com/r/Ubuntu/comments/a0whdw/failed_to_connect_to_lvmetad_bug_still_exists/

cat /etc/crypttab 
sda2_crypt UUID=91558a55-9299-492f-b3b7-324fa7d07396 none luks,swap,discard
sda3_crypt UUID=04bbb9dd-9c3f-48c9-ad65-617c4030cd8a none luks,discard


cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/sda3_crypt /   ext4errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=bedf1183-2c1a-4271-a983-f4924a87bb09 /boot   ext4noatime   
 0   2
/dev/mapper/sda2_crypt noneswapsw  0   0

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Incomplete

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1827916] Re: Enable eBPF JIT in the linux-azure kernels

[Marcelo Cerri]

@Josh, @Joseph,

I used this bug to apply the mlx* and ib* changes to the linux-azure
kernels. If AKS really needs another config change for eBPF, please open
a new bug.

Thank you.

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

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

Title:
  Enable eBPF JIT in the linux-azure kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Disco:
  Fix Committed

Bug description:
  eBPF is available as of kernel version 4.15, which is used on AKS nodes.
  Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF 
aware tools.
  eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable.
  More details for eBPF JIT - 
https://www.kernel.org/doc/Documentation/sysctl/net.txt
   
  The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes.  

  Also, to support eBPF in AKS, we are requesting to switch the mlx* and
  ib* drivers to loadable modules instead of static.

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

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

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 240-6ubuntu5.1

---
systemd (240-6ubuntu5.1) disco; urgency=medium

  * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)
  * d/p/network-wireguard-fixes-sending-wireguard-peer-setti.patch,
d/p/test-network-add-more-checks-in-NetworkdNetDevTests..patch,
d/p/sd-netlink-introduce-sd_netlink_message_append_socka.patch,
d/p/network-wireguard-use-sd_netlink_message_append_sock.patch:
- systemd doesn't set wireguard peer endpoint (LP: #1825378)
  * d/t/boot-smoke:
- Fix false negative checking for running jobs after boot
  (LP: #1825997)

 -- Dan Streetman   Thu, 16 May 2019 06:07:49
-0400

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Kernel-packages] [Bug 1814373] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Kernel-packages] [Bug 1827916] Re: Enable eBPF JIT in the linux-azure kernels

[Marcelo Cerri]

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

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

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

Title:
  Enable eBPF JIT in the linux-azure kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Disco:
  In Progress

Bug description:
  eBPF is available as of kernel version 4.15, which is used on AKS nodes.
  Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF 
aware tools.
  eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable.
  More details for eBPF JIT - 
https://www.kernel.org/doc/Documentation/sysctl/net.txt
   
  The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes.  

  Also, to support eBPF in AKS, we are requesting to switch the mlx* and
  ib* drivers to loadable modules instead of static.

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

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

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

[Chris Gregan]

It does seem to have improved in the last update

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

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

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

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

[Kernel-packages] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure

[Marcelo Cerri]

** Changed in: linux-azure (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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

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

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

[Chris Gregan]

May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.182335  
  7167 wrap.go:47] PUT 
/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: 
(3.332254ms) 200 [kube-controller-manager/v1.14.1 (linux/amd64) 
kubernetes/b739410/leader-election 127.0.0.1:56726]
May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.634891  
  7167 wrap.go:47] GET 
/api/v1/nodes?resourceVersion=5708807=450=true: 
(7m30.001685916s) 200 [heapster/v0.0.0 (linux/amd64) kubernetes/$Format 
192.168.86.33:48032]
May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.637456  
  7167 get.go:251] Starting watch for /api/v1/nodes, rv=5709318 labels= fields= 
timeout=5m16s
May 25 08:50:47 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:47.005793  
  7167 wrap.go:47] GET 
/api/v1/namespaces/kube-system/endpoints/kube-scheduler?timeout=10s: 
(2.286855ms) 200 [kube-scheduler/v1.14.1 (linux/amd64) 
kubernetes/b739410/leader-election 127.0.0.1:49932]
May 25 08:50:47 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:47.010412  
  7167 wrap.go:47] PUT 
/api/v1/namespaces/kube-system/endpoints/kube-scheduler?timeout=10s: 
(3.348305ms) 200 [kube-scheduler/v1.14.1 (linux/amd64) 
kubernetes/b739410/leader-election 127.0.0.1:49932]
May 25 08:50:47 Thermia systemd-logind[1166]: Lid closed.
May 25 08:50:47 Thermia systemd-logind[1166]: Suspending...
May 25 08:50:47 Thermia NetworkManager[1197]:   [1558788647.9902] 
manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 25 08:50:47 Thermia NetworkManager[1197]:   [1558788647.9905] device 
(p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
May 25 08:50:47 Thermia NetworkManager[1197]:   [1558788647.9931] 
manager: NetworkManager state is now ASLEEP
May 25 08:50:48 Thermia systemd[1]: Reached target Sleep.
--
May 25 14:41:02 Thermia kernel: Bluetooth: hci0: API lock is enabled
May 25 14:41:02 Thermia kernel: Bluetooth: hci0: Debug lock is disabled
May 25 14:41:02 Thermia kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
May 25 14:41:02 Thermia kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
May 25 14:41:02 Thermia kernel: done.
May 25 14:41:01 Thermia systemd-logind[1166]: Lid opened.
May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.990168  
  7167 wrap.go:47] GET 
/apis/extensions/v1beta1/daemonsets?resourceVersion=5585151=5m26s=326=true:
 (5m26.091210748s) 200 [kube-controller-manager/v1.14.1 (linux/amd64) 
kubernetes/b739410/shared-informers 127.0.0.1:49858]
May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.993603  
  7167 wrap.go:47] GET 
/api/v1/namespaces/kube-system/endpoints/kube-scheduler?timeout=10s: 
(4.25ms) 200 [kube-scheduler/v1.14.1 (linux/amd64) 
kubernetes/b739410/leader-election 127.0.0.1:49932]
May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.993898  
  7167 wrap.go:47] GET 
/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: 
(4.104768ms) 200 [kube-controller-manager/v1.14.1 (linux/amd64) 
kubernetes/b739410/leader-election 127.0.0.1:56726]
May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.997048  
  7167 get.go:251] Starting watch for /apis/extensions/v1beta1/daemonsets, 
rv=5585151 labels= fields= timeout=6m15s
May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.999249  
  7167 wrap.go:47] GET 
/apis/coordination.k8s.io/v1beta1/namespaces/kube-node-lease/leases/thermia?timeout=10s:
 (8.048104ms) 200 [kubelet/v1.14.1 (linux/amd64) kubernetes/b739410 
127.0.0.1:60774]

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

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 10. June 2019 13:30 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Pending -- packages copied to Proposed signed:building

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Monday, 10. June 2019 14:08 UTC
  reason:
promote-to-proposed: Pending -- packages copied to Proposed signed:building

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

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

[Kernel-packages] [Bug 1829179] Re: linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

All tasks have been completed and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   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
  
  derivatives: bug 1829178 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
- phase: Ready for Security
- phase-changed: Friday, 07. June 2019 11:03 UTC
+ phase: Security
+ phase-changed: Monday, 10. June 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy

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

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

Title:
  linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

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

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 1829178 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
  phase: Security
  phase-changed: Monday, 10. June 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1829180] Re: linux-azure: 4.18.0-1019.19 -proposed tracker

[Ubuntu Kernel Bot]

All tasks have been completed and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   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
  
  backports: bug 1829179 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
- phase: Ready for Security
- phase-changed: Friday, 07. June 2019 11:00 UTC
+ phase: Security
+ phase-changed: Monday, 10. June 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy

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

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

Title:
  linux-azure: 4.18.0-1019.19 -proposed tracker

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

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 1829179 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
  phase: Security
  phase-changed: Monday, 10. June 2019 14:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker

[Ubuntu Kernel Bot]

All tasks have been completed and the bug is being set to Fix Released


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

** Changed in: kernel-sru-workflow
   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
  
  backports: bug 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- phase: Ready for Security
- phase-changed: Saturday, 08. June 2019 10:01 UTC
+ phase: Security
+ phase-changed: Monday, 10. June 2019 14:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy

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

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

Title:
  linux-azure: 4.15.0-1046.50 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) 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 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Security
  phase-changed: Monday, 10. June 2019 14:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1681909] Re: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone.

[Manoj Iyer]

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

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

Title:
  [FEAT 18.10] dump is not captured in remote host when kdump over ssh
  is configured on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  == Comment: #8 - Urvashi Jawere  - 2017-03-08 02:48:15 ==
  I am able to see some errors in syslog ;

  auxiliary
  Mar  7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed 
for question 

[Kernel-packages] [Bug 1829180] Re: linux-azure: 4.18.0-1019.19 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => 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/1829180

Title:
  linux-azure: 4.18.0-1019.19 -proposed tracker

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

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 1829179 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829186
  phase: Ready for Security
  phase-changed: Friday, 07. June 2019 11:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => 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/1829214

Title:
  linux-azure: 4.15.0-1046.50 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) 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 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Security
  phase-changed: Saturday, 08. June 2019 10:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1829179] Re: linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => 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/1829179

Title:
  linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

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

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 1829178 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
  phase: Ready for Security
  phase-changed: Friday, 07. June 2019 11:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy

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

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

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

[Andrew Cloke]

Marking as "incomplete" while waiting for IBM to test the PPA referenced
in comment #14.

** Changed in: ubuntu-power-systems
   Status: In Progress => Incomplete

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

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

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

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

  Warn on message is seen while running perf fuzzer tests.

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

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

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

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

  
  Call trace :
  ===
  [  329.228031] [ cut here ]
  [  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
  [  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
  [  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
  [  329.228070] task: c03f776ac900 task.stack: c03f77728000
  [  329.228071] NIP: c0299b70 LR: c02a4534 CTR: 
c029bb80
  [  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
  [  329.228073] MSR: 9282b033 
  [  329.228079]   CR: 24008822  XER: 
  [  329.228080] CFAR: c0299a70 SOFTE: 0 
 GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
 GPR04: c03f776ac900 0001  
003fee73 
 GPR08:   c11220d8 
0002 
 GPR12: c029bb80 c7a3d900  
 
 GPR16:    
 
 GPR20:   c03f776ad090 
c0c71354 
 GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
 GPR28: c11220d8 0001 c14c6108 
c03fef858900 
  [  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
  [  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
  [  329.228101] Call Trace:
  [  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
  [  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
  [  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
  [  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
  [  329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0
  [  329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0
  [  329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0
  [  329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0
  [  329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c
  [  329.228121] Instruction dump:
  [  329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 
38210050 
  [  329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 
6000 6042 
  [  329.228131] ---[ end trace 8c46856d314c1811 ]---
  [  375.755943] hrtimer: interrupt took 31601 ns

  == Comment: #4 - SEETEENA THOUFEEK  - 2018-02-05
  06:34:09 ==

  
  == Comment: #5 - SEETEENA THOUFEEK  - 2018-02-05 
06:36:12 ==
  We have similar issue reported on 

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

[Terry Rudd]

Chris, any chance we can get the data that Andrea is asking for above?

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

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 10. June 2019 11:06 UTC
+ boot-testing-requested: true
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 10. June 2019 13:30 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:queued
+   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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1832206

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 10. June 2019 13:30 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/1832206/+subscriptions

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.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
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:queued

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:queued

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

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

[Kernel-packages] [Bug 1830266] Re: [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels

[Marcelo Cerri]

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

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

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

Title:
  [linux-azure] Please Include Mainline Commit ebaf39e6032f  in the
  16.04 and 18.04 linux-azure kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  A team within Microsoft is running the linux-azure Ubuntu kernel on a
  large AI cluster.  They are hitting an issue which is resolved by the
  following commit:

  
https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0

  
  The bug is that threads can get stuck in the kernel. This bug can happen when 
removing network namespaces. This is something docker swarm does anytime it 
removes a container.

  Commit ebaf39e6032f was added to the mainline kernel tree in
  v4.20-rc6. It was not cc’d to upstream stable, so only v4.20-rc6 and
  newer kernels will have it.

  A test kernel was built with this commit, which resolves the issue.

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

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

[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)

[Marcelo Cerri]

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

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

Title:
   Azure: Backport vIOMMU driver (increase vCPU limits)

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Disco:
  Incomplete

Bug description:
  Description:

  To support VM instances with >255 vCPUS, we need the patch set below
  backported to the Azure 4.18 kernel. These patches include -

- New Hyper-V IOMMU driver. This driver will be Hyper-V specific.
- Minor update to the Hyper-V specific virtual PCI code. Need to expand the 
size of an array to allow for a larger number of vCPUs.

  There are very large VM instance sizes coming to Azure in 2019, and
  Ubuntu will require the following patches in order to function
  properly:

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller
  /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37

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

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

[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels

[Marcelo Cerri]

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

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

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

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

Title:
  [Packaging] Improve config annotations check on custom kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gcp source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-gcp source package in Bionic:
  New
Status in linux-azure source package in Cosmic:
  Fix Committed
Status in linux-gcp source package in Cosmic:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Committed
Status in linux-gcp source package in Disco:
  New

Bug description:
  [Impact]

  Currently for custom kernels, it's necessary to keep a separate
  annotations file that often gets out of sync with the corresponding
  file in debian.master/.

  The "debian/scripts/config-check" script can be changed to allow
  additional annotations files to act as overlays over the original
  annotations file, allowing custom kernels to override the policies
  just for the relevant configs.

  The proposal is to add support for an include directive in the
  annotations file so custom kernels can include the annotations file
  from its base kernel and override policies on a config basis.

  [Test Case]

  A kernel build should complete successfully after the change.

  
  [Regression Potential] 

  Low regression potential since that's a change on the build process
  that doesn't affect the final kernel that is built.

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

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

[Kernel-packages] [Bug 1830242] Re: [linux-azure] Commits Requested in 16.04 for the Azure Kernel

[Marcelo Cerri]

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

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

Title:
  [linux-azure] Commits Requested in 16.04 for the Azure Kernel

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  The 4.15 kernel require three patches for NVMe, those patches are
  required to get to the target number of IOPS.

  The commits are:

  7ac257b862f2c (“blk-mq: remove the request_list usage”)
  f9dde187fa921 ("nvme-pci: remove cq check after submission")
  1ab0cd6966fc4 ("nvme-pci: split the nvme queue lock into submission and 
completion locks")

  Please include these commits in the 4.15 based kernel.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Kernel-packages] [Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04

[Tom Stewart]

Can you clarify what you want me to do with dmesg? Do you want me to run
"dmesg" and report back to you with the output? Please be very specific:
I'm not at all skilled using the terminal.

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

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.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
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:building,main:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:building

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:building

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

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

[Kernel-packages] [Bug 1830050] Re: nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.2.0-0.1

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-390 -
390.116-0ubuntu2

---
nvidia-graphics-drivers-390 (390.116-0ubuntu2) eoan; urgency=medium

  * debian/dkms_nvidia/patches/buildfix_kernel_5.2.patch,
debian/templates/dkms_nvidia.conf.in:
- Add support for Linux 5.2 (LP: #1830050).

 -- Alberto Milone   Mon, 10 Jun 2019
12:25:00 +0200

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+subscriptions

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.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
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
meta:building,signed:building,main:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:building,main:building

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
signed:building,meta:building,main:building

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

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

[Kernel-packages] [Bug 1830050] Re: nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.2.0-0.1

[Alberto Milone]

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

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+subscriptions

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

[Andy Whitcroft]

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
meta:building,signed:building,main:building

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -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/prepare-package-signed
   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 --
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 10. June 2019 11:06 UTC
+ reason:
+   promote-to-proposed: Pending -- builds not complete in ppa 
meta:building,signed:building,main:building

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. June 2019 11:06 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
meta:building,signed:building,main:building

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

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

[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing

[Andy Whitcroft]

Worked with ~cjwatson to add Secure Initial Program Load signing to
launchpad.  Changes deployed to dogfood and test packages uploaded.
This results in a vmlinuz.sipl gaining a vmlinuz.sipl.sig, and an
appropriate control/sipl.x509 file.  The signed binary validates
correctly using the public key.  Looks good.

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

Title:
  Please add support for zipl signing

Status in Launchpad itself:
  Fix Committed
Status in linux-signed package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  Please add support for zipl ("z/ecureBoot") signing.

  It should be similar to opal signing, but using the new zipl signing
  key.

  I am expecting to sign s390-tools stage3.bin and kernel images using
  this key.

  s390-tools -> can be signed already
  kernels -> should only sign v5.2+

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

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

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

[AceLan Kao]

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Qualcomm WiFi/Bluetooth may disappear after boot. 

  [Fix]
  Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM
  L1. Pull back the device to full power before shutdown imitates the
  behavior on Windows.

  [Test] 
  The affected user confimed it fixes the issue.
  I can also confirm that
  a) The power drain in S5 is much lower,
  b) Both WiFi and Bluetooth are always present during reboot stress test.

  [Regression Potential]
  Low. Only a limited number of USB2 devices that support LPM.

  === Original Bug Report ===
  Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This 
caused, on prior versions, a kernel panic at boot. With Bionic, the system 
boots but is unable to use wireless network. On dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1639299] Re: acpi_pad consumes 100% of resources

[JCarsique]

Cannot run apport-collect but confirmed on Ubuntu 16.04.6 LTS 4.4.0-104-generic.
Issued "rmmod acpi_pad" to get the system back, then blacklisted it in 
/etc/modprobe.d/blacklist.conf.

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

Title:
  acpi_pad consumes 100% of resources

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

Bug description:
  acpi_pad will take up 100% of the CPU resources and slow the system to
  a crawl.  'rmmod acpi_pad' removes the offender and brings the system
  response back.

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  20765 root  20   0   0  0  0 R 100.0  0.0   5:07.99 xhpl
  20879 root  -2   0   0  0  0 R 100.0  0.0   7:12.40 acpi_pad/5
  20887 root  -2   0   0  0  0 R 100.0  0.0   6:57.72 
acpi_pad/13
  20891 root  -2   0   0  0  0 R 100.0  0.0   7:05.74 
acpi_pad/17
  20874 root  -2   0   0  0  0 R 100.0  0.0   7:15.16 acpi_pad/0
  20875 root  -2   0   0  0  0 R 100.0  0.0   7:14.76 acpi_pad/1
  20876 root  -2   0   0  0  0 R 100.0  0.0   7:13.54 acpi_pad/2
  20877 root  -2   0   0  0  0 R 100.0  0.0   7:13.54 acpi_pad/3
  20880 root  -2   0   0  0  0 R 100.0  0.0   7:11.44 acpi_pad/6
  20881 root  -2   0   0  0  0 R 100.0  0.0   7:11.17 acpi_pad/7
  20882 root  -2   0   0  0  0 R 100.0  0.0   7:05.42 acpi_pad/8
  20883 root  -2   0   0  0  0 R 100.0  0.0   7:10.80 acpi_pad/9
  20884 root  -2   0   0  0  0 R 100.0  0.0   7:09.50 
acpi_pad/10
  20885 root  -2   0   0  0  0 R 100.0  0.0   7:09.66 
acpi_pad/11
  20888 root  -2   0   0  0  0 R 100.0  0.0   7:07.30 
acpi_pad/14
  20889 root  -2   0   0  0  0 R 100.0  0.0   7:07.37 
acpi_pad/15
  20890 root  -2   0   0  0  0 R 100.0  0.0   7:05.50 
acpi_pad/16
  20892 root  -2   0   0  0  0 R 100.0  0.0   7:04.40 
acpi_pad/18
  20893 root  -2   0   0  0  0 R 100.0  0.0   7:04.21 
acpi_pad/19
  20894 root  -2   0   0  0  0 R 100.0  0.0   7:03.70 
acpi_pad/20
  20895 root  -2   0   0  0  0 R 100.0  0.0   7:03.63 
acpi_pad/21
  20896 root  -2   0   0  0  0 R 100.0  0.0   7:01.61 
acpi_pad/22
  20897 root  -2   0   0  0  0 R 100.0  0.0   7:01.66 
acpi_pad/23
  20898 root  -2   0   0  0  0 R 100.0  0.0   7:00.80 
acpi_pad/24
  20899 root  -2   0   0  0  0 R 100.0  0.0   7:00.81 
acpi_pad/25
  20901 root  -2   0   0  0  0 R 100.0  0.0   6:58.79 
acpi_pad/26
  20902 root  -2   0   0  0  0 R 100.0  0.0   6:58.96 
acpi_pad/27
  20903 root  -2   0   0  0  0 R 100.0  0.0   6:57.82 
acpi_pad/28
  20904 root  -2   0   0  0  0 R 100.0  0.0   6:57.83 
acpi_pad/29
  20906 root  -2   0   0  0  0 R 100.0  0.0   6:55.54 
acpi_pad/31
  20886 root  -2   0   0  0  0 R  99.7  0.0   7:08.80 
acpi_pad/12
  20878 root  -2   0   0  0  0 R  98.4  0.0   7:12.20 acpi_pad/4
  20905 root  -2   0   0  0  0 R  98.4  0.0   6:55.85 
acpi_pad/30
   3049 newrelic  20   0  245800   8388   4724 S  22.3  0.0   0:14.74 nrsysmond
  22126 root  20   0   19592   3876   2392 R   6.0  0.0   0:00.99 top
   1441 root  39  19   0  0  0 S   3.4  0.0   3:05.47 kipmi0
  20720 root  20   0  870276  13080   6208 S   1.6  0.0   0:01.50 collectd
  8 root  20   0   0  0  0 S   0.9  0.0   0:03.19 rcu_sched
 13 root  rt   0   0  0  0 S   0.3  0.0   0:00.03 
watchdog/0 

  
  This has been seen on the 4.2 and 4.4 kernels.  I believe the LINPACK test 
suite was running in all cases this was seen.  However, it occurs pretty 
infrequently, and I don't know how to reliably recreate the issue.  It has only 
been seen on the DGX-1 Server, not on the DGX Station.  I'm not sure if any 
other systems have seen it.

  Another data point which may or may not be relevant is that C-states
  and P-states are enabled.

  We can workaround this issue by blacklisting the acpi_pad module, or
  by using the acpi_pad.disable=1 kernel bootarg.  What are the
  implications of disabling acpi_pad are?

  Googling "acpi_pad uses up all the resource" returns many hits where
  they all suggest to simply disable it.

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

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

[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

[Po-Hsu Lin]

https://lists.ubuntu.com/archives/kernel-team/2019-June/101275.html

** Tags removed: ppc64el
** Tags added: amd64 cosmic disco ubuntu-kernel-security

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
  This issue can be verified with test_410_config_lock_down_kernel
  test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, we already have this config enabled in the generic kernel.

  
  == Original bug report ==
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

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

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

[Kernel-packages] [Bug 1832207] Re: linux: -proposed tracker

[Andy Whitcroft]

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  New
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:
  New
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 snap-certification-testing 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 package in Ubuntu:
  Incomplete
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

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

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

[Kernel-packages] [Bug 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

[Daniel van Vugt]

** Summary changed:

- not working list
+ Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

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

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

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  New

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1831037] [NEW] Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

thunderbird - send email
keyboard from laptop 
no physical shut down or reeboot

tried all the information online

have a nice day

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu May 30 11:02:33 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
InstallationDate: Installed on 2015-10-28 (1309 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
 Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire ES1-311
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Aspire ES1-311
dmi.board.vendor: Acer
dmi.board.version: V1.11
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
dmi.product.family: BayTrail
dmi.product.name: Aspire ES1-311
dmi.product.version: V1.11
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Mon May 21 13:03:46 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: apport-bug bionic i386 ubuntu
-- 
Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.
https://bugs.launchpad.net/bugs/1831037
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1831371] Re: Touchpad stops working for a period of time

[Kai-Heng Feng]

Hi,

Please test this kernel and attach dmesg:
https://people.canonical.com/~khfeng/lp1831371-2/

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

Title:
  Touchpad stops working for a period of time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occasionally the touchpad will stop working for a period of time, the
  mouse cursor disappears but the touchpad buttons still work. The
  keyboard and touchscreen still work normally.

  Eventually after a few minutes the touchpad starts working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob   13195 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  2 22:09:46 2019
  InstallationDate: Installed on 2019-04-24 (38 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Stream x360 Convertible 11-ag1XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8501
  dmi.board.vendor: HP
  dmi.board.version: 05.21
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Stream x360 Convertible 11-ag1XX
  dmi.product.sku: 4RV86PA#ABG
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter

[Robert Udvardi]

Problem solved for windows:

https://www.youtube.com/watch?reload=9=1zIOD9Wv-Vc

my processor performance limited till 95% form battery and AC as well not sure 
it changed on the set up what the guy recomend on the video...
But for me after 1,5 year suffering finaly works.

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

Title:
  Asus Zenbook UX31E powers off on plugin in/out AC adapter

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When I have logged in to Unity and plug in or out AC adapter to Asus
  Zenbook UX31E, computer powers off. Sometimes this needs couple of
  tries (waiting or not waiting in between) when plugin in or out AC
  adapter.

  This problem doesn't occur when I have switched to console or when in LightDM 
login screen. Problem doesn't happen with MS Windows either.
  And yes, there's enough power in my battery too, I can boot up and use the 
computer without AC adapter.

  syslog prints these lines to stdout in console, when plugin AC adapter first 
out and then in:
    [  869.521396] asus_wmi: Unknown key 57 pressed
    [  874.704525] asus_wmi: Unknown key 58 pressed
    [  876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

  What you also need:

  1) lsb_release -rd
    Description:Ubuntu 12.04 LTS
    Release:12.04

  2) I could guess kernel, but it happens _only_ when I have logged in
  to Unity (or Unity 2D)...

  3) I expect that my computer doesn't power off.

  4) Computer powers off.

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

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

[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM

[Po-Hsu Lin]

** Description changed:

+ == SRU Justification ==
+ Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.
+ 
+ == Test ==
+ Test kernels could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
+ This issue can be verified with test_410_config_lock_down_kernel
+ test from q-r-t, the test will pass with the patched kernel.
+ 
+ == Regression Potential ==
+ Low, we already have this config enabled in the generic kernel.
+ 
+ 
+ == Original bug report ==
  Kernel Version: 4.15.0-44.47
  
  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9
  
  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Cosmic:
  In Progress
Status in linux-kvm source package in Disco:
  In Progress

Bug description:
  == SRU Justification ==
  Security team requires the CONFIG_LOCK_DOWN_KERNEL to be enabled in all of 
our kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811981-kvm-lockdown/
  This issue can be verified with test_410_config_lock_down_kernel
  test from q-r-t, the test will pass with the patched kernel.

  == Regression Potential ==
  Low, we already have this config enabled in the generic kernel.

  
  == Original bug report ==
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

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

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

[Kernel-packages] [Bug 1831873] Re: test_095_kernel_symbols_missing_proc_net_tcp from ubuntu_qrt_kernel_security failed on B/C KVM

[Po-Hsu Lin]

Thanks for the quick fix, tested on a KVM node and this cannot be
reproduced.

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

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

Title:
  test_095_kernel_symbols_missing_proc_net_tcp from
  ubuntu_qrt_kernel_security failed on B/C KVM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  This issue can only be reproduced on the first run. The second run it
  will pass.

ERROR: test_095_kernel_symbols_missing_proc_net_tcp 
(__main__.KernelSecurityTest)
kernel addresses in /proc/net/tcp are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1392, in 
test_095_kernel_symbols_missing_proc_net_tcp
self._check_pK_files(self. _095_kernel_symbols_missing_proc_net_tcp)
  File "./test-kernel-security.py", line 1235, in _check_pK_files
test_function(expected_unrestricted)
  File "./test-kernel-security.py", line 1350, in 
_095_kernel_symbols_missing_proc_net_tcp
expected)
  File "./test-kernel-security.py", line 1153, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s - 
contents:\n%s" % (filename, address, root))
ValueError: invalid literal for int() with base 16: '(ptrval)'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13
  ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20
  Uname: Linux 4.18.0-1013-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Thu Jun  6 09:25:10 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-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]

[adam.creativeasset]

I've tried changing the BIOS settings but on boot this issue still happens? 
https://www.creative-asset.co.uk/insights/principles-quality-web-design

-- 
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 1829749] Re: Please add support for zipl signing

[Colin Watson]

** Changed in: launchpad
   Importance: Undecided => High

** Changed in: launchpad
   Status: New => Fix Committed

** Changed in: launchpad
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Branch linked: lp:~apw/launchpad/signing-sipl

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

Title:
  Please add support for zipl signing

Status in Launchpad itself:
  Fix Committed
Status in linux-signed package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  Please add support for zipl ("z/ecureBoot") signing.

  It should be similar to opal signing, but using the new zipl signing
  key.

  I am expecting to sign s390-tools stage3.bin and kernel images using
  this key.

  s390-tools -> can be signed already
  kernels -> should only sign v5.2+

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

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

[Kernel-packages] [Bug 1832189] Re: linux-oem: -proposed tracker

[Andy Whitcroft]

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

** This bug has been marked a duplicate of bug 1832206
   linux-oem:  -proposed tracker

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

Title:
  linux-oem:  -proposed tracker

Status in Kernel SRU Workflow:
  New
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:
  New
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-oem package in Ubuntu:
  New
Status in linux-oem 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

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker

[AceLan Kao]

** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1041.46 -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) => AceLan Kao 
(acelankao)

** 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) => AceLan Kao 
(acelankao)

** 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) => AceLan Kao 
(acelankao)

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

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

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

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

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

[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260

[Anthony Wong]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.2-rc4 kernel[1].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc4

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

Title:
  Bluetooth not work on INTEL WIRELESS-AC 9260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1832207] Re: linux: -proposed tracker

[Andy Whitcroft]

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

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

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

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: (unassigned) => Canonical Security Team (canonical-security)

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

** Changed in: kernel-sru-workflow/snap-certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  New
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:
  New
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 snap-certification-testing 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 package in Ubuntu:
  Incomplete
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

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

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

[Kernel-packages] [Bug 1832206] [NEW] linux-oem: 4.15.0-1041.46 -proposed tracker

[Andy Whitcroft]

Public bug reported:

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

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

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

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

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

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

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

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


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.05.13-5

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

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

** Tags added: bionic

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1832206] Re: linux-oem: -proposed tracker

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -proposed tracker

[Andy Whitcroft]

** 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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
- derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1831978 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)
+ derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829194 (linux-aws), bug 1829200 (linux-gcp), bug 1829202 (linux-gke-4.15), bug 
1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), bug 1829210 (linux-oracle), 
bug 1829211 (linux-fips), bug 1829846 (linux)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Security
  phase-changed: Wednesday, 05. June 2019 13:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) 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 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829194 (linux-aws), bug 1829200 (linux-gcp), bug 1829202 (linux-gke-4.15), bug 
1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), bug 1829210 (linux-oracle), 
bug 1829211 (linux-fips), bug 1829846 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Security
  phase-changed: Wednesday, 05. June 2019 13:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1831978] Re: linux-oem: 4.15.0-1040.45 -proposed tracker

[Andy Whitcroft]

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

** Tags removed: kernel-sru-derivative-of-1829219

** 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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- kernel-stable-master-bug: 1829219
  phase: Ready for Promote to Proposed
  phase-changed: Sunday, 09. June 2019 11:32 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

** This bug has been marked a duplicate of bug 1832206
   linux-oem:  -proposed tracker

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Ready for Promote to Proposed
  phase-changed: Sunday, 09. June 2019 11:32 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

[Po-Hsu Lin]

Status change as per request in comment #25

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

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

Title:
  kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 
1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can 
no longer boot with the 4.15.0-50 kernel installed with 1804.
  We tried various kernel flags without luck, and installed latest 4.18.0-20 
from HWE and got the same result.
  Unfortunately, no logs are created in /var/logs when the issue happens, and 
we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to 
get a backtrace in a photo.
  The issue happens consistently, i.e. the backtrace looks always the same just 
happens on different cores.
  Attached the boot-info output and the picture taken at the end of the kernel 
loading.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  steventang   2047 F pulseaudio
   /dev/snd/controlC0:  steventang   2047 F pulseaudio
   /dev/snd/controlC1:  steventang   2047 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870
  InstallationDate: Installed on 2019-05-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacPro5,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic 
root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-148-generic N/A
   linux-backports-modules-4.4.0-148-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.4.0-148-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP51.88Z.0084.B00.1708080528
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.name: MacPro5,1
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

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

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