[Kernel-packages] [Bug 1942347] Re: proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute

[Kleber Sacilotto de Souza]

** Description changed:

  Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with:
  
  12:48:34 DEBUG| [stdout] proc01  1  TFAIL  :  proc01.c:400: read
  failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address
+ 
+ I was also able to reproduce this on a amd64 VM running
+ 5.11.0-31-generic by loading the spl module and running:
+ 
+ $ sudo cat /proc/sys/kernel/spl/hostid 
+ cat: /proc/sys/kernel/spl/hostid: Bad address
+ 
+ This is probably not a regression, affecting only s390x now likely
+ because the spl module wasn't loaded on the previous runs. s390x systems
+ are not re-deployed for the regression tests, so this could be a
+ lingering module loaded for previous tests.

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

Title:
  proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute

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

Bug description:
  Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems
  with:

  12:48:34 DEBUG| [stdout] proc01  1  TFAIL  :  proc01.c:400: read
  failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address

  I was also able to reproduce this on a amd64 VM running
  5.11.0-31-generic by loading the spl module and running:

  $ sudo cat /proc/sys/kernel/spl/hostid 
  cat: /proc/sys/kernel/spl/hostid: Bad address

  This is probably not a regression, affecting only s390x now likely
  because the spl module wasn't loaded on the previous runs. s390x
  systems are not re-deployed for the regression tests, so this could be
  a lingering module loaded for previous tests.

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


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

[Kernel-packages] [Bug 1942347] [NEW] proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute

[Kleber Sacilotto de Souza]

Public bug reported:

Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with:

12:48:34 DEBUG| [stdout] proc01  1  TFAIL  :  proc01.c:400: read
failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address

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

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

** Affects: linux (Ubuntu Hirsute)
 Importance: Undecided
 Status: Confirmed

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

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

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

Title:
  proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute

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

Bug description:
  Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems
  with:

  12:48:34 DEBUG| [stdout] proc01  1  TFAIL  :  proc01.c:400: read
  failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address

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


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

[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')

[Kleber Sacilotto de Souza]

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

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

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

Bug description:
  
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25


  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests fails on hirsute (KeyError: 'flavour')

[Kleber Sacilotto de Souza]

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

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

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

** Tags added: sru-20210816

** Summary changed:

- devlink_port_split from ubuntu_kernel_selftests fails on hirsute (KeyError: 
'flavour')
+ devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute 
(KeyError: 'flavour')

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

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

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

Bug description:
  
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25


  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 1900644] Re: tls from net in ubuntu_kernel_selftests failed on G/H/I (multi_chunk_sendfile)

[Kleber Sacilotto de Souza]

This is fixed for hirsute (checked with linux and linux-riscv) by the
following commit:

commit 5e7d3d1edcad9b96fe0ddfb155f0109856019f9a
Author: Jakub Kicinski 
Date:   Fri Jun 18 13:34:06 2021 -0700

tls: prevent oversized sendfile() hangs by ignoring MSG_MORE

BugLink: https://bugs.launchpad.net/bugs/1938340

[ Upstream commit d452d48b9f8b1a7f8152d33ef52cfd7fe1735b0a ]

The 5.8 kernels (checked with focal/linux-hwe-5.8) is still affected.
But given that the 5.8 kernels are not receiving upstream stable updates
anymore this issue will likely not be fixed.

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

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

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

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

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

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

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

** Changed in: linux-hwe-5.8 (Ubuntu Hirsute)
   Status: New => Invalid

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

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

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

** Summary changed:

- tls from net in ubuntu_kernel_selftests failed on G/H/I (multi_chunk_sendfile)
+ tls from net in ubuntu_kernel_selftests failed on G/H (multi_chunk_sendfile)

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

Title:
  tls from net in ubuntu_kernel_selftests failed on G/H
  (multi_chunk_sendfile)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.8 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.8 source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Fix Released
Status in linux-hwe-5.8 source package in Hirsute:
  Invalid

Bug description:
  Issue found on Groovy AWS 5.8.0-1010.10

  Test failed with:
   # [==] Running 93 tests from 4 test cases.
   # [ RUN ] global.non_established
   # [ OK ] global.non_established
   # [ RUN ] global.keysizes
   # [ OK ] global.keysizes
   # [ RUN ] tls_basic.base_base
   # [ OK ] tls_basic.base_base
   # [ RUN ] tls.12.sendfile
   # [ OK ] tls.12.sendfile
   # [ RUN ] tls.12.send_then_sendfile
   # [ OK ] tls.12.send_then_sendfile
   # [ RUN ] tls.12.multi_chunk_sendfile
   # [ FAIL ] tls.12.multi_chunk_sendfile
   # [ RUN ] tls.12.recv_max
   # [ OK ] tls.12.recv_max
   # [ RUN ] tls.12.recv_small
   # [ OK ] tls.12.recv_small
   # [ RUN ] tls.12.msg_more
   # [ OK ] tls.12.msg_more
   # [ RUN ] tls.12.msg_more_unsent
   # [ OK ] tls.12.msg_more_unsent
   # [ RUN ] tls.12.sendmsg_single
   # [ OK ] tls.12.sendmsg_single
   # [ RUN ] tls.12.sendmsg_fragmented
   # [ OK ] tls.12.sendmsg_fragmented
   # [ RUN ] tls.12.sendmsg_large
   # [ OK ] tls.12.sendmsg_large
   # [ RUN ] tls.12.sendmsg_multiple
   # [ OK ] tls.12.sendmsg_multiple
   # [ RUN ] tls.12.sendmsg_multiple_stress
   # [ OK ] tls.12.sendmsg_multiple_stress
   # [ RUN ] tls.12.splice_from_pipe
   # [ OK ] tls.12.splice_from_pipe
   # [ RUN ] tls.12.splice_from_pipe2
   # [ OK ] tls.12.splice_from_pipe2
   # [ RUN ] tls.12.send_and_splice
   # [ OK ] tls.12.send_and_splice
   # [ RUN ] tls.12.splice_to_pipe
   # [ OK ] tls.12.splice_to_pipe
   # [ RUN ] tls.12.recvmsg_single
   # [ OK ] tls.12.recvmsg_single
   # [ RUN ] tls.12.recvmsg_single_max
   # [ OK ] tls.12.recvmsg_single_max
   # [ RUN ] tls.12.recvmsg_multiple
   # [ OK ] tls.12.recvmsg_multiple
   # [ RUN ] tls.12.single_send_multiple_recv
   # [ OK ] tls.12.single_send_multiple_recv
   # [ RUN ] tls.12.multiple_send_single_recv
   # [ OK ] tls.12.multiple_send_single_recv
   # [ RUN ] tls.12.single_send_multiple_recv_non_align
   # [ OK ] tls.12.single_send_multiple_recv_non_align
   # [ RUN ] tls.12.recv_partial
   # [ OK ] tls.12.recv_partial
   # [ RUN ] tls.12.recv_nonblock
   # [ OK ] tls.12.recv_nonblock
   # [ RUN ] tls.12.recv_peek
   # [ OK ] tls.12.recv_peek
   # [ RUN ] tls.12.recv_peek_multiple
   # [ OK ] tls.12.recv_peek_multiple
   # [ RUN ] tls.12.recv_peek_multiple_records
   # [ OK ] tls.12.recv_peek_multiple_records
   # [ RUN ] tls.12.recv_peek_large_buf_mult_recs
   # [ OK ] tls.12.recv_peek_large_buf_mult_recs
   # [ RUN ] tls.12.recv_lowat
   # [ OK ] tls.12.recv_lowat
   # [ RUN ] tls.12.bidir
   # [ OK ] tls.12.bidir
   # [ RUN ] tls.12.pollin
   # [ OK ] tls.12.pollin
   # [ RUN ] tls.12.poll_wait
   # [ OK ] tls.12.poll_wait
   # [ RUN ] tls.12.poll_wait_split
   # [ OK ] tls.12.poll_wait_split
   # [ RUN ] tls.12.blocking
   # [ 

[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic

[Kleber Sacilotto de Souza]

Hello alex dekker,

have you installed also linux-modules-5.11.0-34-generic and linux-
modules-extra-5.11.0-34-generic?

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

Title:
  Wobbly graphics on built-in display since linux-
  image-5.11.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Confirmed
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  == SRU Justification ==

  [Impact]
  Wobbly graphics after a kernel update. 

  [Fix]
  Older panels may require more bandwidth then advertised, so we need to
  use max params for them.

  [Test]
  Multiple users tested with positive result.

  [Where problems could occur]
  This patch reverts to the old behavior, which is to use max parameters,
  for older panels. If there's any new panel reports with older DP
  version, this might change the behavior on it.

  == Original Bug Report ==

  Lenovo laptop with Intel + Nvidia graphics.

  Since booting from  linux-image-5.11.0-22-generic, the built-in display is 
unusable, with wobbling horizontal stripes from the disk decryption prompt 
onwards:
  https://www.youtube.com/watch?v=LyRTuPzCe2I
  HDMI output works fine.

  If I boot from linux-image-5.11.0-18-generic instead, all is well.
  If I use Recovery mode with linux-image-5.11.0-22-generic and continue 
bootup, it's usable but there's no HDMI output.

  I think others may be having this issue too:
  
https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base#

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-22-generic 5.11.0-22.23
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1598 F pulseaudio
   /dev/snd/controlC0:  alex   1598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul 17 09:50:31 2021
  InstallationDate: Installed on 2021-01-03 (194 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 80DU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-22-generic N/A
   linux-backports-modules-5.11.0-22-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN31WW(V1.14)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80DU
  dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout

[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/1932966

Title:
  kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout

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

Bug description:
  [Impact]
  Our Bionic 4.15 kernel lacks of movups/movupd emulation support.

  With the following commit added into the emulator test in
  ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu 
Date: Wed Apr 21 16:12:57 2021 -0700

x86: add movups/movupd sse testcases to emulator.c

Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for 
movups/movupd").

Signed-off-by: Jacob Xu 
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini 

  It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd 
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490 
RSP=0051b470
R8 =000a R9 =03f8 R10=000d 
R11=
R12=e000 R13= R14=d000 
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010   00c09300 DPL=0 DS [-WA]
CS =0008   00a09b00 DPL=0 CS64 [-RA]
SS =0010   00c09300 DPL=0 DS [-WA]
DS =0010   00c09300 DPL=0 DS [-WA]
FS =0010   00c09300 DPL=0 DS [-WA]
GS =0010 0051a510  00c09300 DPL=0 DS [-WA]
LDT=   8200 DPL=0 LDT
TR =0080 0041207a  8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2= 
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03 
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)

  [Fix]
  * 29916968c48691 kvm: Add emulation for movups/movupd

  This patch can be cherry-picked into Bionic.

  It can fix our test failure plus, as mentioned in the commit message,
  emulation failures with openbsd as guest and with Windows 10 with
  intel HD graphics pass through.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/

  Run the emulator test from ubuntu_kvm_unit_tests, with this patch
  applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to 
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)

  [Where problems could occur]
  I didn't see any other patch that claims to be a fix of this one in
  the upstream tree. The problem I think of for the moment is that we
  might see other failures when using this in the future.


  [Original Bug Report]
  Found this on B/KVM, current cycle (sru-20210531):

  18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
  18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
  18:27:11 DEBUG| [stderr] emulation failure
  18:27:11 

[Kernel-packages] [Bug 1939915] Re: memory leaking when removing a profile

[Kleber Sacilotto de Souza]

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

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

Title:
  memory leaking when removing a profile

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  There's a memory leak in the kernel when removing a profile.
  A simple reproducible example:

  root@ubuntu:~# echo "profile foo {}" > profile
  root@ubuntu:~# apparmor_parser profile
  root@ubuntu:~# apparmor_parser -R profile
  root@ubuntu:~# echo scan > /sys/kernel/debug/kmemleak
  root@ubuntu:~# cat /sys/kernel/debug/kmemleak
  unreferenced object 0x99bcf5128bb0 (size 16):
    comm "apparmor_parser", pid 1318, jiffies 4295139856 (age 33.196s)
    hex dump (first 16 bytes):
  01 00 00 00 00 00 00 00 98 1f 01 fd bc 99 ff ff  
    backtrace:
  [] kmem_cache_alloc_trace+0xd8/0x1e0
  [<86ca7bd9>] aa_alloc_proxy+0x30/0x60
  [<0e34f34c>] aa_alloc_profile+0xd4/0x100
  [] unpack_profile+0x16f/0xe10
  [<19033e2b>] aa_unpack+0x119/0x500
  [] aa_replace_profiles+0x94/0xca0
  [<1833f520>] policy_update+0x124/0x1e0
  [<992f950e>] profile_load+0x7d/0xa0
  [] __vfs_write+0x1b/0x40
  [<4e709f5d>] vfs_write+0xb9/0x1a0
  [<280db840>] SyS_write+0x5e/0xe0
  [<14c5ab5d>] do_syscall_64+0x79/0x130
  [] entry_SYSCALL_64_after_hwframe+0x41/0xa6
  [<9d368497>] 0x

  This issue was already fixed upstream 3622ad25d4d6 v5.8-rc1~102^2
  It still needs to be applied on xenial, bionic and focal.

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


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

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[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/1939618

Title:
  CryptoExpress EP11 cards are going offline

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

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


-- 
Mailing 

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[Kleber Sacilotto de Souza]

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

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

Title:
  CryptoExpress EP11 cards are going offline

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4

[Kleber Sacilotto de Souza]

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

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

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

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

** Changed in: linux-hwe-5.4 (Ubuntu Bionic)
   Status: New => Invalid

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

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

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

** Changed in: linux-hwe-5.4 (Ubuntu Focal)
   Status: New => Invalid

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

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

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

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

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

Title:
  memfd from ubuntu_kernel_selftests failed to build on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe source package in Focal:
  Invalid
Status in linux-hwe-5.4 source package in Focal:
  Invalid

Bug description:
  Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with:
error: ‘F_SEAL_FUTURE_WRITE’ undeclared

  Build log:
  $ sudo make TARGETS=memfd
  make --no-builtin-rules ARCH=x86 -C ../../.. headers_install
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ 
-I../../../../usr/include/memfd_test.c common.o  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test
  memfd_test.c: In function ‘test_seal_future_write’:
  memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in 
this function); did you mean ‘F_SEAL_WRITE’?
mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE);
 ^~~
 F_SEAL_WRITE
  memfd_test.c:749:27: note: each undeclared identifier is reported only once 
for each function it appears in
  ../lib.mk:141: recipe for target 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test'
 failed
  make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test]
 Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  Makefile:143: recipe for target 'all' failed
  make: *** [all] Error 2

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


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

[Kernel-packages] [Bug 1939855] Re: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands

