[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

I can confirm that openafs-modules-dkms/1.6.15-1ubuntu1.1 can be built
and installed on both older and newer xenial/linux kernels:

$ dkms status
openafs, 1.6.15, 4.4.0-206-generic, x86_64: installed
openafs, 1.6.15, 4.4.0-208-generic, x86_64: installed


autopkgtests were also successful:

* xenial/linux 4.4.0-208.240
  - amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210407_161651_8b22b@/log.gz
  - armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210407_163444_963c5@/log.gz
  - i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/openafs/20210407_161429_59fe1@/log.gz
  - s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210407_161222_963c5@/log.gz

* xenial/linux 4.4.0-206.238:
  - amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210407_142619_8fbc1@/log.gz
  - armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210407_142941_8fbc1@/log.gz
  - i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/openafs/20210407_142002_8fbc1@/log.gz
  - s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210407_142101_8fbc1@/log.gz

Note: arm64 and ppc64el has never passed.

Thanks,
Kleber

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

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.

  [Where problems could occur]
  The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

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

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

[Kernel-packages] [Bug 1868243] Re: ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X s390x

[Kleber Sacilotto de Souza]

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

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

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

Title:
  ld_abs+vlan_push/pop from test_bpf in ubuntu_bpf_jit will fail on X
  s390x

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Issue separated from bug 1768452
  The ubuntu_bpf_jit will report the following failure on Xenial s390x:
    * test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524

  This test has been moved to the test_verifier test in bpf of kselftests:
  
https://github.com/torvalds/linux/commit/93731ef086cee90af594e62874bb98ae6d6eee91

  "Remove all eBPF tests involving LD_ABS/LD_IND from test_bpf.ko. Reason
  is that the eBPF tests from test_bpf module do not go via BPF verifier
  and therefore any instruction rewrites from verifier cannot take place.

  Therefore, move them into test_verifier which runs out of user space,
  so that verfier can rewrite LD_ABS/LD_IND internally in upcoming patches.
  It will have the same effect since runtime tests are also performed from
  there. This also allows to finally unexport bpf_skb_vlan_{push,pop}_proto
  and keep it internal to core kernel."

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

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

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

** Changed in: openafs (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  In Progress

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.

  [Where problems could occur]
  The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

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

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

[Kernel-packages] [Bug 1922596] Re: linux ADT test failure with linux/4.4.0-208.240

[Kleber Sacilotto de Souza]

** Patch added: "patch for 
qa-regression-testing/scripts/test-kernel-security.py"
   
https://bugs.launchpad.net/qa-regression-testing/+bug/1922596/+attachment/5484650/+files/0001-scripts-test-kernel-security.py-update-test-for-CVE-.patch

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

Title:
  linux ADT test failure with linux/4.4.0-208.240

Status in QA Regression Testing:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-208.240 on xenial. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210405_165921_51e87@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210405_171150_5e4c6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210405_171645_a1619@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210402_051319_d4fe2@/log.gz


  15:47:57 ERROR| [stderr] 
==
  15:47:57 ERROR| [stderr] FAIL: test_160_setattr_CVE_2015_1350 
(__main__.KernelSecurityTest)
  15:47:57 ERROR| [stderr] Ensure unpriv user cannot strip setattr attributes 
via chown() (CVE-2015-1350)
  15:47:57 ERROR| [stderr] 
--
  15:47:57 ERROR| [stderr] Traceback (most recent call last):
  15:47:57 ERROR| [stderr]   File "./test-kernel-security.py", line 1891, in 
test_160_setattr_CVE_2015_1350
  15:47:57 ERROR| [stderr] self.assertShellOutputEquals(exp_output, 
['sudo', '-u', user, 'getcap', testbin])
  15:47:57 ERROR| [stderr]   File 
"/tmp/autopkgtest.UEYHB2/build.S4Z/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1206, in assertShellOutputEquals
  15:47:57 ERROR| [stderr] self.assertEqual(text, out, msg + result + 
report)
  15:47:57 ERROR| [stderr] AssertionError: Got exit code 0. Looking for exact 
text "" (sudo -u ubuntu getcap /tmp/setattr-GwRjva/true)
  15:47:57 ERROR| [stderr] Command: 'sudo', '-u', 'ubuntu', 'getcap', 
'/tmp/setattr-GwRjva/true'
  15:47:57 ERROR| [stderr] Output:
  15:47:57 ERROR| [stderr] /tmp/setattr-GwRjva/true = cap_sys_nice+ep
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] 
--
  15:47:57 ERROR| [stderr] Ran 125 tests in 24.852s
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] FAILED (failures=1)

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

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

[Kernel-packages] [Bug 1922596] Re: linux ADT test failure with linux/4.4.0-208.240

[Kleber Sacilotto de Souza]

test_160_setattr_CVE_2015_1350 from qa-regression-testing/scripts/test-
kernel-security.py assumes that all Ubuntu kernels prior to 4.9 lack the
fix for CVE-2015-1350. The latest Xenial kernel in -proposed
(linux/4.4.0-208.240) has the fixes for this CVE applied, therefore the
testcase needs to be update with something like:

--- a/scripts/test-kernel-security.py
+++ b/scripts/test-kernel-security.py
@@ -1885,8 +1885,8 @@ class KernelSecurityTest(KernelSecurityBaseTest):
 # chown should fail, but also should not clear fs caps
 self.assertShellExitEquals(1, ['sudo', '-u', user, 'chown', user, 
testbin])
 
-if not self.kernel_at_least('4.9'):
-self._skipped("Kernels before 4.9 need to fix CVE-2015-1350")
+if not self.kernel_at_least('4.4'):
+self._skipped("Kernels before 4.4 need to fix CVE-2015-1350")
 exp_output = ''
 self.assertShellOutputEquals(exp_output, ['sudo', '-u', user, 
'getcap', testbin])


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-1350

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: qa-regression-testing
   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/1922596

Title:
  linux ADT test failure with linux/4.4.0-208.240

Status in QA Regression Testing:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-208.240 on xenial. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210405_165921_51e87@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210405_171150_5e4c6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210405_171645_a1619@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210402_051319_d4fe2@/log.gz


  15:47:57 ERROR| [stderr] 
==
  15:47:57 ERROR| [stderr] FAIL: test_160_setattr_CVE_2015_1350 
(__main__.KernelSecurityTest)
  15:47:57 ERROR| [stderr] Ensure unpriv user cannot strip setattr attributes 
via chown() (CVE-2015-1350)
  15:47:57 ERROR| [stderr] 
--
  15:47:57 ERROR| [stderr] Traceback (most recent call last):
  15:47:57 ERROR| [stderr]   File "./test-kernel-security.py", line 1891, in 
test_160_setattr_CVE_2015_1350
  15:47:57 ERROR| [stderr] self.assertShellOutputEquals(exp_output, 
['sudo', '-u', user, 'getcap', testbin])
  15:47:57 ERROR| [stderr]   File 
"/tmp/autopkgtest.UEYHB2/build.S4Z/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1206, in assertShellOutputEquals
  15:47:57 ERROR| [stderr] self.assertEqual(text, out, msg + result + 
report)
  15:47:57 ERROR| [stderr] AssertionError: Got exit code 0. Looking for exact 
text "" (sudo -u ubuntu getcap /tmp/setattr-GwRjva/true)
  15:47:57 ERROR| [stderr] Command: 'sudo', '-u', 'ubuntu', 'getcap', 
'/tmp/setattr-GwRjva/true'
  15:47:57 ERROR| [stderr] Output:
  15:47:57 ERROR| [stderr] /tmp/setattr-GwRjva/true = cap_sys_nice+ep
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] 
--
  15:47:57 ERROR| [stderr] Ran 125 tests in 24.852s
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] FAILED (failures=1)

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

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

[Kernel-packages] [Bug 1922200] Re: linux ADT test failure with linux/4.4.0-207.239 - ubuntu_qrt_kernel_security.test-kernel-security.py

[Kleber Sacilotto de Souza]

According to the autopkgtests logs:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210405_165921_51e87@/log.gz

The following testcases are now passing as expected with xenial/linux
4.4.0-208.240:

test_095_kernel_symbols_missing_kallsyms
test_095_kernel_symbols_missing_proc_modules
test_095_kernel_symbols_missing_proc_net_tcp
test_300_test_kaslr_base

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

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

Title:
  linux ADT test failure with linux/4.4.0-207.239 -
  ubuntu_qrt_kernel_security.test-kernel-security.py

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The backport of upstream commit ad67b74d2469d9b82aaa572d76474c95bc484d57 
("printk: hash addresses printed with %p"), applied to fix CVEs 
CVE-2018-5953/CVE-2018-5995/CVE-2018-7754 on xenial/linux 4.4.0-207.239, 
introduced a regression caught by testcases from 
ubuntu_qrt_kernel_security.test-kernel-security.py testsuite.

  The failing testcases are:
  test_095_kernel_symbols_missing_kallsyms
  test_095_kernel_symbols_missing_proc_modules
  test_095_kernel_symbols_missing_proc_net_tcp
  test_300_test_kaslr_base

  The '095' testcases expect the addresses read by a regular user to be
  zeroed out and test '300' expects the default address for 'startup_64'
  to be '8100' for non-kaslr kernels (<4.15). The applied
  backport leaks what the address 0x0 hashes to on the /proc interfaces
  instead of the expected values.

  Examples:
  $ head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  b845aaf2 A vector_irq
  b845aaf2 A unsafe_stack_register_backup
  b845aaf2 A cpu_debug_store
  b845aaf2 A cpu_tss
  b845aaf2 A exception_stacks
  b845aaf2 A gdt_page
  b845aaf2 A espfix_waddr

  $ sudo head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  cd84b193 A vector_irq
  f271a77b A unsafe_stack_register_backup
  b451cc91 A cpu_debug_store
  108c2558 A cpu_tss
  1484be48 A exception_stacks
  0a1b6bc6 A gdt_page
  f38c128a A espfix_waddr

  $ sudo grep -w startup_64 /proc/kallsyms
  28c44c50 T startup_64

  [Fix]
  For the backport to work as expected, we would likely need to backport the 
following commits as well:

  57e734423add vsprintf: refactor %pK code out of pointer()
  ef0010a30935 vsprintf: don't use 'restricted_pointer()' when not restricting

  However, this could introduce other regressions as there are several
  corner cases in this code path.

  Given that the CVEs which are fixed by this patch are all low or
  negligible, the best solution seems to be to revert this patch
  altogether.

  [Test]
  Run ubuntu_qrt_kernel_security.test-kernel-security.py tests from the kernel 
team autotest repository.

  [Where problems could occur]
  Reverting this patch can't introduce any regression as it would return the 
code to the previous state, however it would keep the kernel vulnerable to 
these CVEs.

  [Additional Info]
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922596] Re: linux ADT test failure with linux/4.4.0-208.240

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  linux ADT test failure with linux/4.4.0-208.240

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

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-208.240 on xenial. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210405_165921_51e87@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210405_171150_5e4c6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210405_171645_a1619@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210402_051319_d4fe2@/log.gz


  15:47:57 ERROR| [stderr] 
==
  15:47:57 ERROR| [stderr] FAIL: test_160_setattr_CVE_2015_1350 
(__main__.KernelSecurityTest)
  15:47:57 ERROR| [stderr] Ensure unpriv user cannot strip setattr attributes 
via chown() (CVE-2015-1350)
  15:47:57 ERROR| [stderr] 
--
  15:47:57 ERROR| [stderr] Traceback (most recent call last):
  15:47:57 ERROR| [stderr]   File "./test-kernel-security.py", line 1891, in 
test_160_setattr_CVE_2015_1350
  15:47:57 ERROR| [stderr] self.assertShellOutputEquals(exp_output, 
['sudo', '-u', user, 'getcap', testbin])
  15:47:57 ERROR| [stderr]   File 
"/tmp/autopkgtest.UEYHB2/build.S4Z/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1206, in assertShellOutputEquals
  15:47:57 ERROR| [stderr] self.assertEqual(text, out, msg + result + 
report)
  15:47:57 ERROR| [stderr] AssertionError: Got exit code 0. Looking for exact 
text "" (sudo -u ubuntu getcap /tmp/setattr-GwRjva/true)
  15:47:57 ERROR| [stderr] Command: 'sudo', '-u', 'ubuntu', 'getcap', 
'/tmp/setattr-GwRjva/true'
  15:47:57 ERROR| [stderr] Output:
  15:47:57 ERROR| [stderr] /tmp/setattr-GwRjva/true = cap_sys_nice+ep
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] 
--
  15:47:57 ERROR| [stderr] Ran 125 tests in 24.852s
  15:47:57 ERROR| [stderr] 
  15:47:57 ERROR| [stderr] FAILED (failures=1)

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

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

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

** Description changed:

- This is a scripted bug report about ADT failures while running openafs
- tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
- dep8 tests of thetested source or the kernel has yet to be determined.
+ [Impact]
+ autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).
  
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz
  
  Build error:
  
    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors
  
+ This was caused by commit "fs: Give dentry to inode_change_ok() instead
+ of inode" applied to xenial/linux as part of the fixes for
+ CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().
  
- This was caused by commit "fs: Give dentry to inode_change_ok() instead of 
inode" applied to xenial/linux as part of the fixes for CVE-2015-1350, which 
renamed inode_change_ok() to setattr_prepare().
+ [Fix]
+ The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).
+ 
+ [Test]
+ Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface change (<4.4.0-207) and with a newer kernel with the 
interface change (>=4.4.0-207). The openafs module should be built and loaded 
with all kernels.
+ 
+ [Where problems could occur]
+ The fix is based on the detection made during build time of the function 
available on the kernel headers. If the detection doesn't work correctly the 
build would fail.

** Patch added: "debdiff for openafs on xenial version 1.6.15-1ubuntu2"
   
https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1922242/+attachment/5483223/+files/openafs_1.6.15-1ubuntu2.debdiff

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Triaged

Bug description:
  [Impact]
  autopkgtest caught a build failure with openafs-modules-dkms with the 
xenial/linux kernel currently in -proposed (4.4.0-207.239).

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  This was caused by commit "fs: Give dentry to inode_change_ok()
  instead of inode" applied to xenial/linux as part of the fixes for
  CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare().

  [Fix]
  The proposed fix is to cherry-pick commit 
8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes 
setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git).

  [Test]
  Install openafs-modules-dkms on a xenial system running an older kernel 
without the interface 

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