[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/1939855

Title:
  [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with
  ethtool specific register commands

Status in dellserver:
  Incomplete
Status in focal package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in focal source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  When we run the command, ethtool -d  with Intel cards (ice 
driver), the kernel crashes because of the ice driver.
  The same works fine with HWE kernel (5.11). Here, we do not see any crash.

  [FIXES]

  ice: Fix bad register reads
  The "ethtool -d" handler reads registers in the ice_regs_dump_list array
  and returns read values back to the userspace.

  commitID:  1fba4a8a92706c89716449b1aab1b6879f438d34

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34

  [TESTING]

  Install Focal on a system with an E810 network device.
  Ensure the network device has an IP address and has connectivity
  Run ethtool -d 
  Expected result: Prints a register dump for the specified network device

  [REGRESSION RISK]

  The regression risk is low

  [OTHER INFO]

  I have added the fix, built the kernel and tested the fix.

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next

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


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

[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()

[Kleber Sacilotto de Souza]

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

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

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

Title:
  ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with
  dump_page()

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux-oem-5.13 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  The memory-hotplug test has been intermittently timing out (or trashing the 
test
  VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now.

  While the offline memory test obey ratio limit, the same test with
  error injection does not and tries to offline all the hotpluggable
  memory, spamming system logs with hundreds of thousands of dump_page()
  entries, slowing system down (to the point the test itself timesout and
  gets terminated) and excessive fs occupation:

  ...
  [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 
mapping:c001fc03e950 index:0xe7b
  [ 9784.393355] def_blk_aops
  [ 9784.393356] flags: 0x382062(referenced|active|workingset|private)
  [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 
c001fc03e950
  [ 9784.393359] raw: 0e7b c6607b18 0003 
c490d000
  [ 9784.393359] page dumped because: migration failure
  [ 9784.393360] page->mem_cgroup:c490d000
  [ 9784.393416] migrating pfn 1f46d failed ret:1
  ...

  $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l
  2405558

  $ ls -la /var/log/kern.log
  -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log

  [Fix]
  * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with 
dump_page(), ratio limit hot-remove error test

  [Test Plan]
  Run the memory-hotplug test, this log spamming issue should not happen again.

  [Where problems could occur]
  If this fix is incorrect we might be unable to catch some other issue.

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


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

[Kernel-packages] [Bug 1941669] Re: alsa: the soundwire audio doesn't work on the Dell TGL-H machines

[Kleber Sacilotto de Souza]

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

Title:
  alsa: the soundwire audio doesn't work on the Dell TGL-H machines

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  These 2 patches were merged to upstream kernel from v5.12, no need to
  send them to impish/oem-5.13/unstable kernels. And this patch is
  already in the oem-5.10 kernel, for focal kernel, since focal kernel
  doesn't support soundwire audio, these 2 patches are useless for focal
  kernel.

  
  [Impact]
  The Dell precision 5760 is a TGL-H machine, and it has soundwire audio
  design, when running the hirsute kernel, the audio driver fails to
  load sof-firmware, then the whole audio fails to initialize and fails
  to work.

  [Fix]
  Backport 2 patches, these will remove hardcoded firmware name and
  allow load firmware according to the firmware name defined by pciid

  [Test]
  Booting the patched kernel, check dmesg, there is no errors about
  loading audio sof-firmware, playsound to spk and headphone, all worked
  well, record sound from internal mic and external mic, all worked well.

  [Where problems could occur]
  The patch remove the hardcoded firmware for all TGL soundwire machines,
  this could make the TGL soundwire machines fail to load the
  sof-firmware then the whole audio fail to work. But this possibiliy is
  low, since we tested the patches on different TGL soundwire machines,
  all worked well.

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


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

[Kernel-packages] [Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM

[Kleber Sacilotto de Souza]

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

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

Title:
  e1000e blocks the boot process when it tried to write checksum to its
  NVM

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  While probing e1000e, it checks its NVM checksum, and write correct checksum 
back if the checksum is not correct. But for recent GBE update for security, 
its NVM could be written once for MAC address during production, so write 
checksum during driver probing is not allowed and would block the boot process.

  [Fix]
  Intel provides a fix for it.
  
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.nef...@intel.com/

  [Test]
  Verified on a Dell machine which has wrong NVM checksum.

  [Where problems could occur]
  From what Intel told us, the checksum isn't correct is not a big deal, we 
could ignore it and it won't lead to any issues.

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


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

[Kernel-packages] [Bug 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version

[Kleber Sacilotto de Souza]

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

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

Title:
  disable “CONFIG_HISI_DMA” config for ubuntu version

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 ubuntu-20.04-hwe series:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  Setup soft RAID5 on kunpeng920 machine and system will crash because of 
hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with 
hisi_dma.

  [Test Plan]
  Setup soft RAID5 and wait for few seconds. Kernel will crash.

  [Regression Risk]
  CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other 
platform, and full regression test is needed on kunpeng920.

  ===
  [Bug Description]
  disable “CONFIG_HISI_DMA” config for ubuntu version

  [Steps to Reproduce]
  1)
  2)
  3)

  [Actual Results]
  this module cause some error

  [Expected Results]
  ok
  [Reproducibility]

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

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


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

[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Kleber Sacilotto de Souza]

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

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  In Progress

Bug description:
  This patch is for soundwire audio, and only ubuntu 5.11-generic
  and later kernels support soundwire audio driver, so this patch is not
  sent to groovy and focal kernels.

  For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM
  project, it is not urgent to merge this patch to OEM kenrels, after
  the patch is in the hirsute and impish kernels, the oem kernels will
  have this patch when syncing with generic kernels.

  [Impact]
  On the Dell XPS 17 (9710) machine, the audio card is not detected when
  booting hirsute or impish kernels. So the audio doesn't work on this
  machine with ubuntu linux 21.04 or 21.10.

  [Fix]
  Backport a upstream patch, this will set the correct codec config
  for this machine: rt711 for headset, dual rt1308 for spks and rt715
  for internal mic.

  [Test]
  Booting up with the patched kernel, the audio card is detected, test
  internal speaker and internal mic, all work well, plug a headset,
  the headphone and external mic work well too.

  
  [Where problems could occur]
  This change only applis to the Dell machines with the 
  DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the
  regression, it will make the audio (speaker, internal mic and headset)
  can't work anymore on the Dell machine with that PRODUCT_SKU, but this
  possibility is very low, and we tested the patch on the machine, so
  far no regression is found.

  
  No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 
20.10 or 21.04  .  Can connect via USB headset and audio will work.   Tried 
suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not 
work. Currently running 21.04 with proposed.

  Have tried hirsute-proposed (5.11.0-24-generic) with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
  Uname: Linux 5.11.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mblack 1698 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 12 11:21:27 2021
  InstallationDate: Installed on 2021-07-07 (4 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 012MMP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9710
  dmi.product.sku: 0A5D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1939473] Re: mute/micmute LEDs no function on HP ProBook 650 G8

[Kleber Sacilotto de Souza]

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

Title:
  mute/micmute LEDs no function on HP ProBook 650 G8

Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1940610] Re: Fix mic noise on HP ProBook 445 G8

[Kleber Sacilotto de Souza]

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

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

Title:
   Fix mic noise on HP ProBook 445 G8

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  There's mic noise on HP ProBook 445 G8.

  [Fix]
  Limit mic boost to make the audio capture crystal clear.

  [Test]
  $ arecord -f dat test
  $ aplay test
  With the fix, the mic noise is gone.

  [Where problems could occur]
  If someone would like to let others hear the noise in Zoom, this will
  deprive of their pleasure.

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


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

[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel

[Kleber Sacilotto de Souza]

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

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade kernel to 5.11.0-25 which introduce some ODM patches from 
AAEON, user encounters below errors
  [   5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  [Fix]
  AAEON provides a patch to check the BFPI version before loading the driver.
  Which fixes the issue introduced by
  Hirsute:
 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices
  Impish:
 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices

  
  [Test]
  Verified by AAEON.

  [Where problems could occur]
  It adds a check while probing the driver, should have no impact to normal 
user.

  =

  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

     5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
    *-core
     description: Motherboard
     product: TUF GAMING B550M-PLUS (WI-FI)
     vendor: ASUSTeK COMPUTER INC.
     physical id: 0
     version: Rev X.0x
     serial: 201176738701636
     slot: Default string
   *-firmware
    description: BIOS
    vendor: American Megatrends Inc.
    physical id: 0
    version: 2403
    date: 06/16/2021
    size: 64KiB
    capacity: 16MiB
    capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock

[Kleber Sacilotto de Souza]

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

Title:
  External displays not working on Thinkpad T490 with ThinkPad
  Thunderbolt 3 Dock

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

Bug description:
  I have two external displays chained via Display port connected to the
  ThinkPad Thunderbolt 3 Dock.

  They are working with kernel 5.8.0-63 but not with the new 5.11.0-25
  kernel.

  I could reproduce this behavior several times for both kernels, as
  follows: I booted up with disconnected dock, logged in, then I
  connected it, disconnected it, and connected it again.

  With the 5.11.0-25 kernel the external displays go black; the main
  screen turns off and on several times. Sometimes the main screen
  remains working, but UI is lagging.

  I'm attaching the logs. Two separate boots for each variant are marked
  'a'/'b'.

  SRU Justifications:
  ===
  [Impact]
  External displays not working on Thinkpad T490 with ThinkPad Thunderbolt
  3 Dock

  [Fix]
  Some SKL systems DP output fails when AUX timeout of LTTPR detection.
  Disable the LTTPR detection until GLK to fix the link training.

  [Test]
  Verified on hardware, external DP work fine.
  Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock 
are good.

  [Where problems could occur]
  It may break output of external DP.

  This patch from 5.12-rc5, only Hirsute kernel is SRUed.

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


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

[Kernel-packages] [Bug 1936682] Re: Fix kernel panic caused by legacy devices on AMD platforms

[Kleber Sacilotto de Souza]

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

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

Title:
  Fix kernel panic caused by legacy devices on AMD platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  When a legacy device is only 32bit DMA capable and it's in the same
  IOMMU group with iommu_v2 capable devices, the device in question will
  be forced to use identity mapping and triggers kernel panic on DMA
  operation because it can't do 64bit DMA.

  [Fix]
  Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also
  how Intel and ARM64 platforms deal with legacy devices.

  [Test]
  Boot an affected system. Kernel panic in Realtek WiFi driver's probe
  routine.

  After the patch is applied, the system can work normally.

  [Where problems could occur]
  The default swiotlb uses 64MB memory, so if the system doesn't have any
  legacy device, there are 64MB ram less for the system to use.

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


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

[Kernel-packages] [Bug 1942123] Re: Hirsute update: upstream stable patchset 2021-08-30

[Kleber Sacilotto de Souza]

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

Title:
  Hirsute update: upstream stable patchset 2021-08-30

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  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-08-30

  Ported from the following upstream stable releases:
  v5.10.57, v5.13.9
  v5.10.58, v5.13.10

     from git://git.kernel.org/

  drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser"
  Revert "drm/i915: Propagate errors on awaiting already signaled fences"
  regulator: rtmv20: Fix wrong mask for strobe-polarity-high
  regulator: rt5033: Fix n_voltages settings for BUCK and LDO
  spi: stm32h7: fix full duplex irq handler handling
  ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
  r8152: Fix potential PM refcount imbalance
  qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
  ASoC: rt5682: Fix the issue of garbled recording after powerd_dbus_suspend
  net: Fix zero-copy head len calculation.
  ASoC: ti: j721e-evm: Fix unbalanced domain activity tracking during startup
  ASoC: ti: j721e-evm: Check for not initialized parent_clk_id
  efi/mokvar: Reserve the table only if it is in boot services data
  nvme: fix nvme_setup_command metadata trace event
  drm/amd/display: Fix comparison error in dcn21 DML
  drm/amd/display: Fix max vstartup calculation for modes with borders
  Revert "Bluetooth: Shutdown controller after workqueues are flushed or 
cancelled"
  firmware: arm_scmi: Add delayed response status check
  Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"
  selftest/bpf: Adjust expected verifier errors
  bpf, selftests: Adjust few selftest result_unpriv outcomes
  bpf: Update selftests to reflect new error states
  bpf, selftests: Adjust few selftest outcomes wrt unreachable code
  selftest/bpf: Verifier tests for var-off access
  spi: mediatek: Fix fifo transfer
  cifs: use helpers when parsing uid/gid mount options and validate them
  cifs: add missing parsing of backupuid
  net: dsa: sja1105: parameterize the number of ports
  ASoC: Intel: boards: handle hda-dsp-common as a module
  UBUNTU: [Config] updateconfigs for SND_SOC_INTEL_HDA_DSP_COMMON
  ASoC: Intel: boards: create sof-maxim-common module
  UBUNTU: [Config] updateconfigs for SND_SOC_INTEL_SOF_MAXIM_COMMON
  ASoC: Intel: boards: fix xrun issue on platform with max98373
  r8152: Fix a deadlock by doubly PM resume
  UBUNTU: upstream stable to v5.10.57, v5.13.9
  Revert "ACPICA: Fix memory leak caused by _CID repair function"
  ALSA: seq: Fix racy deletion of subscriber
  bus: ti-sysc: Fix gpt12 system timer issue with reserved status
  net: xfrm: fix memory leak in xfrm_user_rcv_msg
  arm64: dts: ls1028a: fix node name for the sysclk
  ARM: imx: add missing iounmap()
  ARM: imx: add missing clk_disable_unprepare()
  ARM: dts: imx6qdl-sr-som: Increase the PHY reset duration to 10ms
  arm64: dts: ls1028: sl28: fix networking for variant 2
  ARM: dts: colibri-imx6ull: limit SDIO clock to 25MHz
  ARM: imx: fix missing 3rd argument in macro imx_mmdc_perf_init
  ARM: dts: imx: Swap M53Menlo pinctrl_power_button/pinctrl_power_out pins
  arm64: dts: armada-3720-turris-mox: fixed indices for the SDHC controllers
  arm64: dts: armada-3720-turris-mox: remove mrvl,i2c-fast-mode
  ALSA: usb-audio: fix incorrect clock source setting
  clk: stm32f4: fix post divisor setup for I2S/SAI PLLs
  ARM: dts: am437x-l4: fix typo in can@0 node
  omap5-board-common: remove not physically existing vdds_1v8_main 
fixed-regulator
  dmaengine: uniphier-xdmac: Use readl_poll_timeout_atomic() in atomic state
  clk: tegra: Implement disable_unused() of tegra_clk_sdmmc_mux_ops
  dmaengine: stm32-dma: Fix PM usage counter imbalance in stm32 dma ops
  dmaengine: stm32-dmamux: Fix PM usage counter unbalance in stm32 dmamux ops
  spi: imx: mx51-ecspi: Reinstate low-speed CONFIGREG delay
  spi: imx: mx51-ecspi: Fix low-speed CONFIGREG delay calculation
  scsi: sr: Return correct event when media event code is 3
  media: videobuf2-core: dequeue if start_streaming fails
  ARM: dts: stm32: Disable LAN8710 EDPD on DHCOM
  ARM: dts: stm32: Fix touchscreen IRQ line assignment on DHCOM
  dmaengine: imx-dma: configure the generic DMA type to make 

[Kernel-packages] [Bug 1941898] [NEW] ubuntu_kernel_selftests.ftrace timeout on H/riscv

[Kleber Sacilotto de Souza]

Public bug reported:

ubuntu_kernel_selftests.ftrace times out always after the same step when
running on hirsute/linux-riscv on the regression tests infrastructure
(QEMU VM).

Log from the tests running with hirsute/linux-riscv 5.11.0-1018.19:

18:02:56 INFO | START   ubuntu_kernel_selftests.ftrace  
ubuntu_kernel_selftests.ftrace  timestamp=1629568976timeout=1800
localtime=Aug 21 18:02:56   
18:02:56 DEBUG| Persistent state client._record_indent now set to 2
18:02:56 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.ftrace', 'ubuntu_kernel_selftests.ftrace')
18:02:56 DEBUG| Waiting for pid 29328 for 1800 seconds
18:02:56 WARNI| System python is too old, crash handling disabled
18:02:56 DEBUG| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
18:02:56 DEBUG| Running 'sudo make -C linux/tools/testing/selftests 
TARGETS=ftrace run_tests'
18:02:57 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
18:02:57 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../.. 
headers_install
18:02:57 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18:03:13 DEBUG| [stdout]   INSTALL ./usr/include
18:03:14 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18:03:14 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
18:03:14 DEBUG| [stdout] make[1]: Nothing to be done for 'all'.
18:03:14 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
18:03:15 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
18:03:15 DEBUG| [stdout] TAP version 13
18:03:15 DEBUG| [stdout] 1..1
18:03:15 DEBUG| [stdout] # selftests: ftrace: ftracetest
18:03:15 ERROR| [stderr] perl: warning: Setting locale failed.
18:03:15 ERROR| [stderr] perl: warning: Please check that your locale settings:
18:03:15 ERROR| [stderr]LANGUAGE = (unset),
18:03:15 ERROR| [stderr]LC_ALL = (unset),
18:03:15 ERROR| [stderr]LC_CTYPE = "C.UTF-8",
18:03:15 ERROR| [stderr]LANG = "en_US.UTF-8"
18:03:15 ERROR| [stderr] are supported and installed on your system.
18:03:15 ERROR| [stderr] perl: warning: Falling back to the standard locale 
("C").
18:03:16 DEBUG| [stdout] # === Ftrace unit tests ===
18:03:21 DEBUG| [stdout] # [1] Basic trace file check   [PASS]
18:03:58 DEBUG| [stdout] # [2] Basic test for tracers   [PASS]
18:04:04 DEBUG| [stdout] # [3] Basic trace clock test   [PASS]
18:04:10 DEBUG| [stdout] # [4] Basic event tracing check[PASS]
18:04:16 DEBUG| [stdout] # [5] Change the ringbuffer size   [PASS]
18:04:21 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS]
18:04:27 DEBUG| [stdout] # [7] trace_pipe and trace_marker  [PASS]
18:04:32 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers 
[UNRESOLVED]
18:04:33 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes 
[UNSUPPORTED]
18:04:38 DEBUG| [stdout] # [10] Generic dynamic event - add/remove kprobe 
events[FAIL]
18:04:39 DEBUG| [stdout] # [11] Generic dynamic event - add/remove synthetic 
events [UNSUPPORTED]
18:04:39 DEBUG| [stdout] # [12] Generic dynamic event - selective clear 
(compatibility) [UNSUPPORTED]
18:04:40 DEBUG| [stdout] # [13] Generic dynamic event - generic clear event 
[UNSUPPORTED]
18:04:46 DEBUG| [stdout] # [14] event tracing - enable/disable with event level 
files   [PASS]
18:04:54 DEBUG| [stdout] # [15] event tracing - restricts events based on pid 
notrace filtering [PASS]
18:05:00 DEBUG| [stdout] # [16] event tracing - restricts events based on pid   
[PASS]
18:05:07 DEBUG| [stdout] # [17] event tracing - enable/disable with subsystem 
level files   [PASS]
18:05:14 DEBUG| [stdout] # [18] event tracing - enable/disable with top level 
files [PASS]
18:05:21 DEBUG| [stdout] # [19] Test trace_printk from module   [PASS]
18:05:39 DEBUG| [stdout] # [20] ftrace - function graph filters with stack 
tracer   [PASS]
18:05:50 DEBUG| [stdout] # [21] ftrace - function graph filters [PASS]
18:06:04 DEBUG| [stdout] # [22] ftrace - function pid notrace filters   [PASS]
18:06:18 DEBUG| [stdout] # [23] ftrace - function pid filters   [PASS]
18:06:28 DEBUG| [stdout] # [24] ftrace - stacktrace filter command  [PASS]
18:06:38 DEBUG| [stdout] # [25] ftrace - function trace with cpumask[PASS]
18:07:09 DEBUG| [stdout] # [26] ftrace - test for function event triggers   
[FAIL]
18:07:28 DEBUG| [stdout] # [27] ftrace - function trace on module   [PASS]
18:07:37 INFO | Timer expired (1800 sec.), nuking pid 29328

[Kernel-packages] [Bug 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => Won't Fix

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

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

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

Title:
  ftrace from ubuntu_kernel_selftests failed with "test for function
  event triggers" on F/G/H

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Won't Fix
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  ftrace from ubuntu_kernel_selftests failed with "test for function
  event triggers" on Groovy riscv 5.8.0-21.23

  This test was recently added, not considering a regression

  Log is getting cut off from regression test report. the below is all
  that could be retrieved at the moment:

  04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules 
ARCH=riscv -C ../../.. headers_install
  04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  04/13 23:48:14 DEBUG| utils:0153| [stdout]   INSTALL ./usr/include
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
  04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
  04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale 
failed.
  04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check 
that your locale settings:
  04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
  04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
  04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
  04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
  04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and 
installed on your system.
  04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to 
the standard locale ("C").
  04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct 
functions against tracers [UNRESOLVED]
  04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct 
functions against kprobes [UNSUPPORTED]
  04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
add/remove kprobe events[FAIL]
  04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
add/remove synthetic events [UNSUPPORTED]
  04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - 
selective clear (compatibility) [UNSUPPORTED]
  04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - 
generic clear event [UNSUPPORTED]
  04/13 23:49:44 DEBUG| utils:0153| [stdout] # [14] event tracing - 

[Kernel-packages] [Bug 1909521] Re: ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8

[Kleber Sacilotto de Souza]

Focal/linux-hwe-5.8 is no longer supported.

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Won't Fix

** Changed in: ubuntu-kernel-tests
   Status: New => Won't Fix

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

Title:
  ftrace test from ubuntu_kernel_selftests timeout on F-5.8 P8

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Won't Fix

Bug description:
  Issue found on Focal 5.8.0-33, with P8 node dryden
  The ftracetest will timeout with:
  [17] event tracing - enable/disable with subsystem level files

  
  $ sudo ./ftracetest 
  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] Change the ringbuffer size[PASS]
  [6] Snapshot and tracing setting  [PASS]
  [7] trace_pipe and trace_marker   [PASS]
  [8] Test ftrace direct functions against tracers  [UNRESOLVED]
  [9] Test ftrace direct functions against kprobes  [UNRESOLVED]
  [10] Generic dynamic event - add/remove kprobe events [PASS]
  [11] Generic dynamic event - add/remove synthetic events  [PASS]
  [12] Generic dynamic event - selective clear (compatibility)  [PASS]
  [13] Generic dynamic event - generic clear event  [PASS]
  [14] event tracing - enable/disable with event level files[PASS]
  [15] event tracing - restricts events based on pid notrace filtering  [PASS]
  [16] event tracing - restricts events based on pid[PASS]
  [17] event tracing - enable/disable with subsystem level files
  (test timeout here)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-33-generic 5.8.0-33.36~20.04.1
  ProcVersionSignature: User Name 5.8.0-33.36~20.04.1-generic 5.8.17
  Uname: Linux 5.8.0-33-generic ppc64le
  .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: 
'/sys/firmware/opal/msglog'
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: ppc64el
  CasperMD5CheckResult: skip
  Date: Tue Dec 29 05:11:04 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 1.19 1.24 2.68 3/1472 929062
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 2447 00:19:576 0 EOF
   2: POSIX  ADVISORY  WRITE 2720 00:19:597 0 EOF
   3: FLOCK  ADVISORY  WRITE 2685 00:19:647 0 EOF
  ProcSwaps:
   Filename TypeSizeUsed
Priority
   /swap.img   file 8388544 0   
-2
  ProcVersion: Linux version 5.8.0-33-generic (buildd@bos02-ppc64el-009) (gcc 
(User Name 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for User Name) 
2.34) #36~20.04.1-User Name SMP Wed Dec 9 16:57:18 UTC 2020
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

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


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

[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on H/F-riscv

[Kleber Sacilotto de Souza]

Groovy has reached EOL and hirsute/linux-riscv is also affected.
Adjusting bug accordingly.

** Summary changed:

- ubuntu_ftrace_smoke_test timeout on F/G-riscv
+ ubuntu_ftrace_smoke_test timeout on H/F-riscv

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

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: New => Won't Fix

** Tags removed: kqa-blocker
** Tags added: sru-20210816

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

Title:
  ubuntu_ftrace_smoke_test timeout on H/F-riscv

Status in ubuntu-kernel-tests:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux-riscv source package in Groovy:
  Won't Fix
Status in linux-riscv source package in Hirsute:
  New

Bug description:
  Issue found on 5.8.0-13.15 RISCV with a KVM instance.

  Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control 
  03:46:12 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  03:46:12 DEBUG| Initializing the state engine
  03:46:12 DEBUG| Persistent state client.steps now set to []
  03:46:13 DEBUG| Persistent option harness now set to None
  03:46:13 DEBUG| Persistent option harness_args now set to None
  03:46:13 DEBUG| Selected harness: standalone
  03:46:15 INFO | START timestamp=1609127175localtime=Dec 
28 03:46:15   
  03:46:16 DEBUG| Persistent state client._record_indent now set to 1
  03:46:16 DEBUG| Test has timeout: 1350 sec.
  03:46:16 INFO |   START   ubuntu_ftrace_smoke_test.ftrace-smoke-test  
ubuntu_ftrace_smoke_test.ftrace-smoke-test  timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16   
  03:46:16 DEBUG| Persistent state client._record_indent now set to 2
  03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_ftrace_smoke_test.ftrace-smoke-test', 
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
  03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
  03:46:16 WARNI| System python is too old, crash handling disabled
  03:46:16 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
  03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in 
/boot/config-5.8.0-13-generic)
  03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in 
/boot/config-5.8.0-13-generic)
  03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files 
exist
  03:46:19 DEBUG| [stdout] PASSED (function_graph in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:19 DEBUG| [stdout] PASSED (function in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:20 DEBUG| [stdout] PASSED (nop in 
/sys/kernel/debug/tracing/available_tracers)
  03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
  03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
  03:46:35 DEBUG| [stdout]  - tracer function_graph got enough data
  03:46:35 DEBUG| [stdout]  - tracer function_graph completed
  03:46:36 DEBUG| [stdout]  - tracer function_graph being turned off
  03:46:36 DEBUG| [stdout]  - tracer got 532 irq events
  03:46:43 DEBUG| [stdout]  - tracer hwlat got enough data
  03:46:43 DEBUG| [stdout]  - tracer hwlat completed
  03:46:43 DEBUG| [stdout]  - tracer hwlat being turned off
  03:46:44 DEBUG| [stdout]  - tracer nop being set as current tracer
  03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of 
tracing output))
  03:46:48 DEBUG| [stdout]  - tracer blk got enough data
  03:46:48 DEBUG| [stdout]  - tracer blk completed
  03:46:48 DEBUG| [stdout]  - tracer blk being turned off
  03:46:48 DEBUG| [stdout]  - tracer nop being set as current tracer
  03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of 
tracing output))
  03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
  03:46:57 INFO |   ERROR   
ubuntu_ftrace_smoke_test.ftrace-smoke-test  
ubuntu_ftrace_smoke_test.ftrace-smoke-test  timestamp=1609127216
localtime=Dec 28 03:46:56   Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
  File "/home/ubuntu/autotest/client/parallel.py", line 112, in 
fork_waitfor_timed
utils.nuke_pid(pid)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in 
nuke_pid
raise error.AutoservRunError('Could not kill %d' % pid, None)

[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

Confirmed that lttng-modules-dkms 2.12.5-1ubuntu2~21.04.1 in hirsute-
proposed can be installed, build and loaded successfully:

$ dkms status
lttng-modules, 2.12.5, 5.11.0-33-generic, x86_64: installed

$ lsmod | grep "^lttng" | awk '{ print $1 }'
lttng_test
lttng_ring_buffer_metadata_mmap_client
lttng_ring_buffer_metadata_client
lttng_ring_buffer_client_overwrite
lttng_ring_buffer_client_mmap_overwrite
lttng_ring_buffer_client_mmap_discard
lttng_ring_buffer_client_discard
lttng_probe_writeback
lttng_probe_workqueue
lttng_probe_vmscan
lttng_probe_v4l2
lttng_probe_udp
lttng_probe_timer
lttng_probe_sunrpc
lttng_probe_statedump
lttng_probe_sock
lttng_probe_skb
lttng_probe_signal
lttng_probe_scsi
lttng_probe_sched
lttng_probe_regulator
lttng_probe_rcu
lttng_probe_random
lttng_probe_printk
lttng_probe_power
lttng_probe_net
lttng_probe_napi
lttng_probe_module
lttng_probe_kvm
lttng_probe_kmem
lttng_probe_jbd2
lttng_probe_irq
lttng_probe_gpio
lttng_probe_compaction
lttng_probe_block
lttng_probe_asoc
lttng_probe_9p
lttng_tracer
lttng_statedump
lttng_wrapper
lttng_uprobes
lttng_lib_ring_buffer
lttng_kretprobes
lttng_kprobes
lttng_clock_plugin_test
lttng_clock

autopkgtest also completed successfully:

amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/lttng-modules/20210827_092600_f29e1@/log.gz
arm64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/lttng-modules/20210827_093210_e3a3a@/log.gz
admhf - not supported
ppc64el - 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/lttng-modules/20210827_092927_f29e1@/log.gz
s390x - 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/lttng-modules/20210827_091858_e3a3a@/log.gz

Thanks!

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

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

Title:
  lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  New
Status in linux-hwe-5.11 source package in Focal:
  Invalid
Status in lttng-modules source package in Focal:
  Fix Released
Status in lttng-modules source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  lttng-modules-dkms is reporting many build errors with linux-hwe-5.11,
  because of many kernel ABI changes.

  [Fix]

  Backporting the individual patches to fix all the build errors would
  be a lot of work and the risk to introduce regressions would be pretty
  high, therefore it seems safer to update to the version that is also
  used in impish, that works with 5.11 and it's backward compatible (so
  it works also with 5.4).

  [Test]

  ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest-
  client-tests)

  [Where problems could occur]

  This is a major version update, so it does not contain trivial changes
  as backporting individual patches/fixes, so there's a risk to see
  regressions with lttng (however potential regressions are *only*
  limited to lttng).

  However, this way is definitely safer than backporting all the
  individual changes to fix the all the kernel ABI changes introduced in
  5.11.

  [Original bug report]

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz

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


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

[Kernel-packages] [Bug 1940449] Re: package linux-image-5.11.0-27-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-27-generic package pre-removal script subprocess retur

[Kleber Sacilotto de Souza]

Hello Nate,

Could you please paste the output of the following command?

$ apt-get remove --purge linux-image-5.11.0-27-generic

I'm interested in the package pre-removal script error, which seems to
be the reason why the package can't be removed.

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

Title:
  package linux-image-5.11.0-27-generic (not installed) failed to
  install/upgrade: installed linux-image-5.11.0-27-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  Whenever I (or some other process) try to remove kernel 5.11, the
  process fails. This matters for me because 5.11 introduces a
  regression that I can only mitigate by running an older kernel (like
  5.8 or 5.4).

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-27-generic (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Aug 18 09:32:40 2021
  ErrorMessage: installed linux-image-5.11.0-27-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-signed-hwe-5.11
  Title: package linux-image-5.11.0-27-generic (not installed) failed to 
install/upgrade: installed linux-image-5.11.0-27-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1940449/+subscriptions


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

[Kernel-packages] [Bug 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume

[Kleber Sacilotto de Souza]

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

Title:
  dell300x: rsi wifi and bluetooth crash after suspend and resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-dell300x package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-dell300x source package in Bionic:
  Fix Committed

Bug description:
  I tested the upstream stable kernel 4.19.191, also could reproduce
  this issue, and reported this testing result to stable mail list.

  
  [Impact]
  On the Dell300x machine, after system suspend and resume, the wifi
  and bluetooth can't work anymore.

  [Fix]
  Revert a patch which was applied to bionic kernel from stable update.

  [Test]
  Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10,
  then check dmesg to make sure there is crashing log, and run 'nmcli d
  wifi' and 'bluetoothctl, power on, scan on', all worked well.

  [Where problems could occur]
  After applying this SRU, the rsi wifi and bluetooth could have come
  change, like wifi and bluetooth can't work well after resume, but this
  possibility is very low, I already run '$sudo rtcwake -m freeze -s 10'
  for 50 times, the wifi and bluetooth still worked well.

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


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

[Kernel-packages] [Bug 1939310] Re: Intel Warnings while booting Ice Lake w/VROC

[Kleber Sacilotto de Souza]

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

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

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

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

** Tags added: sru-20210816

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

Title:
  Intel Warnings while booting Ice Lake w/VROC

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

Bug description:
  The Following Intel Specific Warnings have been found while booting
  the Bionic 4.15 Kernel, (4.15.0-154.161)

  16:11:03 INFO | Checking error message in /var/log/syslog:
  16:11:03 INFO | Scanning for pattern "kernel: \[ *\d+\.\d+\] BUG:.*"
  16:11:03 INFO | PASSED, log clean.
  16:11:03 INFO | Scanning for pattern "kernel: \[ *\d+\.\d+\] Oops:.*"
  16:11:03 INFO | PASSED, log clean.
  16:11:03 INFO | Scanning for pattern "kernel: \[ *\d+\.\d+\] kernel BUG at.*"
  16:11:03 INFO | PASSED, log clean.
  16:11:03 INFO | Scanning for pattern "kernel: \[ *\d+\.\d+\] WARNING:.*"
  16:11:03 INFO | Pattern found. Matching lines as follows:
  16:11:03 INFO | kernel: [0.052278] WARNING: CPU: 0 PID: 1 at 
/build/linux-HN7Wi9/linux-4.15.0/arch/x86/events/intel/core.c:4495 
intel_pmu_init+0x1141/0x134b
  16:11:03 INFO | kernel: [0.040061] WARNING: CPU: 0 PID: 1 at 
/build/linux-RR1r0f/linux-4.15.0/arch/x86/events/intel/core.c:4495 
intel_pmu_init+0x1141/0x134b
  16:11:03 INFO | kernel: [0.040060] WARNING: CPU: 0 PID: 1 at 
/build/linux-RR1r0f/linux-4.15.0/arch/x86/events/intel/core.c:4495 
intel_pmu_init+0x1141/0x134b
  16:11:03 ERROR| Exception escaping from test:

  The Following messages did not cause any problems during kernel
  bootup, They appear to be performance related, these does not appear
  to be a regression as it does occur in previous cycles, however it was
  NOT bugged. Bugging this and generating hints. appropriately.

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


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

[Kernel-packages] [Bug 1934873] Re: ubuntu_aufs_smoke_test fails on Focal cloud v5.11

[Kleber Sacilotto de Souza]

Confirmed the testcase completes successfully with focal/linux-
oracle-5.11 5.11.0-1016.17~20.04.1:

[...]
12:11:41 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_aufs_smoke_test/ubuntu_aufs_smoke_test.sh'
12:11:41 DEBUG| [stdout] aufs: mount: PASSED
12:11:41 DEBUG| [stdout] aufs: checksum file1: PASSED
12:11:41 DEBUG| [stdout] aufs: checksum file2: PASSED
12:11:41 DEBUG| [stdout] aufs: checksum file3: PASSED
12:11:42 DEBUG| [stdout] aufs: delete: PASSED
12:11:42 DEBUG| [stdout] aufs: rename file: PASSED
12:11:42 DEBUG| [stdout] aufs: move file to subdirectory: PASSED
12:11:42 DEBUG| [stdout] aufs: rename file2 to dir1: PASSED
12:11:42 DEBUG| [stdout] aufs: move file3 to root and then to dir1: PASSED
12:11:42 DEBUG| [stdout] aufs: truncate: PASSED
12:11:42 DEBUG| [stdout] aufs: stacked: PASSED
12:11:42 DEBUG| [stdout] aufs: modify: PASSED
12:11:43 DEBUG| [stdout] aufs: check hardlink count in root: PASSED
12:11:43 DEBUG| [stdout] aufs: check hardlink count in root after 1 link 
removed: PASSED
12:11:43 DEBUG| [stdout] aufs: check hardlink count in root after 1 more link 
removed: PASSED
12:11:43 DEBUG| [stdout] aufs: attempt to create invalid cross link on root: 
PASSED
12:11:43 DEBUG| [stdout] aufs: remove root view of original file: PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check: PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (touch file): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod u-x): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod u+x): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod g-w): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod g+w): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod o-r): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod o+r): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (chmod 0777): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (access time): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (modify time): PASSED
12:11:43 DEBUG| [stdout] aufs: simple stat check (change size): PASSED
12:11:43 DEBUG| [stdout] aufs: umount: PASSED
12:11:47 DEBUG| [stdout] aufs: mount/umount (repeated) PASSED
12:11:48 INFO | GOODubuntu_aufs_smoke_test.aufs-smoke-test  
ubuntu_aufs_smoke_test.aufs-smoke-test  timestamp=1628856708localtime=Aug 
13 12:11:48   completed successfully

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

Title:
  ubuntu_aufs_smoke_test fails on Focal cloud v5.11

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws-5.11 package in Ubuntu:
  New
Status in linux-azure-5.11 package in Ubuntu:
  New
Status in linux-gcp-5.11 package in Ubuntu:
  New
Status in linux-oracle-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-aws-5.11 source package in Focal:
  New
Status in linux-azure-5.11 source package in Focal:
  New
Status in linux-gcp-5.11 source package in Focal:
  New
Status in linux-oracle-5.11 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Several Focal v5.11 edge kernels are missing AUFS.

   * This is a regression against previous Focal kernels (v5.4 and v5.8)
  because it is expected to support same set of features on v5.11.

  [Test Plan]

   * Run ubuntu_aufs_smoke_test autotest.

  [Where problems could occur]

   * Mounting AUFS file system could succeed introducing a variety of
  failures due to bugs in AUFS.

  lp:1925407 disabled the test for Hirsute but now we have v5.11 edge
  kernels on Focal and it fails the same.

  It's not a regression but test should be hinted.

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


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

[Kernel-packages] [Bug 1928686] Re: Some cloud kernels have Android related config options disabled

[Kleber Sacilotto de Souza]

linux-gcp (5.11.0-1017.19) hirsute:

$ wget https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+files/linux-
buildinfo-5.11.0-1017-gcp_5.11.0-1017.19_amd64.deb

$ egrep 'ANDROI|ASHMEM' -R .
./usr/lib/linux/5.11.0-1017-gcp/config:CONFIG_ASHMEM=m
./usr/lib/linux/5.11.0-1017-gcp/config:CONFIG_ANDROID=y
./usr/lib/linux/5.11.0-1017-gcp/config:CONFIG_ANDROID_BINDER_IPC=m
./usr/lib/linux/5.11.0-1017-gcp/config:CONFIG_ANDROID_BINDERFS=m
./usr/lib/linux/5.11.0-1017-gcp/config:CONFIG_ANDROID_BINDER_DEVICES=""
./usr/lib/linux/5.11.0-1017-gcp/config:# CONFIG_ANDROID_BINDER_IPC_SELFTEST is 
not set

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

Title:
  Some cloud kernels have Android related config options disabled

Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-gcp source package in Groovy:
  New
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-gcp source package in Hirsute:
  New
Status in linux-oracle source package in Hirsute:
  Fix Released

Bug description:
  For Anbox Cloud we require certain CONFIG_ANDROID_* options to be
  enabled in the kernel. We do this already for most of our cloud
  kernels (GCE, AWS, Azure) and the generic kernel and should do so for
  the oracle (and possible others too). We have customers looking at
  running Anbox Cloud on OCI instances and having the ashmem and binder
  kernel modules available is a precondition for this to work.

  
  The following options are what we need

  CONFIG_ANDROID=y
  CONFIG_ANDROID_BINDER_IPC=m
  CONFIG_ANDROID_BINDERFS=m
  CONFIG_ANDROID_BINDER_DEVICES=""
  # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
  CONFIG_ASHMEM=m

  These should be the same across all our kernels where we're going to
  support Anbox Cloud.

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


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

[Kernel-packages] [Bug 1928686] Re: Some cloud kernels have Android related config options disabled

[Kleber Sacilotto de Souza]

linux-gcp (5.4.0-1051.55) focal:

$ wget https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+files/linux-
buildinfo-5.4.0-1051-gcp_5.4.0-1051.55_amd64.deb

$ egrep 'ANDROI|ASHMEM' ./usr/lib/linux/5.4.0-1051-gcp/config
CONFIG_ASHMEM=m
CONFIG_ANDROID_VSOC=m
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=m
CONFIG_ANDROID_BINDER_DEVICES=""
# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set

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

Title:
  Some cloud kernels have Android related config options disabled

Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-gcp source package in Groovy:
  New
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-gcp source package in Hirsute:
  New
Status in linux-oracle source package in Hirsute:
  Fix Released

Bug description:
  For Anbox Cloud we require certain CONFIG_ANDROID_* options to be
  enabled in the kernel. We do this already for most of our cloud
  kernels (GCE, AWS, Azure) and the generic kernel and should do so for
  the oracle (and possible others too). We have customers looking at
  running Anbox Cloud on OCI instances and having the ashmem and binder
  kernel modules available is a precondition for this to work.

  
  The following options are what we need

  CONFIG_ANDROID=y
  CONFIG_ANDROID_BINDER_IPC=m
  CONFIG_ANDROID_BINDERFS=m
  CONFIG_ANDROID_BINDER_DEVICES=""
  # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
  CONFIG_ASHMEM=m

  These should be the same across all our kernels where we're going to
  support Anbox Cloud.

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


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

[Kernel-packages] [Bug 1939287] Re: dbgsym package is missing for ubuntu focal hwe kernel 5.11

[Kleber Sacilotto de Souza]

Hello,

Thank you reporting this issue. I have done a quick investigation and
confirmed that we are not building the "linux-image-
unsigned-5.11.0-25-generic-dbgsym" which is needed to install the debug
symbols. We are going to work on a fix for this.

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

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

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

Title:
  dbgsym package is missing for ubuntu focal hwe kernel 5.11

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux-hwe-5.11 source package in Focal:
  Confirmed

Bug description:
  Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing
  from http://ddebs.ubuntu.com/dists/focal-updates/main/binary-
  amd64/Packages

  This breaks our workflow when the system is automatically upgraded
  from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic-
  dbgsym" for focal, which is also an HWE kernel. So why not do the same
  for 5.11.0 kernels?

  Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which
  depends on the unsigned one, but the latter does not exist. This seems
  to indicate something is broken.

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


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

[Kernel-packages] [Bug 1939333] Re: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post-installation script subpr

[Kleber Sacilotto de Souza]

Hello,

Thank you for your feedback.

I will mark this bug report as 'Invalid' as it doesn't seem to be an
issue with the hwe-5.11 kernel. Please feel free to re-open this bug if
you disagree.

Thank you.