** Changed in: openafs (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: openafs (Ubuntu Xenial)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running openafs
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

    CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

  
  This was caused by commit "fs: Give dentry to inode_change_ok() instead of 
inode" applied to xenial/linux as part of the fixes for CVE-2015-1350, which 
renamed inode_change_ok() to setattr_prepare().

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

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

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

** Description changed:

  This is a scripted bug report about ADT failures while running openafs
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.
  
  Testing failed on:
- amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
- armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
- s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
+ armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
+ s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz
+ 
+ Build error:
+ 
+   CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
+ 
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
+ 
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
+  code = inode_change_ok(inode, );
+ ^
+ cc1: some warnings being treated as errors

** Description changed:

  This is a scripted bug report about ADT failures while running openafs
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.
  
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz
  
  Build error:
  
-   CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
+   CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
-  code = inode_change_ok(inode, );
- ^
+  code = inode_change_ok(inode, );
+ ^
  cc1: some warnings being treated as errors
+ 
+ 
+ This was caused by commit "fs: Give dentry to inode_change_ok() instead of 
inode" applied to xenial/linux as part of the fixes for CVE-2015-1350, which 
renamed inode_change_ok() to setattr_prepare().

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

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

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

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

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

** Changed in: openafs (Ubuntu)
   Status: New => Invalid

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in openafs package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in openafs source package in Xenial:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running openafs
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 

[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/1922242/+attachment/5483180/+files/make.log

** Also affects: openafs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  New
Status in openafs package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in openafs source package in Xenial:
  New

Bug description:
  This is a scripted bug report about ADT failures while running openafs
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

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

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

[Kernel-packages] [Bug 1922240] [NEW] linux ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

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

Public bug reported:

This is a scripted bug report about ADT failures while running linux
tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
dep8 tests of thetested source or the kernel has yet to be determined.

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

** This bug has been marked a duplicate of bug 1922200
   linux ADT test failure with linux/4.4.0-207.239 - 
ubuntu_qrt_kernel_security.test-kernel-security.py

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

Title:
  linux ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922200] Re: linux ADT test failure with linux/4.4.0-207.239 - ubuntu_qrt_kernel_security.test-kernel-security.py

[Kleber Sacilotto de Souza]

** Tags added: kernel-adt-failure

** Tags added: xenial

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

Title:
  linux ADT test failure with linux/4.4.0-207.239 -
  ubuntu_qrt_kernel_security.test-kernel-security.py

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The backport of upstream commit ad67b74d2469d9b82aaa572d76474c95bc484d57 
("printk: hash addresses printed with %p"), applied to fix CVEs 
CVE-2018-5953/CVE-2018-5995/CVE-2018-7754 on xenial/linux 4.4.0-207.239, 
introduced a regression caught by testcases from 
ubuntu_qrt_kernel_security.test-kernel-security.py testsuite.

  The failing testcases are:
  test_095_kernel_symbols_missing_kallsyms
  test_095_kernel_symbols_missing_proc_modules
  test_095_kernel_symbols_missing_proc_net_tcp
  test_300_test_kaslr_base

  The '095' testcases expect the addresses read by a regular user to be
  zeroed out and test '300' expects the default address for 'startup_64'
  to be '8100' for non-kaslr kernels (<4.15). The applied
  backport leaks what the address 0x0 hashes to on the /proc interfaces
  instead of the expected values.

  Examples:
  $ head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  b845aaf2 A vector_irq
  b845aaf2 A unsafe_stack_register_backup
  b845aaf2 A cpu_debug_store
  b845aaf2 A cpu_tss
  b845aaf2 A exception_stacks
  b845aaf2 A gdt_page
  b845aaf2 A espfix_waddr

  $ sudo head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  cd84b193 A vector_irq
  f271a77b A unsafe_stack_register_backup
  b451cc91 A cpu_debug_store
  108c2558 A cpu_tss
  1484be48 A exception_stacks
  0a1b6bc6 A gdt_page
  f38c128a A espfix_waddr

  $ sudo grep -w startup_64 /proc/kallsyms
  28c44c50 T startup_64

  [Fix]
  For the backport to work as expected, we would likely need to backport the 
following commits as well:

  57e734423add vsprintf: refactor %pK code out of pointer()
  ef0010a30935 vsprintf: don't use 'restricted_pointer()' when not restricting

  However, this could introduce other regressions as there are several
  corner cases in this code path.

  Given that the CVEs which are fixed by this patch are all low or
  negligible, the best solution seems to be to revert this patch
  altogether.

  [Test]
  Run ubuntu_qrt_kernel_security.test-kernel-security.py tests from the kernel 
team autotest repository.

  [Where problems could occur]
  Reverting this patch can't introduce any regression as it would return the 
code to the previous state, however it would keep the kernel vulnerable to 
these CVEs.

  [Additional Info]
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922242] [NEW] openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

Public bug reported:

This is a scripted bug report about ADT failures while running openafs
tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
dep8 tests of thetested source or the kernel has yet to be determined.

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

Build error:

  CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
 code = inode_change_ok(inode, );
^
cc1: some warnings being treated as errors

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

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

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

** Affects: openafs (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  New
Status in openafs package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in openafs source package in Xenial:
  New

Bug description:
  This is a scripted bug report about ADT failures while running openafs
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  dep8 tests of thetested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz

  Build error:

CC [M]  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:
 In function ‘osi_UFSTruncate’:
  
/var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12:
 error: implicit declaration of function ‘inode_change_ok’ 
[-Werror=implicit-function-declaration]
   code = inode_change_ok(inode, );
  ^
  cc1: some warnings being treated as errors

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

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

[Kernel-packages] [Bug 1922200] Re: linux ADT test failure with linux/4.4.0-207.239 - ubuntu_qrt_kernel_security.test-kernel-security.py

[Kleber Sacilotto de Souza]

** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1922200

Title:
  linux ADT test failure with linux/4.4.0-207.239 -
  ubuntu_qrt_kernel_security.test-kernel-security.py

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The backport of upstream commit ad67b74d2469d9b82aaa572d76474c95bc484d57 
("printk: hash addresses printed with %p"), applied to fix CVEs 
CVE-2018-5953/CVE-2018-5995/CVE-2018-7754 on xenial/linux 4.4.0-207.239, 
introduced a regression caught by testcases from 
ubuntu_qrt_kernel_security.test-kernel-security.py testsuite.

  The failing testcases are:
  test_095_kernel_symbols_missing_kallsyms
  test_095_kernel_symbols_missing_proc_modules
  test_095_kernel_symbols_missing_proc_net_tcp
  test_300_test_kaslr_base

  The '095' testcases expect the addresses read by a regular user to be
  zeroed out and test '300' expects the default address for 'startup_64'
  to be '8100' for non-kaslr kernels (<4.15). The applied
  backport leaks what the address 0x0 hashes to on the /proc interfaces
  instead of the expected values.

  Examples:
  $ head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  b845aaf2 A vector_irq
  b845aaf2 A unsafe_stack_register_backup
  b845aaf2 A cpu_debug_store
  b845aaf2 A cpu_tss
  b845aaf2 A exception_stacks
  b845aaf2 A gdt_page
  b845aaf2 A espfix_waddr

  $ sudo head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  cd84b193 A vector_irq
  f271a77b A unsafe_stack_register_backup
  b451cc91 A cpu_debug_store
  108c2558 A cpu_tss
  1484be48 A exception_stacks
  0a1b6bc6 A gdt_page
  f38c128a A espfix_waddr

  $ sudo grep -w startup_64 /proc/kallsyms
  28c44c50 T startup_64

  [Fix]
  For the backport to work as expected, we would likely need to backport the 
following commits as well:

  57e734423add vsprintf: refactor %pK code out of pointer()
  ef0010a30935 vsprintf: don't use 'restricted_pointer()' when not restricting

  However, this could introduce other regressions as there are several
  corner cases in this code path.

  Given that the CVEs which are fixed by this patch are all low or
  negligible, the best solution seems to be to revert this patch
  altogether.

  [Test]
  Run ubuntu_qrt_kernel_security.test-kernel-security.py tests from the kernel 
team autotest repository.

  [Where problems could occur]
  Reverting this patch can't introduce any regression as it would return the 
code to the previous state, however it would keep the kernel vulnerable to 
these CVEs.

  [Additional Info]
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922200] Re: linux ADT test failure with linux/4.4.0-207.239 - ubuntu_qrt_kernel_security.test-kernel-security.py

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  linux ADT test failure with linux/4.4.0-207.239 -
  ubuntu_qrt_kernel_security.test-kernel-security.py

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]
  The backport of upstream commit ad67b74d2469d9b82aaa572d76474c95bc484d57 
("printk: hash addresses printed with %p"), applied to fix CVEs 
CVE-2018-5953/CVE-2018-5995/CVE-2018-7754 on xenial/linux 4.4.0-207.239, 
introduced a regression caught by testcases from 
ubuntu_qrt_kernel_security.test-kernel-security.py testsuite.

  The failing testcases are:
  test_095_kernel_symbols_missing_kallsyms
  test_095_kernel_symbols_missing_proc_modules
  test_095_kernel_symbols_missing_proc_net_tcp
  test_300_test_kaslr_base

  The '095' testcases expect the addresses read by a regular user to be
  zeroed out and test '300' expects the default address for 'startup_64'
  to be '8100' for non-kaslr kernels (<4.15). The applied
  backport leaks what the address 0x0 hashes to on the /proc interfaces
  instead of the expected values.

  Examples:
  $ head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  b845aaf2 A vector_irq
  b845aaf2 A unsafe_stack_register_backup
  b845aaf2 A cpu_debug_store
  b845aaf2 A cpu_tss
  b845aaf2 A exception_stacks
  b845aaf2 A gdt_page
  b845aaf2 A espfix_waddr

  $ sudo head /proc/kallsyms
  b845aaf2 A irq_stack_union
  b845aaf2 A __per_cpu_start
  b845aaf2 A __per_cpu_user_mapped_start
  cd84b193 A vector_irq
  f271a77b A unsafe_stack_register_backup
  b451cc91 A cpu_debug_store
  108c2558 A cpu_tss
  1484be48 A exception_stacks
  0a1b6bc6 A gdt_page
  f38c128a A espfix_waddr

  $ sudo grep -w startup_64 /proc/kallsyms
  28c44c50 T startup_64

  [Fix]
  For the backport to work as expected, we would likely need to backport the 
following commits as well:

  57e734423add vsprintf: refactor %pK code out of pointer()
  ef0010a30935 vsprintf: don't use 'restricted_pointer()' when not restricting

  However, this could introduce other regressions as there are several
  corner cases in this code path.

  Given that the CVEs which are fixed by this patch are all low or
  negligible, the best solution seems to be to revert this patch
  altogether.

  [Test]
  Run ubuntu_qrt_kernel_security.test-kernel-security.py tests from the kernel 
team autotest repository.

  [Where problems could occur]
  Reverting this patch can't introduce any regression as it would return the 
code to the previous state, however it would keep the kernel vulnerable to 
these CVEs.

  [Additional Info]
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922200] Re: linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

** Description changed:

- This is a scripted bug report about ADT failures while running linux
- tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
- tested source or the kernel has yet to be determined.
+ [Impact]
+ The backport of upstream commit ad67b74d2469d9b82aaa572d76474c95bc484d57 
("printk: hash addresses printed with %p"), applied to fix CVEs 
CVE-2018-5953/CVE-2018-5995/CVE-2018-7754 on xenial/linux 4.4.0-207.239, 
introduced a regression caught by testcases from 
ubuntu_qrt_kernel_security.test-kernel-security.py testsuite.
  
+ The failing testcases are:
+ test_095_kernel_symbols_missing_kallsyms
+ test_095_kernel_symbols_missing_proc_modules
+ test_095_kernel_symbols_missing_proc_net_tcp
+ test_300_test_kaslr_base
+ 
+ The '095' testcases expect the addresses read by a regular user to be
+ zeroed out and test '300' expects the default address for 'startup_64'
+ to be '8100' for non-kaslr kernels (<4.15). The applied
+ backport leaks what the address 0x0 hashes to on the /proc interfaces
+ instead of the expected values.
+ 
+ Examples:
+ $ head /proc/kallsyms
+ b845aaf2 A irq_stack_union
+ b845aaf2 A __per_cpu_start
+ b845aaf2 A __per_cpu_user_mapped_start
+ b845aaf2 A vector_irq
+ b845aaf2 A unsafe_stack_register_backup
+ b845aaf2 A cpu_debug_store
+ b845aaf2 A cpu_tss
+ b845aaf2 A exception_stacks
+ b845aaf2 A gdt_page
+ b845aaf2 A espfix_waddr
+ 
+ $ sudo head /proc/kallsyms
+ b845aaf2 A irq_stack_union
+ b845aaf2 A __per_cpu_start
+ b845aaf2 A __per_cpu_user_mapped_start
+ cd84b193 A vector_irq
+ f271a77b A unsafe_stack_register_backup
+ b451cc91 A cpu_debug_store
+ 108c2558 A cpu_tss
+ 1484be48 A exception_stacks
+ 0a1b6bc6 A gdt_page
+ f38c128a A espfix_waddr
+ 
+ $ sudo grep -w startup_64 /proc/kallsyms
+ 28c44c50 T startup_64
+ 
+ [Fix]
+ For the backport to work as expected, we would likely need to backport the 
following commits as well:
+ 
+ 57e734423add vsprintf: refactor %pK code out of pointer()
+ ef0010a30935 vsprintf: don't use 'restricted_pointer()' when not restricting
+ 
+ However, this could introduce other regressions as there are several
+ corner cases in this code path.
+ 
+ Given that the CVEs which are fixed by this patch are all low or
+ negligible, the best solution seems to be to revert this patch
+ altogether.
+ 
+ [Test]
+ Run ubuntu_qrt_kernel_security.test-kernel-security.py tests from the kernel 
team autotest repository.
+ 
+ [Where problems could occur]
+ Reverting this patch can't introduce any regression as it would return the 
code to the previous state, however it would keep the kernel vulnerable to 
these CVEs.
+ 
+ [Additional Info]
  Testing failed on:
- amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
- i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
- ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
- s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
+ i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
+ ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
+ s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

** Summary changed:

- linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239
+ linux ADT test failure with linux/4.4.0-207.239 - 
ubuntu_qrt_kernel_security.test-kernel-security.py

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

Title:
  linux ADT test failure with linux/4.4.0-207.239 -
  ubuntu_qrt_kernel_security.test-kernel-security.py

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]
  The backport of upstream commit ad67b74d2469d9b82aaa572d76474c95bc484d57 
("printk: hash addresses printed with %p"), applied to fix CVEs 

[Kernel-packages] [Bug 1922200] Re: linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  tested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922199] Re: linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

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

** This bug has been marked a duplicate of bug 1922200
   linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

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

Title:
  linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  tested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922199] [NEW] linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

Public bug reported:

This is a scripted bug report about ADT failures while running linux
tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
tested source or the kernel has yet to be determined.

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

Title:
  linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  tested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1922200] [NEW] linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

[Kleber Sacilotto de Souza]

Public bug reported:

This is a scripted bug report about ADT failures while running linux
tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
tested source or the kernel has yet to be determined.

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

Title:
  linux/4.4.0-207.239 ADT test failure with linux/4.4.0-207.239

Status in linux package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.4.0-207.239 on xenial. Whether this is caused by the
  tested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20210331_014541_79861@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20210331_012734_ec0bc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20210331_014757_ec0bc@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20210330_031532_e87f8@/log.gz

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

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