** Changed in: linux-signed-hwe-5.11 (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to
  install/upgrade: installed linux-image-5.11.0-25-generic package post-
  installation script subprocess returned error exit status 1

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Invalid

Bug description:
  This issue appeared while VirtualBox kernel modules were being
  compiled for installation of the newest Guest Additions

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 13:57:45 2021
  ErrorMessage: installed linux-image-5.11.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-02-13 (177 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-signed-hwe-5.11
  Title: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to 
install/upgrade: installed linux-image-5.11.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939333/+subscriptions


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

[Kernel-packages] [Bug 1939178] Re: Bluetooth not working after an update

[Kleber Sacilotto de Souza]

Hello Yinka,

My apologies, I have pasted the wrong package name for the terminal
command. Could you please run it again but with the following package
name as parameter?

$ dpkg -l linux-modules-extra-5.11.0-25-generic

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

Title:
  Bluetooth not working after an update

Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth not working after an update.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yinka  2369 F pulseaudio
   /dev/snd/controlC0:  yinka  2369 F pulseaudio
   /dev/snd/controlC2:  yinka  2369 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 22:29:07 2021
  InstallationDate: Installed on 2021-04-16 (112 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=a4150dca-83c9-4b4d-8376-b13fbd5c172f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2020
  dmi.bios.release: 1.49
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.49
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.89
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.49:bd02/24/2020:br1.49:efr21.89:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: K5T62UP#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL

[Kleber Sacilotto de Souza]

** Changed in: linux-hwe-5.11 (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/1939301

Title:
  REGRESSION: shiftfs lets sendfile fail with EINVAL

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux-meta-hwe-5.11 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux-meta-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-meta-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
  tools we're using in bionic containers as part of Anbox Cloud start to
  fail when executed on the 5.11 kernel.

  A simple reproducer looks like this:

  1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 
5.11.0-25-generic #27~20.04.1-Ubuntu)
  2. Install LXD and enable shiftfs
  $ snap install lxd
  $ snap set lxd shiftfs.enable true
  $ snap restart --reload lxd
  3. Launch bionic container and run `lxc-info`
  $ lxc launch ubuntu:b c0
  $ lxc shell c0
  c0$ apt update
  c0$ apt install -y lxc-utils
  root@c1:~# apt show lxc-utils | grep Version
  Version: 3.0.3-0ubuntu1~18.04.1
  c0$ mkdir -p containers/test
  c0$ touch containers/test/config
  c0$ lxc-info -P containers -n test
  Failed to load config for test
  Failure to retrieve information on containers:test

  Looking into the failing `lxc-info` call with strace reveals:

  ...
  memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4
  openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5
  sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument
  ...

  LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't
  affected. Any other tool using sendfile however is affected and will
  fail. Bionic is affected as the 3.0.3 version of LXC it includes still
  uses sendfile.

  Disabling shiftfs makes things work again and can be considered as a
  workaround to a certain degree, but not be applicable in all cases.

  Further analysis with Christian (cbrauner) from the LXD team this
  morning showed that shiftfs is missing an implementation for the now
  required slice_read handler in the file_operations structure. So
  whenever shiftfs is being used, all calls to sendfile will fail
  because of the missing implementation. The generic handler for this
  got removed in the following upstream change:
  https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/

  Christian implemented a quick fix:
  https://paste.ubuntu.com/p/TPsjfCpnD5/

  As of today I don't know of any customer of Anbox Cloud who is
  affected by this as most of them run with one of our cloud kernels.
  However as soon as 5.11 rolls out to the cloud kernels, we will hit
  production systems and cause them to fail.

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


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

[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver

[Kleber Sacilotto de Souza]

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

** Changed in: linux-hwe-5.11 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-hwe-5.11 (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/1933518

Title:
  Update SmartPQI driver

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  Improves support in SmartPQI for most recent controllers

  [Fixes]
  All are in mainline currently and cleanly cherry pick into Hirsute.
  c64aab41c5e1 scsi: smartpqi: Remove unused functions
  5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static 
checker issue
  667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue
  d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045
  75fbeacca3ad scsi: smartpqi: Add new PCI IDs
  43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from 
hibernation
  d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs
  18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets
  55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and 
target_port_protocols
  ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives
  a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf()
  3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues
  66f1c2b40270 scsi: smartpqi: Update device scan operations
  2790cd4d3f6a scsi: smartpqi: Update OFA management
  5be9db069d3f scsi: smartpqi: Update RAID bypass handling
  9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown
  37f3318199ce scsi: smartpqi: Synchronize device resets with mutex
  4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA
  06b41e0d1800 scsi: smartpqi: Update event handler
  7a84a821f194 scsi: smartpqi: Add support for wwid
  ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds
  99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks
  5be746d7d74b scsi: smartpqi: Add host level stream detection enable
  c7ffedb3a774 scsi: smartpqi: Add stream detection
  583891c9e509 scsi: smartpqi: Align code with oob driver
  598bef8d7942 scsi: smartpqi: Add support for long firmware version
  f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and 
feature bits
  7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes
  6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes
  1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code
  281a817f232e scsi: smartpqi: Refactor aio submission code
  2708a25643ab scsi: smartpqi: Add support for new product ids
  b622a601a13a scsi: smartpqi: Correct request leakage during reset operations
  c6d3ee209b9e scsi: smartpqi: Use host-wide tag space

  The patches they provided only apply the hunk that applies to the SmartPQI 
driver. This commit was a much wider commit that removes references to 
MODULE_SUPPORTED_DEVICE in many drivers across the kernel.
  6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE

  [Testing]
  On machines equipped with SmartPQI SCSI controller:
  1. reboot tests
  2. insmod/rmmod tests
  3. fio testing: no performance regressions

  [Regression Risk]
  Patchset changes only smartpqi driver so regression is limited to systems 
equipped with this SCSI device.  On such SmartPQI-equipped systems the patchset 
can cause data corruption, data loss or unavailability of SCSI storage and boot 
failure.

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


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

[Kernel-packages] [Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference

[Kleber Sacilotto de Souza]

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

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

** Changed in: linux-hwe-5.11 (Ubuntu Hirsute)
   Status: Fix Committed => Invalid

** Changed in: linux-hwe-5.11 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  HWE kernels: NFSv4.1 NULL pointer dereference

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid

Bug description:
  Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing
  crashes (in this case with a NetApp filer mounted):

  [  266.199481] BUG: kernel NULL pointer dereference, address: 
  [  266.199495] #PF: supervisor read access in kernel mode
  [  266.199500] #PF: error_code(0x) - not-present page
  [  266.199503] PGD 0 P4D 0
  [  266.199511] Oops:  [#1] SMP PTI
  [  266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 
5.11.0-25-generic #27~20.04.1-Ubuntu
  [  266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS 
SE5C600.86B.02.06.0006.032420170950 03/24/2017
  [  266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4]
  [  266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 
45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 
24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20
  [  266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297
  [  266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: 

  [  266.199646] RDX: a04847636780 RSI: a04847636780 RDI: 
a048621ef200
  [  266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: 
a086febdcc10
  [  266.199653] R10: a0677ffd6b80 R11: 0003 R12: 

  [  266.199657] R13: a048621ef228 R14: a048621ef228 R15: 

  [  266.199661] FS:  7f9de3440340() GS:a086febc() 
knlGS:
  [  266.199665] CS:  0010 DS:  ES:  CR0: 80050033
  [  266.199669] CR2:  CR3: 00012ed86006 CR4: 
001706e0
  [  266.199674] Call Trace:
  [  266.199682]  _pnfs_return_layout+0x13d/0x2c0 [nfsv4]
  [  266.199755]  ? nfs_put_delegation+0x4c/0x70 [nfsv4]
  [  266.199814]  nfs4_evict_inode+0x78/0x80 [nfsv4]
  [  266.199870]  evict+0xd2/0x180
  [  266.199879]  iput+0x18f/0x200
  [  266.199884]  nfs_dentry_iput+0x33/0x60 [nfs]
  [  266.199934]  dentry_unlink_inode+0xb8/0x110
  [  266.199946]  __dentry_kill+0xdf/0x180
  [  266.199953]  dput+0x171/0x320
  [  266.199960]  do_renameat2+0x387/0x500
  [  266.199968]  __x64_sys_rename+0x45/0x50
  [  266.199974]  do_syscall_64+0x38/0x90
  [  266.199987]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  266.16] RIP: 0033:0x7f9de644200b
  [  266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 
1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8
  [  266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 
0052
  [  266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 
7f9de644200b
  [  266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 
55a5ed4aea00
  [  266.200022] RBP: 55a5ed503060 R08:  R09: 

  [  266.200025] R10: 000d R11: 0246 R12: 
0001
  [  266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 
55a5ed37b980
  [  266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_
  pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 
rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec 
rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s
  ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl 
ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common 
xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn

  This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11).
  I believe it is fixed by https://patchwork.kernel.org/project/linux-
  nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please
  consider backporting this patch.

  (The bug was briefly also 

[Kernel-packages] [Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference

[Kleber Sacilotto de Souza]

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

** Changed in: linux-hwe-5.11 (Ubuntu Hirsute)
   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/1939157

Title:
  HWE kernels: NFSv4.1 NULL pointer dereference

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Fix Committed

Bug description:
  Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing
  crashes (in this case with a NetApp filer mounted):

  [  266.199481] BUG: kernel NULL pointer dereference, address: 
  [  266.199495] #PF: supervisor read access in kernel mode
  [  266.199500] #PF: error_code(0x) - not-present page
  [  266.199503] PGD 0 P4D 0
  [  266.199511] Oops:  [#1] SMP PTI
  [  266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 
5.11.0-25-generic #27~20.04.1-Ubuntu
  [  266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS 
SE5C600.86B.02.06.0006.032420170950 03/24/2017
  [  266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4]
  [  266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 
45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 
24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20
  [  266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297
  [  266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: 

  [  266.199646] RDX: a04847636780 RSI: a04847636780 RDI: 
a048621ef200
  [  266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: 
a086febdcc10
  [  266.199653] R10: a0677ffd6b80 R11: 0003 R12: 

  [  266.199657] R13: a048621ef228 R14: a048621ef228 R15: 

  [  266.199661] FS:  7f9de3440340() GS:a086febc() 
knlGS:
  [  266.199665] CS:  0010 DS:  ES:  CR0: 80050033
  [  266.199669] CR2:  CR3: 00012ed86006 CR4: 
001706e0
  [  266.199674] Call Trace:
  [  266.199682]  _pnfs_return_layout+0x13d/0x2c0 [nfsv4]
  [  266.199755]  ? nfs_put_delegation+0x4c/0x70 [nfsv4]
  [  266.199814]  nfs4_evict_inode+0x78/0x80 [nfsv4]
  [  266.199870]  evict+0xd2/0x180
  [  266.199879]  iput+0x18f/0x200
  [  266.199884]  nfs_dentry_iput+0x33/0x60 [nfs]
  [  266.199934]  dentry_unlink_inode+0xb8/0x110
  [  266.199946]  __dentry_kill+0xdf/0x180
  [  266.199953]  dput+0x171/0x320
  [  266.199960]  do_renameat2+0x387/0x500
  [  266.199968]  __x64_sys_rename+0x45/0x50
  [  266.199974]  do_syscall_64+0x38/0x90
  [  266.199987]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  266.16] RIP: 0033:0x7f9de644200b
  [  266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 
1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8
  [  266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 
0052
  [  266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 
7f9de644200b
  [  266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 
55a5ed4aea00
  [  266.200022] RBP: 55a5ed503060 R08:  R09: 

  [  266.200025] R10: 000d R11: 0246 R12: 
0001
  [  266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 
55a5ed37b980
  [  266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_
  pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 
rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec 
rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s
  ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl 
ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common 
xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn

  This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11).
  I believe it is fixed by https://patchwork.kernel.org/project/linux-
  nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please
  consider backporting this patch.

  (The bug was briefly also present in the 5.4 kernels, but was fixed in
  5.4.0-79: see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673)

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


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

[Kernel-packages] [Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL

[Kleber Sacilotto de Souza]

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

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

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

** Changed in: linux-hwe-5.11 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-hwe-5.11 (Ubuntu Impish)
   Status: New => Invalid

** Changed in: linux-hwe-5.11 (Ubuntu Focal)
   Status: New => In Progress

** No longer affects: linux-meta-hwe-5.11 (Ubuntu)

** Changed in: linux-meta-hwe-5.11 (Ubuntu Focal)
   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/1939301

Title:
  REGRESSION: shiftfs lets sendfile fail with EINVAL

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  In Progress
Status in linux-meta-hwe-5.11 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux-meta-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-meta-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
  tools we're using in bionic containers as part of Anbox Cloud start to
  fail when executed on the 5.11 kernel.

  A simple reproducer looks like this:

  1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 
5.11.0-25-generic #27~20.04.1-Ubuntu)
  2. Install LXD and enable shiftfs
  $ snap install lxd
  $ snap set lxd shiftfs.enable true
  $ snap restart --reload lxd
  3. Launch bionic container and run `lxc-info`
  $ lxc launch ubuntu:b c0
  $ lxc shell c0
  c0$ apt update
  c0$ apt install -y lxc-utils
  root@c1:~# apt show lxc-utils | grep Version
  Version: 3.0.3-0ubuntu1~18.04.1
  c0$ mkdir -p containers/test
  c0$ touch containers/test/config
  c0$ lxc-info -P containers -n test
  Failed to load config for test
  Failure to retrieve information on containers:test

  Looking into the failing `lxc-info` call with strace reveals:

  ...
  memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4
  openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5
  sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument
  ...

  LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't
  affected. Any other tool using sendfile however is affected and will
  fail. Bionic is affected as the 3.0.3 version of LXC it includes still
  uses sendfile.

  Disabling shiftfs makes things work again and can be considered as a
  workaround to a certain degree, but not be applicable in all cases.

  Further analysis with Christian (cbrauner) from the LXD team this
  morning showed that shiftfs is missing an implementation for the now
  required slice_read handler in the file_operations structure. So
  whenever shiftfs is being used, all calls to sendfile will fail
  because of the missing implementation. The generic handler for this
  got removed in the following upstream change:
  https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/

  Christian implemented a quick fix:
  https://paste.ubuntu.com/p/TPsjfCpnD5/

  As of today I don't know of any customer of Anbox Cloud who is
  affected by this as most of them run with one of our cloud kernels.
  However as soon as 5.11 rolls out to the cloud kernels, we will hit
  production systems and cause them to fail.

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


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

[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver

[Kleber Sacilotto de Souza]

Focal hwe-5.11 (5.11.0-26.28_20.04.1) has not been promoted to
-proposed. We are going to re-spin the previous cycle kernel to include
the SmartPQI driver update, I'll post here the new kernel version for
tests.

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

Title:
  Update SmartPQI driver

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Won't Fix
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  Improves support in SmartPQI for most recent controllers

  [Fixes]
  All are in mainline currently and cleanly cherry pick into Hirsute.
  c64aab41c5e1 scsi: smartpqi: Remove unused functions
  5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static 
checker issue
  667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue
  d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045
  75fbeacca3ad scsi: smartpqi: Add new PCI IDs
  43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from 
hibernation
  d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs
  18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets
  55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and 
target_port_protocols
  ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives
  a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf()
  3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues
  66f1c2b40270 scsi: smartpqi: Update device scan operations
  2790cd4d3f6a scsi: smartpqi: Update OFA management
  5be9db069d3f scsi: smartpqi: Update RAID bypass handling
  9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown
  37f3318199ce scsi: smartpqi: Synchronize device resets with mutex
  4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA
  06b41e0d1800 scsi: smartpqi: Update event handler
  7a84a821f194 scsi: smartpqi: Add support for wwid
  ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds
  99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks
  5be746d7d74b scsi: smartpqi: Add host level stream detection enable
  c7ffedb3a774 scsi: smartpqi: Add stream detection
  583891c9e509 scsi: smartpqi: Align code with oob driver
  598bef8d7942 scsi: smartpqi: Add support for long firmware version
  f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and 
feature bits
  7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes
  6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes
  1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code
  281a817f232e scsi: smartpqi: Refactor aio submission code
  2708a25643ab scsi: smartpqi: Add support for new product ids
  b622a601a13a scsi: smartpqi: Correct request leakage during reset operations
  c6d3ee209b9e scsi: smartpqi: Use host-wide tag space

  The patches they provided only apply the hunk that applies to the SmartPQI 
driver. This commit was a much wider commit that removes references to 
MODULE_SUPPORTED_DEVICE in many drivers across the kernel.
  6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE

  [Testing]
  On machines equipped with SmartPQI SCSI controller:
  1. reboot tests
  2. insmod/rmmod tests
  3. fio testing: no performance regressions

  [Regression Risk]
  Patchset changes only smartpqi driver so regression is limited to systems 
equipped with this SCSI device.  On such SmartPQI-equipped systems the patchset 
can cause data corruption, data loss or unavailability of SCSI storage and boot 
failure.

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


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

[Kernel-packages] [Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault

[Kleber Sacilotto de Souza]

Hello,

Could you please try the kernel update which is currently in -proposed
(version 5.4.0-81.91) to see if it fixes the issue you are having?

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. 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/1939417

Title:
  Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT,
  amdgpu :09:00.0: [gfxhub0] retry page fault

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu GUI crashes (w and w/o Wayland)
  on
  AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, 
stepping: 0x1)

  sometimes total OS crash, sometimes ssh access still possible.

  1) The release of Ubuntu you are using
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  Codename: focal

  2) The version of the package you are using
  the GUI crashes at different times in different situations, no specific 
application or package identified.

  3) What you expected to happen
  Ubuntu working, applications like LibreOffice do their job.

  4) What happened instead
  After some time of successful work (from seconds to hour) suddenly no input 
by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen 
(sometimes not), one time flickering GUI.
  Sometimes remote ssh reboot possible. Sometimes not even successful ping to 
the network interface possible.

  No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with 
Wayland"; several reboots;
  no issues experienced when accessing machine via ssh (remote). Using 
application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not 
show this issue.

  dmesg says when crashed:

  [ 4926.673857] [drm] enabling link 0 failed: 15
  [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed
  [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 
ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c
  s0 pid 7854)
  [ 6478.430481] amdgpu :09:00.0:   in page starting at address 
0x80010ea95000 from client 27
  [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [ 6478.430487] amdgpu :09:00.0:  MORE_FAULTS: 0x1
  [ 6478.430490] amdgpu :09:00.0:  WALKER_ERROR: 0x0
  [ 6478.430492] amdgpu :09:00.0:  PERMISSION_FAULTS: 0x3
  [ 6478.430495] amdgpu :09:00.0:  MAPPING_ERROR: 0x0
  [ 6478.430497] amdgpu :09:00.0:  RW: 0x0
  [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 
ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c
  s0 pid 7854)
  [ 6478.430509] amdgpu :09:00.0:   in page starting at address 
0x80010eac9000 from client 27
  [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [ 6478.430514] amdgpu :09:00.0:  MORE_FAULTS: 0x1
  [ 6478.430516] amdgpu :09:00.0:  WALKER_ERROR: 0x0
  [ 6478.430518] amdgpu :09:00.0:  PERMISSION_FAULTS: 0x3
  [ 6478.430520] amdgpu :09:00.0:  MAPPING_ERROR: 0x0
  [ 6478.430522] amdgpu :09:00.0:  RW: 0x0
  [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 
ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c
  s0 pid 7854)

  

  [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 
ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854)
  [ 6488.436542] amdgpu :09:00.0:   in page starting at address 
0x80010eae3000 from client 27
  [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [ 6488.436545] amdgpu :09:00.0:  MORE_FAULTS: 0x1
  [ 6488.436546] amdgpu :09:00.0:  WALKER_ERROR: 0x0
  [ 6488.436547] amdgpu :09:00.0:  PERMISSION_FAULTS: 0x3
  [ 6488.436548] amdgpu :09:00.0:  MAPPING_ERROR: 0x0
  [ 6488.436549] amdgpu :09:00.0:  RW: 0x0
  [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
but soft recovered

  
---
  
---

  [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc 
version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr
  i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic 
root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Hygon HygonGenuine
  [0.00]   Centaur CentaurHauls
  [0.00]   zhaoxin   Shanghai
  [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
  [

[Kernel-packages] [Bug 1939333] Re: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-25-generic package post-installation script subpr

[Kleber Sacilotto de Souza]

Hello Evgueni,

The HWE kernel in Focal Fossa 20.04 has recently been updated from 5.8
to 5.11. Reading the logs attached, it seems your system is trying to
install the new 5.11 kernel packages and is failing at this stage:

Processing triggers for linux-image-5.11.0-25-generic (5.11.0-25.27~20.04.1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
run-parts: failed to stat component /etc/kernel/postinst.d/vboxadd: No such 
file or directory

The file '/etc/kernel/postinst.d/vboxadd' was likely supposed to be
installed by Virtualbox Guest Additions but it's either empty or not
present. You mentioned that you are trying to install the newest
Virtualbox Guest Additions. Was a previous version already installed
before? If yes, could you try removing it and installing again?

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

Title:
  package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to
  install/upgrade: installed linux-image-5.11.0-25-generic package post-
  installation script subprocess returned error exit status 1

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  This issue appeared while VirtualBox kernel modules were being
  compiled for installation of the newest Guest Additions

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 13:57:45 2021
  ErrorMessage: installed linux-image-5.11.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-02-13 (177 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-signed-hwe-5.11
  Title: package linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 failed to 
install/upgrade: installed linux-image-5.11.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939333/+subscriptions


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

[Kernel-packages] [Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL

[Kleber Sacilotto de Souza]

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

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

** Also affects: linux-meta-hwe-5.11 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

** Also affects: linux-meta-hwe-5.11 (Ubuntu Impish)
   Importance: Undecided
   Status: Confirmed

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

** Also affects: linux-meta-hwe-5.11 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-hwe-5.11 (Ubuntu Focal)
   Status: New => Confirmed

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

** Changed in: linux-meta-hwe-5.11 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-meta-hwe-5.11 (Ubuntu Impish)
   Status: Confirmed => Invalid

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

Title:
  REGRESSION: shiftfs lets sendfile fail with EINVAL

Status in linux package in Ubuntu:
  New
Status in linux-meta-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-meta-hwe-5.11 source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux-meta-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  New
Status in linux-meta-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
  tools we're using in bionic containers as part of Anbox Cloud start to
  fail when executed on the 5.11 kernel.

  A simple reproducer looks like this:

  1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 
5.11.0-25-generic #27~20.04.1-Ubuntu)
  2. Install LXD and enable shiftfs
  $ snap install lxd
  $ snap set lxd shiftfs.enable true
  $ snap restart --reload lxd
  3. Launch bionic container and run `lxc-info`
  $ lxc launch ubuntu:b c0
  $ lxc shell c0
  c0$ apt update
  c0$ apt install -y lxc-utils
  root@c1:~# apt show lxc-utils | grep Version
  Version: 3.0.3-0ubuntu1~18.04.1
  c0$ mkdir -p containers/test
  c0$ touch containers/test/config
  c0$ lxc-info -P containers -n test
  Failed to load config for test
  Failure to retrieve information on containers:test

  Looking into the failing `lxc-info` call with strace reveals:

  ...
  memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4
  openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5
  sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument
  ...

  LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't
  affected. Any other tool using sendfile however is affected and will
  fail. Bionic is affected as the 3.0.3 version of LXC it includes still
  uses sendfile.

  Disabling shiftfs makes things work again and can be considered as a
  workaround to a certain degree, but not be applicable in all cases.

  Further analysis with Christian (cbrauner) from the LXD team this
  morning showed that shiftfs is missing an implementation for the now
  required slice_read handler in the file_operations structure. So
  whenever shiftfs is being used, all calls to sendfile will fail
  because of the missing implementation. The generic handler for this
  got removed in the following upstream change:
  https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/

  Christian implemented a quick fix:
  https://paste.ubuntu.com/p/TPsjfCpnD5/

  As of today I don't know of any customer of Anbox Cloud who is
  affected by this as most of them run with one of our cloud kernels.
  However as soon as 5.11 rolls out to the cloud kernels, we will hit
  production systems and cause them to fail.

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


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

[Kernel-packages] [Bug 1939178] Re: Bluetooth not working after an update

[Kleber Sacilotto de Souza]

Hello Yinka,

Could you please check if you have the linux-modules-extra-* package
installed? This can be done by typing the following command on the
terminal:

$ dpkg -l linux-modules-5.11.0-25-generic

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

Title:
  Bluetooth not working after an update

Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth not working after an update.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yinka  2369 F pulseaudio
   /dev/snd/controlC0:  yinka  2369 F pulseaudio
   /dev/snd/controlC2:  yinka  2369 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 22:29:07 2021
  InstallationDate: Installed on 2021-04-16 (112 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=a4150dca-83c9-4b4d-8376-b13fbd5c172f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2020
  dmi.bios.release: 1.49
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.49
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.89
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.49:bd02/24/2020:br1.49:efr21.89:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: K5T62UP#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1939164] Re: Samba fstab mount does not work

[Kleber Sacilotto de Souza]

Hello Florian,

Could you please check if you have the 'cifs' kernel module loaded? If
not, check if you have the package 'linux-modules-5.11.0-25-generic'
installed and if you can load the module with 'sudo modprobe cifs'.

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

Title:
  Samba fstab mount does not work

Status in linux package in Ubuntu:
  New

Bug description:
  I use "Linux Mint 20.2 x86_64", since the kernel update to version
  5.11.0-25, Samba share access no longer works, only when I start my
  system with kernel 5.8.0-63 does everything work again.

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


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

[Kernel-packages] [Bug 1938848] Re: My touchpad is not detected by the OS, I think it might be kernal problem but please see as I cant use my laptop's touchpad at all

[Kleber Sacilotto de Souza]

Hello Om Prakash,

Could you please try updating the packages in your system? I expect that
your installed kernel version would be upgraded to 5.11, more
specifically 5.11.0-25.27~20.04.1.

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

Title:
  My touchpad is not detected by the OS,I think it might be kernal
  problem but please see as I cant use my laptop's touchpad at all

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  I have recently installed ubuntu after my windows os got cleaned like
  its not there anymore.Everything works fine but My touchpad isn't
  working at all.I have used xinput in terminal but I cant find any
  touchpad driver

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  4 09:25:06 2021
  InstallationDate: Installed on 2021-08-01 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1938848/+subscriptions


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

[Kernel-packages] [Bug 1938893] Re: Network perpherals not detected

[Kleber Sacilotto de Souza]

Hello Capsia,

Could you please check if you have the corresponding linux-modules-
extra-* installed? For your kernel this would be linux-modules-
extra-5.11.0-25-generic.

The best way to make sure you will always get all modules installed when
updating the kernel version is to install the kernel packages via the
meta package linux-generic-hwe-20.04.

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

Title:
  Network perpherals not detected

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  After updating the kernel to the version 5.11.0.22 all network
  peripherals stopped working. It appears they are not detected on lshw
  or lsusb. I've tried with the ethernet port on the motherboard and an
  external wifi board and also using USB tethering from a phone. None
  was detected and network is not working. Then I've tried to go back to
  kernel version 5.8 which is still working correctly. If you need more
  info, feel free to ask me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  4 13:17:14 2021
  InstallationDate: Installed on 2021-06-11 (53 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1938893/+subscriptions


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

[Kernel-packages] [Bug 1938742] Re: 5.8.0-63 Breaks Wifi on RTL8822BE

[Kleber Sacilotto de Souza]

Hello ndst,

Groovy 20.10 has reached EOL, and so has the HWE kernel in Focal 20.04
based on the 5.8 kernel. Could you please update the HWE kernel to the
latest 5.11-based version (5.11.0-25.27~20.04.1) and check whether the
problem persists? The easiest way is to update the hwe meta package
(likely linux-generic-hwe-20.04).

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

Title:
  5.8.0-63 Breaks Wifi on RTL8822BE

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen,
  but wifi networks cannot be found. If the nvidia driver 470.57 is
  installed the wifi card is no longer found.

  lspci | grep -i realtek:
  07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter (rev ff)

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  2 22:37:25 2021
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username  2540 F pulseaudio
   /dev/snd/controlC1:  username  2540 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  MachineType: LENOVO 81LF
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 i915drmfb
   1 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=79951aeb-477e-4f92-a571-ce78702269da ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-63-generic N/A
   linux-backports-modules-5.8.0-63-generic  N/A
   linux-firmware1.187.15
  Tags:  wayland-session focal
  Uname: Linux 5.8.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN22WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y7000P-1060
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN22WW:bd11/30/2020:br1.22:efr1.22:svnLENOVO:pn81LF:pvrLenovoLegionY7000P-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P-1060:
  dmi.product.family: Legion Y7000P-1060
  dmi.product.name: 81LF
  dmi.product.sku: LENOVO_MT_81LF_BU_idea_FM_Legion Y7000P-1060
  dmi.product.version: Lenovo Legion Y7000P-1060
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1938742/+subscriptions


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

[Kernel-packages] [Bug 1930527] Re: [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung 16727 panel

[Kleber Sacilotto de Souza]

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

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

Title:
  [SRU][OEM-5.10/H] UBUNTU: SAUCE: Fix backlight control on Samsung
  16727 panel

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  In Progress

Bug description:
  SRU justification:

  [Impact]
  Backlight can't be controlled on 5.11- version of kernel.

  [Fix]
  The panel needs DPCD to get control of backlight.
  After 5.12 kernel introduced new Intel HDR backlight control, and it works 
well
  on this panel.
  Add quirk ID to enable DPCD on 5.11- kernel.

  [Test]
  Vendor Verified on hardware, with this quirk backlight can be changed on 5.10 
and 5.11 kernel.

  [Where problems could occur]
  The panel backlight may not be changed.

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


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

[Kernel-packages] [Bug 1933268] Re: net kselftest failures in the tls bidir test case

[Kleber Sacilotto de Souza]

Confirmed to be fixed with the current SRU cycle's hirsute/linux kernel:

Before (5.11.0-24.25):
# #  RUN   tls.12_chacha.bidir ...
# # tls.c:845:bidir:Expected ret (-1) == 0 (0)
# # bidir: Test terminated by assertion
# #  FAIL  tls.12_chacha.bidir
# not ok 123 tls.12_chacha.bidir

Latest kernel (5.11.0-26.28):
# #  RUN   tls.12_chacha.bidir ...
# #OK  tls.12_chacha.bidir
# ok 123 tls.12_chacha.bidir

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

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

Title:
  net kselftest failures in the tls bidir test case

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  The tls bidir test from the network kselftests fails with the ChaCha
  cipher:

   #  RUN   tls.12_chacha.bidir ...
   # tls.c:845:bidir:Expected ret (-1) == 0 (0)
   # bidir: Test terminated by assertion
   #  FAIL  tls.12_chacha.bidir

  This is a problem with the test. The test fixture setup configures tls
  in one direction on the test socket pair according to the cipher being
  tested. The test case configures tls in the other direction, however
  it always configures for GCM regardless of the cipher being tested.
  When the test cipher is ChaCha the setsockopt() calls fail as the
  cipher is required to be the same in both directions.

  [Test Plan]

  Run the tls test from the net kselftests and confirm that the bidir
  test now passes when the test cipher is ChaCha.

  [Where problems could occur]

  This is a fix for a test case and should have no user impact. A
  serious problem in the test case might cause passing test cases to
  fail or prevent subsequent test cases from running. Any such issues
  should be caught during testing in -proposed before releasing kernels
  to users.

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


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

[Kernel-packages] [Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19

[Kleber Sacilotto de Souza]

Found with hirsute/linux 5.11.0-26.28.

** Tags added: sru-20210719

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

Title:
  test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure
  with linux/5.11.0-18.19

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

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

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz


test_zz_cleanup_source_tree (__main__.ApparmorTestsuites)
Cleanup downloaded source ... ok

==
FAIL: test_utils_testsuite (__main__.ApparmorTestsuites)
Run utils (make check)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 1841, in test_utils_testsuite
self.assertEqual(expected, rc, result + report)
AssertionError: 0 != 2 : Got exit code 2, expected 0
ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1


==
FAIL: test_utils_testsuite3 (__main__.ApparmorTestsuites)
Run utils (make check with python3)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 1862, in test_utils_testsuite3
self.assertEqual(expected, rc, result + report)
AssertionError: 0 != 2 : Got exit code 2, expected 0
ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1


--
Ran 58 tests in 1448.768s

FAILED (failures=2)
  23:36:54 INFO |   END ERROR   ubuntu_qrt_apparmor.test-apparmor.py
ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1621035414localtime=May 
14 23:36:54

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


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

[Kernel-packages] [Bug 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Disco ARM64 / B-hwe P9

[Kleber Sacilotto de Souza]

Re-openning bug report.

Spotted with hirsute/linux 5.11.0-26.28, flavor generic-64k, on dazzle
arm64.

# [94] (instance)  ftrace - test for function traceon/off triggers
[FAIL]

** Changed in: ubuntu-kernel-tests
   Status: Invalid => New

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

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

** Tags added: 5.11 generic-64k hirsute sru-20210719

** Summary changed:

- function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on 
Disco ARM64 / B-hwe P9
+ function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on 
ARM64 / B-hwe P9

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

Title:
  function traceon/off triggers in ftace from ubuntu_kernel_selftests
  failed on ARM64 / B-hwe P9

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Disco:
  Invalid
Status in linux source package in Hirsute:
  New

Bug description:
  Test failed with the disco master-next branch, issue spotted on
  Thunder X ARM64 (passed with Moonshot ARM64):

  TAP version 13
  selftests: ftrace: ftracetest
  
  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] Change the ringbuffer size[PASS]
  [6] Snapshot and tracing setting  [PASS]
  [7] trace_pipe and trace_marker   [PASS]
  [8] Generic dynamic event - add/remove kprobe events  [PASS]
  [9] Generic dynamic event - add/remove synthetic events   [PASS]
  [10] Generic dynamic event - selective clear (compatibility)  [PASS]
  [11] Generic dynamic event - generic clear event  [PASS]
  [12] event tracing - enable/disable with event level files[PASS]
  [13] event tracing - restricts events based on pid[PASS]
  [14] event tracing - enable/disable with subsystem level files[PASS]
  [15] event tracing - enable/disable with top level files  [PASS]
  [16] Test trace_printk from module[PASS]
  [17] ftrace - function graph filters with stack tracer[PASS]
  [18] ftrace - function graph filters  [PASS]
  [19] ftrace - function glob filters   [PASS]
  [20] ftrace - function pid filters[PASS]
  [21] ftrace - stacktrace filter command   [PASS]
  [22] ftrace - function trace with cpumask [PASS]
  [23] ftrace - test for function event triggers[PASS]
  [24] ftrace - function trace on module[PASS]
  [25] ftrace - function profiling  [PASS]
  [26] ftrace - function profiler with function tracing [PASS]
  [27] ftrace - test reading of set_ftrace_filter   [PASS]
  [28] ftrace - Max stack tracer[PASS]
  [29] ftrace - test for function traceon/off triggers  [FAIL]
  [30] Test creation and deletion of trace instances while setting an event 
[PASS]
  [31] Test creation and deletion of trace instances[PASS]
  [32] Kprobe dynamic event - adding and removing   [PASS]
  [33] Kprobe dynamic event - busy event check  [PASS]
  [34] Kprobe dynamic event with arguments  [PASS]
  [35] Kprobe event with comm arguments [PASS]
  [36] Kprobe event string type argument[PASS]
  [37] Kprobe event symbol argument [PASS]
  [38] Kprobe event argument syntax [PASS]
  [39] Kprobes event arguments with types   [PASS]
  [40] Kprobe event auto/manual naming  [PASS]
  [41] Kprobe dynamic event with function tracer[PASS]
  [42] Kprobe dynamic event - probing module[PASS]
  [43] Kretprobe dynamic event with arguments   [PASS]
  [44] Kretprobe dynamic event with maxactive   [PASS]
  [45] Register/unregister many kprobe events   [PASS]
  [46] Kprobe events - probe points [PASS]
  [47] Kprobe dynamic event - adding and removing   [PASS]
  [48] test for the preemptirqsoff tracer   [UNSUPPORTED]
  [49] Test wakeup tracer   [PASS]
  [50] Test wakeup RT tracer[PASS]
  [51] event trigger - test extended error support  [PASS]
  [52] event trigger - test field variable support  [PASS]
  [53] event trigger - test inter-event combined histogram trigger  [PASS]
  [54] event trigger - test multiple actions on hist trigger[PASS]
  [55] event trigger - test inter-event histogram trigger onmatch action
[PASS]
  [56] event trigger - test inter-event histogram trigger onmatch-onmax action  
[PASS]
  [57] event trigger - test inter-event histogram trigger onmax action  [PASS]
  [58] event trigger - test synthetic event create remove   [PASS]
  [59] event trigger - test synthetic_events syntax parser  [PASS]
  [60] event trigger - test event enable/disable trigger[PASS]
  [61] event trigger - test trigger filter  [PASS]
  [62] event trigger - test histogram modifiers 

[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13'

[Kleber Sacilotto de Souza]

** Summary changed:

- tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
+ tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13'

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

Title:
  tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13'

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With bug 1868707 fixed, the tpci test can finish now, and it's reporting 
another issue here:
     test_pci  489  TFAIL  :  tpci.c:73: PCI bus 01 slot 01 : Test-case '13'

  Please find attachment for dmesg log and the full test log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 13 10:08 seq
   crw-rw 1 root audio 116, 33 May 13 10:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  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: Wed May 13 10:19:01 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47

[Kleber Sacilotto de Souza]

This fix has already been released with impish/linux 5.13.0-11.1.
Marking the task for the development kernel as fix released.

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

** No longer affects: linux-gcp (Ubuntu)

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

** No longer affects: linux (Ubuntu Hirsute)

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

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

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

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Khaled El Mously (kmously)

** Changed in: linux-gcp (Ubuntu Hirsute)
   Status: New => Fix Released

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

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

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

Title:
  Google Confidential Compute fails to boot with shim version 1.47

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-gcp source package in Hirsute:
  Fix Released

Bug description:
  # Overview

  Hirsute and Impish daily builds are currently not booting on Google
  Confidential Compute.  Confidential compute is Google's platform that
  enables the use of Secure Encrypted Virtualization extension via AMD
  EPYC CPUs. Booting an image with version 1.45 works, but once upgraded
  to 1.47, the VM no longer boots, and instead the kernel panics.

  Launching the image with secure boot, but without confidential compute
  works as expected.

  # Expected result

  The system is able to reboot after the upgrade.

  # Actual result

  Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/

  # Steps to reproduce

  Launch a VM in GCE with confidential compute enabled with a serial
  v20210511a or later and look at the serial log for the kernel panic.
  Example CLI command to launch a VM:

  $ gcloud beta compute instances create $USER-confidential-testing
  --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily-
  ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel
  --confidential-compute --maintenance-policy=TERMINATE

  The last known good working image is daily-
  ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim
  signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2

  # Logs & notes

  * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/
  * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/
  * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/
  * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/

  # Cause:

  shim changed the memory type for pages reserved for EFI runtime
  services, from EfiRuntimeServicesData to EfiBootServicesData.

  Memory reserved for EFI runtime/boot services must be remapped as
  encrypted in the kernel (during boot) if SEV (secure encrypted
  virtualization) is enabled. The original kernel implementation of
  ioremap only correctly mapped the region as encrypted for
  EfiRuntimeServicesData regions, so when shim changed the type to
  EfiBootServicesData the kernel bug was exposed

  Note that this affects all 5.11 kernels not just gcp. It is possible
  that gcp is the only cloud that uses sev currently (for "Confidential
  Computing").

  # Fix:

  Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as
  encrypted if SEV is active, as per:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b

  
  # Test

  Without the fix applied, confirmed that I was able to reproduce the issue 
described here (complete failure to boot, kernel panic)
  With fix, confirmed no issues booting

  # Regression potential

  The fix could potentially cause boot failures, if a memory region is
  marked encrypted when it shouldn't be. I assume in that case it would
  cause a panic similar to the one seen here for this bug:

  general protection fault, probably for non-canonical address
  0x314836c31124d346:  [#1] SMP NOPTI

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


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

[Kernel-packages] [Bug 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47

[Kleber Sacilotto de Souza]

This fix has already been released with hirsute/linux-gcp 5.11.0-1015.17
which is currently in hirsute-updates. For the generic hirsute/linux
kernel the fix will be applied for the next SRU cycle.

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

Title:
  Google Confidential Compute fails to boot with shim version 1.47

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  # Overview

  Hirsute and Impish daily builds are currently not booting on Google
  Confidential Compute.  Confidential compute is Google's platform that
  enables the use of Secure Encrypted Virtualization extension via AMD
  EPYC CPUs. Booting an image with version 1.45 works, but once upgraded
  to 1.47, the VM no longer boots, and instead the kernel panics.

  Launching the image with secure boot, but without confidential compute
  works as expected.

  # Expected result

  The system is able to reboot after the upgrade.

  # Actual result

  Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/

  # Steps to reproduce

  Launch a VM in GCE with confidential compute enabled with a serial
  v20210511a or later and look at the serial log for the kernel panic.
  Example CLI command to launch a VM:

  $ gcloud beta compute instances create $USER-confidential-testing
  --zone=us-west1-b --machine-type=n2d-standard-2 --image=daily-
  ubuntu-2104-hirsute-v20210511a --image-project=ubuntu-os-cloud-devel
  --confidential-compute --maintenance-policy=TERMINATE

  The last known good working image is daily-
  ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim
  signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2

  # Logs & notes

  * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/
  * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/
  * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/
  * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/

  # Cause:

  shim changed the memory type for pages reserved for EFI runtime
  services, from EfiRuntimeServicesData to EfiBootServicesData.

  Memory reserved for EFI runtime/boot services must be remapped as
  encrypted in the kernel (during boot) if SEV (secure encrypted
  virtualization) is enabled. The original kernel implementation of
  ioremap only correctly mapped the region as encrypted for
  EfiRuntimeServicesData regions, so when shim changed the type to
  EfiBootServicesData the kernel bug was exposed

  Note that this affects all 5.11 kernels not just gcp. It is possible
  that gcp is the only cloud that uses sev currently (for "Confidential
  Computing").

  # Fix:

  Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as
  encrypted if SEV is active, as per:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b

  
  # Test

  Without the fix applied, confirmed that I was able to reproduce the issue 
described here (complete failure to boot, kernel panic)
  With fix, confirmed no issues booting

  # Regression potential

  The fix could potentially cause boot failures, if a memory region is
  marked encrypted when it shouldn't be. I assume in that case it would
  cause a panic similar to the one seen here for this bug:

  general protection fault, probably for non-canonical address
  0x314836c31124d346:  [#1] SMP NOPTI

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


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

[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed

[Kleber Sacilotto de Souza]

** Tags added: sru-20210719

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

Title:
  memcg_stat from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

  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:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 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: 

[Kernel-packages] [Bug 1845919] Re: memcg_failcnt in mm from ubuntu_ltp failed on B 4.15

[Kleber Sacilotto de Souza]

The same issue seems to be happening with memcg_move_charge_at_immigrat
on hirsute/linux 5.11.


tag=memcg_max_usage_in_bytes stime=1626909193 dur=5 exit=exited stat=0 core

startup='Wed Jul 21 23:13:18 2021'
memcg_move_charge_at_immigrate_test 1 TINFO: timeout per run is 0h 5m 0s
[...]
memcg_move_charge_at_immigrate_test 3 TINFO: Test move file
memcg_move_charge_at_immigrate_test 3 TINFO: Running memcg_process --mmap-anon 
--shm --mmap-file -s 135168 
memcg_move_charge_at_immigrate_test 3 TINFO: Warming up pid: 762538
memcg_move_charge_at_immigrate_test 3 TINFO: Process is still here after warm 
up: 762538
memcg_move_charge_at_immigrate_test 3 TBROK: timed out on memory.usage_in_bytes
memcg_move_charge_at_immigrate_test 3 TINFO: AppArmor enabled, this may affect 
test results
memcg_move_charge_at_immigrate_test 3 TINFO: it can be disabled with 
TST_DISABLE_APPARMOR=1 (requires super/root)
memcg_move_charge_at_immigrate_test 3 TINFO: loaded AppArmor profiles: none

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

Title:
  memcg_failcnt in mm from ubuntu_ltp failed on B 4.15

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Issue found on node amaura, with Bionic 4.15 AMD64:
   tag=memcg_test_3 stime=1569410880 dur=0 exit=exited stat=0 core=no cu=9 cs=17
   startup='Wed Sep 25 11:28:01 2019'
   memcg_failcnt 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 8192
   memcg_failcnt 1 TBROK: timeouted on memory.usage_in_bytes
   tag=memcg_failcnt stime=1569410881 dur=10 exit=exited stat=2 core=no cu=9 
cs=2

  
  Probably a test case issue, it needs to be investigated

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


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

[Kernel-packages] [Bug 1939035] [NEW] memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

[Kleber Sacilotto de Souza]

Public bug reported:

memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge
times out when running with hirsute/linux 5.11.

startup='Mon Jul 19 15:17:41 2021'
memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s
memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no relationship
memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336
memcg_subgroup_charge 1 TINFO: Warming up pid: 443417
memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417
memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes
memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results
memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 
(requires super/root)
memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none
 
Summary:
passed   0
failed   0
broken   1
skipped  0
warnings 0
tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no 
cu=19 cs=12


This is not a regression as it already failed on previous releases.

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

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

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


** Tags: 5.11 hirsute sru-20210719

** Tags added: 5.11 hirsute sru-20210719

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

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

Title:
  memory.usage_in_bytes from
  ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Hirsute:
  New

Bug description:
  memory.usage_in_bytes from
  ubuntu_ltp.controllers.memcg_subgroup_charge times out when running
  with hirsute/linux 5.11.

  startup='Mon Jul 19 15:17:41 2021'
  memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s
  memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no 
relationship
  memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336
  memcg_subgroup_charge 1 TINFO: Warming up pid: 443417
  memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417
  memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes
  memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results
  memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 
(requires super/root)
  memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none
   
  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0
  tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no 
cu=19 cs=12

  
  This is not a regression as it already failed on previous releases.

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


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

[Kernel-packages] [Bug 1925261] Re: memory leak on AWS kernels when using docker

[Kleber Sacilotto de Souza]

Hi Paul,

Thank you for coming back to us. I will ask my colleagues that work with
the AWS kernels to look at this.

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

Title:
  memory leak on AWS kernels when using docker

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Focal:
  New

Bug description:
  Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu
  AMI was released which has the "5.3.0-1032-aws" kernel we have been
  hitting a 100% repro memory leak that causes our app that is running
  under docker to be OOM killed.

  The scenario is that we have an app running in a docker container and
  it occasionally catches a crash happening within itself and when that
  happens it creates another process which triggers a gdb dump of that
  parent app. Normally this works fine but under these specific kernels
  it causes the memory usage to grow and grow until it hits the maximum
  allowed memory for the container at which point the container is
  killed.

  I have tested using several of the latest available Ubuntu AMIs
  including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which
  has the "5.4.0-1045-aws" kernel and the bug still exists.

  I also tested a bunch of the mainline kernels and found the fix was
  introduced for this memory leak in the v5.9-rc4 kernel
  (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES).

  Do you all have any idea if or when that set of changes will be
  backported into a supported kernel for Ubuntu 18.04 or 20.04?

  Release we are running:
  root@:~# lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  Docker / containerd.io versions:
  - containerd.io: 1.4.4-1
  - docker-ce: 5:20.10.5~3-0~ubuntu-bionic

  Latest supported kernel I tried which still sees the memory leak:
  root@hostname:~# apt-cache policy linux-aws
  linux-aws:
    Installed: 5.4.0.1045.27
    Candidate: 5.4.0.1045.27
    Version table:
   *** 5.4.0.1045.27 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.15.0.1007.7 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages

  Thanks,
  Paul

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


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

[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

[Kleber Sacilotto de Souza]

Confirmed with hirsute/linux 5.11.0-26.28 that icmp_redirect.sh results
are as expected:

# selftests: net: icmp_redirect.sh
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
#
# Tests passed:  36
# Tests failed:   0
# Tests xfailed:   4
ok 38 selftests: net: icmp_redirect.sh


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

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

Title:
  icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
  F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.13 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The IPv6: mtu exception plus redirect test in icmp_redirect.sh test
  from kselftest/net is expected to fail due to a known bug in the
  IPv6 logic.

  When trying to run this test you will see this sub test fail with:
  TEST: IPv6: mtu exception plus redirect [FAIL]

  and thus causing non-zero return value for this script.

  [Fix]
  * 0a36a75c681880 selftests: icmp_redirect: support expected failures

  This fix can be cherry-picked into all affected series. And it has
  already landed on Unstable, test passed with Impish 5.13.

  Although we have this script in Focal kernel as well, but it's not
  being executed at all. This is another issue that will be dealt in
  a different bug report.

  [Test]
  Run the patched icmp_redirect.sh test manually in
  tools/testing/selftests/net, this sub-test will be marked as XFAIL
  and the return value of this script will be 0:
  $ sudo ./icmp_redirect.sh
  
  #
  Routing with nexthop objects and VRF
  #
  TEST: IPv6: mtu exception plus redirect [XFAIL]

  Tests passed: 36
  Tests failed: 0
  Tests xfailed: 4
  $ echo $?
  0

  [Where problems could occur]
  Change limited to testing tool, not affecting actual kernel
  functionality. The only possible issue that I can think of is that
  as this script is no longer complaining about this failure, people
  might forgot there is such an issue exist in ipv6.

  [Original Bug Report]
  Issue found on Focal 5.6.0-1011.11-oem

  
ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
  sudo ./icmp_redirect.sh

  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu   

[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

[Kleber Sacilotto de Souza]

Confirmed with focal/linux 5.4.0-81.91 that icmp_redirect.sh results are
as expected:

# selftests: net: icmp_redirect.sh
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
#
# Tests passed:  36
# Tests failed:   0
# Tests xfailed:   4
# ok 35 selftests: net: icmp_redirect.sh

** 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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1880645

Title:
  icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
  F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.13 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The IPv6: mtu exception plus redirect test in icmp_redirect.sh test
  from kselftest/net is expected to fail due to a known bug in the
  IPv6 logic.

  When trying to run this test you will see this sub test fail with:
  TEST: IPv6: mtu exception plus redirect [FAIL]

  and thus causing non-zero return value for this script.

  [Fix]
  * 0a36a75c681880 selftests: icmp_redirect: support expected failures

  This fix can be cherry-picked into all affected series. And it has
  already landed on Unstable, test passed with Impish 5.13.

  Although we have this script in Focal kernel as well, but it's not
  being executed at all. This is another issue that will be dealt in
  a different bug report.

  [Test]
  Run the patched icmp_redirect.sh test manually in
  tools/testing/selftests/net, this sub-test will be marked as XFAIL
  and the return value of this script will be 0:
  $ sudo ./icmp_redirect.sh
  
  #
  Routing with nexthop objects and VRF
  #
  TEST: IPv6: mtu exception plus redirect [XFAIL]

  Tests passed: 36
  Tests failed: 0
  Tests xfailed: 4
  $ echo $?
  0

  [Where problems could occur]
  Change limited to testing tool, not affecting actual kernel
  functionality. The only possible issue that I can think of is that
  as this script is no longer complaining about this failure, people
  might forgot there is such an issue exist in ipv6.

  [Original Bug Report]
  Issue found on Focal 5.6.0-1011.11-oem

  
ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
  sudo ./icmp_redirect.sh

  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu 

[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all

[Kleber Sacilotto de Souza]

Confirmed with focal/linux 5.4.0-81.91 that the following testcases from
kernel selftests net are now being run:

fib_nexthop_multiprefix.sh
fib_nexthops.sh
icmp_redirect.sh
ip6_gre_headroom.sh
route_localnet.sh

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

Title:
  Some test in kselftest/net on focal source tree were not tested at all

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Found this issue while debugging devlink_port_split.py test issue in
  bug 1928889.

  There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and
  etc are not in the Makefile of the net directory, thus they are not
  tested at all.

  [Fix]
  * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile

  Backport needed for Focal as we only have these tests unadded:
  $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done
  fib_nexthop_multiprefix.sh
  fib_nexthops.sh
  icmp_redirect.sh
  ip6_gre_headroom.sh
  route_localnet.sh

  [Test]
  Run the "net" test suite in the kselftest directory from a patched
  source tree. These tests will be executed.

  [Where problems could occur]
  This change will bring in more tests for our SRU, we might see new
  failures because of these test in the future.

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


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

[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message

[Kleber Sacilotto de Souza]

I can confirm the issue is now fixed on the 5.4 kernels.

Results with bionic/linux-oracle-5.4 5.4.0-1053.57~18.04.1:

# selftests: net: pmtu.sh
# TEST: ipv4: PMTU exceptions [ OK ]
# TEST: ipv6: PMTU exceptions [ OK ]
#   vxlan4 not supported
# TEST: IPv4 over vxlan4: PMTU exceptions [SKIP]
#   vxlan4 not supported
# TEST: IPv6 over vxlan4: PMTU exceptions [SKIP]
# TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
# TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
#   geneve4 not supported
# TEST: IPv4 over geneve4: PMTU exceptions[SKIP]
#   geneve4 not supported
# TEST: IPv6 over geneve4: PMTU exceptions[SKIP]
# TEST: IPv4 over geneve6: PMTU exceptions[ OK ]
# TEST: IPv6 over geneve6: PMTU exceptions[ OK ]
# TEST: IPv4 over fou4: PMTU exceptions   [ OK ]
# TEST: IPv6 over fou4: PMTU exceptions   [ OK ]
# TEST: IPv4 over fou6: PMTU exceptions   [ OK ]
# TEST: IPv6 over fou6: PMTU exceptions   [ OK ]
# TEST: IPv4 over gue4: PMTU exceptions   [ OK ]
# TEST: IPv6 over gue4: PMTU exceptions   [ OK ]
# TEST: IPv4 over gue6: PMTU exceptions   [ OK ]
# TEST: IPv6 over gue6: PMTU exceptions   [ OK ]
# TEST: vti6: PMTU exceptions [ OK ]
# TEST: vti4: PMTU exceptions [ OK ]
# TEST: vti4: default MTU assignment  [ OK ]
# TEST: vti6: default MTU assignment  [ OK ]
# TEST: vti4: MTU setting on link creation[ OK ]
# TEST: vti6: MTU setting on link creation[ OK ]
# TEST: vti6: MTU changes on link changes [ OK ]
#   vxlan4 not supported
# TEST: ipv4: cleanup of cached exceptions[SKIP]
# TEST: ipv6: cleanup of cached exceptions[ OK ]
# TEST: ipv4: list and flush cached exceptions[ OK ]
# TEST: ipv6: list and flush cached exceptions[ OK ]
# TEST: ipv4: PMTU exception w/route replace  [ OK ]
# TEST: ipv6: PMTU exception w/route replace  [ OK ]
ok 16 selftests: net: pmtu.sh


** 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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887661

Title:
  pmtu.sh from net in ubuntu_kernel_selftests failed with no error
  message

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 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:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
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.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.6 source package in Impish:
  Invalid

Bug description:
  [Impact]
  The pmtu.sh test in net from ubuntu_kernel_selftests will be marked
  as failed even there is no obvious failure message from the test:
  $ sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
vxlan4 not supported
  TEST: IPv4 over vxlan4: PMTU exceptions [SKIP]
vxlan4 not supported
  TEST: IPv6 over vxlan4: PMTU exceptions [SKIP]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
geneve4 not supported
  TEST: IPv4 over geneve4: PMTU exceptions [SKIP]
geneve4 not supported
  TEST: IPv6 over geneve4: PMTU exceptions [SKIP]
  TEST: IPv4 over geneve6: PMTU exceptions [ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions [ OK ]
  TEST: IPv4 over fou4: PMTU exceptions [ OK ]
  TEST: IPv6 over fou4: PMTU exceptions [ OK ]
  TEST: IPv4 over fou6: PMTU exceptions [ OK ]
  TEST: IPv6 over fou6: PMTU exceptions [ OK ]
  TEST: IPv4 over gue4: PMTU exceptions [ OK ]
  TEST: IPv6 over gue4: PMTU exceptions [ OK ]
  

[Kernel-packages] [Bug 1938626] Re: PPS API broken

[Kleber Sacilotto de Souza]

Hello Jim,

Did it work before with your system and got broken after a kernel
update? If yes, would you be able to identify the kernel version which
was working before? If you didn't run this use case before, would you be
able to boot with an older kernel version and check whether it works?

Thanks.

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

Title:
  PPS API broken

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

Bug description:
  The kernel PPS API appears to be broken. I have a serial GPS with PPS
  attached to /dev/ttyS4. If I use gpsd to create /dev/pps0, gpsd fails
  to see PPS data. If I disable gpsd and create /dev/pps0 with ldattach,
  any app or tool run against ttyS4 works fine and does see the CTS
  transitions every second, i.e. gpsmon and ppscheck. Anything run
  against pps0 fails, i.e. ppstest, ppswatch. ntpd gets data from ttyS4
  but not pps0.

  There are some issues with stock apparmor with gpsd and ntpd, but I
  have solved those.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-80-generic 5.4.0-80.90
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jimp   6811 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sat Jul 31 16:41:32 2021
  HibernationDevice: RESUME=UUID=90289c8f-5a00-46c4-8f1f-79dd26128f39
  InstallationDate: Installed on 2016-08-05 (1820 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=389dcb0d-84f2-4340-ad6c-e4f1dbe55b67 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-80-generic N/A
   linux-backports-modules-5.4.0-80-generic  N/A
   linux-firmware1.187.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-09 (264 days ago)
  dmi.bios.date: 11/26/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TYG4110H.86A.0036.2009.1126.2047
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG41TY
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE47335-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTYG4110H.86A.0036.2009.1126.2047:bd11/26/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41TY:rvrAAE47335-302:cvn:ct3:cvr:

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


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

[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

[Kleber Sacilotto de Souza]

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

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

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

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

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

Bug description:
  This issue was extracted from the comment in bug 1812638, since that
  bug will be specific for i386

  This reuseport_bpf_numa in net will fail on PowerPC with:

  The output on B-5.3 P8 is:
   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # send node 1, receive socket 7
   # ./reuseport_bpf_numa: node id/receive socket mismatch
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

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


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

[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

[Kleber Sacilotto de Souza]

** Summary changed:

- vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure 
with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
+ vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test 
failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

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

Title:
  vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT
  test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too
  big)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Hirsute:
  New
Status in linux-oem-5.10 source package in Hirsute:
  New

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

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  
  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  
  00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh
  00:09:30 DEBUG| [stdout] # 
  00:09:30 DEBUG| [stdout] # 
###
  00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup 
ping
  00:09:30 DEBUG| [stdout] # 
###
  00:09:30 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded  
 [ OK ]
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup 
traceroute
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error 
route lookup ping
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # 
  00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed   
 [ OK ]
  00:09:34 DEBUG| [stdout] # 
  00:09:34 DEBUG| [stdout] # 
###
  00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup 
ping
  00:09:34 DEBUG| [stdout] # 
###
  00:09:34 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded  
 [ OK ]
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup 
traceroute
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup 
ping
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # 
  00:09:40 DEBUG| [stdout] # TEST: Basic IPv6 connectivity  
 [FAIL]
  00:09:40 DEBUG| [stdout] # TEST: Ping received ICMP Hop limit 
 [ OK ]
  00:09:40 DEBUG| [stdout] # 
  00:09:40 DEBUG| 

[Kernel-packages] [Bug 1938537] Re: Potential reverts of 4.19.y stable changes in 18.04

[Kleber Sacilotto de Souza]

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

Title:
  Potential reverts of 4.19.y stable changes in 18.04

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

Bug description:
  == SRU Justification ==

  Impact: While reviewing patches done as part of stable work there were
  two changes which came from linux-4.19.y and seemed not quite right
  for the 4.15 kernel version we have in 18.04/Bionic:

  2e1eb7b6e1e0 locking/mutex: clear MUTEX_FLAGS if wait_list is empty
  due to signal

  This change is only in 4.19y and not in 4.14.y despite it is implied
  that the breaking commit was already in 3.13. It also seems to pair up
  with a mode of mutex which only got added to 4.19. Although there were
  no reports yet, which could prove this wrong, it feels like we rather
  should not take this change without a case where the current code is
  reported to be wrong.

  6c0065eb69de drm/amd/amdgpu: fix refcount leak

  The driver in 4.15 does take refcounts the same way as 4.19 does. We
  are missing 37ac3dc00da0 ("drm/amdgpu: Use device specific BO size &
  stride check.") which changed that. So we really should revert this
  one.

  Testing: These are proactive reverts, so there is no real test that
  could be done. However this just moves back to a state which we had
  before. And for that state we had no bug reports.

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


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

[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

I verified lttng-modules 2.12.5-1ubuntu2~20.04.1 build, install and
basic functionality in a Focal VM running both generic 5.4 and hwe-5.11
kernels.

autopkgtests with both kernels also completed successfully:

* hwe-5.11
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210727_163927_ce8c0@/log.gz
  - arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210727_163709_bdf0f@/log.gz
  - ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210727_163437_883e8@/log.gz
  - s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210727_163019_9d43f@/log.gz

* generic (5.4)
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210727_122206_6ae80@/log.gz
  - arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210727_121907_6ae80@/log.gz
  - ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210727_121636_6ae80@/log.gz
  - s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210727_121307_6ae80@/log.gz


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

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

** Changed in: linux-hwe-5.11 (Ubuntu Focal)
   Status: New => Invalid

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

Title:
  lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  New
Status in linux-hwe-5.11 source package in Focal:
  Invalid
Status in lttng-modules source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  lttng-modules-dkms is reporting many build errors with linux-hwe-5.11,
  because of many kernel ABI changes.

  [Fix]

  Backporting the individual patches to fix all the build errors would
  be a lot of work and the risk to introduce regressions would be pretty
  high, therefore it seems safer to update to the version that is also
  used in impish, that works with 5.11 and it's backward compatible (so
  it works also with 5.4).

  [Test]

  ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest-
  client-tests)

  [Where problems could occur]

  This is a major version update, so it does not contain trivial changes
  as backporting individual patches/fixes, so there's a risk to see
  regressions with lttng (however potential regressions are *only*
  limited to lttng).

  However, this way is definitely safer than backporting all the
  individual changes to fix the all the kernel ABI changes introduced in
  5.11.

  [Original bug report]

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz

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


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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Kleber Sacilotto de Souza]

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the system
  can't detect them, and couldn't output sound through headphone and
  record sound through Mic.

  [Fix]
  Backport a upstream patch, this will set the Mic to auto-detection
  mode and set the headphone to left location.

  
  [Test]
  Plug a headset to the headset audio jack, both headphone and mic
  could be detected. And output the sound to headphone, could hear
  the sound, record the sound through Mic, the sound could be recorded.

  
  [Where problems could occur]
  The patch is specific to Acer Aspire 5 machine, if it could introduce
  regression, it will make the audio like internal mic and internal spk
  stop working. But this possibility is very low.


  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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


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

[Kernel-packages] [Bug 1937068] Re: "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot on bionic/linux s390x

[Kleber Sacilotto de Souza]

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

Marking as duplicate as bug 1937276, which has more info about the root
cause.

** This bug has been marked a duplicate of bug 1937276
   log_check test in ubuntu_boot will erroneously get error on manually 
provisioned systems

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

Title:
  "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot
  on bionic/linux s390x

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

Bug description:
  [Impact]

  When booting bionic/linux 4.15.0-152.159 on a s390x machine there's a
  lot of the following error message on the kernel log:

  BUG: non-zero pgtables_bytes on freeing mm: 16384

  This error doesn't seem to happen on every boot.

  I could trace this happening as far back as 4.15.0-143.147, but this
  could be older as I don't have test results for older releases.

  This is similar to bug 1840046, which was supposedly fixed by an
  upstream stable patch around Sep/2019.

  [Test case]

  Boot bionic/linux on a s390x system.

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


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

[Kernel-packages] [Bug 1937220] [NEW] ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el Power9

[Kleber Sacilotto de Souza]

Public bug reported:

[Impact]

memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with
Power9) with focal/linux 5.4.0-81.91.

memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s 
memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed 
memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no relationship
memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 4325376
memcg_subgroup_charge 1 TINFO: Warming up pid: 530613
memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613
memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected 
memcg_subgroup_charge 1 TPASS: rss is 0 as expected 
memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376
memcg_subgroup_charge 2 TINFO: Warming up pid: 530633
memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633
memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected 
memcg_subgroup_charge 2 TPASS: rss is 0 as expected 
memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376
memcg_subgroup_charge 3 TINFO: Warming up pid: 530653
memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653
memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected 
memcg_subgroup_charge 3 TPASS: rss is 0 as expected 
memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results
memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 
(requires super/root)
memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none

Summary:
passed   3
failed   3
broken   0
skipped  0
warnings 0

There has been some major changed on the testcase, so it's not clear if
this is a test case issue or a kernel regression.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
 Status: Confirmed


** Tags: 5.11 5.4 focal ppc64el ubuntu-ltp

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

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

Title:
  ubuntu_ltp.memcg_subgroup_charge fails on focal/linux on ppc64el
  Power9

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

Bug description:
  [Impact]

  memcg_subgroup_charge from ubuntu_ltp is failing on ppc64el (only with
  Power9) with focal/linux 5.4.0-81.91.

  memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s 
  memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed 
  memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no 
relationship
  memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 4325376
  memcg_subgroup_charge 1 TINFO: Warming up pid: 530613
  memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 530613
  memcg_subgroup_charge 1 TFAIL: rss is 2949120, 4325376 expected 
  memcg_subgroup_charge 1 TPASS: rss is 0 as expected 
  memcg_subgroup_charge 2 TINFO: Running memcg_process --mmap-anon -s 4325376
  memcg_subgroup_charge 2 TINFO: Warming up pid: 530633
  memcg_subgroup_charge 2 TINFO: Process is still here after warm up: 530633
  memcg_subgroup_charge 2 TFAIL: rss is 3997696, 4325376 expected 
  memcg_subgroup_charge 2 TPASS: rss is 0 as expected 
  memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 4325376
  memcg_subgroup_charge 3 TINFO: Warming up pid: 530653
  memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 530653
  memcg_subgroup_charge 3 TFAIL: rss is 2883584, 4325376 expected 
  memcg_subgroup_charge 3 TPASS: rss is 0 as expected 
  memcg_subgroup_charge 4 TINFO: AppArmor enabled, this may affect test results
  memcg_subgroup_charge 4 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 
(requires super/root)
  memcg_subgroup_charge 4 TINFO: loaded AppArmor profiles: none

  Summary:
  passed   3
  failed   3
  broken   0
  skipped  0
  warnings 0

  There has been some major changed on the testcase, so it's not clear
  if this is a test case issue or a kernel regression.

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


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

[Kernel-packages] [Bug 1937068] [NEW] "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot on bionic/linux s390x

[Kleber Sacilotto de Souza]

Public bug reported:

[Impact]

When booting bionic/linux 4.15.0-152.159 on a s390x machine there's a
lot of the following error message on the kernel log:

BUG: non-zero pgtables_bytes on freeing mm: 16384

This error doesn't seem to happen on every boot.

I could trace this happening as far back as 4.15.0-143.147, but this
could be older as I don't have test results for older releases.

This is similar to bug 1840046, which was supposedly fixed by an
upstream stable patch around Sep/2019.

[Test case]

Boot bionic/linux on a s390x system.

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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Confirmed


** Tags: 4.15 bionic s390x sru-20210719 ubuntu-boot

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

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

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

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

** Tags added: 4.15 bionic s390x sru-20210719

** Tags added: ubuntu-boot

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

Title:
  "BUG: non-zero pgtables_bytes on freeing mm: 16384" errors during boot
  on bionic/linux s390x

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

Bug description:
  [Impact]

  When booting bionic/linux 4.15.0-152.159 on a s390x machine there's a
  lot of the following error message on the kernel log:

  BUG: non-zero pgtables_bytes on freeing mm: 16384

  This error doesn't seem to happen on every boot.

  I could trace this happening as far back as 4.15.0-143.147, but this
  could be older as I don't have test results for older releases.

  This is similar to bug 1840046, which was supposedly fixed by an
  upstream stable patch around Sep/2019.

  [Test case]

  Boot bionic/linux on a s390x system.

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


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

[Kernel-packages] [Bug 1932173] Re: xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

Confirmed that xtables-addons (3.9-1ubuntu0.2~20.04.3) can be built and
loaded in a Focal amd64 VM running both -generic 5.4 and -hwe-5.11
kernels.

Autopkgtests also completed successfully with hwe-5.11:

amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons/20210720_101545_595b0@/log.gz
arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/x/xtables-addons/20210720_101859_595b0@/log.gz
armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/x/xtables-addons/20210720_101957_00961@/log.gz
ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/x/xtables-addons/20210720_101926_595b0@/log.gz
s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/x/xtables-addons/20210720_101745_595b0@/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 linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932173

Title:
  xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in xtables-addons package in Ubuntu:
  New
Status in linux-hwe-5.11 source package in Focal:
  New
Status in xtables-addons source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running
  xtables-addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons/20210611_210642_1c193@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/x/xtables-addons/20210612_124839_710ee@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/x/xtables-addons/20210611_211032_cbce4@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/x/xtables-addons/20210611_210646_8bf21@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/x/xtables-addons/20210611_210425_4d74a@/log.gz

  [Test Plan]

  sudo apt-get install xtables-addons-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11.

  [Other]

  NB! dkms ftbfs fixes must be built in security, such that after SRU
  process in -proposed & -updates it can be copied into -security pocket
  too.

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


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

[Kernel-packages] [Bug 1932169] Re: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

Confirmed that rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3)
can be built and loaded on a focal amd64 VM with both -generic 5.4 and
-hwe-5.11 kernels.

Autopkgtests also completed successfully with hwe-5.11:

- amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210720_102918_140c6@/log.gz
- arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210720_102947_1d4c6@/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 linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932169

Title:
  rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure
  with linux-hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Invalid
Status in rtl8812au source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running
  rtl8812au tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz

  [Test Plan]

  sudo apt-get install rtl8812au-dkms

  [Where problems could occur]

  There could be run time regressions in the functionality of the driver
  due to the compatibility changes required for successful compilation
  against linux-hwe-5.11

  [Other Info]

  NB! dkms ftbfs fixes must be built in security, such that after SRU
  process in -proposed & -updates it can be copied into -security pocket
  too.

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


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

[Kernel-packages] [Bug 1932169] Re: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

** Description changed:

- 
- [Impact] 
+ [Impact]
  
  This is a scripted bug report about ADT failures while running rtl8812au
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz
  
  [Test Plan]
  
  sudo apt-get install rtl8812au-dkms
  
  [Where problems could occur]
  
  There could be run time regressions in the functionality of the driver
  due to the compatibility changes required for successful compilation
  against linux-hwe-5.11
  
  [Other Info]
+ 
+ NB! dkms ftbfs fixes must be built in security, such that after SRU
+ process in -proposed & -updates it can be copied into -security pocket
+ too.

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

Title:
  rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure
  with linux-hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Invalid
Status in rtl8812au source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running
  rtl8812au tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz

  [Test Plan]

  sudo apt-get install rtl8812au-dkms

  [Where problems could occur]

  There could be run time regressions in the functionality of the driver
  due to the compatibility changes required for successful compilation
  against linux-hwe-5.11

  [Other Info]

  NB! dkms ftbfs fixes must be built in security, such that after SRU
  process in -proposed & -updates it can be copied into -security pocket
  too.

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


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

[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

Confirmed that bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.3) in focal-
proposed can be built and loaded with both -generic 5.4 and hwe-5,11
kernels.

Autopkgtests also completed successfully:

* focal/linux:
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210720_092544_316be@/log.gz

* focal/linux-hwe-5.11:
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210720_095111_c5dbb@/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 bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1932159

Title:
  bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in bcmwl source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running bcmwl
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz

  [Test Plan]

  sudo apt-get install bcmwl-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11

  
  [Other Info]

  Please migrate this package update to -security as well in order not
  to break users when the default hwe kernel in Focal upgrades to 5.11.

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


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

[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

** Description changed:

  [Impact]
  
  This is a scripted bug report about ADT failures while running bcmwl
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz
  
  [Test Plan]
  
  sudo apt-get install bcmwl-dkms
  
  [Where problems could occur]
  
  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11
  
+ 
  [Other Info]
+ 
+ Please migrate this package update to -security as well in order not to
+ break users when the default hwe kernel in Focal upgrades to 5.11.

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

Title:
  bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in bcmwl source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running bcmwl
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz

  [Test Plan]

  sudo apt-get install bcmwl-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11

  
  [Other Info]

  Please migrate this package update to -security as well in order not
  to break users when the default hwe kernel in Focal upgrades to 5.11.

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


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

[Kernel-packages] [Bug 1932160] Re: broadcom-sta/6.30.223.271-12 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

autopkgtests with linux-hwe-5.11 also completed successfully:

amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/amd64/b/broadcom-sta/20210720_094014_cb2c7@/log.gz

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

** Description changed:

  [Impact]
  
  This is a scripted bug report about ADT failures while running broadcom-
  sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz
  
  [Test Plan]
  
  sudo apt-get install broadcom-sta-dkms
  
  [Where problems could occur]
  
  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11
  
  [Other Info]
+ 
+ Please migrate this package update to -security as well in order not to
+ break users when the default hwe kernel in Focal upgrades to 5.11.

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

Title:
  broadcom-sta/6.30.223.271-12 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running
  broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz

  [Test Plan]

  sudo apt-get install broadcom-sta-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11

  [Other Info]

  Please migrate this package update to -security as well in order not
  to break users when the default hwe kernel in Focal upgrades to 5.11.

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


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

[Kernel-packages] [Bug 1932160] Re: broadcom-sta/6.30.223.271-12 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

I was able to build and load broadcom-sta (6.30.223.271-12ubuntu0.1) in
a focal VM with both generic 5.4 and hwe-5.11 kernels.

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

Title:
  broadcom-sta/6.30.223.271-12 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running
  broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz

  [Test Plan]

  sudo apt-get install broadcom-sta-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11

  [Other Info]

  Please migrate this package update to -security as well in order not
  to break users when the default hwe kernel in Focal upgrades to 5.11.

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


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

[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

Yes, this needs to go to -security as well. The reason is that users
tracking only -security will need to get this update when the default
hwe kernel in focal upgrades to 5.11.

What's the standard way of documenting this on the SRU template?

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

Title:
  dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in dahdi-linux package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in dahdi-linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  New

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running dahdi-
  linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz

  [Test Plan]

  sudo apt-get install dahdi-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11.

  [Other Info]

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


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

[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

Yes, please promote this dkms update to -security and -updates. Thanks.

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

Title:
  lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in lime-forensics source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running lime-
  forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz

  [Test Plan]

  sudo apt-get install lime-forensics-dkms

  [Where problems could occur]

  There could be run time regressions due to the compatibility changes
  required for linux-hwe-5.11

  [Other Info]

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


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

[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

autopkgtests completed successfully.

* focal/linux
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210719_135442_87652@/log.gz
  - arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210719_135457_6e36a@/log.gz
  - armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/l/lime-forensics/20210719_135407_87652@/log.gz
  - ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210719_135241_6e36a@/log.gz
  - s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210719_135031_6e36a@/log.gz

* focal/linux-hwe-5.11
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210719_135154_47661@/log.gz
  - arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210719_135211_df9d6@/log.gz
  - armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/l/lime-forensics/20210719_135326_d1cb7@/log.gz
  - ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210719_135204_d1cb7@/log.gz
  - s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210719_135005_d1cb7@/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 linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932164

Title:
  lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in lime-forensics source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running lime-
  forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz

  [Test Plan]

  sudo apt-get install lime-forensics-dkms

  [Where problems could occur]

  There could be run time regressions due to the compatibility changes
  required for linux-hwe-5.11

  [Other Info]

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


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

[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

autopkgtest completed successfully with dahdi-linux
1:2.11.1~dfsg-1ubuntu6.3.

* focal/linux
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210719_133611_b6779@/log.gz

* focal/linux-hwe-5.11
  - amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210719_133526_b778d@/log.gz

** Tags added: verification-done-focal

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

Title:
  dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in dahdi-linux package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in dahdi-linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  New

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running dahdi-
  linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz

  [Test Plan]

  sudo apt-get install dahdi-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11.

  [Other Info]

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


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

[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

lime-forensics 1.9-1ubuntu0.3 can be built and loaded on focal with both
5.4 and 5.11 kernels. Waiting for autopkgtests to complete to confirm
the verification.

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

Title:
  lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in lime-forensics source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  Invalid

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running lime-
  forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal.
  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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz

  [Test Plan]

  sudo apt-get install lime-forensics-dkms

  [Where problems could occur]

  There could be run time regressions due to the compatibility changes
  required for linux-hwe-5.11

  [Other Info]

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


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

[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Kleber Sacilotto de Souza]

dahdi-linux 1:2.11.1~dfsg-1ubuntu6.3 can be built and loaded on focal
with both 5.4 and 5.11 kernels. Waiting for autopkgtests to complete to
confirm the verification.

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

Title:
  dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in dahdi-linux package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in dahdi-linux source package in Focal:
  Fix Committed
Status in linux-hwe-5.11 source package in Focal:
  New

Bug description:
  [Impact]

  This is a scripted bug report about ADT failures while running dahdi-
  linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. 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://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz

  [Test Plan]

  sudo apt-get install dahdi-dkms

  [Where problems could occur]

  Run time regressions could occur due to compatibility changes required
  for linux-hwe-5.11.

  [Other Info]

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


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

[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000

[Kleber Sacilotto de Souza]

Hello Lars,

Thank you for reporting the issue.

We have a 20.04 kernel update in focal-proposed (version 5.4.0-79.88)
which has the following patch applied which might fix this problem:

NFSv4: Fix a NULL pointer dereference in
pnfs_mark_matching_lsegs_return()

Could you please try running this kernel version and check whether the
bug is really fixed?

Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed.

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

Title:
  BUG: kernel NULL pointer dereference, address: 

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Kernelguys,

  after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get
  a kernelpanic when putting load onto my NFSv4.1 mount.


  
  About the System:

  I run a Galera Cluster on a VMWare VM with data stored on a NetApp
  system with NFSv4.1:

  # grep nfs4 /proc/mounts
  server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 
rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip
 0 0
  nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 
rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip
 0 0
  nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 
rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip
 0 0

  The panic I get when I give a little load on the NFS mount with my
  mariadb-server is:

  Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database 
server...
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.549355] BUG: kernel NULL 
pointer dereference, address: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.551391] #PF: supervisor read 
access in kernel mode
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.553377] #PF: 
error_code(0x) - not-present page
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.555350] PGD 0 P4D 0 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.557268] Oops:  [#7] SMP PTI
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.559186] CPU: 0 PID: 44171 
Comm: mysqld Tainted: P  DO  5.4.0-77-generic #86-Ubuntu
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.560644] Hardware name: VMware, 
Inc. VMware7,1/440BX Desktop Reference Platform, BIOS 
VMW71.00V.17369862.B64.2012240522 12/24/2020
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.562497] RIP: 
0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.563447] Code: 01 f0 80 4b 40 
08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 
41 38 48 8d 51 38 48 39 c2 74 23 <41>
   8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.565380] RSP: 
0018:a6e91c113d68 EFLAGS: 00010283
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.566361] RAX: 95e263669540 
RBX: 95e263669268 RCX: 95e263669240
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.567364] RDX: 95e263669278 
RSI: 95e263669540 RDI: 95e263669240
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.568358] RBP: a6e91c113db0 
R08: 0064 R09: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.569356] R10: 95e24b0ed480 
R11: 003d R12: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.570355] R13: 95e263669278 
R14: 95e263669268 R15: 
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.571353] FS:  
7f5d988cf800() GS:95e277a0() knlGS:
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.572340] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.573317] CR2:  
CR3: 0002229a2003 CR4: 001606f0
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.574289] Call Trace:
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.575260]  
_pnfs_return_layout+0x118/0x230 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.576272]  ? 
nfs_inode_detach_delegation+0x29/0x70 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.577244]  
nfs4_evict_inode+0x70/0x80 [nfsv4]
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.578205]  evict+0xd2/0x1b0
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.579174]  iput+0x148/0x210
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.580104]  
do_unlinkat+0x1c5/0x2d0
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.581014]  
__x64_sys_unlink+0x23/0x30
  Jul 16 15:26:10 maria2021-muc-2 kernel: [  678.581905]  
do_syscall_64+0x57/0x190
  Jul 16 

[Kernel-packages] [Bug 1934709] Re: btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly filesystem

[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/1934709

Title:
  btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly
  filesystem

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1934709

  [Impact]

  During an automatic balance, users may encounter an error when writing
  the transaction log to disk, when the log tree is being parsed, which
  forces the filesystem to be remounted read-only and outputs the
  following kernel oops:

  BTRFS: error (device dm-14) in balance_level:1962: errno=-117 unknown
  BTRFS info (device dm-14): forced readonly
  BTRFS: Transaction aborted (error -117)
  WARNING: CPU: 7 PID: 10818 at 
/build/linux-99Rib2/linux-4.15.0/fs/btrfs/tree-log.c:2908 
btrfs_sync_log+0xa28/0xbc0 [btrfs]
  CPU: 7 PID: 10818 Comm: qemu-system-s39 Tainted: G   OE
4.15.0-136-generic #140-Ubuntu
  Hardware name: IBM 3907 LR1 A00 (LPAR)
  Krnl PSW : 76bc1d64 9cc65255 (btrfs_sync_log+0xa28/0xbc0 
[btrfs])
     R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
  Krnl GPRS: 007899a6 0006 0027 0007
     03ff801fdd8c 0002394c 0053650a7000 ff8b
     00536b7f6000 0053ff8b 0053650a3800 005385935000
     00532054de01 005385935290 03ff801fdd8c 004eebb1fae0
  Krnl Code: 03ff801fdd80: c022a032 larl%r2,03ff80251de4
     03ff801fdd86: c0e5fffb2181 brasl   %r14,03ff80162088
    #03ff801fdd8c: a7f40001 brc 15,03ff801fdd8e
    >03ff801fdd90: e3a0f0a80004 lg  %r10,168(%r15)
     03ff801fdd96: b9040057 lgr %r5,%r7
     03ff801fdd9a: a7490b5c lghi%r4,2908
     03ff801fdd9e: b904002a lgr %r2,%r10
     03ff801fdda2: c032604f larl%r3,03ff80249e40
  Call Trace:
  ([<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs])
   [<03ff801c74e2>] btrfs_sync_file+0x3e2/0x550 [btrfs]
   [<003ce6ce>] do_fsync+0x5e/0x90
   [<003ce9ca>] SyS_fdatasync+0x32/0x48
   [<008ffe5c>] system_call+0xd8/0x2c8
  Last Breaking-Event-Address:
   [<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs]
  BTRFS: error (device dm-14) in btrfs_sync_log:2908: errno=-117 unknown
  BTRFS error (device dm-14): pending csums is 269639680

  This bug appears to be linked to bug 1933172, but is different and has
  a different root cause. Again, I believe that this is a regression
  introduced in the fixing of CVE-2019-19036, from 4.15.0-109-generic.

  [Fix]

  Analysis of the kernel oops is as follows:

  The first thing we see is that BTRFS entered ERROR state with the
  reason:

  in balance_level:1962: errno=-117 unknown

  Now errno -117 is:

  100 #define EUCLEAN 117 /* Structure needs cleaning */

  btrfs treats -EUCLEAN as if corruption has happened. Let's see where
  this is returned from.

  If we start at fs/btrfs/ctree.c in balance_level(), line 1962:

  1917 static noinline int balance_level(struct btrfs_trans_handle *trans,
  1918  struct btrfs_root *root,
  1919  struct btrfs_path *path, int level)
  1920 {
  ...
  1958 /* promote the child to a root */
  1959 child = read_node_slot(fs_info, mid, 0);
  1960 if (IS_ERR(child)) {
  1961 ret = PTR_ERR(child);
  1962 btrfs_handle_fs_error(fs_info, ret, NULL);
  1963 goto enospc;
  1964 }
  ...
  2136 }

  We are in the middle of a balancing operation, and if you happen to be
  familiar with how b-tree data structures work, we are promoting a
  child node to a topmost root node.

  The error most likely happens in read_node_slot(), with the lines
  after it printing that an error has happened.

  1887 static noinline struct extent_buffer *
  1888 read_node_slot(struct btrfs_fs_info *fs_info, struct extent_buffer 
*parent,
  1889int slot)
  1890 {
  ...
  1900 btrfs_node_key_to_cpu(parent, _key, slot);
  1901 eb = read_tree_block(fs_info, btrfs_node_blockptr(parent, slot),
  1902  btrfs_node_ptr_generation(parent, slot),
  1903  level - 1, _key);
  ...
  1910 }

  There are two calls here which are relevant. btrfs_node_key_to_cpu()
  and read_tree_block().

  Let's look at read_tree_block() in fs/btrfs/disk-io.c:

  1147 struct extent_buffer *read_tree_block(struct btrfs_fs_info *fs_info, u64 
bytenr,
  1148   u64 parent_transid, int level,
  1149   struct btrfs_key *first_key)
  1150 {
  1151 struct 

[Kernel-packages] [Bug 1934759] Re: Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on Bionic

[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/1934759

Title:
  Enable fib-onlink-tests.sh and msg_zerocopy.sh in kselftests/net on
  Bionic

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

Bug description:
  [Impact]
  Found this issue while debugging missing tests with bug 1934282.

  On Bionic there are 3 scripts that are not in the Makefile of the 
kselftests/net:
  $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done
  fib-onlink-tests.sh
  in_netns.sh
  msg_zerocopy.sh

  [Fix]
  * 830669e691464c selftests/net: enable msg_zerocopy test
  * 1751eb42ddb56b selftests: net: use TEST_PROGS_EXTENDED
  * a52b839752aab7 selftests: Add fib-onlink-tests.sh to TEST_PROGS
  * Set fib-onlink-tests.sh as executable

  They all need to be backported to Bionic.
  For the in_netns.sh it's not causing any issue to us when being called by 
run_afpackettests, but I think it's no harm to fix it to reduce confusions. 
Commit 1751eb42ddb56b will replace the change in 9faedd64 selftests: net: add 
in_netns.sh TEST_GEN_PROGS_EXTENDED [1] and 5ff9c1a3 selftests: net: add 
in_netns.sh to TEST_PROGS [2], and since we need to backport it there is no 
need to work on these two.

  [1] https://github.com/torvalds/linux/commit/9faedd643fd9
  [2] https://github.com/torvalds/linux/commit/5ff9c1a3dd92

  [Test]
  Run the "net" test suite in the kselftest directory from a patched source 
tree. fib-onlink-tests.sh and msg_zerocopy.sh tests will be executed.

  [Where problems could occur]
  This change will bring in more test for our SRU, we might see new failures 
because of these test in the future.

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


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

[Kernel-packages] [Bug 1934175] Re: Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)

[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/1934175

Title:
  Kernel oops due to uninitialized list on kernfs (kernfs_kill_sb)

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

Bug description:
  [Impact]
  * We had a recent report of a kernel crash due to a NULL pointer dereference 
in a Bionic 4.15 derivative kernel, as per the following log collected:

  [...]
  [537105.767348] SLUB: Unable to allocate memory on node -1, 
gfp=0x14000c0(GFP_KERNEL)
  [...]
  [537105.767368] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [537105.11] IP: kernfs_kill_sb+0x31/0x70
  [537105.783582] PGD 0 P4D 0
  [537105.787844] Oops: 0002 [#1] SMP PTI
  [...]
  RIP: 0010:kernfs_kill_sb+0x31/0x70
  RSP: 0018:b90aec1afd00 EFLAGS: 00010286
  RAX:  RBX: 9fdbd567d900 RCX: a0143885ae01
  RDX:  RSI: a0143885ae00 RDI: a2937c40
  RBP: b90aec1afd10 R08: a0150b581510 R09: 0001814d
  R10: b90aec1afcd8 R11: 0100 R12: a01436e43000
  R13: a01436e43000 R14:  R15: 9fdbd567d900
  FS:  7fe41a615b80() GS:a01afea4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0008 CR3: 007dfe3cc003 CR4: 003606e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   sysfs_kill_sb+0x1f/0x40
   deactivate_locked_super+0x48/0x80
   kernfs_mount_ns+0x1eb/0x230
   sysfs_mount+0x66/0xc0
   mount_fs+0x37/0x160
   ? alloc_vfsmnt+0x1b3/0x230
   vfs_kern_mount.part.24+0x5d/0x110
   do_mount+0x5ed/0xce0
  [...]

  * The following detailed call stack plus the disassembly help to
  understand the cause of the issue:

  mount_fs()
  --sysfs_mount()
  kernfs_mount_ns() 
  --deactivate_locked_super() 
  sysfs_kill_sb()
  --kernfs_kill_sb() 

  The below disassembly of kernfs_kill_sb() clarifies exactly the issue:

  812f46e0 :
  [ ... prologue ...]
  48 8b 9f 08 04 00 00mov0x408(%rdi),%rbx # %rbx = kernfs_super_info 
*info = sb->s_fs_info
  49 89 fcmov%rdi,%r12 # %r12 = super_block *sb
  48 c7 c7 40 7c 53 82mov$0x82537c40,%rdi # %rdi = 
_mutex (global)
  812f46f9: R_X86_64_32S  kernfs_mutex
  e8 ee da 67 00  callq  819721f0  # 
mutex_lock(_mutex);
  [...]
  48 8b 53 18 mov0x18(%rbx),%rdx # %rdx = info->node
  48 8b 43 20 mov0x20(%rbx),%rax # based on splat, RAX == 0x0 
[info->head.prev]
  48 89 42 08 mov%rax,0x8(%rdx) # <- OOPS [tried to assign 
next->prev = prev, see __list_del()]
  48 89 10mov%rdx,(%rax)
  48 b8 00 01 00 00 00movabs $0xdead0100,%rax # node->next = 
LIST_POISON1
  [...]

  * The fix for this issue comes from upstream commit 82382acec0c9
  ("kernfs: deal with kernfs_fill_super() failures"); this commit is a
  very trivial fix that adds an INIT_LIST_HEAD(>node) in
  kernfs_mount_ns(), making the list prev/next pointers valid since the
  beginning. Unfortunately this commit wasn't CCed to stable email when
  sent, so it wasn't automatically picked up by Ubuntu kernel; now it
  was properly submitted to stable list [0].

  * Along with this fix, we found another commit (7b745a4e4051) which is
  a small/simple fix to correlated code, that also should have been sent
  to 4.14.y stable branch, but for some reason wasn't. Since both
  commits were accepted in linux-stable, we are hereby proposing the
  backport for Ubuntu kernel 4.15.

  [0]
  https://lore.kernel.org/stable/20210622210622.9925-1-gpicc...@canonical.com/

  
  [Test Case]
  * We don't have a real test case, although low-memory condition or an 
artificial kprobe reproducer could easily trigger the issue.

  * We booted a qemu virtual machine with a kernel containing both
  patches with no issues.

  
  [Where problems could occur]
  * The likelihood of issues are low, specially due to the fact both patches 
are very simple and they are on upstream kernel for more than 3 years (and were 
quickly accepted in 4.14.y stable branch last week).

  * With that sad, the second patch could potentially introduce issues
  with super_block references - I honestly cannot conceive any issues
  potentially caused by patch 1.

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


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

[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message

[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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887661

Title:
  pmtu.sh from net in ubuntu_kernel_selftests failed with no error
  message

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 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.10 source package in Groovy:
  Invalid
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.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.6 source package in Impish:
  Invalid

Bug description:
  [Impact]
  The pmtu.sh test in net from ubuntu_kernel_selftests will be marked
  as failed even there is no obvious failure message from the test:
  $ sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
vxlan4 not supported
  TEST: IPv4 over vxlan4: PMTU exceptions [SKIP]
vxlan4 not supported
  TEST: IPv6 over vxlan4: PMTU exceptions [SKIP]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
geneve4 not supported
  TEST: IPv4 over geneve4: PMTU exceptions [SKIP]
geneve4 not supported
  TEST: IPv6 over geneve4: PMTU exceptions [SKIP]
  TEST: IPv4 over geneve6: PMTU exceptions [ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions [ OK ]
  TEST: IPv4 over fou4: PMTU exceptions [ OK ]
  TEST: IPv6 over fou4: PMTU exceptions [ OK ]
  TEST: IPv4 over fou6: PMTU exceptions [ OK ]
  TEST: IPv6 over fou6: PMTU exceptions [ OK ]
  TEST: IPv4 over gue4: PMTU exceptions [ OK ]
  TEST: IPv6 over gue4: PMTU exceptions [ OK ]
  TEST: IPv4 over gue6: PMTU exceptions [ OK ]
  TEST: IPv6 over gue6: PMTU exceptions [ OK ]
  TEST: vti6: PMTU exceptions [ OK ]
  TEST: vti4: PMTU exceptions [ OK ]
  TEST: vti4: default MTU assignment [ OK ]
  TEST: vti6: default MTU assignment [ OK ]
  TEST: vti4: MTU setting on link creation [ OK ]
  TEST: vti6: MTU setting on link creation [ OK ]
  TEST: vti6: MTU changes on link changes [ OK ]
vxlan4 not supported
  TEST: ipv4: cleanup of cached exceptions [SKIP]
  TEST: ipv6: cleanup of cached exceptions [ OK ]
  TEST: ipv4: list and flush cached exceptions [ OK ]
  TEST: ipv6: list and flush cached exceptions [ OK ]
  $ echo $?
  1

  This is because the test script treats all non-zero return code as a
  failure, thus it will be marked as FAILED when some sub-test got
  skipped.

  [Fix]
  * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return
   code
  * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing

  This patchset will:
1. Use the kselftest framework skip code $ksft_skip to replace the
   hardcoded SKIP return code.
2. Improve the result processing, the test will be marked as PASSED
   if nothing goes wrong and not all the tests were skipped.

  These have already landed in newer releases and this test does not
  exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G.

  The first patch needs to be backported (except on F-OEM-5.10) as some
  test cases were not added yet.
  The second one can be cherry-picked.

  [Test]
  Run this test directly on a patched kernel. The skipped test will cause
  failure to this test.

  [Where problems could occur]
  Changes limited to testing tools, it's unlikely to cause any problem
  to kernel functions.

  
  [Original Bug Report]
  Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1

  The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed 
even there is no obvious failure message from the test:
  $ sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
    vxlan4 not supported
  TEST: IPv4 over vxlan4: PMTU exceptions [SKIP]
    vxlan4 not supported
  TEST: IPv6 over vxlan4: PMTU exceptions [SKIP]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
    geneve4 not supported
  TEST: IPv4 over geneve4: PMTU exceptions[SKIP]
    

[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  large_dir in ext4 broken

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Triaged

Bug description:
  == SRU, Bionic, Focal, Groovy, Hirsute, Impish ==

  [Impact]

  Creating millions of files on ext4 partition with large_dir support by
  touching them will eventually trip an ext4 leaf node issue in the
  index hash. This occurs more frequently when also using smaller block
  sizes and ends up either with a EXIST or EUCLEAN failure.

  This occurs on the restart condition when performing do_split.

  [ Fix ]

  The fix protects do_split() from the restart condition, making it safe
  from both current and future ordering of goto statements in earlier
  sections of the code.

  The fix is from a patch sent upstream and cc'd to Ted Tso but didn't
  appear on the ext4 mailing list presumably because it got marked as
  SPAM.

  [ Test Case ]

  Without the fix touching tens of thousands of empty files will trip
  the issue. It seems to occur more frequently with memory pressure and
  smaller block sizes, e.g.:

  sudo mkdir -p /mnt/tmpfs /mnt/storage
  sudo mount -t tmpfs -o size=9000M tmpfs /mnt/tmpfs
  sudo dd if=/dev/urandom of=/mnt/tmpfs/ext4.img bs=1M
  sudo mkfs.ext4 -O large_dir -N 2100 -O dir_index /mnt/tmpfs/ext4.img -b 
1024 -F
  sudo mount /mnt/tmpfs/ext4.img /mnt/storage

  and compile and run the attached C program (see
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+attachment/5509402/+files/touch.c)
  that quickly populates /mnt/storage with empty files.  Without the fix
  this will terminate with an -EEXIST or -EUCLEAN error on the file
  creation after several tens of thousands of files.

  [Where problems could occur]

  This changes the behaviour of the directory indexing hashing so there
  is a regression potential that this may introduce subsequent index
  hashing issues when needed (or not) to do a split.  This patch seems
  to cover all the necessary cases, so I believe this risk is relatively
  low.  I have also tested this on all the kernel series in the SRU with
  21,000,000 files so I am confident we have enough test coverage to
  show the fix is OK.

  --

  I believe, I found a bug in ext4 in recent kernel versions.
  I stumbled across this while I was trying to restore a backup to a new VM.

  How to reproduce this bug:

  1. Use a virtual/physical machine with "Ubuntu 18.04.5 LTS" and kernel 
version 4.15.0-144-generic.
  2. add a secondary disk to hold the test files.
  3. prepare and mount the filesystem with enabled 'large_dir' flag:
  mkfs.ext4 -m0 /dev/sdb1;
  tune2fs -O large_dir /dev/sdb1;
  mkdir /mnt/storage;
  mount /dev/sdb1 /mnt/storage;
  4. change to directory and create approx. 16 mio files
  cd /mnt/storage;
  i=0;
  while (( $i < 2000 )); do
    i=$(( $i + 1 ));
    (( $i % 1000 == 0 )) && echo $i;
    touch file_$i.dat || break;
  done

  Expected behaviour:
  - 20 mio files shoud be created without error

  What happened instead:
  - The loop aborts with an error message:
  # 16263100
  # touch: cannot touch 'file_16263173.dat': Structure needs cleaning
  - dmesg gives a little more details:
  # [Mon Jun 21 03:15:18 2021] EXT4-fs error (device sdb): dx_probe:855: inode 
#2: block 146221: comm touch: directory leaf block found instead of index block

  Additional notes:
  - This occurs on kernel version 4.15.0-144-generic
  - Not sure, but I believe one test was run on 4.15.0-143-generic and failed 
too.
  - Did not check against 4.15.0-142-generic
  - On 4.15.0-141-generic, the problem does not exist. Behaviour is as expected.

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


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

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[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/1918427

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  Confirmed
Status in curtin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in curtin source package in Focal:
  New
Status in linux source package in Focal:
  Fix Committed
Status in curtin source package in Hirsute:
  New
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact (linux)]
  The only package that currently satisfies the bootloader Recommends 
relationship on ARM systems is flash-kernel. This ignores EFI-based systems, 
which will instead require GRUB. Our installers know to install GRUB anyway - 
but flash-kernel also gets installed. Normally flash-kernel realizes it is not 
needed and just exits - so the impact is limited to wasting space and CPU 
cycles on each kernel update. However, there can be cases where calling 
flash-kernel can cause problems. The original report here describes one where 
flash-kernel thinks it recognizes the system and tries to run anyway, when in 
fact GRUB is the correct boot loader.

  [Test Case (linux)]
  On an arm64 system, confirm that grub-efi-arm64 is an option in the 
Recommends field:

  $ apt show linux-image-unsigned-5.4.0-78-generic  | grep Recommends

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Recommends: flash-kernel | grub-efi-arm64, initramfs-tools | linux-
  initramfs-tool

  [What Could Go Wrong (linux)]
  First let me describe the mitigations against something going wrong. The 
proposed patch was already in the hirsute kernel at the time of hirsute GA, so 
it's had some real world testing, including in our installers. In addition, the 
patch still leaves flash-kernel as the *default* bootloader Recommends (first 
in the |'d list) - it only adds grub-efi-arm64 as a secondary option, 
preventing the installation of flash-kernel if GRUB is already there.

  So, the only scenario where I can see a problem might be if something
  depends on flash-kernel getting installed due to a Recommends even
  though GRUB is already present.

  = Original Report Follows =

  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787
  [8] 

[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all

[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/1934282

Title:
  Some test in kselftest/net on focal source tree were not tested at all

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Found this issue while debugging devlink_port_split.py test issue in
  bug 1928889.

  There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and
  etc are not in the Makefile of the net directory, thus they are not
  tested at all.

  [Fix]
  * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile

  Backport needed for Focal as we only have these tests unadded:
  $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done
  fib_nexthop_multiprefix.sh
  fib_nexthops.sh
  icmp_redirect.sh
  ip6_gre_headroom.sh
  route_localnet.sh

  [Test]
  Run the "net" test suite in the kselftest directory from a patched
  source tree. These tests will be executed.

  [Where problems could occur]
  This change will bring in more tests for our SRU, we might see new
  failures because of these test in the future.

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


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

[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back

[Kleber Sacilotto de Souza]

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

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

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

Title:
  Add l2tp.sh in net from ubuntu_kernel_selftests back

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.13 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  We have this test disabled intentionally in the past because of the
  lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from
  l2tp_xmit_skb()" in our kernels.

  The way we disable it is to override the executable bit with our
  autotest-client-tests suite [1], but this makes the test suite
  complain about script is not executable. Henceforth we further
  disable it by removing it from the Makefile in the patch "UBUNTU:
  SAUCE: selftests/net -- disable timeout"

  Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in
  our test suite [2], we still need to revert that SAUCE patch to get
  it tested.

  [1] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16
  [2] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d

  [Fix]
  Revert "UBUNTU: SAUCE: selftests/net -- disable timeout"

  This test only exists in our tree since Focal.

  [Test]
  Run the net test suite in kselftest with patched source tree:
    sudo make -C linux/tools/testing/selftests TARGETS=net run_tests

  The l2tp.sh test will be executed.

  [Where problems could occur]
  This is only for testing tools, however if commit 27d53323664c54 "l2tp:
  remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we
  might crash our testing node like in bug 1854968. Also, we might see
  new failures caused by this test in the test report.

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


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

[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

[Kleber Sacilotto de Souza]

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

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

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

Title:
  icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
  F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
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.10 source package in Groovy:
  Invalid
Status in linux-oem-5.13 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The IPv6: mtu exception plus redirect test in icmp_redirect.sh test
  from kselftest/net is expected to fail due to a known bug in the
  IPv6 logic.

  When trying to run this test you will see this sub test fail with:
  TEST: IPv6: mtu exception plus redirect [FAIL]

  and thus causing non-zero return value for this script.

  [Fix]
  * 0a36a75c681880 selftests: icmp_redirect: support expected failures

  This fix can be cherry-picked into all affected series. And it has
  already landed on Unstable, test passed with Impish 5.13.

  Although we have this script in Focal kernel as well, but it's not
  being executed at all. This is another issue that will be dealt in
  a different bug report.

  [Test]
  Run the patched icmp_redirect.sh test manually in
  tools/testing/selftests/net, this sub-test will be marked as XFAIL
  and the return value of this script will be 0:
  $ sudo ./icmp_redirect.sh
  
  #
  Routing with nexthop objects and VRF
  #
  TEST: IPv6: mtu exception plus redirect [XFAIL]

  Tests passed: 36
  Tests failed: 0
  Tests xfailed: 4
  $ echo $?
  0

  [Where problems could occur]
  Change limited to testing tool, not affecting actual kernel
  functionality. The only possible issue that I can think of is that
  as this script is no longer complaining about this failure, people
  might forgot there is such an issue exist in ipv6.

  [Original Bug Report]
  Issue found on Focal 5.6.0-1011.11-oem

  
ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
  sudo ./icmp_redirect.sh

  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception 

[Kernel-packages] [Bug 1934878] Re: Mute/mic LEDs no function on some HP platfroms

[Kleber Sacilotto de Souza]

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

Title:
  Mute/mic LEDs no function on some HP platfroms

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP ProBook 630 G8 Notebook PC
  2) HP ProBook 445 G8 Notebook PC
  3) HP ProBook 450 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1934864] Re: [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU

[Kleber Sacilotto de Souza]

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

Title:
  [SRU][OEM-5.10/H] Fix HDMI output issue on Intel TGL GPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]
  When plugin HDMI cable, no HDMI output, kernel reported error:
  [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port

  [Fix]
  Legacy LSPCON chip from MCA and Parade is only used for platforms,
  Limit the support between GEN9 and GEN10.
  The commit is already in 5.13, so only SRU for oem-5.10 and hirsute.

  [Test]
  Verified on hardware, HDMI output works fine.

  [Where problems could occur]
  The HDMI output may break.

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


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