[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239

[Kleber Sacilotto de Souza]

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

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

Title:
  lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz


  
  Starting c1
  action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror 
msg="Failed starting container" name=c1 stateful=false 
t=2021-03-30T02:42:14+
  error: Error calling 'lxd forkstart c1 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': 
err='Failed to run: /usr/bin/lxd forkstart c1 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: '
lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script 
exited with status 137.
lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to 
run mount hooks for container 'c1'.
lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to 
setup container "c1".
lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error 
occurred in another process (expected sequence number 5)
lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed 
to spawn container "c1".
lxc 20210330024214.663 ERROR lxc_container - 
lxccontainer.c:wait_on_daemonized_start:804 - Received container state 
"ABORTING" instead of "RUNNING"

  Try `lxc info --show-log lxd2:c1` for more info
  ==> Cleaning up
  ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
  ==> Deleting all containers
  ==> Deleting all images
  ==> Deleting all profiles
  Profile default deleted
  Profile docker deleted
  ==> Checking for locked DB tables
  ==> Checking for leftover files
  ==> Checking for leftover DB entries
  ==> Tearing down directory backend in 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
  ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
  ==> Deleting all containers
  ==> Deleting all images
  ==> Deleting all profiles
  Profile default deleted
  Profile docker deleted
  ==> Checking for locked DB tables
  ==> Checking for leftover files
  ==> Checking for leftover DB entries
  ==> Tearing down directory backend in 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt

  
  ==> TEST DONE: remote usage
  ==> Test result: failure

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

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

[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239

[Kleber Sacilotto de Souza]

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

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

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

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

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

Title:
  lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz


  
  Starting c1
  action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror 
msg="Failed starting container" name=c1 stateful=false 
t=2021-03-30T02:42:14+
  error: Error calling 'lxd forkstart c1 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': 
err='Failed to run: /usr/bin/lxd forkstart c1 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: '
lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script 
exited with status 137.
lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to 
run mount hooks for container 'c1'.
lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to 
setup container "c1".
lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error 
occurred in another process (expected sequence number 5)
lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed 
to spawn container "c1".
lxc 20210330024214.663 ERROR lxc_container - 
lxccontainer.c:wait_on_daemonized_start:804 - Received container state 
"ABORTING" instead of "RUNNING"

  Try `lxc info --show-log lxd2:c1` for more info
  ==> Cleaning up
  ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
  ==> Deleting all containers
  ==> Deleting all images
  ==> Deleting all profiles
  Profile default deleted
  Profile docker deleted
  ==> Checking for locked DB tables
  ==> Checking for leftover files
  ==> Checking for leftover DB entries
  ==> Tearing down directory backend in 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
  ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
  ==> Deleting all containers
  ==> Deleting all images
  ==> Deleting all profiles
  Profile default deleted
  Profile docker deleted
  ==> Checking for locked DB tables
  ==> Checking for leftover files
  ==> Checking for leftover DB entries
  ==> Tearing down directory backend in 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt

  
  ==> TEST DONE: remote usage
  ==> Test result: failure

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

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

[Kernel-packages] [Bug 1920995] Re: selftests: bpf verifier fails after sanitize_ptr_alu fixes

[Kleber Sacilotto de Souza]

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

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

Title:
  selftests: bpf verifier fails after sanitize_ptr_alu fixes

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  bpf selftests will fail after applying fixes from 5.8.0-48 and 5.4.0-70.

  [Fix]
  Apply selftests fixes and bpf verifier simplification and hardening.

  [Test Plan]
  Ran the verifier test and other tests for the latest BPF fixes.

  [Potential regression]
  BPF programs that worked before may stop working or, worse, programs that 
should not be allowed may start working.

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

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

[Kernel-packages] [Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable

[Kleber Sacilotto de Souza]

** Summary changed:

- mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with 
script is not executable on B-AWS-5.3
+ mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with 
script is not executable

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed with script is not executable

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Issue found on Bionic 5.3.0-1033.35-aws

  TAP version 13
   1..1
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Warning: file mem-on-off-test.sh is not executable, correct this.
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug'
   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  ubuntu_ker:0242| == Summary ===
  ubuntu_ker:0076| Sub test case: mem-on-off-test.sh failed.

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

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

[Kernel-packages] [Bug 1909647] Re: xfrm_policy.sh in net from ubuntu_kernel_selftests passed with failed sub-cases

[Kleber Sacilotto de Souza]

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

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

Title:
  xfrm_policy.sh in net from ubuntu_kernel_selftests passed with failed
  sub-cases

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  Even with failed cases reported in the xfrm_policy.sh test, the overall 
result is still "PASS"
  $ sudo ./xfrm_policy.sh
   # selftests: net: xfrm_policy.sh
   # PASS: policy before exception matches
   # FAIL: expected ping to .254 to fail (exceptions)
   # PASS: direct policy matches (exceptions)
   # PASS: policy matches (exceptions)
   # FAIL: expected ping to .254 to fail (exceptions and block policies)
   # PASS: direct policy matches (exceptions and block policies)
   # PASS: policy matches (exceptions and block policies)
   # FAIL: expected ping to .254 to fail (exceptions and block policies after 
hresh changes)
   # PASS: direct policy matches (exceptions and block policies after hresh 
changes)
   # PASS: policy matches (exceptions and block policies after hresh changes)
   # FAIL: expected ping to .254 to fail (exceptions and block policies after 
hthresh change in ns3)
   # PASS: direct policy matches (exceptions and block policies after hthresh 
change in ns3)
   # PASS: policy matches (exceptions and block policies after hthresh change 
in ns3)
   # FAIL: expected ping to .254 to fail (exceptions and block policies after 
htresh change to normal)
   # PASS: direct policy matches (exceptions and block policies after htresh 
change to normal)
   # PASS: policy matches (exceptions and block policies after htresh change to 
normal)
   # PASS: policies with repeated htresh change
   ok 12 selftests: net: xfrm_policy.sh
  $ echo $?
  0

  This is because of the variable "lret" in check_xfrm() is not a local
  variable, and it looks like it will override the one in
  check_exceptions() thus making the return value become 0 for the
  passed test case after the failed one.

  [Fix]
  * f6e9ceb7a7fc32 (" selftests: xfrm: fix test return value override issue in 
xfrm_policy.sh")

  Focal kernel got this patch via stable update, and we don't have this
  test in Bionic. Only Groovy and OEM-5.6 are affected.

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

  [Test]
  Run the xfrm_policy.sh test, if there is any failed case the final result 
will not be 0.

  [Regression Potential]
  This change is just for testing tools, it's unlikely to affect real kernel 
functionality. However it's expected to generate failures in our test report as 
it's reflecting the real test result.

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

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

[Kernel-packages] [Bug 1918228] Re: Fix missing HDMI/DP audio on NVidia card after S3

[Kleber Sacilotto de Souza]

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

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

Title:
  Fix missing HDMI/DP audio on NVidia card after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  NVidia DP/HDMI aduio disappears after S3.
  This is a regression introduced by LP: #1867704.

  [Fix]
  Update ELD properly so jack status is correctly reported.

  [Test]
  Perform S3 and open Sound Settings. With the fix applied, the DP/HDMI
  audio is always present after S3.

  [Where problems could occur]
  This series changes how ELD gets update. So if device depends on the
  original behavior, jack status could be wrong after this fix.

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

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

[Kernel-packages] [Bug 1918330] Re: Bionic update: upstream stable patchset 2021-03-09

[Kleber Sacilotto de Souza]

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

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

Title:
  Bionic update: upstream stable patchset 2021-03-09

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2021-03-09

  Ported from the following upstream stable releases:
  v4.14.219, v4.19.173,
  v4.14.220, v4.19.174,
  v4.14.221, v4.19.175,
 v4.19.176

     from git://git.kernel.org/

  ACPI: sysfs: Prefer "compatible" modalias
  ARM: dts: imx6qdl-gw52xx: fix duplicate regulator naming
  wext: fix NULL-ptr-dereference with cfg80211's lack of commit()
  net: usb: qmi_wwan: added support for Thales Cinterion PLSx3 modem family
  drivers: soc: atmel: Avoid calling at91_soc_init on non AT91 SoCs
  drivers: soc: atmel: add null entry at the end of at91_soc_allowed_list[]
  KVM: x86/pmu: Fix HW_REF_CPU_CYCLES event pseudo-encoding in 
intel_arch_events[]
  KVM: x86: get smi pending status correctly
  xen: Fix XenStore initialisation for XS_LOCAL
  leds: trigger: fix potential deadlock with libata
  mt7601u: fix kernel crash unplugging the device
  mt7601u: fix rx buffer refcounting
  xen-blkfront: allow discard-* nodes to be optional
  ARM: imx: build suspend-imx6.S with arm instruction set
  netfilter: nft_dynset: add timeout extension to template
  xfrm: Fix oops in xfrm_replay_advance_bmp
  RDMA/cxgb4: Fix the reported max_recv_sge value
  iwlwifi: pcie: use jiffies for memory read spin time limit
  iwlwifi: pcie: reschedule in long-running memory reads
  mac80211: pause TX while changing interface type
  can: dev: prevent potential information leak in can_fill_info()
  x86/entry/64/compat: Preserve r8-r11 in int $0x80
  x86/entry/64/compat: Fix "x86/entry/64/compat: Preserve r8-r11 in int $0x80"
  iommu/vt-d: Gracefully handle DMAR units with no supported address widths
  iommu/vt-d: Don't dereference iommu_device if IOMMU_API is not built
  NFC: fix resource leak when target index is invalid
  NFC: fix possible resource leak
  team: protect features update by RCU to avoid deadlock
  tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN
  kernel: kexec: remove the lock operation of system_transition_mutex
  PM: hibernate: flush swap writer after marking
  pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()
  net/mlx5: Fix memory leak on flow table creation error flow
  rxrpc: Fix memory leak in rxrpc_lookup_local
  UBUNTU: upstream stable to v4.14.219, v4.19.173
  net: dsa: bcm_sf2: put device node before return
  ibmvnic: Ensure that CRQ entry read are correctly ordered
  ACPI: thermal: Do not call acpi_thermal_check() directly
  net_sched: gen_estimator: support large ewma log
  phy: cpcap-usb: Fix warning for missing regulator_disable
  x86: __always_inline __{rd,wr}msr()
  scsi: scsi_transport_srp: Don't block target in failfast state
  scsi: libfc: Avoid invoking response handler twice if ep is already completed
  mac80211: fix fast-rx encryption check
  scsi: ibmvfc: Set default timeout to avoid crash during migration
  objtool: Don't fail on missing symbol table
  kthread: Extract KTHREAD_IS_PER_CPU
  workqueue: Restrict affinity change to rescuer
  UBUNTU: upstream stable to v4.14.220, v4.19.174
  USB: serial: cp210x: add pid/vid for WSDA-200-USB
  USB: serial: cp210x: add new VID/PID for supporting Teraoka AD2000
  USB: serial: option: Adding support for Cinterion MV31
  arm64: dts: ls1046a: fix dcfg address range
  net: lapb: Copy the skb before sending a packet
  elfcore: fix building with clang
  USB: gadget: legacy: fix an error code in eth_bind()
  USB: usblp: don't call usb_set_interface if there's a single alt
  usb: dwc2: Fix endpoint direction check in ep_from_windex
  ovl: fix dentry leak in ovl_get_redirect
  mac80211: fix station rate table updates on assoc
  kretprobe: Avoid re-registration of the same kretprobe earlier
  xhci: fix bounce buffer usage for non-sg list case
  cifs: report error instead of invalid when revalidating a dentry fails
  smb3: Fix out-of-bounds bug in SMB2_negotiate()
  mmc: core: Limit retries when analyse of SDIO tuples fails
  nvme-pci: avoid the deepest sleep state on Kingston A2000 SSDs
  ARM: 

[Kernel-packages] [Bug 1917918] Re: SRU: Add FUA support for XFS

[Kleber Sacilotto de Souza]

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

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

Title:
  SRU: Add FUA support for XFS

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]

  This 4 patch set adds backported support for Forced Unit Access (FUA)
  on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS
  was added upstream in 4.18.

  FUA on XFS is important for SQL server work loads.

  [Test Plan]
  SQLIOSIM (a package from Microsoft) was used to test performance 
improvements. Tests were run with an XFS file system mounted on a persistent 
memory block device (PMEM) partition. Performance metrics were found to exhibit 
satisfactory improvement gains from the GA kernel.

  [Where problems could occur]

  Well, these are patches to file system code. They _could_ cause
  widespread corruption. However, multiple test passes with sqliosim
  exhibited no issues.

  [Other Info]

  See attached sqliosim.cfg.ini configuration file for test run
  parameters.

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

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

[Kernel-packages] [Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure

[Kleber Sacilotto de Souza]

I suspect the "ERROR: testbed failure: testbed auxverb failed with exit
code 255" messages are only the symptom and not the cause of the
failures.

All the arm64 failures are consistent and the last tests executed are
always the following:

[...]
19:05:33 INFO | START   ubuntu_kernel_selftests.ftrace  
ubuntu_kernel_selftests.ftrace  timestamp=1600715133timeout=1800
localtime=Sep 21 19:05:33   
[...]
19:06:44 DEBUG| [stdout] # [46] Create/delete multiprobe on kprobe event
[PASS]
19:06:46 DEBUG| [stdout] # [47] Kprobe event parser error log check [PASS]
19:06:46 DEBUG| [stdout] # [48] Kretprobe dynamic event with arguments  [PASS]
19:06:47 DEBUG| [stdout] # [49] Kretprobe dynamic event with maxactive  [PASS]
autopkgtest-virt-ssh [19:26:52]: --- nova console-log 
939a7972-4eb7-4814-a489-046ce015ad8e (adt-groovy-arm64-linux-20200921-123119) 
--
[...]

>From comment #2 on bug 1549425:

"The auxverb is "ssh" in this case, and it exiting with 255 means that
the ssh connection was interrupted."

So I suspect some ftrace test is causing a kernel hang, killing the ssh
connection. I don't see anything suspicious on the adt console logs
though. We might need to try to reproduce this manually to get some more
information.

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

Title:
  testbed auxverb failed with exit code 255 with linux on Groovy ADT
  failure

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

Bug description:
  Testing failed on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/linux/20210308_234307_e716b@/log.gz

  
  Looks to be a flaky test with this error occurring frequently. This is not a 
regression. 

  Found a previously reported (expired) bug with the same error:
  https://launchpad.net/bugs/1549425

  
  [ 6606.751232] audit: backlog limit Creating nova instance 
adt-groovy-arm64-linux-20210308-143145 from image 
adt/ubuntu-groovy-arm64-server-20210308.img (UUID 
1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)...
  Creating nova instance adt-groovy-arm64-linux-20210308-143145 from image 
adt/ubuntu-groovy-arm64-server-20210308.img (UUID 
1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)...
  autopkgtest [23:42:55]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

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

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

[Kernel-packages] [Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure

[Kleber Sacilotto de Souza]

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

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

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

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

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

Title:
  testbed auxverb failed with exit code 255 with linux on Groovy ADT
  failure

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

Bug description:
  Testing failed on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/linux/20210308_234307_e716b@/log.gz

  
  Looks to be a flaky test with this error occurring frequently. This is not a 
regression. 

  Found a previously reported (expired) bug with the same error:
  https://launchpad.net/bugs/1549425

  
  [ 6606.751232] audit: backlog limit Creating nova instance 
adt-groovy-arm64-linux-20210308-143145 from image 
adt/ubuntu-groovy-arm64-server-20210308.img (UUID 
1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)...
  Creating nova instance adt-groovy-arm64-linux-20210308-143145 from image 
adt/ubuntu-groovy-arm64-server-20210308.img (UUID 
1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)...
  autopkgtest [23:42:55]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

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

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

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Kleber Sacilotto de Souza]

Hi Dimitri,

These are the dkms packages which had the build failure fixed after the
-hwe switch in Focal from 5.4 to 5.8:

bcmwl=6.30.223.271+bdcom-0ubuntu7~20.04.1
nvidia-graphics-drivers-340=340.108-0ubuntu5.20.04.1
virtualbox-hwe=6.1.16-dfsg-6ubuntu1.20.04.1

And this is the list of all the other dkms packages which had to be
updated to fix build failures in Focal with the 5.8 kernel:

acpi-call=1.1.0-5ubuntu0.1
backport-iwlwifi-dkms=8324-0ubuntu3~20.04.2
dahdi-linux=1:2.11.1~dfsg-1ubuntu6.1
dm-writeboost=2.2.9-1ubuntu1.1
evdi=1.7.0+dfsg-1ubuntu1~20.04.2
gost-crypto=0.3.2-2ubuntu0.1
iptables-netflow=2.4-2ubuntu0.2
lime-forensics=1.9-1ubuntu0.1
lttng-modules=2.12.2-1ubuntu1~20.04.1
openafs=1.8.4~pre1-1ubuntu2.1
oss4=4.2-build2010-5ubuntu6~20.04.1
r8168=8.048.00-1ubuntu0.20.04.1
rtl8812au=4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.1
sysdig=0.26.4-1ubuntu0.2
v4l2loopback=0.12.3-1ubuntu0.3
virtualbox=6.1.16-dfsg-6~ubuntu1.20.04.1
zfs-linux=0.8.3-1ubuntu12.6

None of these updates has been released to -security, so if we want to
make sure that users running the hwe-5.8 kernel from -security will not
get broken dkms packages we need to release them all.

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Kleber Sacilotto de Souza]

The issue with the dkms package has been fixed via bug 1915051.

** Changed in: dkms (Ubuntu)
   Status: New => Fix Released

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy

[Kleber Sacilotto de Souza]

Patch sent to the ML:

https://lists.ubuntu.com/archives/kernel-team/2021-March/117753.html

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

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

Title:
  [Regression] ubuntu_bpf failed to build on Groovy

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Upstream commit d3bec0138bfbe58606fc1d6f57a4cdc1a20218db (bpf: Zero-fill 
re-used per-cpu map element) was applied to Groovy as part of an upstream 
stable update. This patch fixes a bpf issue and at the same time adds new 
selftests to verify these changes. However, the selftests can't be compiled on 
5.8 due to missing helper functions that were added only later. The bpf 
selftest build fails with errors such as:

  /usr/bin/ld: 
/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/map_init.test.o:
 in function `prog_run_insert_elem':

/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/prog_tests/map_init.c:89:
 undefined reference to `ASSERT_OK'

  [Fix]
  The proposed fix it to partially revert this commit by removing the selftests 
parts.

  [Testcase]
  On a groovy/linux repo:

  $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS=

  [Where problems could occur]
  By removing the selftests we could be introducing a regression with the bpf 
code change which would be likely unoticed during the tests.

  
   Original Description 

  Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle

  Test failed to build, I didn't see any meaningful error message, this
  might need to be double checked.

  HDRINST usr/include/asm/fcntl.h
  HDRINST usr/include/asm/termbits.h
  HDRINST usr/include/asm/errno.h
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    make: *** [Makefile:159: all] Error 1

  Please find attachment for the complete test log.

  == Process to reproduce this ==
  1. git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy
  2. cd groovy/tools/testing/selftests
  3. make TARGETS=bpf
  You will see the build failed if it's affected by this.

  I think this is affecting the ubuntu_kernel_selftests as well, as the
  net test would require the bpf test to be built first.

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

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

[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy

[Kleber Sacilotto de Souza]

** Description changed:

+ [Impact]
+ Upstream commit d3bec0138bfbe58606fc1d6f57a4cdc1a20218db (bpf: Zero-fill 
re-used per-cpu map element) was applied to Groovy as part of an upstream 
stable update. This patch fixes a bpf issue and at the same time adds new 
selftests to verify these changes. However, the selftests can't be compiled on 
5.8 due to missing helper functions that were added only later. The bpf 
selftest build fails with errors such as:
+ 
+ /usr/bin/ld: 
/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/map_init.test.o:
 in function `prog_run_insert_elem':
+   
/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/prog_tests/map_init.c:89:
 undefined reference to `ASSERT_OK'
+ 
+ [Fix]
+ The proposed fix it to partially revert this commit by removing the selftests 
parts.
+ 
+ [Testcase]
+ On a groovy/linux repo:
+ 
+ $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS=
+ 
+ [Where problems could occur]
+ By removing the selftests we could be introducing a regression with the bpf 
code change which would be likely unoticed during the tests.
+ 
+ 
+  Original Description 
+ 
  Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle
  
  Test failed to build, I didn't see any meaningful error message, this
  might need to be double checked.
  
  HDRINST usr/include/asm/fcntl.h
  HDRINST usr/include/asm/termbits.h
  HDRINST usr/include/asm/errno.h
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    make: *** [Makefile:159: all] Error 1
  
  Please find attachment for the complete test log.
  
  == Process to reproduce this ==
  1. git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy
  2. cd groovy/tools/testing/selftests
  3. make TARGETS=bpf
  You will see the build failed if it's affected by this.
  
  I think this is affecting the ubuntu_kernel_selftests as well, as the
  net test would require the bpf test to be built first.

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

Title:
  [Regression] ubuntu_bpf failed to build on Groovy

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Upstream commit d3bec0138bfbe58606fc1d6f57a4cdc1a20218db (bpf: Zero-fill 
re-used per-cpu map element) was applied to Groovy as part of an upstream 
stable update. This patch fixes a bpf issue and at the same time adds new 
selftests to verify these changes. However, the selftests can't be compiled on 
5.8 due to missing helper functions that were added only later. The bpf 
selftest build fails with errors such as:

  /usr/bin/ld: 
/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/map_init.test.o:
 in function `prog_run_insert_elem':

/tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/prog_tests/map_init.c:89:
 undefined reference to `ASSERT_OK'

  [Fix]
  The proposed fix it to partially revert this commit by removing the selftests 
parts.

  [Testcase]
  On a groovy/linux repo:

  $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS=

  [Where problems could occur]
  By removing the selftests we could be introducing a regression with the bpf 
code change which would be likely unoticed during the tests.

  
   Original Description 

  Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle

  Test failed to build, I didn't see any meaningful error message, this
  might need to be double checked.

  HDRINST usr/include/asm/fcntl.h
  HDRINST usr/include/asm/termbits.h
  HDRINST usr/include/asm/errno.h
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    make: *** [Makefile:159: all] Error 1

  Please find attachment for the complete test log.

  == Process to reproduce this ==
  1. git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy
  2. cd groovy/tools/testing/selftests
  3. make TARGETS=bpf
  You will see the build failed if it's affected by this.

  I think this is affecting the ubuntu_kernel_selftests as well, as the
  net test would require the bpf test to be built first.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy

[Kleber Sacilotto de Souza]

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

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

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

Title:
  [Regression] ubuntu_bpf failed to build on Groovy

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle

  Test failed to build, I didn't see any meaningful error message, this
  might need to be double checked.

  HDRINST usr/include/asm/fcntl.h
  HDRINST usr/include/asm/termbits.h
  HDRINST usr/include/asm/errno.h
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    make: *** [Makefile:159: all] Error 1

  Please find attachment for the complete test log.

  == Process to reproduce this ==
  1. git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy
  2. cd groovy/tools/testing/selftests
  3. make TARGETS=bpf
  You will see the build failed if it's affected by this.

  I think this is affecting the ubuntu_kernel_selftests as well, as the
  net test would require the bpf test to be built first.

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

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

[Kernel-packages] [Bug 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM

[Kleber Sacilotto de Souza]

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

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

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

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

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed on X-gcp-4.15 / F-5.4 zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on Focal 5.4.0-49.53 zVM kernel04

  Test failed with:
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Test scope: 2% hotplug memory
   # online all hot-pluggable memory in offline state:
   # SKIPPED - no hot-pluggable memory in offline state
   # offline 2% hot-pluggable memory in online state
   # trying to offline 1 out of 16 memory block(s):
   # online->offline memory0
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 0: unexpected fail
   # online->offline memory1
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 1: unexpected fail
   # online->offline memory10
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 10: unexpected fail
   # online->offline memory11
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 11: unexpected fail
   # online->offline memory12
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 12: unexpected fail
   # online->offline memory13
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 13: unexpected fail
   # online->offline memory14
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 14: unexpected fail
   # online->offline memory15
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 15: unexpected fail
   # online->offline memory2
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 2: unexpected fail
   # online->offline memory3
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 3: unexpected fail
   # online->offline memory4
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 4: unexpected fail
   # online->offline memory5
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 5: unexpected fail
   # online->offline memory6
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 6: unexpected fail
   # online->offline memory7
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 7: unexpected fail
   # online->offline memory8
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 8: unexpected fail
   # online->offline memory9
   # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
   # offline_memory_expect_success 9: unexpected fail
   # FAILED - unable to offline some memory blocks, device busy?
   # online all hot-pluggable memory in offline state:
   # SKIPPED - no hot-pluggable memory in offline state
   # Test with memory notifier error injection
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1

  This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well.
  Passed with 5.4.0-44.48
  Passed with 5.4.0-43.47
  Failed with 5.4.0-42.46

  Looks like it's not very stable.

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

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

[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy

[Kleber Sacilotto de Souza]

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

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

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

Title:
  [Regression] ubuntu_bpf failed to build on Groovy

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle

  Test failed to build, I didn't see any meaningful error message, this
  might need to be double checked.

  HDRINST usr/include/asm/fcntl.h
  HDRINST usr/include/asm/termbits.h
  HDRINST usr/include/asm/errno.h
  INSTALL ./usr/include
    make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux'
    make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
    stderr:
    make: *** [Makefile:159: all] Error 1

  Please find attachment for the complete test log.

  == Process to reproduce this ==
  1. git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy
  2. cd groovy/tools/testing/selftests
  3. make TARGETS=bpf
  You will see the build failed if it's affected by this.

  I think this is affecting the ubuntu_kernel_selftests as well, as the
  net test would require the bpf test to be built first.

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Kleber Sacilotto de Souza]

The upstream fix "b160c28548bc tcp: do not mess with cloned skbs in
tcp_add_backlog()" has been applied to focal/linux as part of the fixes
for bug 1915195 (Focal update: v5.4.93 upstream stable release). It will
be included for the next focal/linux-raspi, however this bug report will
not be closed automatically.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  A mix of incoming TCP traffic, forwarding packets and saturating the
  link results in lan78xx TX queue timeouts which brings the network
  interface down.

  [Test Case]

  Se comment #99 below.

  [Where Problems Could Occur]

  Probably lost or corrupted TCP packets. Most likely not worse than
  what we're currently seeing.

  [Original Description]

  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  

[Kernel-packages] [Bug 1893024] Re: failing ftrace self tests from 5.7+ onwards

[Kleber Sacilotto de Souza]

ftrace testcase completed successfully with focal/linux 5.4.0-66.74 in
-proposed:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/l/linux/20210205_135222_29af6@/log.gz

** Tags removed: verification-needed-focal
** Tags added: verification-doe-focal

** Tags removed: verification-doe-focal
** Tags added: verification-done-focal

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

Title:
  failing ftrace self tests from 5.7+ onwards

Status in Linux:
  Confirmed
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Ftrace regression tests in tools/testing/selftests/ftrace are picking
  up regressions in 5.7+ - not sure if these are kernel regressions or
  bugs in ftrace selftests.

  I'm seeing the following ftrace test regresions:

  5.9-rc2 test failures with ARM64 in a 4GM VM + 8 CPUs

  Test 12, "Generic dynamic event - selective clear (compatibility)"
  Test 39, "Kprobe event with comm arguments"
  Test 40, "Kprobe event string type argument"
  Test 41, "Kprobe event symbol argument"
  Test 43, "Kprobe dynamic event with arguments"
  Test 44, "Kprobes event arguments with types"
  Test 45, "Kprobe event user-memory access"
  Test 47, "Kprobe dynamic event with function tracer" 
  Test 48, "Kprobe dynamic event - probing module"
  Test 51, "Kretprobe dynamic event with arguments"

  5.8.3, 5.7.17 test failures:
  Test 45, "Kprobe event user-memory access"
  Test 48, "Kprobe dynamic event - probing module"
  Test 51, "Kretprobe dynamic event with arguments"

  These tests were working fine when I tested with 5.4.60, 5.5.19,
  5.6.19, so these are definite regressions

  Attached is a spreadsheet of the full set of test results

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

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

[Kernel-packages] [Bug 1912803] Re: switch to an autogenerated nvidia series based core via dkms-versions

[Kleber Sacilotto de Souza]

Verified in Focal, by comparing the list of packages produced by the lrm
package for groovy/linux and also comparing the file installed by one of
the nvidia packages (linux-modules-nvidia-450-generic_*).


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

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

Title:
  switch to an autogenerated nvidia series based core via dkms-versions

Status in linux package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  Fix Released

Bug description:
  Switch the linux-restricted-modules payload to an autogenerated core
  based on the contents of the debian/dkms-versions.

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

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

[Kernel-packages] [Bug 1912803] Re: switch to an autogenerated nvidia series based core via dkms-versions

[Kleber Sacilotto de Souza]

Verified in Bionic, by comparing the list of packages produced by the
lrm package for groovy/linux and also comparing the file installed by
one of the nvidia packages (linux-modules-nvidia-450-generic_*).


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

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

Title:
  switch to an autogenerated nvidia series based core via dkms-versions

Status in linux package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  Fix Released

Bug description:
  Switch the linux-restricted-modules payload to an autogenerated core
  based on the contents of the debian/dkms-versions.

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

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

[Kernel-packages] [Bug 1912803] Re: switch to an autogenerated nvidia series based core via dkms-versions

[Kleber Sacilotto de Souza]

Verified in Groovy, by comparing the list of packages produced by the
lrm package for groovy/linux and also comparing the file installed by
one of the nvidia packages (linux-modules-nvidia-450-generic_*).

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

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

Title:
  switch to an autogenerated nvidia series based core via dkms-versions

Status in linux package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  Fix Released

Bug description:
  Switch the linux-restricted-modules payload to an autogenerated core
  based on the contents of the debian/dkms-versions.

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

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

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

[Kleber Sacilotto de Souza]

I have reviewed the update_excuses failures and none of them should
block the release of 'dkms'.

The following failures can be hinted by the kernel team:

Focal:
- nvidia-graphics-drivers-390/390.141-0ubuntu0.20.04.1: the armhf regression 
was caused by a kernel patch and not by the new dkms upload.
- virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.1: virtualbox is not expected to 
work for non-x86 arches.
- west-chamber/20100405+svn2007.r124-12: this is a known failure and it's 
being handled on bug 1912783.

Groovy:
- nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1: same as in Focal.
- virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.10.1: same as in Focal.

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

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  Fix Committed
Status in dkms source package in Focal:
  Fix Committed
Status in dkms source package in Groovy:
  Fix Committed
Status in dkms source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
  0ubuntu5) and the 5.8 kernel and even with this version of the driver
  failing to build with the 5.8 kernel, the test succeeds. The expected
  behavior, is that that dkms-autopkgtest should fail in this case.

  [Where problems could occur]

  The main issue that we can have here is selecting additional packages
  for the DKMS test that are not DKMS packages.

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

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

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

[Kleber Sacilotto de Souza]

Verification results for groovy:

bcmwl is an example of a package that is not currently being built 
automatically:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/b/bcmwl/20210210_143008_c07d5@/log.gz

Running autopkgtest locally with dkms 2.8.3-4ubuntu0.1 it gets built:

autopkgtest [17:04:13]: test dkms-autopkgtest: /usr/lib/dkms/dkms-autopkgtest
autopkgtest [17:04:13]: test dkms-autopkgtest: [---
I: Removing binary package bcmwl-kernel-source, to get clean state
I: Installing binary package bcmwl-kernel-source
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  bcmwl-kernel-source
0 upgraded, 1 newly installed, 0 to remove and 50 not upgraded.
Need to get 0 B/1551 kB of archives.
After this operation, 8071 kB of additional disk space will be used.
Get:1 file:/tmp/autopkgtest.1cGFPr/binaries  bcmwl-kernel-source 
6.30.223.271+bdcom-0ubuntu7 [1551 kB]
Selecting previously unselected package bcmwl-kernel-source.
(Reading database ... 121777 files and directories currently installed.)
Preparing to unpack ..././bcmwl-kernel-source.deb ...
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ...
autoinstall for dkms modules has been disabled.
modprobe: FATAL: Module wl not found in directory /lib/modules/5.8.0-44-generic
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.137ubuntu12) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-44-generic
dpkg: dependency problems prevent removal of dkms:
 bcmwl-kernel-source depends on dkms.

dpkg: error processing package dkms (--remove):
 dependency problems - not removing
Errors were encountered while processing:
 dkms
I: Testing binary package bcmwl-kernel-source
I: Trying to build bcmwl/6.30.223.271+bdcom for 5.8.0-41-generic

Creating symlink /var/lib/dkms/bcmwl/6.30.223.271+bdcom/source ->
 /usr/src/bcmwl-6.30.223.271+bdcom

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...
applying patch 0002-Makefile.patch...patching file Makefile
Hunk #1 succeeded at 113 with fuzz 1.
Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line).

applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines).

applying patch 
0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 221 (offset -14 lines).

applying patch 0013-gcc.patch...patching file Makefile

applying patch 
0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #1 succeeded at 2169 (offset 12 lines).

applying patch 0020-add-support-for-linux-4.3.patch...patching file
src/shared/linux_osl.c

applying patch 0021-add-support-for-Linux-4.7.patch...patching file
src/wl/sys/wl_cfg80211_hybrid.c

applying patch 0022-add-support-for-Linux-4.8.patch...patching file 
src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 2391 (offset 3 lines).
Hunk #2 succeeded at 2501 (offset 3 lines).
Hunk #3 succeeded at 2933 (offset 9 lines).

applying patch 0023-add-support-for-Linux-4.11.patch...patching file 
src/include/linuxver.h
patching file src/wl/sys/wl_linux.c
Hunk #1 succeeded at 2919 (offset 4 lines).

applying patch 0024-add-support-for-Linux-4.12.patch...patching file 
src/wl/sys/wl_cfg80211_hybrid.c
Hunk #1 succeeded at 55 (offset 5 lines).
Hunk #2 succeeded at 472 (offset 5 lines).
Hunk #3 succeeded at 2371 (offset 5 lines).
Hunk #4 succeeded at 2388 (offset 5 lines).

applying patch 0025-add-support-for-Linux-4.14.patch...patching file 
src/shared/linux_osl.c
Hunk #1 succeeded at 1080 (offset 4 lines).

applying patch 0026-add-support-for-Linux-4.15.patch...patching file 
src/wl/sys/wl_linux.c
Hunk #2 succeeded at 2306 (offset 4 lines).
Hunk #3 succeeded at 2368 (offset 4 lines).

applying patch 0027-add-support-for-linux-5.1.patch...patching file 
src/include/linuxver.h
Hunk #1 succeeded at 595 (offset 4 lines).

applying patch 0028-add-support-for-linux-5.6.patch...patching file 
src/shared/linux_osl.c
Hunk #1 succeeded at 946 (offset 4 lines).
patching file src/wl/sys/wl_linux.c
Hunk #1 succeeded at 590 (offset 8 lines).
Hunk #2 succeeded at 784 (offset 8 lines).
Hunk #3 succeeded at 3365 (offset 22 lines).


Building module:
cleaning build area...
make -j1 KERNELRELEASE=5.8.0-41-generic -C /lib/modules/5.8.0-41-generic/build 
M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build
Signing module:
 - /var/lib/dkms/bcmwl/6.30.223.271+bdcom/5.8.0-41-generic/x86_64/module/wl.ko
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
cleaning build area...

DKMS: build completed.

wl.ko:
Running module 

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

[Kleber Sacilotto de Souza]

Verification results for focal:

bcmwl is an example of a package that is not currently being built 
automatically:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/b/bcmwl/20210205_105527_d024f@/log.gz

Running autopkgtest locally with dkms 2.8.1-5ubuntu2 it gets built:

autopkgtest [15:11:14]: test dkms-autopkgtest: /usr/lib/dkms/dkms-autopkgtest
autopkgtest [15:11:14]: test dkms-autopkgtest: [---
(Reading database ... 312652 files and directories currently installed.)
Removing dkms (2.8.1-5ubuntu2) ...
Processing triggers for man-db (2.9.1-1) ...
I: removing binary package bcmwl-kernel-source, to get clean state
I: Installing binary package bcmwl-kernel-source
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  dkms
Suggested packages:
  menu
The following NEW packages will be installed:
  bcmwl-kernel-source dkms
0 upgraded, 2 newly installed, 0 to remove and 83 not upgraded.
Need to get 66.8 kB/1620 kB of archives.
After this operation, 8367 kB of additional disk space will be used.
Get:1 file:/tmp/autopkgtest.L09GqF/binaries  bcmwl-kernel-source 
6.30.223.271+bdcom-0ubuntu7~20.04.1 [1553 kB]
Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 dkms all 
2.8.1-5ubuntu2 [66.8 kB]
Fetched 66.8 kB in 0s (290 kB/s)
Selecting previously unselected package dkms.
(Reading database ... 312624 files and directories currently installed.)
Preparing to unpack .../dkms_2.8.1-5ubuntu2_all.deb ...
Unpacking dkms (2.8.1-5ubuntu2) ...
Selecting previously unselected package bcmwl-kernel-source.
Preparing to unpack ..././bcmwl-kernel-source.deb ...
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7~20.04.1) ...
Setting up dkms (2.8.1-5ubuntu2) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7~20.04.1) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.4.0-66-generic 5.8.0-44-generic
Building for architecture x86_64
Building initial module for 5.4.0-66-generic
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.

wl.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.0-66-generic/updates/dkms/

depmod...

DKMS: install completed.
Building initial module for 5.8.0-44-generic
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.

wl.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/

depmod...

DKMS: install completed.
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6.3) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-44-generic
I: Testing binary package bcmwl-kernel-source
I: Testing if bcmwl modules are correctly installed
bcmwl, 6.30.223.271+bdcom, 5.4.0-66-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 5.8.0-44-generic, x86_64: installed
autopkgtest: DBG: testbed command exited with code 0
autopkgtest [15:11:48]: test dkms-autopkgtest: ---]


It can also be verified by the automatic triggered test:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/b/bcmwl/20210217_154354_810bb@/log.gz

--
backport-iwlwifi-dkms is an example of a package that was already been 
automatically built before. I have tested it to make sure it didn't regress.

Automatically triggered tests:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/b/backport-iwlwifi-dkms/20210217_161847_cae52@/log.gz

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

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

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  Fix Committed
Status in dkms source package in Focal:
  Fix Committed
Status in dkms source package in Groovy:
  Fix Committed
Status in dkms source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source 

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

dep-8 tests triggered for bionic/linux-hwe-5.4:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/amd64/l/linux-
hwe-5.4/20210208_175055_01cbe@/log.gz

While not regressing the tests for focal/linux:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20210205_135222_29af6@/log.gz

Although bionic/linux-hwe-5.4 had already been fixed on the local
branch, the local patch has been "replaced" on rebase this cycle by the
one applied on focal/linux.

Marking verification for Focal as done.

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

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

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.8 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-hwe-5.8 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.

  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

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

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

dep-8 tests triggered for focal/linux-hwe-5.8:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/l/linux-
hwe-5.8/20210215_182942_7266d@/log.gz

Although focal/linux-hwe-5.8 had already been fixed on the local branch,
the local patch has been "replaced" on rebase this cycle by the one
applied on groovy/linux.

Marking verification for Groovy as done.

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

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

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.8 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-hwe-5.8 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.

  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

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

[Kernel-packages] [Bug 1908779] Re: Usb doens't work with kernel 5.4.0-56 -58

[Kleber Sacilotto de Souza]

Hello,

Thank you for your feedback. With that information we know this is
probably a regression introduced on 5.4.0-56 and that it is fixed on
mainline kernel.

The current linux version in focal-updates is 5.4.0-65.73, could you
please try it? If this version is still broken, it would be also be good
to test the version in focal-proposed (5.4.0-66.74). Both of these
version have several bug fixes. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.

Please also double check if you have the linux-modules-extra package
installed for all of the tested versions.

Thank you.

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

Title:
  Usb doens't work with  kernel 5.4.0-56 -58

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  After upgrading to these kernel the usb ports are unavailable.

  No device appear connected to USB -

  Keyboard is not working, no usb device are visible, reverting to
  5.4.0-54 the machine is working fine, all usb port are working and
  available.

  No information found googling.

  # lsb_release -rd 
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sat Dec 19 12:24:54 2020
  HibernationDevice: RESUME=UUID=28772c06-77f7-4664-819b-dfae3eedb38e
  InstallationDate: Installed on 2017-01-04 (1444 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: Dell Inc. OptiPlex FX160
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IE@euro
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=6c606617-f63e-4c0a-980e-2f6d1efb1b80 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-06-14 (187 days ago)
  dmi.bios.date: 01/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0FMJ85
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd01/19/2012:svnDellInc.:pnOptiPlexFX160:pvrNotSpecified:rvnDellInc.:rn0FMJ85:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: OptiPlex FX160
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1908779] Re: Usb doens't work with kernel 5.4.0-56 -58

[Kleber Sacilotto de Souza]

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

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

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

Title:
  Usb doens't work with  kernel 5.4.0-56 -58

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  After upgrading to these kernel the usb ports are unavailable.

  No device appear connected to USB -

  Keyboard is not working, no usb device are visible, reverting to
  5.4.0-54 the machine is working fine, all usb port are working and
  available.

  No information found googling.

  # lsb_release -rd 
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sat Dec 19 12:24:54 2020
  HibernationDevice: RESUME=UUID=28772c06-77f7-4664-819b-dfae3eedb38e
  InstallationDate: Installed on 2017-01-04 (1444 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: Dell Inc. OptiPlex FX160
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IE@euro
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=6c606617-f63e-4c0a-980e-2f6d1efb1b80 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-06-14 (187 days ago)
  dmi.bios.date: 01/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0FMJ85
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd01/19/2012:svnDellInc.:pnOptiPlexFX160:pvrNotSpecified:rvnDellInc.:rn0FMJ85:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: OptiPlex FX160
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1914411] Re: Fix broken efifb on graphics device without driver

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => In Progress

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

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

Title:
  Fix broken efifb on graphics device without driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  New
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  New

Bug description:
  [Impact]
  EFIFB stops working after graphics device is runtime suspended in
  D3cold.

  [Fix]
  Prevent the graphics device from being runtime suspended.

  [Test]
  With the patch applied, using efifb on graphics device without driver
  always work, because the device stays at D0 all the time.

  [Where problems could occur]
  Potentially this can affect power consumption, if user expects to put
  graphics device to D3cold, and is fine to get a broken efifb.

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

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

[Kernel-packages] [Bug 1913520] Re: Restore palm ejection on multi-input devices

[Kleber Sacilotto de Souza]

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

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

Title:
  Restore palm ejection on multi-input devices

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  Palm ejection stops working on Elan and Synaptics touchpads with
  pointstick.

  [Fix]
  Re-apply "confidence" quirk on those devices.

  [Test]
  Move the palm on touchpad, cursor moves too.
  With the fix applied, moving palm on touchpad won't move the cursor and
  won't generate click events.

  [Where problems could occur]
  Not that I can think of. Originally these touchpads are working fine
  with palm ejection, it's just overlooked when enabling pointsticks.

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

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

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Kleber Sacilotto de Souza]

The false positives on kernel ADT matrix were caused by an issue in
dkms-autopkgtest shipped by the dkms package, as we discussed here:

https://lists.ubuntu.com/archives/kernel-team/2021-February/116985.html

All the dkms packages which were failing to build in Focal with the
hwe-5.8 kernel are now fixed. We need now to fix dkms to make sure this
won't happen again.

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

[Kleber Sacilotto de Souza]

Xenial kernel 4.4.0-203.235 in -proposed contains a revert for a patch
that we believe was causing this issue. Could someone please test this
version to help us validate the fix?

Thank you.

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

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Hi there,
  I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 
4.4.0.202-generic today and it broke my system.
  Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely 
and not even root issued kill -KILL will terminate them. Only thing that helps 
is to kill the shell that started such commands.

  I had to reboot back to 4.4.0-201, however during shutdown various
  stop jobs hanged as well and after more than 25 minutes I had to go
  for hard reboot.

  My current—NOT BROKEN—kernel has signature (cat /proc/version_signature):
  Ubuntu 4.4.0-201.233-generic 4.4.247

  I am attaching the lspci-vnvn.log, also created with the non-broken
  kernel.

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

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

[Kernel-packages] [Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

[Kleber Sacilotto de Souza]

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

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

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

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

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

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Hi there,
  I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 
4.4.0.202-generic today and it broke my system.
  Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely 
and not even root issued kill -KILL will terminate them. Only thing that helps 
is to kill the shell that started such commands.

  I had to reboot back to 4.4.0-201, however during shutdown various
  stop jobs hanged as well and after more than 25 minutes I had to go
  for hard reboot.

  My current—NOT BROKEN—kernel has signature (cat /proc/version_signature):
  Ubuntu 4.4.0-201.233-generic 4.4.247

  I am attaching the lspci-vnvn.log, also created with the non-broken
  kernel.

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

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

[Kernel-packages] [Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

[Kleber Sacilotto de Souza]

Hello Marcel and everyone else affected,

Thank you for reporting this issue. Xenial kernel 4.4.0-202 is still in
-proposed therefore it's expected to be unstable. We are investigating
the issues with this kernel version and will publish an update as soon
as possible. In the meantime please downgrade to version -201 to have an
usable system again.

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

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,
  I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 
4.4.0.202-generic today and it broke my system.
  Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely 
and not even root issued kill -KILL will terminate them. Only thing that helps 
is to kill the shell that started such commands.

  I had to reboot back to 4.4.0-201, however during shutdown various
  stop jobs hanged as well and after more than 25 minutes I had to go
  for hard reboot.

  My current—NOT BROKEN—kernel has signature (cat /proc/version_signature):
  Ubuntu 4.4.0-201.233-generic 4.4.247

  I am attaching the lspci-vnvn.log, also created with the non-broken
  kernel.

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Kleber Sacilotto de Souza]

** Changed in: linux-raspi (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux-raspi (Ubuntu Groovy)
   Status: Confirmed => In Progress

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  In Progress
Status in linux-raspi source package in Groovy:
  In Progress

Bug description:
  [Impact]

  A mix of incoming TCP traffic, forwarding packets and saturating the
  link results in lan78xx TX queue timeouts which brings the network
  interface down.

  [Test Case]

  Se comment #99 below.

  [Where Problems Could Occur]

  Probably lost or corrupted TCP packets. Most likely not worse than
  what we're currently seeing.

  [Original Description]

  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 

[Kernel-packages] [Bug 1907151] Re: Focal update: v5.4.79 upstream stable release

[Kleber Sacilotto de Souza]

Only some of the patches from this upstream stable update has been
released, therefore I will reopen this bug.

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

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

Title:
  Focal update: v5.4.79 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.4.79 upstream stable release
     from git://git.kernel.org/

  powerpc: Only include kup-radix.h for 64-bit Book3S
  MIPS: PCI: Fix MIPS build
  net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
  net/mlx5: poll cmd EQ in case of command timeout
  net/mlx5: Fix a race when moving command interface to events mode
  net/mlx5: Add retry mechanism to the command entry index allocation
  powerpc/8xx: Always fault when _PAGE_ACCESSED is not set
  net: lantiq: Add locking for TX DMA channel
  Input: sunkbd - avoid use-after-free in teardown paths
  mac80211: always wind down STA state
  can: proc: can_remove_proc(): silence remove_proc_entry warning
  KVM: x86: clflushopt should be treated as a no-op by emulation
  ACPI: GED: fix -Wformat
  Linux 5.4.79
  UBUNTU: upstream stable to v5.4.79

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

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

[Kernel-packages] [Bug 1908555] Re: Groovy update: upstream stable patchset 2020-12-17

[Kleber Sacilotto de Souza]

Only some of the patches from this upstream stable update has been
released, therefore I will reopen this bug.

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

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

Title:
  Groovy update: upstream stable patchset 2020-12-17

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-12-17

  Ported from the following upstream stable releases:
  v5.4.78, v5.9.9

     from git://git.kernel.org/

  drm/i915: Hold onto an explicit ref to i915_vma_work.pinned
  drm/i915/gem: Flush coherency domains on first set-domain-ioctl
  mm: memcg: link page counters to root if use_hierarchy is false
  nbd: don't update block size after device is started
  KVM: arm64: Force PTE mapping on fault resulting in a device mapping
  ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup function
  genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
  hv_balloon: disable warning when floor reached
  net: xfrm: fix a race condition during allocing spi
  ASoC: codecs: wsa881x: add missing stream rates and format
  irqchip/sifive-plic: Fix broken irq_set_affinity() callback
  kunit: Fix kunit.py --raw_output option
  kunit: Don't fail test suites if one of them is empty
  usb: gadget: fsl: fix null pointer checking
  selftests: filter kselftest headers from command in lib.mk
  ASoC: codecs: wcd934x: Set digital gain range correctly
  ASoC: codecs: wcd9335: Set digital gain range correctly
  mtd: spi-nor: Fix address width on flash chips > 16MB
  xfs: set xefi_discard when creating a deferred agfl free log intent item
  mac80211: don't require VHT elements for HE on 2.4 GHz
  netfilter: nftables: fix netlink report logic in flowtable and genid
  netfilter: use actual socket sk rather than skb sk when routing harder
  netfilter: nf_tables: missing validation from the abort path
  netfilter: ipset: Update byte and packet counters regardless of whether they 
match
  irqchip/sifive-plic: Fix chip_data access within a hierarchy
  powerpc/eeh_cache: Fix a possible debugfs deadlock
  drm/vc4: bo: Add a managed action to cleanup the cache
  IB/srpt: Fix memory leak in srpt_add_one
  mm: memcontrol: correct the NR_ANON_THPS counter of hierarchical memcg
  drm/panfrost: rename error labels in device_init
  drm/panfrost: move devfreq_init()/fini() in device
  drm/panfrost: Fix module unload
  perf trace: Fix segfault when trying to trace events by cgroup
  perf tools: Add missing swap for ino_generation
  perf tools: Add missing swap for cgroup events
  ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
  iommu/vt-d: Fix a bug for PDP check in prq_event_thread
  afs: Fix warning due to unadvanced marshalling pointer
  afs: Fix incorrect freeing of the ACL passed to the YFS ACL store op
  vfio/pci: Implement ioeventfd thread handler for contended memory lock
  can: rx-offload: don't call kfree_skb() from IRQ context
  can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context
  can: dev: __can_get_echo_skb(): fix real payload length return value for RTR 
frames
  can: can_create_echo_skb(): fix echo skb generation: always use skb_clone()
  can: j1939: swap addr and pgn in the send example
  can: j1939: j1939_sk_bind(): return failure if netdev is down
  can: ti_hecc: ti_hecc_probe(): add missed clk_disable_unprepare() in error 
path
  can: xilinx_can: handle failure cases of pm_runtime_get_sync
  can: peak_usb: add range checking in decode operations
  can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
  can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback is 
on
  can: flexcan: remove FLEXCAN_QUIRK_DISABLE_MECR quirk for LS1021A
  can: flexcan: flexcan_remove(): disable wakeup completely
  xfs: flush new eof page on truncate to avoid post-eof corruption
  xfs: fix missing CoW blocks writeback conversion retry
  xfs: fix scrub flagging rtinherit even if there is no rt device
  spi: fsl-dspi: fix wrong pointer in suspend/resume
  ceph: add check_session_state() helper and make it global
  ceph: check the sesion state and return false in case it is closed
  ceph: check session state after bumping session->s_seq
  x86/speculation: Allow IBPB to be conditionally enabled on CPUs with 

[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8

[Kleber Sacilotto de Souza]

My laptop running Groovy (20.10) is affected by this bug as well, but I
also can't figure or at least isolate where the problem could be. The
hardware is similar to what other people have reported (it's a ASUS
K501UQ, with a Core i7-6500U, Nvidia 940MX and Intel HD 520).

It seemed to have started after I installed linux-modules-
nvidia-460-generic but even after uninstalling the nvidia drivers it
still hangs once in a while. I also tried blackisting nouveau but
without success. So I'm not sure this is directly related to any nvidia
modules as it was happening even without loading them. I couldn't
reliably reproduce the issue with any of combinations between 3 versions
of 5.8 kernels installed and nvidia/nouveau.

In my case it seems to hand right after loading the kernel and initrd,
but I don't get any message on the screen or on the logs and the
keyboard is totally unresponsive (I can't switch between tty's).

The only data point that seems to be consistent so far is that I wasn't
able to reproduce it when booting the kernel on recovery mode.

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

Title:
  Black screen on boot after 20.04 upgraded to kernel 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday Ubuntu asked me to reboot after automatic updates, and when
  I rebooted it doesn't start up. Sometimes it stays on the Dell logo,
  sometimes it goes to a black screen and doesn't get past that (not
  sure what causes each variation -- perhaps for reboot it does the Dell
  logo, cold start up it does the black screen?).

  After the updates it's trying to boot the 5.8.0 kernel. In the boot
  menu, if I manually select the 5.4.0 kernel everything works fine. So
  presumably it's something about the 5.8 kernel on this hardware.

  When this occurred I was running the Nouveau open source graphics
  driver. I switched to the NVIDIA driver (460) to see if that would
  help, but it didn't change anything. So it may or may not be graphics
  related.

  I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday
  -- Jan 12, I think it would be around 13:30 that I first rebooted
  after the upgrade (and a bunch of times after that). I ran the logs
  through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the
  lines were this (presumably irrelevant):

  Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400
  audit(1610431795.003:29126): apparmor="DENIED" operation="open"
  namespace="root//lxd-juju-804318-0_"
  profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906
  comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  For reference:

  * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I 
think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB 
RAM.
  * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on 
"Ubuntu 20.04.1 LTS".
  * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78
  * "sudo lspci -vnvn" output is included in the attached logs.zip
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben4518 F pulseaudio
   /dev/snd/pcmC0D0p:   ben4518 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-27 (138 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 15 9550
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing 

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[Kleber Sacilotto de Souza]

Hello Alan or anyone else affected,

The fix for this bug is also available on the hwe kernel for Focal
currently in -proposed (version 5.8.0-41.46~20.04.1). Feedback whether
this kernel fixes the nvme issue would be appreciated.

Thank you.

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[Kleber Sacilotto de Souza]

Thank you Andrew for your feedback!

We have applied the fix for groovy/linux (and focal/linux-hwe-5.8) and
the new kernels will be available in -proposed soon. These packages are
planned to be promoted to -updates early next week.

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  RebootRequiredPkgs:
 

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[Kleber Sacilotto de Souza]

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

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  RebootRequiredPkgs:
   linux-image-5.8.0-36-generic
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Kleber Sacilotto de Souza]

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

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

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

Title:
  initramfs unpacking failed

Status in OEM Priority Project:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in grub2 source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in grub2 source package in Groovy:
  Invalid
Status in initramfs-tools source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Fix Committed
Status in grub2 source package in Hirsute:
  Invalid
Status in initramfs-tools source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

  [Impact]

   * Decoding failure messages in dmsg with a single lz4 initrd

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when loaded by grub

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when there is padding between them

  [Test Case]

   * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4

   * Create an lz4 compressed initrd with a single test-file in it with
  some content. I.e. echo "second-initrd" > test-file, and then pack
  that with cpio hewc owned by root & lz4 -l.

   * Create a combined padded initrd of stock initrd, pad4, and the
  test-marker initrd created above.

   * Boot above with "break=top" kernel command line.

   * With broken kernels, there should be dmesg error message that
  decoding failed, and one will observe that /test-file does not exist
  in the shell.

   * With fixed kernel, /test-file in the initrd shell should exist, and
  should have the expected content "second-initrd".

   * The alignment and padding in the above test case depends on the
  size of the first initrd => if a given padded initrd does not
  reproduce the problem, try varying the size of the first initrd or
  that of the padding between 0..4.

  
  [Where problems could occur]

   * This changes compatible lz4 decompressor in the kernel, which can
  also be used by other kernel modules such as cryptography, squashfs,
  zram, f2fs, comprssed kernel image, pstore. For example, previously
  rejected files with "bogus" length and extra padding may now be
  accepted, whereas they were previously getting rejected by the
  decompressor.

   * Ideally kernel should switch to the stable lz4 format which has
  better specification of end of stream.

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

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

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[Kleber Sacilotto de Souza]

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

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

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  In Progress

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  RebootRequiredPkgs:
   linux-image-5.8.0-36-generic
   linux-base
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox

[Kleber Sacilotto de Souza]

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

** Also affects: virtualbox (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

Title:
  latest kernel breaks display full sizing in virtualbox

Status in linux package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in virtualbox source package in Focal:
  New

Bug description:
  kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1
  going back to kernel 5.4.0-59 makes full size display working again

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 09:12:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-05-01 (250 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb 
nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable 
no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120

[Kleber Sacilotto de Souza]

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

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

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

Title:
  overlay: permission regression in 5.4.0-51.56 due to patches related
  to CVE-2020-16120

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The backports to fix CVE-2020-16120 introduced a regression for
  overlay mounts within user namespaces. Files with ownership outside of
  the user namespace can no longer be accessed, even if allowed by both
  DAC and MAC.

  This issue is fixed by the following upstream commit:

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

  This commit relaxes the check to remove O_NOATIME from the open flags
  for the file in the lower filesystem when the overlay filesystem
  mounter is not privileged with respect to the underlying inode, rather
  than failing the open as happens now.

  [Test Case]

  The attached lp1900141.sh script reproduces the issue.

  [Where problems could occur]

  For the most part this patch restores previous behavior of allowing
  access to these files while keeping the enhanced permission checks
  towards the lower filesystem to help prevent unauthorized access to
  file data in the lower filesystem. The one difference in behavior is
  that files in the lower filesystem may no longer be opened with the
  O_NOATIME flag, potentially causing atime updates for these files
  which were not happening before. If any software expects O_NOATIME
  behavior in this situation then it could cause problems for that
  software. However, the correct behavior is that only the inode owner
  or a process with CAP_FOWNER towards the inode owner is allowed to
  open with O_NOATIME (as documented in open(2)).

  ---

  We use unprivileged user namespaces with overlay mounts for
  containers. After recently upgrading our Focal kernels to 5.4.0-51.56
  this breaks, one cannot access files through the overlay mount in the
  container anymore. This is very likely caused by some of the patches
  that were added in relation to CVE-2020-16120.

  The following commands allow to reproduce the problem when executed as
  an arbitrary non-root user:

  mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
  unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o 
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l 
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"

  The output when broken is this:

  -rwxr-xr-x 1 nobody nogroup 47480 Sep  5  2019 /tmp/test/usr/bin/id
  /tmp/test/usr/bin/id: executable, regular file, no read permission
  /bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted

  The expected output is this:

  -rwxr-xr-x 1 nobody nogroup 43224 Jan 18  2018 /tmp/test/usr/bin/id
  /tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  These commands create a user namespace and within it mount an overlay
  of /usr to /tmp/test/usr and then try to access something in it.

  This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
  already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52
  but is broken on kernel 5.4.0-51.56, no matter whether on Bionic or
  Focal.

  So I strongly suspect that not the actual security fixes for
  CVE-2020-16120 are the cause, but one of the following two patches
  that according to the changelogs were applied in the same revision but
  only to 5.4, not to 4.15:

  ovl: call secutiry hook in ovl_real_ioctl()
  ovl: check permission to open real file

  The mail with the announcement (https://www.openwall.com/lists/oss-
  security/2020/10/13/6) lists these two commits as separate from the
  actual security fixes ("may be desired or necessary").

  Is it possible to revert these two changes or fix them such that our
  unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
  workaround that I can add to my container solution such that this use
  case works again?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-51-generic 5.4.0-51.56
  ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 14 04:48 seq
   crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: 

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Kleber Sacilotto de Souza]

Thank you for the feedback. We'll continue to investigate and post an
update as soon as we have more information.

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Kleber Sacilotto de Souza]

Hi Bruce,

'uname -r' will indeed show the same output, however with 'uname -a' you
should see something like:

$ uname -a
Linux autopkgtest 5.4.0-59-generic #65+lp1909005 SMP Wed Jan 6 08:40:53 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1894964] Re: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build)

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe
  (blocking net test in ubuntu_kernel_selftests to build)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Issue found on 5.8.0-1001.1 - kvm

  Test build failed with:
  Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs 
from latest version at 'include/uapi/linux/netlink.h'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs 
from latest version at 'include/uapi/linux/if_link.h'
  In file included from 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:5,
  from 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/kernel.h:8,
  from 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.h:10,
  from 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:8:
  /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c: In 
function ‘__func_get_name’:
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:38:
 warning: nested extern declaration of ‘__compiletime_assert_0’ 
[-Wnested-externs]
  37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
  | ^
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:16:15:
 note: in definition of macro ‘__compiletime_assert’
  16 | extern void prefix ## suffix(void) __compiletime_error(msg); \
  | ^~
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:2:
 note: in expansion of macro ‘_compiletime_assert’
  37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
  | ^~~
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:39:37:
 note: in expansion of macro ‘compiletime_assert’
  39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
  | ^~
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:50:2:
 note: in expansion of macro ‘BUILD_BUG_ON_MSG’
  50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
  | ^~~~
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:20:2: 
note: in expansion of macro ‘BUILD_BUG_ON’
  20 | BUILD_BUG_ON(ARRAY_SIZE(func_id_str) != __BPF_FUNC_MAX_ID);
  | ^~~~
  libbpf: failed to open format: No such file or directory
  Error: failed to load BTF from format: No such file or directory
  make[1]: *** [Makefile:190: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h]
 Error 2
  make[1]: *** Deleting file 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h'
  make: *** [Makefile:157: all] Error 2

  Please find attachment for the complete build log.

  As the ubuntu_kernel_selftests needs bpf to be built first, this will
  block the ubuntu_kernel_selftests/net to build as well.

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

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

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Kleber Sacilotto de Souza]

Hi Bruce,

Thank you for you the test.

We have a test kernel with some fixes that we would appreciate if
someone could test it. They can be found at:
https://kernel.ubuntu.com/~vilhelm/linux-5.4.0-59.65+lp1909005/amd64/

You would need to install at least:
linux-image-unsigned-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb
linux-modules-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb
linux-modules-extra-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb

Thank you!

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1906907] Re: Laptop unable to wake up after being suspended

[Kleber Sacilotto de Souza]

Hello Rafael, thank you for the tests.

We have a test kernel with some fixes that we would appreciate if
someone could test it. They can be found at:
https://kernel.ubuntu.com/~vilhelm/linux-5.4.0-59.65+lp1909005/amd64/

You would need to install at least:
linux-image-unsigned-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb
linux-modules-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb
linux-modules-extra-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb

Thank you!

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

Title:
  Laptop unable to wake up after being suspended

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop was unable to wake up after being suspended by lid's closing,
  resulting in a blank black screen, while LEDs on the laptop showed
  that it had woken up. This bug happened using kernel 5.4.0-56.62, and
  it was "solved" by changing the kernel used to version 5.4.0-54.60, in
  which the default behavior of suspension when lid was closed and
  lock/login screen after lid being lifted up ocurred as it always was.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-56-generic 5.4.0-56.62
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rafael 1700 F pulseaudio
   /dev/snd/controlC1:  rafael 1700 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 02:35:57 2020
  InstallationDate: Installed on 2020-10-09 (57 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: TOSHIBA Satellite C55t-A
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=9b883e7b-5549-4c98-8084-ff648bf6066e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd04/28/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Durban-Curiosity 10S/10SG
  dmi.product.name: Satellite C55t-A
  dmi.product.sku: PSCFJU
  dmi.product.version: PSCFJU-00T00J
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1909017] Re: bug when suspending the system does not wake up and freezes on black screen

[Kleber Sacilotto de Souza]

Hello,

We have a test kernel with some fixes that we would appreciate if
someone could test it. They can be found at:
https://kernel.ubuntu.com/~vilhelm/linux-5.4.0-59.65+lp1909005/amd64/

You would need to install at least:
linux-image-unsigned-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb
linux-modules-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb
linux-modules-extra-5.4.0-59-generic_5.4.0-59.65+lp1909005_amd64.deb

Thank you!

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

Title:
  bug when suspending the system does not wake up and freezes on black
  screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug when suspending the system does not wake up and freezes on black
  screen.

  If I lower the screen or suspend, when trying to turn on the computer
  the screen is frozen on a black screen and does not obey any command
  that I try, it is stuck on a black screen, and I am forced to turn off
  the forced computer by holding the power until it turns off .

  version.log: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17

  lspci-vnvn.log: https://del.dog/menitofyfy.txt

  
  more info:
  togofire@togofire:~$ cat /etc/*-release
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  NAME="Linux Mint"
  VERSION="20 (Ulyana)"
  ID=linuxmint
  ID_LIKE=ubuntu
  PRETTY_NAME="Linux Mint 20"
  VERSION_ID="20"
  HOME_URL="https://www.linuxmint.com/;
  SUPPORT_URL="https://forums.linuxmint.com/;
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/;
  PRIVACY_POLICY_URL="https://www.linuxmint.com/;
  VERSION_CODENAME=ulyana
  UBUNTU_CODENAME=focal
  cat: /etc/upstream-release: É um diretório
  togofire@togofire:~$ cat /etc/*-release | grep PRETTY
  cat: /etc/upstream-release: É um diretório
  PRETTY_NAME="Linux Mint 20"
  togofire@togofire:~$ lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Linuxmint
  Description:  Linux Mint 20
  Release:  20
  Codename: ulyana
  togofire@togofire:~$ uname -a
  Linux togofire 5.8.0-33-generic #36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  togofire@togofire:~$ cat /proc/version
  Linux version 5.8.0-33-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 
9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) 
#36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 2020
  togofire@togofire:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  togofire   4520 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-07-04 (171 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2113 Acer, Inc Integrated Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81GT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=90612144-f123-47e5-b09e-9c2870210dfb ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.187.6
  Tags:  ulyana
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8JCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN54WW:bd06/15/2020:br1.54:efr1.54:svnLENOVO:pn81GT:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
  dmi.product.family: Legion Y530-15ICH
  dmi.product.name: 81GT
  dmi.product.sku: LENOVO_MT_81GT_BU_idea_FM_Legion Y530-15ICH
  dmi.product.version: Lenovo Legion Y530-15ICH
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1910200] Re: aws: network performance regression due to initial TCP receive buffer size change

[Kleber Sacilotto de Souza]

** Changed in: linux-aws (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-aws (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-aws (Ubuntu Groovy)
   Status: New => Fix Committed

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

Title:
  aws: network performance regression due to initial TCP receive buffer
  size change

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  AWS has seen some customers reporting networking performance
  degradation after they upgraded their Ubuntu instanceses. This
  regression is highly impacting customers who are using MTU=9000 (which
  is the default in EC2).

  [Test case]

  Bug reproduced internally in AWS (no test case provided), but
  apparently it is very easy to reproduce simply by measuring networking
  performance.

  [Fix]

  AWS worked internally and found that the regression has been
  introduced by:

   a337531b942b ("tcp: up initial rmem to 128KB and SYN rwin to around
  64KB")

  To solve the problem we need to apply the following upstream commit
  that explicitly fixes the problem introduced by the commit above:

   33ae7b5bb841 ("tcp: select sane initial rcvq_space.space for big
  MSS")

  [Regression potential]

  Upstream fix that is only affecting the initial TCP buffer space and
  allows the TCP window size to be dynamically increased, basically
  restoring the previous (correct) behavior, so regression potential is
  minimal.

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

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

[Kernel-packages] [Bug 1908609] Re: Kernel: 5.4.0-58-generic and Kernel: 5.4.0-56-generic fail to stay in suspension

[Kleber Sacilotto de Souza]

Hello Federico or anyone else affected,

We have released a new Focal linux kernel (version 5.4.0-59.65) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  Kernel: 5.4.0-58-generic and Kernel: 5.4.0-56-generic fail to stay in
  suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Linux Mint 20

  With the last 2 kernel updates my laptop now doesn't stay in
  suspension.

  -Up to Kernel: 5.4.0-54-generic, all works. Laptop suspends and stays 
suspended until I press the power button.
  -Kernel: 5.4.0-56-generic . Laptop suspends and immeditely resumes without 
staying in suspension.
  -Kernel: 5.4.0-58-generic . Laptop suspends and immeditely resumes without 
staying in suspension.

  It's as if an interrupt of some kind or the EC were waking it up immediately 
after it entered suspension!
  I have 2 identical laptops: same problem.

  Thank you,
  Federico Tejada

  Info:

  $ inxi -Fxz
  System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 4.6.7 
 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
  Machine:   Type: Laptop System: TOSHIBA product: Satellite-L845 v: 
PSKF6P-0LYAR1 serial:  
 Mobo: Type2 - Board Vendor Name1 model: Type2 - Board Product 
Name1 v: Type2 - Board Version serial:  
 UEFI: Insyde v: 6.50 date: 12/27/2012 
  Battery:   ID-1: BAT1 charge: 44.3 Wh condition: 44.3/47.5 Wh (93%) model: 
LGC PA5024U-1BRS status: Full 
  CPU:   Topology: Dual Core model: Intel Core i5-3210M bits: 64 type: MT 
MCP arch: Ivy Bridge rev: 9 L2 cache: 3072 KiB 
 flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19954 
 Speed: 1197 MHz min/max: 1200/3100 MHz Core speeds (MHz): 1: 1197 
2: 1198 3: 1197 4: 1198 
  Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Toshiba 
driver: i915 v: kernel bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 
Mesa 20.0.8 direct render: Yes 
  Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: 
Toshiba driver: snd_hda_intel v: kernel 
 bus ID: 00:1b.0 
 Sound Server: ALSA v: k5.4.0-58-generic 
  Network:   Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel port: 3040 
bus ID: 02:00.0 
 IF: wlp2s0 state: up mac:  
 Device-2: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: 
Toshiba driver: atl1c v: 1.0.1.1-NAPI port: 2000 
 bus ID: 03:00.0 
 IF: enp3s0 state: down mac:  
  Drives:Local Storage: total: 978.09 GiB used: 191.20 GiB (19.5%) 
 ID-1: /dev/sda vendor: Crucial model: CT1050MX300SSD4 size: 978.09 
GiB 
  Partition: ID-1: / size: 117.62 GiB used: 18.90 GiB (16.1%) fs: ext4 dev: 
/dev/sda2 
 ID-2: /home size: 744.01 GiB used: 172.29 GiB (23.2%) fs: ext4 
dev: /dev/sda3 
 ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda4 
  Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 228 Uptime: N/A Memory: 15.54 GiB used: 750.0 MiB 
(4.7%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
 Shell: bash v: 5.0.17 inxi: 3.0.38 

  dmesg from suspension seems right:
  $ dmesg
  ...
  [  645.952756] PM: suspend entry (deep)
  [  646.043052] Filesystems sync: 0.090 seconds
  [  646.043797] Freezing user space processes ... (elapsed 0.003 seconds) done.
  [  646.046839] OOM killer disabled.
  [  646.046840] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  646.048188] printk: Suspending console(s) (use no_console_suspend to debug)
  [  646.102768] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  646.106255] sd 0:0:0:0: [sda] Stopping disk
  [  646.479673] ACPI: EC: interrupt blocked
  [  646.499336] ACPI: Preparing to enter system sleep state S3
  [  646.500300] ACPI: EC: event blocked
  [  646.500301] ACPI: EC: EC stopped
  [  646.500302] PM: Saving platform NVS memory
  [  646.500319] Disabling non-boot CPUs ...
  [  646.501884] smpboot: CPU 1 is now offline
  [  646.506119] IRQ 29: no longer affine to CPU2
  [  646.507156] smpboot: CPU 2 is now offline
  [  646.510897] IRQ 23: no longer affine to CPU3
  [  646.510901] IRQ 27: no longer affine to CPU3
  [  646.510903] IRQ 31: no longer affine to CPU3
  [  646.511903] smpboot: CPU 3 is now offline
  [  646.514344] ACPI: Low-level resume complete
  [  646.514391] ACPI: EC: EC started
  [  646.514391] PM: Restoring platform NVS memory
  [  646.515673] Enabling non-boot CPUs ...
  [  

[Kernel-packages] [Bug 1909017] Re: bug when suspending the system does not wake up and freezes on black screen

[Kleber Sacilotto de Souza]

Hello Ítalo or anyone else affected,

We have released a new Groovy linux kernel (version 5.8.0-34.37) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  bug when suspending the system does not wake up and freezes on black
  screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug when suspending the system does not wake up and freezes on black
  screen.

  If I lower the screen or suspend, when trying to turn on the computer
  the screen is frozen on a black screen and does not obey any command
  that I try, it is stuck on a black screen, and I am forced to turn off
  the forced computer by holding the power until it turns off .

  version.log: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17

  lspci-vnvn.log: https://del.dog/menitofyfy.txt

  
  more info:
  togofire@togofire:~$ cat /etc/*-release
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  NAME="Linux Mint"
  VERSION="20 (Ulyana)"
  ID=linuxmint
  ID_LIKE=ubuntu
  PRETTY_NAME="Linux Mint 20"
  VERSION_ID="20"
  HOME_URL="https://www.linuxmint.com/;
  SUPPORT_URL="https://forums.linuxmint.com/;
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/;
  PRIVACY_POLICY_URL="https://www.linuxmint.com/;
  VERSION_CODENAME=ulyana
  UBUNTU_CODENAME=focal
  cat: /etc/upstream-release: É um diretório
  togofire@togofire:~$ cat /etc/*-release | grep PRETTY
  cat: /etc/upstream-release: É um diretório
  PRETTY_NAME="Linux Mint 20"
  togofire@togofire:~$ lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Linuxmint
  Description:  Linux Mint 20
  Release:  20
  Codename: ulyana
  togofire@togofire:~$ uname -a
  Linux togofire 5.8.0-33-generic #36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  togofire@togofire:~$ cat /proc/version
  Linux version 5.8.0-33-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 
9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) 
#36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 2020
  togofire@togofire:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  togofire   4520 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-07-04 (171 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2113 Acer, Inc Integrated Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81GT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=90612144-f123-47e5-b09e-9c2870210dfb ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.187.6
  Tags:  ulyana
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8JCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN54WW:bd06/15/2020:br1.54:efr1.54:svnLENOVO:pn81GT:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
  dmi.product.family: Legion Y530-15ICH
  dmi.product.name: 81GT
  dmi.product.sku: LENOVO_MT_81GT_BU_idea_FM_Legion Y530-15ICH
  dmi.product.version: Lenovo Legion Y530-15ICH
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1906907] Re: Laptop unable to wake up after being suspended

[Kleber Sacilotto de Souza]

Hello Rafael or anyone else affected,

We have released a new Focal linux kernel (version 5.4.0-59.65) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  Laptop unable to wake up after being suspended

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop was unable to wake up after being suspended by lid's closing,
  resulting in a blank black screen, while LEDs on the laptop showed
  that it had woken up. This bug happened using kernel 5.4.0-56.62, and
  it was "solved" by changing the kernel used to version 5.4.0-54.60, in
  which the default behavior of suspension when lid was closed and
  lock/login screen after lid being lifted up ocurred as it always was.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-56-generic 5.4.0-56.62
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rafael 1700 F pulseaudio
   /dev/snd/controlC1:  rafael 1700 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 02:35:57 2020
  InstallationDate: Installed on 2020-10-09 (57 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: TOSHIBA Satellite C55t-A
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=9b883e7b-5549-4c98-8084-ff648bf6066e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd04/28/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Durban-Curiosity 10S/10SG
  dmi.product.name: Satellite C55t-A
  dmi.product.sku: PSCFJU
  dmi.product.version: PSCFJU-00T00J
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1909496] Re: Blinking login screen

[Kleber Sacilotto de Souza]

Hello Rohit or anyone else affected,

We have released a new Focal linux kernel (version 5.4.0-59.65) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  Blinking login screen

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

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1909856] Re: amdgpu intermittently fails to resume correctly

[Kleber Sacilotto de Souza]

Hello Jamie or anyone else affected,

We have released a new Focal linux kernel (version 5.4.0-59.65) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  amdgpu intermittently  fails to resume correctly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I started seeing my system fail to resume from suspend over the last
  couple of weeks. It happens about 1 in 5 times maybe? I press the
  power button on my system to resume it and my screens stay blank. I am
  able to connect to the system remotely over ssh and check syslog to
  find out what went wrong. I then try to reboot the system with `sudo
  reboot`, the ssh session disconnects but it never actually reboots. I
  have to press the reset button after waiting a while to make it start
  up again.

  dmesg log is attached which contains more info and the call trace. I
  think the interesting part is this:

  kernel: amdgpu :0d:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* 
ring gfx test failed (-110)
  kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP 
block  failed -110
  kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume 
failed (-110).
  kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110
  kernel: PM: Device :0d:00.0 failed to resume async: error -110

  It first happened on 20.04 with kernel 5.4 (can't remember exactly
  what version of 5.4) a couple of weeks ago. I saw 20.10 was available
  with 5.8 so thought I'd try upgrading as there was a variety of amdgpu
  fixes go in between 5.4 and 5.8 but sadly no dice.

  From some research, I think what I'm seeing is similar to this bug,
  but that one looks like 5.4 solved it, whereas I guess some minor
  upgrade on 5.4 appeared to break it for me.
  https://bugs.freedesktop.org/show_bug.cgi?id=112221

  I'm running a Ryzen 3700X on an X570 board with an AMD Radeon Pro WX 4100 GPU.
  Currently using Kubuntu 20.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-33-generic 5.8.0-33.36
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Jan  2 12:40:36 2021
  InstallationDate: Installed on 2020-06-18 (197 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash usbcore.autosuspend=-1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-12-30 (3 days ago)
  dmi.bios.date: 09/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: X570 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd09/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Kleber Sacilotto de Souza]

Hello Philip or anyone else affected,

We have released a new Focal linux kernel (version 5.4.0-59.65) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

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

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

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

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.8 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-hwe-5.8 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.

  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

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

[Kernel-packages] [Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3

[Kleber Sacilotto de Souza]

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

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

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed with script is not executable on B-AWS-5.3

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  Issue found on Bionic 5.3.0-1033.35-aws

  TAP version 13
   1..1
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Warning: file mem-on-off-test.sh is not executable, correct this.
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug'
   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  ubuntu_ker:0242| == Summary ===
  ubuntu_ker:0076| Sub test case: mem-on-off-test.sh failed.

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

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

[Kernel-packages] [Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3

[Kleber Sacilotto de Souza]

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

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

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

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

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed with script is not executable on B-AWS-5.3

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on Bionic 5.3.0-1033.35-aws

  TAP version 13
   1..1
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Warning: file mem-on-off-test.sh is not executable, correct this.
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug'
   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  ubuntu_ker:0242| == Summary ===
  ubuntu_ker:0076| Sub test case: mem-on-off-test.sh failed.

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

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

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

I am nominating this bug for linux-hwe-5.8 in Focal because this package
needs to be re-spun to fix this issue as soon as possible.

This would not be strictly needed as the change will be inherited from
groovy/linux on the next rebase.

** Changed in: linux-hwe-5.8 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-hwe-5.8 (Ubuntu Focal)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-hwe-5.8 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-hwe-5.8 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.

  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

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

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

SRU request:
https://lists.ubuntu.com/archives/kernel-team/2020-December/115759.html

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

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

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

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

** Changed in: linux-hwe-5.8 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-hwe-5.8 (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: linux-hwe-5.8 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-hwe-5.8 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-hwe-5.8 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.

  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

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

[Kernel-packages] [Bug 1908529] Re: dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

** Description changed:

  [ Impact ]
- On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-on basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-5.8 
and are not included on the list.
+ On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-5.8 
and are not included on the list.
  
  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz
  
  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.
  
  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.
  
  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f
  
  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

** Description changed:

  [ Impact ]
- On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-5.8 
and are not included on the list.
+ On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.
  
  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz
  
  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.
  
  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.
  
  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f
  
  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

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

Title:
  dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-*
  kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  [ Impact ]
  On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-in basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-x.y 
and are not included on the list.

  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

  [ Test case ]
  

[Kernel-packages] [Bug 1908529] [NEW] dep-8 ubuntu-regression-suite tests are not run for all linux-hwe-* kernels

[Kleber Sacilotto de Souza]

Public bug reported:

[ Impact ]
On autopkgtest, ubuntu-regression-suite is not run for all kernels because for 
most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-on basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-5.8 
and are not included on the list.

Logs from a skipped test run:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz

[ Test case ]
ADT tests are triggered when packages are promoted to -proposed. Looking at the 
logs one can check whether the tests were skipped or run.

[ Fix ]
The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f

[ Where problems could occur ]
The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect it to cause issues.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: Confirmed

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: Confirmed

** Affects: linux (Ubuntu Groovy)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: Confirmed

** Affects: linux (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: Confirmed

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

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

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

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

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

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

** Description changed:

  [ Impact ]
- On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-on basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-5.8 
and are not included on the list. 
+ On autopkgtest, ubuntu-regression-suite is not run for all kernels because 
for most of them it doesn't make sense to run the tests on the environment 
provided. If a given package is going to be tested is decided on 
'debian/tests/ubuntu-regression-suite' on an opt-on basis. The current criteria 
lists all source packages, however, new hwe kernels are named as linux-hwe-5.8 
and are not included on the list.
  
  Logs from a skipped test run:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux-hwe-5.8/20201216_001007_32069@/log.gz
  
  [ Test case ]
  ADT tests are triggered when packages are promoted to -proposed. Looking at 
the logs one can check whether the tests were skipped or run.
  
  [ Fix ]
  The fix is to use a wild card to include all linux-hwe* kernels. A fix was 
already applied locally for bionic/linux-hwe-5.4, the same patch can be applied 
to F/G/H/U to carry it forward.
  
+ https://git.launchpad.net/~ubuntu-
+ 
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe-5.4=a077e2f94c3a948e293fd31bce09b08c3fef7c1f
+ 
  [ Where problems could occur ]
  The code changed controls which kernel get tested on ADT 
ubuntu-regression-suite, a failure on the selection could result in testing 
kernels which shouldn't be tested or the other way around. However, the change 
is simple and has already been applied to focal/linux-hwe-5.4, so I don't 
expect i

[Kernel-packages] [Bug 1904529] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot

[Kleber Sacilotto de Souza]

Hello Xiyue Wang,

Could you please try the latest bionic kernel from -proposed? The
version would be linux-generic 4.15.0.128.115.

Following are instructions on how to enable proposed:
https://wiki.ubuntu.com/Testing/EnableProposed

Thank you.

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

Title:
  Losing port aggregate with 802.3ad port-channel/bonding aggregation on
  reboot

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

Bug description:
  The exactly the same behavior is observed when upgrade kernel to 
4.15.0-123-generic.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834322

  If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up',
  the port with the mismatched ID appears to renegotiate with the port-
  channel and becomes aggregated.

  ubuntu@vcd41025:~$ sudo lspci -vnvn
  https://pastebin.canonical.com/p/x56r4P6mGB/

  ubuntu@vcd41025:~$ uname -a
  Linux vcd41025 4.15.0-123-generic #126-Ubuntu SMP Wed Oct 21 09:40:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Hardware: Dell PowerEdge R740xd

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

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

[Kernel-packages] [Bug 1904529] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot

[Kleber Sacilotto de Souza]

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

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

Title:
  Losing port aggregate with 802.3ad port-channel/bonding aggregation on
  reboot

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

Bug description:
  The exactly the same behavior is observed when upgrade kernel to 
4.15.0-123-generic.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834322

  If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up',
  the port with the mismatched ID appears to renegotiate with the port-
  channel and becomes aggregated.

  ubuntu@vcd41025:~$ sudo lspci -vnvn
  https://pastebin.canonical.com/p/x56r4P6mGB/

  ubuntu@vcd41025:~$ uname -a
  Linux vcd41025 4.15.0-123-generic #126-Ubuntu SMP Wed Oct 21 09:40:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Hardware: Dell PowerEdge R740xd

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

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

[Kernel-packages] [Bug 1894667] Re: [HP 635] Radeon 6310 brightness control does not work

[Kleber Sacilotto de Souza]

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

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

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

Title:
  [HP 635] Radeon 6310 brightness control does not work

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  Brightness setting does not work on versions 16.04.7 and 20.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep  7 12:10:27 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6310] [103c:3577]
  LiveMediaBuild: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
  MachineType: Hewlett-Packard HP 635 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- debian-installer/language=tr 
keyboard-configuration/layoutcode?=tr
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.48
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.4A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnHP635NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=635
  dmi.product.name: HP 635 Notebook PC
  dmi.product.version: 058A10004C1000260
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Sep  7 14:57:25 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xubuntu1827 F pulseaudio
   /dev/snd/controlC0:  xubuntu1827 F pulseaudio
  CasperMD5CheckMismatches: 
./pool/main/g/glibc/libc-dev-bin_2.31-0ubuntu9_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  LiveMediaBuild: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP 635 Notebook PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- debian-installer/language=tr 
keyboard-configuration/layoutcode?=tr
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1906866] Re: focal: selftests/bpf build broken: test_map_init.skel.h: No such file or directory

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

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

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

Title:
  focal: selftests/bpf build broken: test_map_init.skel.h: No such file
  or directory

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  Please revert [focal] d946d4ddd6af bpf: Zero-fill re-used per-cpu map
  element

  Reported upstream:
   
https://lore.kernel.org/stable/20201204182846.27110-1-ka...@canonical.com/T/#u

  ---

  This v5.4.78 commit breaks the tools/testing/selftests/bpf build:

  [linux-5.4.y] c602ad2b52dc bpf: Zero-fill re-used per-cpu map element
  [focal]   d946d4ddd6af bpf: Zero-fill re-used per-cpu map element

  Like this:

  prog_tests/map_init.c:5:10: fatal error: test_map_init.skel.h: No 
such file or directory
  5 | #include "test_map_init.skel.h"

  Because tools/testing/selftests/bpf/Makefile in v5.4 does not have the
  "skeleton header generation" stuff (circa v5.6).

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

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

[Kernel-packages] [Bug 1906229] Re: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  Refresh ACPI wakeup power to make Thunderbolt hotplug detection work

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  Dell Precision 5550 cannot detect Thunderbolt device hotplug.

  [Fix]
  Refresh ACPI wakeup power if it's already enabled to make GPE work.

  [Test]
  Make sure the root port of TBT hierachy is in D3cold.
  Plug a Thunderbolt Dock or Thunderbolt Disk, the system cannot detect
  anything.

  With the patch applied, OS can always detect hotplugged Thunderbolt
  devices.

  [Where problems could occur]
  Though we refresh the wakeup device power, we didn't disable/enable ACPI
  GPEs, so we won't miss any GPE event from this fix.

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

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

[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed

[Kleber Sacilotto de Souza]

Spotted on focal/linux-kvm 5.4.0-1027.28.

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New

Bug description:
  startup='Wed May 22 08:02:52 2019'
  getaddrinfo_011  TPASS  :  getaddrinfo IPv4 basic lookup
  getaddrinfo_012  TFAIL  :  getaddrinfo_01.c:140: getaddrinfo IPv4 
canonical name ("curly.maas") doesn't match hostname ("curly")
  getaddrinfo_013  TFAIL  :  getaddrinfo_01.c:578: getaddrinfo IPv6 basic 
lookup ("curly") returns -5 ("No address associated with hostname")
  tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 08:04:30 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1902473] Re: select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10

[Kleber Sacilotto de Souza]

Issue found also on groovy/linux-azure: 5.8.0-1013.14.

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

Title:
  select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a new test case, test failed with:

  <<>>
  tag=select03 stime=1604290335
  cmdline="select03"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s
  select_var.h:107: TINFO: Testing libc select()
  select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22)
  select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0
  select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0
  select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0
  select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14)
  select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT 
(14)
  select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT 
(14)
  select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14)
  tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s
  select_var.h:110: TINFO: Testing SYS_select syscall
  select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22)
  select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0
  select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0
  select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0
  select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14)
  select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT 
(14)
  select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT 
(14)
  select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14)
  tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s
  select_var.h:113: TINFO: Testing SYS_pselect6 syscall
  select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22)
  select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0
  select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0
  select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0
  select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14)
  select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT 
(14)
  select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT 
(14)
  select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14)
  tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s
  select_var.h:116: TINFO: Testing SYS_pselect6 time64 syscall
  select_var.h:81: TCONF: __NR_pselect6 time64 variant not supported
  tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s
  select_var.h:119: TINFO: Testing SYS__newselect syscall
  select_var.h:87: TCONF: syscall(-1) __NR__newselect not supported

  Summary:
  passed   15
  failed   9
  skipped  2
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-26-generic 5.8.0-26.27
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 28 09:30 seq
   crw-rw 1 root audio 116, 33 Oct 28 09:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Mon Nov  2 04:10:52 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic 
root=UUID=f06509c5-4a0a-4cae-be3c-e5d21c1687c9 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-26-generic N/A
   linux-backports-modules-5.8.0-26-generic  N/A
   linux-firmware1.190
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  

[Kernel-packages] [Bug 1904595] Re: Fix no headset sound after S3 on Intel HDA

[Kleber Sacilotto de Souza]

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

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

Title:
  Fix no headset sound after S3 on Intel HDA

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After system S3, hotplugging headset cannot produce any sound despite of
  being auto-selected as audio output.

  [Fix]
  Avoid using pm_runtime_force_{suspend,resume} helpers to ensure codec
  suspend/resume flow, and also ensure HDA driver and PCI set correct
  wakeup settings.

  [Test case]
  Plug headset, unplug headset, switch audio ouput from speakers to HDMI
  to let Intel HDA auto suspend. Suspend/resume the system, plug the
  headset again, hear no sound.

  With the patch series applied, the issue is gone.

  [Where problems could occur]
  If there is bad firmware/hardware that makes codec have system-wide
  wakeup capability, direct-complete flow may trigger unwanted system
  wakeup or even break system suspend. The series was tested on both AMD 
  and Intel platforms, with Realtek and Connexant codecs respectively.

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

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

[Kernel-packages] [Bug 1904221] Re: Ask 8821C Bluetooth controller to drop old firmware

[Kleber Sacilotto de Souza]

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

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

Title:
  Ask 8821C Bluetooth controller to drop old firmware

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains
  its firmware even with a cold boot.

  [Fix]
  Use vendor command to drop firmware if the version is old.

  [Test case]
  Use dmesg to check if new firmware is loaded.
  With the patch applied, we can find new firmware is loaded.

  [Where problems could occur]
  There's a 200ms delay which can slow down when BT controller is opened
  by userspace first time.

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

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

[Kernel-packages] [Bug 1904225] Re: Use ACPI S5 for reboot

[Kleber Sacilotto de Souza]

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

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

Title:
  Use ACPI S5 for reboot

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  On some HP laptops, BIOS hotkeys don't work right after reboot, becuase
  OS doesn't call _PTS to indicate ACPI it's rebooting.

  [Fix]
  Follow Windows and use S5 for reboot.

  [Test case]
  Reboot and see if hotkeys like F10/F11 can trigger BIOS functions.
  Hotkeys work great with the patch applied. 

  [Where problems could occur]
  If there are platforms don't expect S5 for reboot then there could be
  unexpected result.
  However Windows uses S5 so that's rather unlikely.

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

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

[Kernel-packages] [Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

[Kleber Sacilotto de Souza]

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

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

Title:
  [i915] Noise-like lines of graphics corruption when moving windows in
  Xorg sessions

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  Noise-like lines of graphics corruption when moving windows in Xorg
  sessions.

  [Fix]
  Revert "UBUNTU: SAUCE: drm/i915: Synchronize active and retire
  callbacks".

  [Test]
  Daniel van Vugt confirmed reverting the commit fixes the issue.
  I can also reproduce the issue on one of my system, I can confirm it
  fixes the issue too.

  [Where problems could occur]
  Race condition the commit solves may appear again.
  The commit was reverted and replaced by an upstream fix, which is already 
included in 5.8. So it should be rather safe here.

  == Original Bug Report ==

  I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
  unattended for a while, and then got the error message and now have
  funny lines on activity, e.g. red lines flashing on top of gnome-shell
  bar when switching windows, or white blocks/lines around typing text.

  This is the second or third time it happened, reboot fixes it until
  the error pops up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 19:14:11 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present 

[Kernel-packages] [Bug 1904521] Re: Intel Tiger Lake IDs supplement

[Kleber Sacilotto de Souza]

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

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

Title:
  Intel Tiger Lake IDs supplement

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Intel Tiger Lake-H platform requires new pin settings and IDs to enable.

  [Fix]
  Intel provides us a list of TGL-H commits from 5.8 and 5.9, we need all of 
the commits to enable TGL-H platforms completely.

  [Test]
  Verified those commits on Intel TGL-H SDP

  [Regression potential]
  Low, all of those commits are adding new IDs for TGL-H platform.

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

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

[Kernel-packages] [Bug 1904941] Re: Groovy update: v5.8.18 upstream stable release

[Kleber Sacilotto de Souza]

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

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

Title:
  Groovy update: v5.8.18 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.8.18 upstream stable release
     from git://git.kernel.org/

  netfilter: nftables_offload: KASAN slab-out-of-bounds Read in 
nft_flow_rule_create
  io_uring: don't run task work on an exiting task
  io_uring: allow timeout/poll/files killing to take task into account
  io_uring: move dropping of files into separate helper
  io_uring: stash ctx task reference for SQPOLL
  io_uring: unconditionally grab req->task
  io_uring: return cancelation status from poll/timeout/files handlers
  io_uring: enable task/files specific overflow flushing
  io_uring: don't rely on weak ->files references
  io_uring: reference ->nsproxy for file table commands
  io_wq: Make io_wqe::lock a raw_spinlock_t
  io-wq: fix use-after-free in io_wq_worker_running
  io_uring: no need to call xa_destroy() on empty xarray
  io_uring: Fix use of XArray in __io_uring_files_cancel
  io_uring: Fix XArray usage in io_uring_add_task_file
  io_uring: Convert advanced XArray uses to the normal API
  scripts/setlocalversion: make git describe output more reliable
  efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure
  fs/kernel_read_file: Remove FIRMWARE_EFI_EMBEDDED enum
  arm64: Run ARCH_WORKAROUND_1 enabling code on all CPUs
  arm64: Run ARCH_WORKAROUND_2 enabling code on all CPUs
  arm64: link with -z norelro regardless of CONFIG_RELOCATABLE
  x86/PCI: Fix intel_mid_pci.c build error when ACPI is not enabled
  x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()
  UBUNTU: [Config] update config for ARCH_HAS_COPY_MC
  x86/copy_mc: Introduce copy_mc_enhanced_fast_string()
  bnxt_en: Check abort error state in bnxt_open_nic().
  bnxt_en: Fix regression in workqueue cleanup logic in bnxt_remove_one().
  bnxt_en: Invoke cancel_delayed_work_sync() for PFs also.
  bnxt_en: Re-write PCI BARs after PCI fatal error.
  bnxt_en: Send HWRM_FUNC_RESET fw command unconditionally.
  chelsio/chtls: fix deadlock issue
  chelsio/chtls: fix memory leaks in CPL handlers
  chelsio/chtls: fix tls record info to user
  cxgb4: set up filter action after rewrites
  gtp: fix an use-before-init in gtp_newlink()
  ibmveth: Fix use of ibmveth in a bridge.
  ibmvnic: fix ibmvnic_set_mac
  mlxsw: core: Fix memory leak on module removal
  netem: fix zero division in tabledist
  net: hns3: Clear the CMDQ registers before unmapping BAR region
  net: ipa: command payloads already mapped
  net/sched: act_mpls: Add softdep on mpls_gso.ko
  r8169: fix issue with forced threading in combination with shared interrupts
  ravb: Fix bit fields checking in ravb_hwtstamp_get()
  tcp: Prevent low rmem stalls with SO_RCVLOWAT.
  tipc: fix memory leak caused by tipc_buf_append()
  net: protect tcf_block_unbind with block lock
  erofs: avoid duplicated permission check for "trusted." xattrs
  arch/x86/amd/ibs: Fix re-arming IBS Fetch
  x86/traps: Fix #DE Oops message regression
  x86/xen: disable Firmware First mode for correctable memory errors
  PCI: aardvark: Fix initialization with old Marvell's Arm Trusted Firmware
  ata: ahci: mvebu: Make SATA PHY optional for Armada 3720
  fuse: fix page dereference after free
  bpf: Fix comment for helper bpf_current_task_under_cgroup()
  evm: Check size of security.evm before using it
  p54: avoid accessing the data mapped to streaming DMA
  cxl: Rework error message for incompatible slots
  RDMA/addr: Fix race with netevent_callback()/rdma_addr_cancel()
  mtd: lpddr: Fix bad logic in print_drs_error
  drm/i915/gem: Serialise debugfs i915_gem_objects with ctx->mutex
  serial: qcom_geni_serial: To correct QUP Version detection logic
  serial: pl011: Fix lockdep splat when handling magic-sysrq interrupt
  PM: runtime: Fix timer_expires data type on 32-bit arches
  ata: sata_rcar: Fix DMA boundary mask
  xen/gntdev.c: Mark pages as dirty
  openrisc: Fix issue with get_user for 64-bit values
  misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp()
  phy: marvell: comphy: Convert internal SMCC firmware return codes to errno
  Linux 5.8.18
  UBUNTU: upstream stable to v5.8.18

To manage notifications about this bug go to: