date:20210519

** Summary changed:

- vrf_route_leaking linux ADT test failure with linux/5.11.0-18.19 (Ping 
received ICMP Packet too big)
+ 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)

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20210510 ubuntu-kernel-selftests

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

Title:
  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)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux 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 
 [

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

** Summary changed:

- evlink_port_split linux ADT test failure with linux/5.11.0-18.19 ( list index 
out of range)
+ devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure 
with linux/5.11.0-18.19 ( list index out of range)

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: sru-20210510 ubuntu-kernel-selftests

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux 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


  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: ubuntu-qrt-apparmor

** Tags added: sru-20210510

** Also affects: qa-regression-testing
   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/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 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic

2021-05-19 Thread Mariusz

Hi,

I have done another test and compared the same server running on
4.15.0-136-generic and kernel 4.15.0-142-generic. Collected zabbix CPU
utilization graph which is showing the problem from the performance
point of view. On 4.15.0-136-generic, the server works normal and there
are no processes stuck on 99% iowait. On 4.15.0-142-generic it is not
working at all and rsync, pg_receivewal or dd processes are hanging with
iowait 99%. I attached the zabbix graph to this bug.

** Attachment added: "kernel_issue.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+attachment/5498858/+files/kernel_issue.png

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

Title:
  Disk IO very slow on kernel 4.15.0-142-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
  4.15.0-142-generic disk IOs (writes) are suffering from terrible
  delay.

  Time required to write 1GB of data to the dist is ~12 minutes.
   
  1GB in 12 minutes:
  strace -ttvvff -o mel.strace dd bs=1024k count=1024  if=/dev/zero 
of=/data/disk_test/dd_test

  Before the upgrade,  it took seconds to complete.
  The only change which was done on the system was security upgrade done with 
unattended-upgrade utility and main repositories for bionic and bionic-security.

  This is physical server LENOVO System x3650 M5, with Symbios Logic
  MegaRAID SAS-3 3108  disk controller.

  The only difference which I see is that there are more modules loaded
  by the latest kernel.

  I would expect that the performance would be the same. There were no
  changes to the physical server and the disks are reported as online
  and healthy. No only dd is affected but also all disk-based operation
  by barman (we are using postgres steaming backup along with rsync/ssh
  archiving).

  I think this could be a kernel bug. I would be happy to provide other
  information which would help in fixing this problem.

  =
  Details:

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  lsmod
  Module  Size  Used by
  ip6_tables 28672  0
  iptable_filter 16384  0
  ip_tables  28672  1 iptable_filter
  x_tables   40960  3 iptable_filter,ip6_tables,ip_tables
  tcp_diag   16384  0
  udp_diag   16384  0
  raw_diag   16384  0
  inet_diag  24576  3 tcp_diag,raw_diag,udp_diag
  unix_diag  16384  0
  binfmt_misc20480  1
  ipmi_ssif  32768  0
  kvm_intel 217088  0
  kvm   614400  1 kvm_intel
  irqbypass  16384  1 kvm
  crct10dif_pclmul   16384  0
  crc32_pclmul   16384  0
  ghash_clmulni_intel16384  0
  pcbc   16384  0
  aesni_intel   188416  0
  aes_x86_64 20480  1 aesni_intel
  crypto_simd16384  1 aesni_intel
  glue_helper16384  1 aesni_intel
  cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
  ipmi_si57344  0
  ipmi_devintf   20480  0
  ipmi_msghandler53248  3 ipmi_devintf,ipmi_si,ipmi_ssif
  acpi_pad  180224  0
  bonding   163840  0
  lp 20480  0
  parport49152  1 lp
  autofs440960  2
  mgag20045056  1
  i2c_algo_bit   16384  1 mgag200
  ttm   106496  1 mgag200
  drm_kms_helper172032  1 mgag200
  syscopyarea16384  1 drm_kms_helper
  tg3   167936  0
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  ptp20480  1 tg3
  drm   401408  4 drm_kms_helper,mgag200,ttm
  pps_core   20480  1 ptp
  megaraid_sas  143360  12


  lspci  -vnn -s 0b:00.0
  0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 
3108 [Invader] [1000:005d] (rev 02)
Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454]
Physical Slot: 9
Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
I/O ports at 2e00 [size=256]
Memory at 903f (64-bit, non-prefetchable) [size=64K]
Memory at 9040 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at  [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=97 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] #19

[Kernel-packages] [Bug 1928183] Re: turbostat doesn't work with AMD Cezanne APUs

2021-05-19 Thread David Bartley

Nope, still doesn't work (specifically after installing the linux-tools-
common deb).  I'm assuming that just included the cherry-pick mentioned
earlier?

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

Title:
  turbostat doesn't work with AMD Cezanne APUs

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985681 describes the
  issue and necessary cherry-pick
  (https://git.kernel.org/linus/301b1d3a9104f4f3a8ab4171cf88d0f55d632b41).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-tools-common 5.11.0-17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartle 2287 F pulseaudio
   /dev/snd/controlC0:  bartle 2287 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 12 01:04:15 2021
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=27b86d91-8e89-49da-ad17-45901581ce2f ro
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (19 days ago)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.10
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd04/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] ERROR Waiting for fences timed out!

Looks like this might be related to bug 1883493.

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen and
  [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences
  timed out!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1905724] Re: Compete system freeze with AMD GPU

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

** This bug has been marked a duplicate of bug 1883493
   amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

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

Title:
  Compete system freeze with AMD GPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  So, several times a week i experience a complete freeze of the system, but in 
rather strange way. Spotify keeps playing, but screen is frozen and even 
NumLock doesnt work.
  Here are the relevant lines from syslog:

  Nov 26 13:59:43 home kernel: [13624.224831] [drm:amdgpu_dm_atomic_commit_tail 
[amdgpu]] *ERROR* Waiting for fences timed out!
  Nov 26 13:59:43 home kernel: [13624.224911] [drm:amdgpu_dm_atomic_commit_tail 
[amdgpu]] *ERROR* Waiting for fences timed out!
  Nov 26 13:59:48 home kernel: [13624.224980] [drm:amdgpu_dm_atomic_commit_tail 
[amdgpu]] *ERROR* Waiting for fences timed out!
  Nov 26 13:59:48 home kernel: [13629.344808] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=954733, emitted 
seq=954735
  Nov 26 13:59:48 home kernel: [13629.344870] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process chrome pid 2341 thread 
chrome:cs0 pid 2356
  Nov 26 13:59:48 home kernel: [13629.344872] [drm] GPU recovery disabled.
  Nov 26 13:59:51 home kernel: [13632.416809] [drm:amdgpu_dm_atomic_commit_tail 
[amdgpu]] *ERROR* Waiting for fences timed out!
  Nov 26 13:59:51 home kernel: [13632.416883] [drm:amdgpu_dm_atomic_commit_tail 
[amdgpu]] *ERROR* Waiting for fences timed out!
  Nov 26 13:59:54 home plank.desktop[2060]: --2020-11-26 13:59:54--  
https://clients2.google.com/cr/report
  Nov 26 13:59:54 home plank.desktop[2060]: Resolving clients2.google.com 
(clients2.google.com)... 216.58.211.142, 2a00:1450:400f:808::200e
  Nov 26 13:59:54 home plank.desktop[2060]: Connecting to clients2.google.com 
(clients2.google.com)|216.58.211.142|:443... connected.
  Nov 26 13:59:55 home plank.desktop[2060]: HTTP request sent, awaiting 
response... 200 OK
  Nov 26 13:59:55 home plank.desktop[2060]: Length: unspecified [text/plain]
  Nov 26 13:59:55 home plank.desktop[2060]: Saving to: ‘/dev/fd/4’
  Nov 26 13:59:55 home plank.desktop[2060]:  0K
  Nov 26 13:59:55 home plank.desktop[2060]:  Crash dump id:  f034d136a81c3341
  Nov 26 13:59:55 home plank.desktop[2060]: 
3,45M=0s
  Nov 26 13:59:55 home plank.desktop[2060]: 2020-11-26 13:59:55 (3,45 MB/s) - 
‘/dev/fd/4’ saved [16]
  Nov 26 14:00:04 home kernel: [13632.416960] [drm:amdgpu_dm_atomic_commit_tail 
[amdgpu]] *ERROR* Waiting for fences timed out!
  Nov 26 14:00:04 home kernel: [13645.984782] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=954733, emitted 
seq=954735
  Nov 26 14:00:04 home kernel: [13645.984843] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
  Nov 26 14:00:04 home kernel: [13645.984845] [drm] GPU recovery disabled.
  Nov 26 14:00:05 home kernel: [13646.391163] GpuWatchdog[28302]: segfault at 0 
ip 7f5afd863c4f sp 7f5af587a1c0 error 6 in 
libcef.so[7f5af97be000+6dbb000]
  Nov 26 14:00:05 home kernel: [13646.391172] Code: 89 de e8 44 c2 9f fe 80 7d 
cf 00 79 09 48 8b 7d b8 e8 15 31 67 fe 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 f1 ae f5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e
  Nov 26 14:00:15 home kernel: [13656.480730] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=954733, emitted 
seq=954735
  Nov 26 14:00:15 home kernel: [13656.480791] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
  Nov 26 14:00:15 home kernel: [13656.480793] [drm] GPU recovery disabled.

  
  Usually this happens when I browse Google Maps.
  System is:
  AMD Ryzen 7 3700X 8-Core Processor
  MSI Radeon 5700XT
  MSI B450M Mortar MAX.

  version.log:
  Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65

  lsb_release -rd
  Description:  elementary OS 5.1.7 Hera
  Release:  5.1.7
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2020-08-22 (100 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200204)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=9d877b85-ac94-4915-bf4c-4c2598f875c3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.

[Kernel-packages] [Bug 1746551] Re: GPU HANG since package update

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  GPU HANG since package update

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Since today, I get occasional crashes freeze-ups of the GUI, followed
  by a restart of the X server. In syslog, I find entries like the ones
  below.

  The system was running stably before, so this is a new phenomenon...
  could this be related to the recent kernel updates?

  Obviously, this leads to data loss...

  Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 
9:0:0x86dd, in Xorg [870], reason: Hang on rcs0, action: reset
  Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
  Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
  Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
  Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on


  Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on


  Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on


  Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on


  Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected  


  Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke 
(error 1). Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 
1). Did the X11 server die?
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]:   after 2218 requests 
(2218 known processed) with 0 events remaining.
  Jan 31 11:23:21 TP

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] ERROR Waiting for fences timed out!

** Summary changed:

- [amdgpu] Gnome locks up with artifacts on screen
+ [amdgpu] Gnome locks up with artifacts on screen and 
[drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen and
  [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences
  timed out!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co.,

[Kernel-packages] [Bug 1928522] Re: seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148

So, s390x ptrace does allow to set the syscall and return code as long
as it sets the return code at exit time.

However, when using seccomp SECCOMP_RET_TRACE, there is no possibility
to change it at exit time (by doing a ptrace after SECCOMP_RET_TRACE
stops the process). It only happens at entry time. Then, either the
syscall or return value could be set. This is aggravated by the fact
that when seccomp checks for an invalid syscall in order to skip
executing it, it checks for int_code, which cannot be changed by ptrace.
This is probably something that could be reviewed, however.

Without the code change that led to this test regression, the test sets
gpr[2] twice, once for the syscall number, then for the return value.
That return value was being used later on as the return code as it was
an invalid syscall number, which made the test accidentally work.

Now, instead, ENOSYS is returned, and the test fails.

One regression, however, that this patch causes (but not on 4.15), is
that when seccomp returns failure because of a signal, the
signal_restart should not be skipped, but it is. This causes a test
(that we don't currently run) to fail on 5.4, but that is not a
regression and has been like that on 5.4 since forever.

Upstream has changed the entry code for a common code, which should not
have this bug. That needs to be verified, though. Then, a different fix
should be applied to our earlier kernels, like this one:

@@ -905,7 +905,7 @@ asmlinkage long do_syscall_trace_enter(struct pt_regs *regs)
sd.args[5] = regs->gprs[7] & mask;
 
if (__secure_computing() == -1)
-   goto skip;
+   return -1;
}
 #endif /* CONFIG_SECCOMP */

Then, seccomp_bpf can be run just fine on 5.8, for example. 5.4 possibly
needs one small fix for s390x to work, instead of the very large
patchset I thought was needed.

That would be:
commit 4bae85b620dc1f7aa4d2338b923d9d9b394b58c4
Author: Sven Schnelle 
Date:   Mon Mar 9 16:56:53 2020 +0100

selftests/seccomp: s390 shares the syscall and return value register

s390 cannot set syscall number and reture code at the same time,
so set the appropriate flag to indicate it.

Signed-off-by: Sven Schnelle 
Signed-off-by: Vasily Gorbik 

Which is the same that is likely needed for 4.15 to skip these tests.

Cascardo.

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

Title:
  seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test
  failure with linux/4.15.0-144.148

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released

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

  Testing failed on:
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz

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

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

[Kernel-packages] [Bug 1925209] Re: No iwilwifi driver in Linux 5.4.0-1034-raspi

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Kernel-packages] [Bug 1924771] Re: hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Kernel-packages] [Bug 1926755] Re: Support Auvidea B101 (TC358743)

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Kernel-packages] [Bug 1927505] Re: pigpio not working with 5.11

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Kernel-packages] [Bug 1927108] Re: Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD

This bug was fixed in the package linux-raspi - 5.11.0-1009.10+21.10.1

---
linux-raspi (5.11.0-1009.10+21.10.1) impish; urgency=medium

  * impish/linux-raspi: 5.11.0-1009.10+21.10.1 -proposed tracker (LP:
#1927571)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions

  [ Ubuntu: 5.11.0-1009.10 ]

  * hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
  * Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi: CONFIG_AS_HAS_LSE_ATOMICS=y
  * Hirsute update: v5.11.13 upstream stable release (LP: #1923415)
- [Config] raspi: CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
  * pigpio not working with 5.11 (LP: #1927505)
- [Config] raspi: Set BCM_VCIO=y
  * hirsute/linux-raspi: Upstream raspberrypi patchset 2021-04-15 (LP: #1924771)
- media/v4l2_m2m: In buffered mode run jobs if either port is streaming
- staging/bcm2835-codec: Correct logging of size_t to %zu
- staging/bcm2835-codec: Add support for pixel aspect ratio
- staging/bcm2835-codec: Implement additional g_selection calls for decode
- staging/bcm2835-codec: Add VC-1 support.
- vc4/drm: Avoid full hdmi audio fifo writes
- vc4/drm: Increase hdmi audio axi priority to avoid lost samples
- overlays: gpio-led: new overlay
- Revert "i2c: bcm2835: Handle untimely DONE signal"
- ARM: dts: bcm2711: Add aliases for additional SPIs
- Make rpi poe fan less noisy in cool environments
- vc4/drm: Fix source offsets with DRM_FORMAT_P030
- vc4/drm: vc4_plane: Remove subpixel positioning check
- clk-raspberrypi: Also support HEVC clock
- dt: Switch hevc clock from fixed to firmware driver
- rpivid: Request maximum hevc clock
- staging/bcm2835-camera: Add support for DMABUFs
- staging: fbtft: Add minipitft13 variant
- overlays: Add minipitft13 overlay
- overlays: ghost-amp: Minor tweaks
- overlays: Add README entry for minipitft13
- ARM: dts: update bcm2711-rpi-cm4.dts and -400
- Revert "usb: xhci: Disable the XHCI 5 second timeout"
- vc4/drm: SQUASH: Fix source offsets with DRM_FORMAT_P030
- dwc-otg: fix clang -Wignored-attributes warning
- dwc-otg: fix clang -Wsometimes-uninitialized warning
- dwc-otg: fix clang -Wpointer-bool-conversion warning
- Update Allo Piano Dac Driver
- sc16is7xx: Defer probe if device read fails
- ASoC: tlv320aic32x4: Register clocks before registering component
- ASoC: tlv320aic32x4: Increase maximum register in regmap
- drm/connector: Create a helper to attach the hdr_output_metadata property
- drm/connector: Add helper to compare HDR metadata
- drm/vc4: Use the new helpers
- drm/connector: Add a helper to attach the colorspace property
- drm/vc4: hdmi: Signal the proper colorimetry info in the infoframe
- staging: vcsm-cma: Fix memory leak from not detaching dmabuf
- vc4/kms: vc4_plane: Support 2020 colourspace for yuv planes
- drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling
- phy: broadcom: Move hunk to match upstream raspberrypi
  * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
  * Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
  * No iwilwifi driver in  Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
  * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
  * linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
  * Hirsute update: v5.11.17 upstream stable release (LP: #1927535)
- vhost-vdpa: protect concurrent access to vhost device iotlb
- Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap 
fails"
- ovl: fix reference counting in ovl_mmap error path
- coda: fix reference counting in coda_file_mmap error path
- amd/display: allow non-linear multi-planar formats
- drm/amdgpu: reserve fence slot to update page table
- drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish
- gpio: omap: Save and restore sysconfig
- KEYS: trusted: Fix TPM reservation for seal/unseal
- vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails
- pinctrl: lewisburg: Update number of pins in community
- block: return -EBUSY when there are open partitions in blkdev_reread_part
- pinctrl: core: Show pin numbers for the controllers with base = 0
- arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
- bpf: Allow variable-offset stack access
- bpf: Refactor and streamline bounds check into helper

[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04

2021-05-19 Thread Herczeg Zsolt

~mesouug I've tested my XPS 9700 on the self-compiled ubuntu kernel, and
it works great with a 4-pin plug, even the microphone input of the
headset is fully functional. There may be hardware differences within
the XPS 9700 line as well, but the driver must be fully functional for
at least some of the hardware sold.

Are you confident your headset should be compatible? Not all 4-pin
headphones have the same pin order, which was historically a common
problem.

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

Title:
  No sound output/input available after installing 21.04

Status in OEM Priority Project:
  Won't Fix
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Image: Hirsute 21.04 (20210415 daily build)

  Device: Dell Precision 5750

  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .

  The only way to hear sound is to connect a Bluetooth speaker.

  Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

  https://certification.ubuntu.com/hardware/202002-27726

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1909814] Re: Keyboard not working

2021-05-19 Thread Did VDT

Content of var/log/Xorg.0.log seems to consider webcam as keyboard if I 
understand it correctly.
Any idea ?


< grep -i keyboard /var/log/Xorg.0.log
[14.661] (II) Initializing extension XKEYBOARD
[14.851] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[14.856] (II) event1  - Power Button: is tagged by udev as: Keyboard
[14.856] (II) event1  - Power Button: device is a keyboard
[14.857] (II) XINPUT: Adding extended input device "Power Button" (type: 
KEYBOARD, id 6)
[14.865] (II) event1  - Power Button: is tagged by udev as: Keyboard
[14.865] (II) event1  - Power Button: device is a keyboard
[14.865] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[14.866] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[14.866] (II) event0  - Sleep Button: device is a keyboard
[14.866] (II) XINPUT: Adding extended input device "Sleep Button" (type: 
KEYBOARD, id 7)
[14.867] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[14.867] (II) event0  - Sleep Button: device is a keyboard
[14.867] (II) config/udev: Adding input device HID Keyboard Device 
(/dev/input/event3)
[14.867] (**) HID Keyboard Device: Applying InputClass "libinput keyboard 
catchall"
[14.867] (II) Using input driver 'libinput' for 'HID Keyboard Device'
[14.868] (**) HID Keyboard Device: always reports core events
[14.868] (II) event3  - HID Keyboard Device: is tagged by udev as: Keyboard
[14.868] (II) event3  - HID Keyboard Device: device is a keyboard
[14.868] (II) event3  - HID Keyboard Device: device removed
[14.868] (II) XINPUT: Adding extended input device "HID Keyboard Device" 
(type: KEYBOARD, id 8)
[14.869] (II) event3  - HID Keyboard Device: is tagged by udev as: Keyboard
[14.869] (II) event3  - HID Keyboard Device: device is a keyboard
[14.870] (II) config/udev: Adding input device HID Keyboard Device Consumer 
Control (/dev/input/event4)
[14.870] (**) HID Keyboard Device Consumer Control: Applying InputClass 
"libinput keyboard catchall"
[14.870] (II) Using input driver 'libinput' for 'HID Keyboard Device 
Consumer Control'
[14.870] (**) HID Keyboard Device Consumer Control: always reports core 
events
[14.871] (II) event4  - HID Keyboard Device Consumer Control: is tagged by 
udev as: Keyboard
[14.871] (II) event4  - HID Keyboard Device Consumer Control: device is a 
keyboard
[14.871] (II) event4  - HID Keyboard Device Consumer Control: device removed
[14.871] (II) libinput: HID Keyboard Device Consumer Control: needs a 
virtual subdevice
[14.871] (II) XINPUT: Adding extended input device "HID Keyboard Device 
Consumer Control" (type: MOUSE, id 9)
[14.871] (**) HID Keyboard Device Consumer Control: (accel) selected scheme 
none/0
[14.871] (**) HID Keyboard Device Consumer Control: (accel) acceleration 
factor: 2.000
[14.871] (**) HID Keyboard Device Consumer Control: (accel) acceleration 
threshold: 4
[14.872] (II) event4  - HID Keyboard Device Consumer Control: is tagged by 
udev as: Keyboard
[14.872] (II) event4  - HID Keyboard Device Consumer Control: device is a 
keyboard
[14.872] (II) config/udev: Adding input device HID Keyboard Device System 
Control (/dev/input/event5)
[14.872] (**) HID Keyboard Device System Control: Applying InputClass 
"libinput keyboard catchall"
[14.872] (II) Using input driver 'libinput' for 'HID Keyboard Device System 
Control'
[14.873] (**) HID Keyboard Device System Control: always reports core events
[14.873] (II) event5  - HID Keyboard Device System Control: is tagged by 
udev as: Keyboard
[14.873] (II) event5  - HID Keyboard Device System Control: device is a 
keyboard
[14.873] (II) event5  - HID Keyboard Device System Control: device removed
[14.873] (II) XINPUT: Adding extended input device "HID Keyboard Device 
System Control" (type: KEYBOARD, id 10)
[14.874] (II) event5  - HID Keyboard Device System Control: is tagged by 
udev as: Keyboard
[14.874] (II) event5  - HID Keyboard Device System Control: device is a 
keyboard
[14.875] (**) USB2.0 HD UVC WebCam: USB2.0 HD: Applying InputClass 
"libinput keyboard catchall"
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: is tagged by udev 
as: Keyboard
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: device is a 
keyboard
[14.876] (II) XINPUT: Adding extended input device "USB2.0 HD UVC WebCam: 
USB2.0 HD" (type: KEYBOARD, id 11)
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: is tagged by udev 
as: Keyboard
[14.876] (II) event6  - USB2.0 HD UVC WebCam: USB2.0 HD: device is a 
keyboard
[14.879] (**) HID Keyboard Device Consumer Control: Applying InputClass 
"libinput keyboard catchall"
[14.879] (II) Using input driver 'libinput' for 'HID Keyboard Device 
Consumer Control'
[14.879] (**) HID Keyboard Device Consumer Control: always reports core 
events
[

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

2021-05-19 Thread bugproxy

--- Comment From naynj...@ibm.com 2021-05-19 16:51 EDT---
(In reply to comment #28)
> @Nayna Jain @Daniel
>
> Hm but we have CONFIG_LOAD_PPC_KEYS=y already which I would expect to be
> the only thing that loads keys into .platform keyring which was enabled as
> part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866909
> LTC-184073 . Which keys are present in firmware / get loaded into .platform
> because of that? I would have expected canonical keys to be loaded by that
> into the .platform keyring, or is that not the case?

Hi,

Yes you are right that CONFIG_LOAD_PPC_KEYS enables loading of keys into
.platform keyring from firmware at runtime. However, as Daniel has
mentioned in his comment dated 2020-12-17 , that the .platform keyring
is currently not loaded in pseries firmware as it is static keys based
solution and at the moment doesn't have any mechanism to expose trusted
keys (this will change with the full key management solution).

>
> Can you please share contents of "powerpc:db"? Ideally it should contain
> Canonical's two OPAL signing certs.
>

> If canonical keys are not in "powerpc:db", does it make sense to then add
> the two Canonical keys to the .builtin_trusted_keys_keyring, and then link
> the whole keyring into .ima keyring?
>
> I will attach the two Canonical OPAL signing keys here, and the ESL for them.

The final conclusion was to add a config option for PLATFORM KEYRING
similar to SYSTEM_TRUSTED_KEYS mechanism. It would allow loading
additional keys compiled into the kernel to be loaded only to .platform
keyring.  This would be in addition to the existing support for loading
firmware keys at runtime on the platfom keyring. It aligns with xnox
comment dated "2012-03-18".

At some point we will probably close the loop hole that allows self
signed certificates loaded onto the builtin keyring to be loaded onto
the IMA keyring.   It's better to define a mechanism for loading
additional certs on the platform keyring that would work today and will
continue to work in the future.

I am supposed to start looking at the patches. I would be starting to
look at them in June timeframe.

Thanks & Regards,
- Nayna

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

Title:
  Power guest secure boot with static keys: kernel portion

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

Bug description:
  == Comment: #2 - Daniel John Axtens  - 2020-11-05 
20:15:10 ==
  This is the kernel side of changes needed for LPAR/guest secure boot.

  Because Ubuntu keeps its kernels so wonderfully up to date, I don't
  think there are any extra patches you need to pick up. (I'll double-
  check against the 21.04 tree once my git pulls finish!)

  However, we potentially need some configuration changes to make sure
  kexec-ing into a crashdump kernel still works.

  Because Lockdown requires that kexec kernels are signed by a key
  trusted by IMA, the public key for used for signing the kdump kernel
  needs to be in the IMA keyring or the platform keyring. For host
  secure boot (and in the UEFI case), it's loaded into the platform
  keyring. But in the case of guest secure boot with static keys, it's
  not loaded into the platform keyring so it needs to be loaded into the
  IMA keyring.

  This is easy enough to do. Firstly, load the Secure Boot CA into the
  .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS
  property. We assume the key used to sign the kernel is signed by this
  CA.

  Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the 
.primary_trusted_keys keyring to be loaded into the IMA keyring. Then set 
IMA_X509_PATH to provide a path to the signing key on installed file system. 
(It may also be possible to do this step in userspace, so long as the CA is 
trusted by the kernel.)
   
  Then that key will be loaded into the .ima keyring at boot and be used to 
appraise the kexec kernel for crashdumps.

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

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

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

2021-05-19 Thread Henrik Juul Hansen

@Koba
I tried kernel 5.13.0-051300rc2-generic. After boot d3cold_allowed was "1", 
ASPM L1 enabled for nvme (and bluetooth did not work). After suspend/resume 
ASPM L1 was disabled for nvme. Power consumption higher. dmesg is attached.

** Attachment added: "dmesg-koba-5.13.0.rc2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5498809/+files/dmesg-koba-5.13.0.rc2.txt

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)

2021-05-19 Thread sharanappa1955

I have problem with webcam which is not showing any picture

** Changed in: libv4l (Ubuntu)
 Assignee: yanuar (dreamerthe12) => sharanappa1955 (sharanappa1955)

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

Title:
  cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show
  v4l2 video output and disables output on gstreamer-based apps ran
  afterwards)

Status in Cheese:
  Unknown
Status in Release Notes for Ubuntu:
  Invalid
Status in cheese package in Ubuntu:
  Invalid
Status in gstreamer0.10 package in Ubuntu:
  Invalid
Status in libv4l package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cheese source package in Intrepid:
  Invalid
Status in gstreamer0.10 source package in Intrepid:
  Invalid
Status in libv4l source package in Intrepid:
  Invalid
Status in linux source package in Intrepid:
  Fix Released

Bug description:
  Binary package hint: cheese

  == Regression details ==
  Discovered in version: 8.10RC
  Last known good version: 8.04.1

  gstreamer-based apps (gstreamer-properties, cheese) doesn't show the
  v4l2 video output.

  cheese can configure webcam (Dell Inspiron integrated webcam) but it
  does not provide any output. after some time the apps hang.

  
  vlc can play with the webcam (including sound).

  the hardware:

  [   11.835433] uvcvideo: Found UVC 1.00 device Laptop Integrated Webcam 
(05a9:2640)
  [   11.835731] uvcvideo: Failed to query (135) UVC control 1 (unit 0) : -32 
(exp. 26).
  [   11.893113] input: Laptop Integrated Webcam as 
/devices/pci:00/:00:1a.7/usb3/3-1/3-1:1.0/input/input11
  [   12.025138] usbcore: registered new interface driver uvcvideo

  
  Steps to Reproduce it:

  1.- Start ekiga, you should get local video
  2.- Start gstreamer-properties, you should get video at the tab and video 
test button
  3.- Start cheese and it would hang after a while
  4.- Kill cheese, remove the uvcvideo (most probably this would happen with 
other modules, pwc, gspca) driver and reload it again
  5.- Try again with ekiga or gstreamer-properties, it would work
  6.- Start cheese, go to properties and configure to the lowest resolution 
available. Cheese would hang, kill it and it would start again.  
  Now you've got low resolution video

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

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

[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi

2021-05-19 Thread William Wilson

This debdiff corrects the accidentally left in debug statement and adds
`optimize=-lto` to DEB_BUILD_MAINT_OPTIONS. Tests are succeeding again.

** Patch added: "lp1912371_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5498808/+files/lp1912371_v2.debdiff

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

Title:
  [MIR] flashrom + libftdi

Status in flashrom package in Ubuntu:
  New
Status in libftdi package in Ubuntu:
  New

Bug description:
  [Summary]
  Further review will be needed. The Package does not have a test suite that 
runs as autopkgtest.

  [Availability]
  Currently in universe.

  [Duplication]
  There is no other package in main providing the same functionality.

  [Rationale]
  fwupd depends on libflashrom1 for its flashrom plugin, something that's 
required to update Coreboot firmware.

  [Security]
  No CVE's, but due to the nature of the package security should review.

  [Quality Assurance]
  Package builds and runs easily

  [Dependencies]
  N/A

  [Standards Compliance]
  Complies with FHS, though the organization of files in the source package 
could be organized better.

  [Common blockers]
  flashrom does NOT have a test suite that runs at build time.
  flashrom does NOT have a test suite that runs as autopkgtest.

  [Maintenance]
  Actively maintained - https://github.com/flashrom/flashrom
  Packaging - https://salsa.debian.org/myczko-guest/flashrom.git

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

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

[Kernel-packages] [Bug 1928788] Re: linux-azure: Add Mana network driver

2021-05-19 Thread Tim Gardner

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

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

Title:
  linux-azure: Add Mana network driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Invalid
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Invalid
Status in linux-azure source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of the "mana" driver from Linux v5.11
  https://canonical.my.salesforce.com/5004K05pZQCQA2

  [Fix]

  This patch set consists of 5 patches that are now in mainline.

  The patches add the VF driver for Microsoft Azure Network Adapter
  (MANA), and also changes the hv_netvsc driver's netvsc/VF binding
  logic to check both the MAC address and the serial number (this is
  required by the MANA VF driver).

  Microsoft would like to request the following 5 patches in all
  supported releases:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=64ff412ad41fe3a5bf759ff4844dc1382176485c

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

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  next.git/commit/?id=55cdc26a91ac270887583945aef2bd460a2805f7

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  next.git/commit/?id=45b102dd81491e30ac7596b5515856141f99319f

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

  [Test Plan]

  2021-05-17 15:25 UTC-
  -We tested the two versions of mana.ko:

  root@decui-u2004-vf:~# uname -a
  Linux decui-u2004-vf 5.4.0-1048-azure #50~sf00310147.1-Ubuntu SMP Tue May 11 
02:06:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  root@decui-u2004-vf:~# modinfo mana | grep filename
  filename: 
/lib/modules/5.4.0-1048-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko

  root@decui-u2004-vf:~# uname -a
  Linux decui-u2004-vf 5.8.0-1032-azure #34~SF00310147.1-Ubuntu SMP Tue May 11 
02:01:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  root@decui-u2004-vf:~# modinfo mana | grep filename
  filename: 
/lib/modules/5.8.0-1032-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko

  Everything worked as expected in our testing:
  1. The MANA driver loads and unloads multiple times without any issue.
  2. iperf TX/RX tests run without any issue, and the performance numbers are 
on par with what we get with the latest mainline kernel: the TX number is 
pretty good; the RX number is sometimes not great but this is a known issue 
with the latest mainline kernel as well.
  3. "ethtool -S" and "ethtool -L" work as expected.
  4. When iperf TX/RX tests are running, changing the number of the MANA NIC 
TX/RX queues and unloading/reloading the MANA driver work without any issue.

  [Where problems could occur]

  The driver may have bug(s) that cause a kernel crash.

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

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

[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations

2021-05-19 Thread Evan Hoffman

Is there any ETA on a supported kernel with this patch?

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

Title:
  raid10: Block discard is very slow, causing severe delays for mkfs and
  fstrim operations

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1896578

  [Impact]

  Block discard is very slow on Raid10, which causes common use cases
  which invoke block discard, such as mkfs and fstrim operations, to
  take a very long time.

  For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe
  devices which support block discard, a mkfs.xfs operation on Raid 10
  takes between 8 to 11 minutes, where the same mkfs.xfs operation on
  Raid 0, takes 4 seconds.

  The bigger the devices, the longer it takes.

  The cause is that Raid10 currently uses a 512k chunk size, and uses
  this for the discard_max_bytes value. If we need to discard 1.9TB, the
  kernel splits the request into millions of 512k bio requests, even if
  the underlying device supports larger requests.

  For example, the NVMe devices on i3.8xlarge support 2.2TB of discard
  at once:

  $ cat /sys/block/nvme0n1/queue/discard_max_bytes
  2199023255040
  $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes
  2199023255040

  Where the Raid10 md device only supports 512k:

  $ cat /sys/block/md0/queue/discard_max_bytes
  524288
  $ cat /sys/block/md0/queue/discard_max_hw_bytes
  524288

  If we perform a mkfs.xfs operation on the /dev/md array, it takes over
  11 minutes and if we examine the stack, it is stuck in
  blkdev_issue_discard()

  $ sudo cat /proc/1626/stack
  [<0>] wait_barrier+0x14c/0x230 [raid10]
  [<0>] regular_request_wait+0x39/0x150 [raid10]
  [<0>] raid10_write_request+0x11e/0x850 [raid10]
  [<0>] raid10_make_request+0xd7/0x150 [raid10]
  [<0>] md_handle_request+0x123/0x1a0
  [<0>] md_submit_bio+0xda/0x120
  [<0>] __submit_bio_noacct+0xde/0x320
  [<0>] submit_bio_noacct+0x4d/0x90
  [<0>] submit_bio+0x4f/0x1b0
  [<0>] __blkdev_issue_discard+0x154/0x290
  [<0>] blkdev_issue_discard+0x5d/0xc0
  [<0>] blk_ioctl_discard+0xc4/0x110
  [<0>] blkdev_common_ioctl+0x56c/0x840
  [<0>] blkdev_ioctl+0xeb/0x270
  [<0>] block_ioctl+0x3d/0x50
  [<0>] __x64_sys_ioctl+0x91/0xc0
  [<0>] do_syscall_64+0x38/0x90
  [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Xiao Ni has developed a patchset which resolves the block discard
  performance problems. These commits have now landed in 5.13-rc1.

  commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:43 2021 +0800
  Subject: md: add md_submit_discard_bio() for submitting discard bio
  Link: 
https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8

  commit c2968285925adb97b9aa4ede94c1f1ab61ce0925
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:44 2021 +0800
  Subject: md/raid10: extend r10bio devs to raid disks
  Link: 
https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925

  commit f2e7e269a7525317752d472bb48a549780e87d22
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:45 2021 +0800
  Subject: md/raid10: pull the code that wait for blocked dev into one function
  Link: 
https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22

  commit d30588b2731fb01e1616cf16c3fe79a1443e29aa
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:46 2021 +0800
  Subject: md/raid10: improve raid10 discard request
  Link: 
https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa

  commit 254c271da0712ea8914f187588e0f81f7678ee2f
  Author: Xiao Ni 
  Date:   Thu Feb 4 15:50:47 2021 +0800
  Subject: md/raid10: improve discard request for far layout
  Link: 
https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f

  There is also an additional commit which is required, and was merged
  after "md/raid10: improve raid10 discard request" was merged. The
  following commit enables Radid10 to use large discards, instead of
  splitting into many bios, since the technical hurdles have now been
  removed.

  commit ca4a4e9a55beeb138bb06e3867f5e486da896d44
  Author: Mike Snitzer 
  Date:   Fri Apr 30 14:38:37 2021 -0400
  Subject: dm raid: remove unnecessary discard limits for raid0 and raid10
  Link: 
https://github.com/torvalds/linux/commit/ca4a4e9a55beeb138bb06e3867f5e486da896d44

  The commits more or less cherry pick to the 5.11, 5.8, 5.4 and 4.15
  kernels, with the following minor backports:

  1) submit_bio_noacct() needed to be renamed to generic_make_request()
  since it was recently changed in:

  commit ed00aabd5eb9fb44d6aff1173234a2e911b9fead

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-05-19 Thread Martin Pecka

Ah, you're right. I expected there should be a metapackage linux-5.12.4,
but now I see I have to install the respective packages like linux-
header-5.12.4* etc. Thanks!

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1928394] Re: CONFIG_LATENCYTOP should be disabled

2021-05-19 Thread Kelsey Skunberg

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

Title:
  CONFIG_LATENCYTOP should be disabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-raspi2 source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  There were some recent changes on the main kernels to fix some syntax
  issues with the annotations files (Propagate "Update annotations and
  fix errors" to all derivatives), after I replicated the changes from
  bionic/linux to bionic/linux-raspi2 I started getting this enforcement
  error:

  check-config: FAIL (y != n): CONFIG_LATENCYTOP policy<{'amd64-generic': 'n', 
'amd64-lowlatency': 'y', 'arm64': 'n', 'armhf': 'n', 'i386': 'n', 'ppc64el': 
'n', 's390x': 'n'}> mark 
note
  It seems we were supposed to have the same enforcement as the main kernel (= 
n) but the raspi2 config has it actually enabled.

  Looking at the url and the bug reference on the enforcement notes, it
  seems it doesn't make much sense to keep it enabled for non-lowlatency
  kernels.

  @juerghaefliger confirmed we should disable this option:

  Yes, it should be disabled. I did the same for hirsute earlier this year 
after Seth fixed the master config annotations:
  ~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/hirsute - [no description]

  If I remember correctly I made some other config changes due to Seth's
  changes.

  [Test Plan]

  Install latencytop, try to run the tool.

  [Where problems could occur]

  Disabling this config removes information that userspace might depend
  on.

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

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

[Kernel-packages] [Bug 1925241] Re: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2

2021-05-19 Thread Kleber Sacilotto de Souza

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

Title:
  Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT,
  CONFIG_I2C_AMD_MP2

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

Bug description:
  
  SRU Justification:

  Enforcement annotations indicate that these config options should
  never have been set.

  [Impact]

  Disable these options for hardware that does not exist in the Google
  cloud fabric. There should be no impact to existing users.

  [Fix]

  CONFIG_DELL_SMBIOS_SMM=n
  CONFIG_DELL_UART_BACKLIGHT=n
  CONFIG_I2C_AMD_MP2=n

  [Test Plan]

  Boot a GCP instance and ensure there are no new kernel log errors.

  [Where problems could occur]

  Regression potential should be low since this HW does not exists in a
  GCP guest instance.

  [Other Info]

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

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-05-19 Thread tuxinvader

@peci1 there's nothing to stop you adding my focal ppa to your bionic
system. The apt-add tool might refuse to add it, but you can manually
create the ppa.list file yourself if it does?

Create: /etc/apt/sources.list.d/mainline-ppa.list with the below content

deb http://ppa.launchpad.net/tuxinvader/lts-mainline/ubuntu focal main 
deb-src http://ppa.launchpad.net/tuxinvader/lts-mainline/ubuntu focal main

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"

2021-05-19 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-groovy

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

Title:
  Enable BLK_DEV_NVME =y to support "shielded VM minimal images"

Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp-4.15 package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Invalid
Status in linux-gcp-4.15 source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Focal:
  Fix Committed
Status in linux-gcp-4.15 source package in Focal:
  Invalid
Status in linux-gcp source package in Groovy:
  Fix Committed
Status in linux-gcp-4.15 source package in Groovy:
  Invalid
Status in linux-gcp source package in Hirsute:
  Fix Committed
Status in linux-gcp-4.15 source package in Hirsute:
  Invalid

Bug description:
  This is requested by CPC -- see the title.

  [Impact]
  nvme.ko exists outside the kernel currently

  [Fix]
  Enable BLK_DEV_NVME=y 

  [Test]
  Tested by CPC crew / Google: 

  > The test images have passed testing and we would like this enabled so we
  > can have minimal images boot with NVME boot disk and so we can enable
  > GCE confidential VMs with minimal images.

  
  [Regression Potential]
  Not aware of any.

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

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

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

2021-05-19 Thread Ubuntu Kernel Bot

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

apport-collect 1928950

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

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

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

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

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

Title:
  ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mind
  19.3)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug/Regression introduced between 5.4.0-73 and 5.4.0-72 (-72 and all previous 
kernels installed by Mint 19.3 had no problems).
  Happens whether docked or undocked.
  Might relate to Bug #1928530.
  System tells to do a journalctl -xb, but I couldn't spot if there's something 
relevant.
  I'll collect the logs twice to help find the difference (one from -73 panic 
shell and one from -72 normally booted).

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

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

[Kernel-packages] [Bug 1928594] Re: Setting up encrypted swap causes ordering cycle

2021-05-19 Thread Dan Streetman

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

** This bug has been marked a duplicate of bug 1875577
   Encrypted swap won't load on 20.04 with zfs root

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

Title:
  Setting up encrypted swap causes ordering cycle

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  root@home:~# cat /etc/crypttab
  # 
  cswap /dev/disk/by-partuuid/95605326-e210-4e13-9f93-50cc3d556aca /dev/urandom 
cipher=aes-xts-plain64,size=256,hash=sha1,swap

  root@home:~# update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic
  cryptsetup: WARNING: Resume target cswap uses a key file

  After reboot:

  root@home:~# systemctl status systemd-random-seed.service
  ● systemd-random-seed.service - Load/Save Random Seed
   Loaded: loaded (/lib/systemd/system/systemd-random-seed.service; static; 
vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:systemd-random-seed.service(8)
   man:random(4)

  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
ordering cycle on systemd-random-seed.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-mount.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import-cache.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/efi.img
  CasperMD5CheckResult: fail
  Date: Sun May 16 18:40:45 2021
  InstallationDate: Installed on 2021-01-21 (115 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 6: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=screen.xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=7c964d4b-ef4d-40df-b297-631e4233f297 ro bootdegraded=true 
transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3801
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor:

[Kernel-packages] [Bug 1928950] [NEW] ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mind 19.3)

2021-05-19 Thread Sandra-Asja

Public bug reported:

Bug/Regression introduced between 5.4.0-73 and 5.4.0-72 (-72 and all previous 
kernels installed by Mint 19.3 had no problems).
Happens whether docked or undocked.
Might relate to Bug #1928530.
System tells to do a journalctl -xb, but I couldn't spot if there's something 
relevant.
I'll collect the logs twice to help find the difference (one from -73 panic 
shell and one from -72 normally booted).

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

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

Title:
  ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mind
  19.3)

Status in linux package in Ubuntu:
  New

Bug description:
  Bug/Regression introduced between 5.4.0-73 and 5.4.0-72 (-72 and all previous 
kernels installed by Mint 19.3 had no problems).
  Happens whether docked or undocked.
  Might relate to Bug #1928530.
  System tells to do a journalctl -xb, but I couldn't spot if there's something 
relevant.
  I'll collect the logs twice to help find the difference (one from -73 panic 
shell and one from -72 normally booted).

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

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

[Kernel-packages] [Bug 1928808] Re: Requiring extra device ID for nvidia-driver-460

2021-05-19 Thread Alberto Milone

** Changed in: nvidia-drivers-ubuntu
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** No longer affects: nvidia-drivers-ubuntu

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Requiring extra device ID for nvidia-driver-460

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged

Bug description:
  There are some new nvidia graphics could be supported by nvidia-driver-460.
  Here are the list:
  1fb1 (Nvidia T600)
  2231 (Nvidia RTX A5000)
  24b7 (Nvidia RTX A4000 mobile)
  24b8 (Nvidia RTX A3000 mobile)
  25b8 (Nvidia RTX A2000 mobile)

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

https://lists.linux.it/pipermail/ltp/2021-May/022765.html

It was tested to work after that change.

Cascardo.

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-05-19 Thread Martin Pecka

@tuxinvader Could you please also set up a bionic PPA? I manually
download the DEBs and install them on Bionic and everything works fine.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

OK. It fails on 4.15. The overcommit logic has changed between 5.1 and
5.2-rc1 with the following commit:

8c7829b04c523cdc732cb77f59f03320e09f3386 ("mm: fix false-positive
OVERCOMMIT_GUESS failures").

Compared to the new logic, the old one is overly complicated, and not
easy to account on the test itself. Allocating half the memory should
probably be enough for the test purpose.

Cascardo.

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

mmap1.c:257: TPASS: System survived.

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

$ head -1 /proc/meminfo
MemTotal:2032728 kB

$ uname -r
5.4.0-1048-aws

On a t2.small instance. But, hey, this is a 5.4 kernel. Will install a
4.15 kernel on this bionic instance.

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

commit 4021854176a1f84d0990c51e88ddd6b2d901a7fe
Author: Bogdan Lezhepekov 
Date:   Wed Dec 30 19:36:15 2020 +0300

mtest06/mmap1: Limit distant mmap size

Limit the distant mmap size by a total memory value.

Signed-off-by: Bogdan Lezhepekov 
Acked-by: Li Wang 

This should have been fixed by this LTP commit. Tested on t2.small with
a 5.4 kernel. I'll try with a 4.15 kernel.

Cascardo.

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

2021-05-19 Thread danmb

Running fine on 5.10.36 from tuxinvader's
https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline-longterm
(mentioned above).

Mainline PPA official packages still broken on focal, 5.10.38 is coming
up.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

2021-05-19 Thread Marcelo Cerri

Hi, Gauthier and Gauthier.

I'm marking linux-azure as invalid for now. If something changes please
let us know. Thank you.

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

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions

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

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

2021-05-19 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2021-05-19 07:18 EDT---
IBM Response:
Yes. this makes sense. Previously Canonical reverted the "s390/cio: remove pm 
support from ccw bus driver" patch because of the issue. Right solution is to 
unrevert the revert-patch and add "s390/cio: remove invalid condition on 
IO_SCH_UNREG" patch. Which makes both available in the kernel.

So, we agree on this.

In stable 5.13-rc1, we have both the patches. Which is same as 5.11.20
for 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/1925211

Title:
  Hot-unplug of disks leaves broken block devices around in Hirsute on
  s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in systemd source package in Hirsute:
  Invalid
Status in udev source package in Hirsute:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Hot removal of disks under kvm on s390 does not result in the kernel
  removing the block device, which can lead to hung tasks and other
  issues.

  [Test Plan]

  See steps to reproduce the bug in the original description below. To
  test, execute these steps and confirm that the block device gets
  removed as expected.

  [Where problems could occur]

  The fix is a revert of the changes which introduced this regression.
  The original commit was a removal of supposedly unused code, but it
  seems a mistake was made in the logic around unregistering of disks.
  Reverting the changes could have potential to introduce bugs related
  to other virt devices, especially if it interacts badly with
  subsequent driver changes. However, the patch reverted cleanly, and
  reverting restores the code to the state which has been working well
  in previous kernels and seems like the lowest risk option until a
  proper fix is available upstream.

  ---

  Repro:
  #1 Get a guest
  $ uvt-kvm create --disk 5  --password=ubuntu h release=hirsute arch=s390x 
label=daily
  $ uvt-kvm wait h release=hirsute arch=s390x label=daily

  #2 Attach and Detach disk
  $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M
  $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
  $ virsh detach-disk h vdc

  From libvirts POV it is gone at this point
  $ virsh domblklist h
   Target   Source
  --
   vda  /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow
   vdb  /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow

  But the guest thinks still it is present
  $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk
    ...
    vdc252:32   0   20M  0 disk

  This even remains a while after (not a race).

  Any access to it in the guest will hang (as you'd expect of a non-existing 
blockdev)
  4 017581739  20   0  12140  4800 -  S+   pts/0  0:00  |   
\_ sudo mkfs.ext4 /dev/vdc
  4 017591758  20   0   6924  1044 -  D+   pts/0  0:00  |   
\_ mkfs.ext4 /dev/vdc

  The result above was originally found with hirsute-guest@hirsute-host
  on s390x

  I do NOT see the same with  groovy-guest@hirsute-host on s390x
  I DO see the same with hirsute-guest@groovy-host on s390x
    => Guest version dependent not Host/Hipervisor dependent
  I DO see the same with ZFS disks AND LVM disks being added
    => not type dependent
  I do NOT see the same on x86.
    => Arch dependent ??

  ... the evidence slowly points towards an issue in the guest, damn we are so
  close to release - but non-fully detaching disks are critical in my POV :-/

  Filing this as-is for awareness, but certainly this will need more debugging.
  Unsure where this is going to eventually I'll now file it for 
kernel/udev/systemd.
  If there are any known issues/components that are related let me know please!
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: udev
  PackageArchitecture: s390x
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen

No luck with 5.13rc2. I'm attaching another prevboot in case it is of
help.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498738/+files/prevboot.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928183] Re: turbostat doesn't work with AMD Cezanne APUs

Hello,
thanks for the bug report, can you give this 5.11 Hirsute kernel a try?
https://people.canonical.com/~phlin/kernel/lp-1928183-turbostat-cezanne/

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

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

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

Title:
  turbostat doesn't work with AMD Cezanne APUs

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985681 describes the
  issue and necessary cherry-pick
  (https://git.kernel.org/linus/301b1d3a9104f4f3a8ab4171cf88d0f55d632b41).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-tools-common 5.11.0-17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartle 2287 F pulseaudio
   /dev/snd/controlC0:  bartle 2287 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 12 01:04:15 2021
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=27b86d91-8e89-49da-ad17-45901581ce2f ro
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (19 days ago)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.10
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd04/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)

2021-05-19 Thread João Bárcia

I agree with Herczeg. This is likely a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924685

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

Title:
sounds not working on Dell XPS 17 (9700)

Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Fix Released

Bug description:
My investigation process:

Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
worked.

I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm
headphones,
using linux-image-5.4.0-42-generic, I did not try blutooth.

I sudo apt upgrade, dist-upgrade to get kernels

linux-image-5.8.0-38-generic
linux-image-5.8.0-40-generic

Sounds did not work.
I download linux-image-unsigned-5.10.9-051009-generic.
Sounds did not work.

I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
Sounds did not work.

After googling I found this solution in the comments:
https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

"""

Download and install dkms module:

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
dkms/+packages

Alternatively, you can install linux-oem-20.04, it will install
the 5.6 kernel with the above driver. Your system may be more stable
with 5.4 kernel since it is in wide use.

Manually install sof-firmware from Arch Linux:

https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
firmware-1.5.1-1-any.pkg.tar.zst.html

You will need to delete the existing "sof" and "sof-tplg" files
from the Ubuntu linux-firmware package first. Note if this package
gets updated from Canoncial and they don't update these, you will have
to delete and then reextract. Files go into the
/usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg
folders.

Manually install the ucm2 files:

http://xps17.ddns.net/sof-soundwire.zip

These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
contents of the existing sof-soundwire folder (if you have it) and
replace them with the ones from the archive.

Reboot. You should now have all your audio devices available. If speakers
do not play, you may need to run alsamixer (non-root) from a terminal and
unmute and set the mixer levels all the way up.
"""

This solution worked for me on linux-image-5.6.0-1042-oem AFTER
manually opening alsa-mixer and changing soundcard to sof. The sound
would otherwise just show 'dummy'.

My sounds still do not work on 5.8 or 5.10, full name listed above. I
did not get to test this temporary fix with 5.4.

my full alsa-info:
http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

based on some google research, this seems to be a common problem:

https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/

https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/

https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
etc...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
Uname: Linux 5.6.0-1042-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: neoh 1786 F pulseaudio
/dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio
/dev/snd/controlC0: neoh 1786 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 12:08:45 2021
InstallationDate: Installed on 2021-01-20 (1 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=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Dependencies:

DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
NonfreeKernelModules: nvidia_modeset nvidia

[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04

2021-05-19 Thread João Bárcia

Same here. Would be great to have an estimated release date.

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

Title:
  No sound output/input available after installing 21.04

Status in OEM Priority Project:
  Won't Fix
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Image: Hirsute 21.04 (20210415 daily build)

  Device: Dell Precision 5750

  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .

  The only way to hear sound is to connect a Bluetooth speaker.

  Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

  https://certification.ubuntu.com/hardware/202002-27726

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1928774] Re: RTL8188EE Wireless Network Adapter not supported

2021-05-19 Thread Juerg Haefliger

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

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

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

Title:
  RTL8188EE Wireless Network Adapter not supported

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Focal:
  In Progress
Status in linux-raspi source package in Groovy:
  In Progress
Status in linux-raspi source package in Hirsute:
  In Progress
Status in linux-raspi source package in Impish:
  Invalid

Bug description:
  [Impact]

  PCIe NIC is not recognized:

  $ sudo lspci -nn -k -v
  00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2711] 
(rev 20) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 41
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: -0fff [size=4K]
Memory behind bridge: f800-f80f [size=1M]
Prefetchable memory behind bridge: [disabled]
Capabilities: [48] Power Management version 3
Capabilities: [ac] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [180] Vendor Specific Information: ID= Rev=0 Len=028 

Capabilities: [240] L1 PM Substates
Kernel driver in use: pcieport

  01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188EE 
Wireless Network Adapter [10ec:8179] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network 
Adapter [10ec:8197]
Flags: fast devsel, IRQ 255
I/O ports at  [disabled]
Memory at 6 (64-bit, non-prefetchable) [disabled] [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-e0-4c-ff-fe-81-91-01
Capabilities: [150] Latency Tolerance Reporting

  [Test Case]

  $ ls /sys/class/net/
  eth0  lo

  [Where Problems Could Occur]

  The usual, when new modules are enabled. Crashes and/or splats due to
  buggy modules.

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Oracle kernel has Android related config options disabled

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

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

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

Title:
  Oracle kernel has Android related config options disabled

Status in linux-oracle package in Ubuntu:
  Confirmed

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-oracle/+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 1928600] ProcCpuinfo.txt

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928600] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1928600/+attachment/5498713/+files/acpidump.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928600] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1928600/+attachment/5498702/+files/Lsusb-t.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928600] AudioDevicesInUse.txt

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1928600/+attachment/5498696/+files/AudioDevicesInUse.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928600] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1928600/+attachment/5498703/+files/Lsusb-v.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen

apport information

** Tags added: apport-collected

** Description changed:

  With this hardware configuration this issue has been a problem only when
  suspending or resuming from suspend under 20.04. Having decided to
  upgrade through 20.10 to 21.04 to see if things improve enough to help
  me identify which package to report a bug against things have become
  significantly worse.
  
  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank screen
  or one with artefacts on, or it would start the resume and then lock.
  
  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved initially
  - including notably improved boot times (no idea if that is related).
  After a bit of checking things out I went to enable the PPAs that had
  been disabled (Teamviewer, Nextcloud, Anydesk and Chrome - all of which
  have been installed after the problems were initially noted). When the
  window to authenticate popped up the screen filled with artefacts and I
  had to reset. After several attempts to reboot into a working desktop
  variously booting to artefacts, or getting artefacts immediately after
  logging in (usually when opening and maximising a terminal to capture
  the logs for later) I managed to change from Wayland to X.Org and logged
  in successfully with no problems for the rest of the day (including a
  Jitsi meeting lasting about 4 hours or more). The next day (today)
  suspend and resume is causing problems as before, boot has slowed down
  again (again, no idea if this is related).
  
  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).
  
  Key things I have noted:
  
  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2020-10-16 (214 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp34s0   no wireless extensions.
+ MachineType: Micro-Star International Co., Ltd. MS-7B79
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-17-generic N/A
+  linux-backports-modules-5.11.0-17-generic  N/A
+  linux-firmware 1.197
+ RfKill:
+  
+ Tags:  hirsute
+ Uname: Linux 5.11.0-17-generic x86_64
+ UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/06/2019
+ dmi.bios.release: 5.14
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: H.40
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
+ dmi.board.vendor: Micro-Star International Co., Ltd.
+ dmi.board.version: 3.0
+ dmi.chassis.asset.tag: To be filled by O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Micro-Star International Co., Ltd.
+ dmi.chassis.version: 3.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH.40:bd11/06/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: MS-7B79
+ dmi.product.sku: To be filled by O.E.M.
+ dmi.product.version: 3.0
+ dmi.sys.vendor: Micro-Star International Co., Ltd.

** Attachment added: "AlsaInfo.txt"

[Kernel-packages] [Bug 1928600] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1928600/+attachment/5498700/+files/Lspci-vt.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

[Kernel-packages] [Bug 1928600] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1928600/+attachment/5498704/+files/PaInfo.txt

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

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

apport information

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

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-10-16 (214 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   
  Tags:  hirsute
  Uname: Linux 5.11.0-17-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 3.0
  dmi.modalias:

Re: [Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi

2021-05-19 Thread Carl-Daniel Hailfinger

Hi,

I thought we had deactivated the github bugtracker because flashrom
development does not happen at github.
The github mirror of flashrom is there purely for people who are
unwilling or unable (due to corporate restrictions etc.) to download the
source code from our self-hosted git trees. I'll try to get the github
tracker deactivated to avoid giving people wrong impressions.

As Stefan wrote, you can reach the flashrom developers at
flash...@flashrom.org and you will also get attention if you send email
there.

Regards,
Carl-Daniel

Am 19.05.21 um 09:33 schrieb Stefan Tauner:
> On Wed, 19 May 2021 06:52:55 -
> Alex Murray <1912...@bugs.launchpad.net> wrote:
>
>> These failures of the mocked tests have been reported upstream at
>> https://github.com/flashrom/flashrom/issues/186 by others but no
>> response
> Hi there,
>
> I was the flashrom maintainer till a few years ago. While I was using
> the github repo+tracker, there is currently ~nobody taking care of that.
> A more promising way to reach the right people is to write an email to
> flash...@flashrom.org

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

Title:
  [MIR] flashrom + libftdi

Status in flashrom package in Ubuntu:
  New
Status in libftdi package in Ubuntu:
  New

Bug description:
  [Summary]
  Further review will be needed. The Package does not have a test suite that 
runs as autopkgtest.

  [Availability]
  Currently in universe.

  [Duplication]
  There is no other package in main providing the same functionality.

  [Rationale]
  fwupd depends on libflashrom1 for its flashrom plugin, something that's 
required to update Coreboot firmware.

  [Security]
  No CVE's, but due to the nature of the package security should review.

  [Quality Assurance]
  Package builds and runs easily

  [Dependencies]
  N/A

  [Standards Compliance]
  Complies with FHS, though the organization of files in the source package 
could be organized better.

  [Common blockers]
  flashrom does NOT have a test suite that runs at build time.
  flashrom does NOT have a test suite that runs as autopkgtest.

  [Maintenance]
  Actively maintained - https://github.com/flashrom/flashrom
  Packaging - https://salsa.debian.org/myczko-guest/flashrom.git

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

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

[Kernel-packages] [Bug 1928825] Re: Focal update: v5.4.118 upstream stable release

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

Title:
  Focal update: v5.4.118 upstream stable release

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

Bug description:
  SRU Justification

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

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

  s390/disassembler: increase ebpf disasm buffer size
  ACPI: custom_method: fix potential use-after-free issue
  ACPI: custom_method: fix a possible memory leak
  ftrace: Handle commands when closing set_ftrace_filter file
  ARM: 9056/1: decompressor: fix BSS size calculation for LLVM ld.lld
  arm64: dts: marvell: armada-37xx: add syscon compatible to NB clk node
  arm64: dts: mt8173: fix property typo of 'phys' in dsi node
  ecryptfs: fix kernel panic with null dev_name
  mtd: spinand: core: add missing MODULE_DEVICE_TABLE()
  mtd: rawnand: atmel: Update ecc_stats.corrected counter
  erofs: add unsupported inode i_format check
  spi: spi-ti-qspi: Free DMA resources
  scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand()
  scsi: mpt3sas: Block PCI config access from userspace during reset
  mmc: uniphier-sd: Fix an error handling path in uniphier_sd_probe()
  mmc: uniphier-sd: Fix a resource leak in the remove function
  mmc: sdhci: Check for reset prior to DMA address unmap
  mmc: sdhci-pci: Fix initialization of some SD cards for Intel BYT-based 
controllers
  mmc: block: Update ext_csd.cache_ctrl if it was written
  mmc: block: Issue a cache flush only when it's enabled
  mmc: core: Do a power cycle when the CMD11 fails
  mmc: core: Set read only for SD cards with permanent write protect bit
  mmc: core: Fix hanging on I/O during system suspend for removable cards
  modules: mark ref_module static
  modules: mark find_symbol static
  modules: mark each_symbol_section static
  modules: unexport __module_text_address
  modules: unexport __module_address
  modules: rename the licence field in struct symsearch to license
  modules: return licensing information from find_symbol
  modules: inherit TAINT_PROPRIETARY_MODULE
  irqchip/gic-v3: Do not enable irqs when handling spurious interrups
  cifs: Return correct error code from smb2_get_enc_key
  btrfs: fix metadata extent leak after failure to create subvolume
  intel_th: pci: Add Rocket Lake CPU support
  posix-timers: Preserve return value in clock_adjtime32()
  fbdev: zero-fill colormap in fbcmap.c
  bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first
  staging: wimax/i2400m: fix byte-order issue
  spi: ath79: always call chipselect function
  spi: ath79: remove spi-master setup and cleanup assignment
  crypto: api - check for ERR pointers in crypto_destroy_tfm()
  crypto: qat - fix unmap invalid dma address
  usb: gadget: uvc: add bInterval checking for HS mode
  usb: webcam: Invalid size of Processing Unit Descriptor
  genirq/matrix: Prevent allocation counter corruption
  usb: gadget: f_uac2: validate input parameters
  usb: gadget: f_uac1: validate input parameters
  usb: dwc3: gadget: Ignore EP queue requests during bus reset
  usb: xhci: Fix port minor revision
  PCI: PM: Do not read power state in pci_enable_device_flags()
  x86/build: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS)
  tee: optee: do not check memref size on return from Secure World
  perf/arm_pmu_platform: Fix error handling
  usb: xhci-mtk: support quirk to disable usb2 lpm
  xhci: check control context is valid before dereferencing it.
  xhci: fix potential array out of bounds with several interrupters
  spi: dln2: Fix reference leak to master
  spi: omap-100k: Fix reference leak to master
  spi: qup: fix PM reference leak in spi_qup_remove()
  usb: musb: fix PM reference leak in musb_irq_work()
  usb: core: hub: Fix PM reference leak in usb_port_resume()
  tty: n_gsm: check error while registering tty devices
  intel_th: Consistency and off-by-one fix
  phy: phy-twl4030-usb: Fix possible use-after-free in twl4030_usb_remove()
  crypto: stm32/hash - Fix PM reference leak on stm32-hash.c
  crypto: stm32/cryp - Fix PM reference leak on stm32-cryp.c
  crypto: omap-aes - Fix PM reference leak on omap-aes.c
  platform/x86: intel_pmc_core: Don't use global pmcdev in quirks
  btrfs: convert logic BUG_ON()'s in replace_path to ASSERT()'s
  drm: Added orientation quirk for OneGX1 Pro
  drm/qxl: release shadow on shutdown

[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71

Patch came to 20.04/Focal via v5.4.117 stable.

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

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

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

Title:
  r8152 tx status -71

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

Bug description:
  I've bought ThinkPad T14s with a USB-based docking station. Everything
  is working marvelously, but from time to time the ethernet port on the
  docking station won't connect. I've discovered the following messages
  in my dmesg:

  [  400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

  Rebooting the machine doesn't seem to work, turning the ethernet
  connection off and on doesn't seem to work. I have a dualboot
  Linux+Windows (one wants to play games from time to time :-p ) and it
  could be that rebooting from Win to Lin causes this issue, but this
  needs to be confirmed yet. I will try to power off the computer and/or
  the docking station, to see whether that would help.

  I've found numerous bug reports, but they are rather old or may not
  apply to this situation, therefore I figured it's best to open a new
  bug report.

  Thank you so much for your hard work!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 10:00:29 2021
  InstallationDate: Installed on 2021-03-24 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20UH001QMX
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic 
root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2020
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET61W(1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UH001QMX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.30
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UH001QMX
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1927997] Re: Focal update: v5.4.115 upstream stable release

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

Title:
  Focal update: v5.4.115 upstream stable release

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

Bug description:
  SRU Justification

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

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

  gpio: omap: Save and restore sysconfig
  pinctrl: lewisburg: Update number of pins in community
  arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS
  perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3
  perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[]
  perf auxtrace: Fix potential NULL pointer dereference
  HID: google: add don USB id
  HID: alps: fix error return code in alps_input_configured()
  HID: wacom: Assign boolean values to a bool variable
  ARM: dts: Fix swapped mmc order for omap3
  net: geneve: check skb is large enough for IPv4/IPv6 header
  s390/entry: save the caller of psw_idle
  xen-netback: Check for hotplug-status existence before watching
  cavium/liquidio: Fix duplicate argument
  csky: change a Kconfig symbol name to fix e1000 build error
  ia64: fix discontig.c section mismatches
  ia64: tools: remove duplicate definition of ia64_mf() on ia64
  x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
  net: hso: fix NULL-deref on disconnect regression
  USB: CDC-ACM: fix poison/unpoison imbalance
  Linux 5.4.115
  UBUNTU: upstream stable to v5.4.115

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

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

[Kernel-packages] [Bug 1928823] Re: Focal update: v5.4.117 upstream stable release

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

Title:
  Focal update: v5.4.117 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mips: Do not include hi and lo in clobber list for R6
  ACPI: tables: x86: Reserve memory occupied by ACPI tables
  ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
  net: usb: ax88179_178a: initialize local variables before use
  igb: Enable RSS for Intel I211 Ethernet Controller
  iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
  bpf: Fix masking negation logic upon negative dst register
  bpf: Fix leakage of uninitialized bpf stack under speculation
  avoid __memcat_p link failure
  iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
  perf data: Fix error return code in perf_data__create_dir()
  perf ftrace: Fix access to pid in array when setting a pid filter
  ALSA: usb-audio: Add MIDI quirk for Vox ToneLab EX
  USB: Add LPM quirk for Lenovo ThinkPad USB-C Dock Gen2 Ethernet
  USB: Add reset-resume quirk for WD19's Realtek Hub
  platform/x86: thinkpad_acpi: Correct thermal sensor allocation
  scsi: ufs: Unlock on a couple error paths
  ovl: allow upperdir inside lowerdir
  perf/core: Fix unconditional security_locked_down() call
  vfio: Depend on MMU
  Linux 5.4.117
  UBUNTU: upstream stable to v5.4.117

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

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

[Kernel-packages] [Bug 1928821] Re: Focal update: v5.4.116 upstream stable release

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

Title:
  Focal update: v5.4.116 upstream stable release

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

Bug description:
  SRU Justification

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

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

  bpf: Move off_reg into sanitize_ptr_alu
  bpf: Ensure off_reg has no mixed signed bounds for all types
  bpf: Rework ptr_limit into alu_limit and add common error path
  bpf: Improve verifier error messages for users
  bpf: Refactor and streamline bounds check into helper
  bpf: Move sanitize_val_alu out of op switch
  bpf: Tighten speculative pointer arithmetic mask
  bpf: Update selftests to reflect new error states
  Linux 5.4.116
  UBUNTU: upstream stable to v5.4.116

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

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

[Kernel-packages] [Bug 1928857] Re: Hirsute update: v5.11.20 upstream stable release

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

Title:
  Hirsute update: v5.11.20 upstream stable release

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:

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

  bus: mhi: core: Fix check for syserr at power_up
  bus: mhi: core: Clear configuration from channel context during reset
  bus: mhi: core: Sanity check values from remote device before use
  bus: mhi: core: Add missing checks for MMIO register entries
  bus: mhi: pci_generic: Remove WQ_MEM_RECLAIM flag from state workqueue
  nitro_enclaves: Fix stale file descriptors on failed usercopy
  dyndbg: fix parsing file query without a line-range suffix
  s390/disassembler: increase ebpf disasm buffer size
  s390/zcrypt: fix zcard and zqueue hot-unplug memleak
  s390/vfio-ap: fix circular lockdep when setting/clearing crypto masks
  vhost-vdpa: fix vm_flags for virtqueue doorbell mapping
  tpm: acpi: Check eventlog signature before using it
  ACPI: custom_method: fix potential use-after-free issue
  ACPI: custom_method: fix a possible memory leak
  ftrace: Handle commands when closing set_ftrace_filter file
  ARM: 9056/1: decompressor: fix BSS size calculation for LLVM ld.lld
  arm64: dts: marvell: armada-37xx: add syscon compatible to NB clk node
  arm64: dts: mt8173: fix property typo of 'phys' in dsi node
  ecryptfs: fix kernel panic with null dev_name
  fs/epoll: restore waking from ep_done_scan()
  reset: add missing empty function reset_control_rearm()
  mtd: spi-nor: core: Fix an issue of releasing resources during read/write
  Revert "mtd: spi-nor: macronix: Add support for mx25l51245g"
  mtd: spinand: core: add missing MODULE_DEVICE_TABLE()
  mtd: rawnand: atmel: Update ecc_stats.corrected counter
  mtd: physmap: physmap-bt1-rom: Fix unintentional stack access
  erofs: add unsupported inode i_format check
  spi: stm32-qspi: fix pm_runtime usage_count counter
  spi: spi-ti-qspi: Free DMA resources
  libceph: bump CephXAuthenticate encoding version
  libceph: allow addrvecs with a single NONE/blank address
  scsi: qla2xxx: Reserve extra IRQ vectors
  scsi: lpfc: Fix rmmod crash due to bad ring pointers to abort_iotag
  scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand()
  scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES
  scsi: mpt3sas: Block PCI config access from userspace during reset
  mmc: uniphier-sd: Fix an error handling path in uniphier_sd_probe()
  mmc: uniphier-sd: Fix a resource leak in the remove function
  mmc: sdhci: Check for reset prior to DMA address unmap
  mmc: sdhci-pci: Fix initialization of some SD cards for Intel BYT-based 
controllers
  mmc: block: Update ext_csd.cache_ctrl if it was written
  mmc: block: Issue a cache flush only when it's enabled
  mmc: core: Do a power cycle when the CMD11 fails
  mmc: core: Set read only for SD cards with permanent write protect bit
  mmc: core: Fix hanging on I/O during system suspend for removable cards
  irqchip/gic-v3: Do not enable irqs when handling spurious interrups
  cifs: Return correct error code from smb2_get_enc_key
  cifs: fix out-of-bound memory access when calling smb3_notify() at mount point
  cifs: fix leak in cifs_smb3_do_mount() ctx
  cifs: detect dead connections only when echoes are enabled.
  cifs: fix regression when mounting shares with prefix paths
  smb2: fix use-after-free in smb2_ioctl_query_info()
  btrfs: handle remount to no compress during compression
  x86/build: Disable HIGHMEM64G selection for M486SX
  btrfs: fix metadata extent leak after failure to create subvolume
  intel_th: pci: Add Rocket Lake CPU support
  btrfs: fix race between transaction aborts and fsyncs leading to 
use-after-free
  posix-timers: Preserve return value in clock_adjtime32()
  fbdev: zero-fill colormap in fbcmap.c
  cpuidle: tegra: Fix C7 idling state on Tegra114
  bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first
  staging: wimax/i2400m: fix byte-order issue
  spi: ath79: always call chipselect function
  spi: ath79: remove spi-master setup and cleanup assignment
  bus: mhi: core: Destroy SBL devices when moving to mission mode
  bus: mhi: core: Process execution environment changes serially
  crypto: api - check for ERR pointers in

[Kernel-packages] [Bug 1928386] Re: Groovy update: upstream stable patchset 2021-05-13

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

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

Title:
  Groovy update: upstream stable patchset 2021-05-13

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-05-13

  Ported from the following upstream stable releases:
  v5.4.112, v5.10.30
  v5.4.113, v5.10.31

     from git://git.kernel.org/

  ALSA: aloop: Fix initialization of controls
  ALSA: hda/realtek: Fix speaker amp setup on Acer Aspire E1
  ALSA: hda/conexant: Apply quirk for another HP ZBook G5 model
  ASoC: intel: atom: Stop advertising non working S24LE support
  nfc: fix refcount leak in llcp_sock_bind()
  nfc: fix refcount leak in llcp_sock_connect()
  nfc: fix memory leak in llcp_sock_connect()
  nfc: Avoid endless loops caused by repeated llcp_sock_connect()
  selinux: make nslot handling in avtab more robust
  xen/evtchn: Change irq_info lock to raw_spinlock_t
  net: ipv6: check for validity before dereferencing cfg->fc_nlinfo.nlh
  net: dsa: lantiq_gswip: Let GSWIP automatically set the xMII clock
  net: dsa: lantiq_gswip: Don't use PHY auto polling
  net: dsa: lantiq_gswip: Configure all remaining GSWIP_MII_CFG bits
  drm/i915: Fix invalid access to ACPI _DSM objects
  ACPI: processor: Fix build when CONFIG_ACPI_PROCESSOR=m
  IB/hfi1: Fix probe time panic when AIP is enabled with a buggy BIOS
  LOOKUP_MOUNTPOINT: we are cleaning "jumped" flag too late
  gcov: re-fix clang-11+ support
  ia64: fix user_stack_pointer() for ptrace()
  nds32: flush_dcache_page: use page_mapping_file to avoid races with swapoff
  ocfs2: fix deadlock between setattr and dio_end_io_write
  fs: direct-io: fix missing sdio->boundary
  ethtool: fix incorrect datatype in set_eee ops
  of: property: fw_devlink: do not link ".*,nr-gpios"
  parisc: parisc-agp requires SBA IOMMU driver
  parisc: avoid a warning on u8 cast for cmpxchg on u8 pointers
  ARM: dts: turris-omnia: configure LED[2]/INTn pin as interrupt pin
  batman-adv: initialize "struct batadv_tvlv_tt_vlan_data"->reserved field
  ice: Increase control queue timeout
  ice: prevent ice_open and ice_stop during reset
  ice: remove DCBNL_DEVRESET bit from PF state
  ice: Fix for dereference of NULL pointer
  ice: Cleanup fltr list in case of allocation issues
  iwlwifi: pcie: properly set LTR workarounds on 22000 devices
  net: hso: fix null-ptr-deref during tty device unregistration
  libbpf: Fix bail out from 'ringbuf_process_ring()' on error
  bpf: Enforce that struct_ops programs be GPL-only
  bpf: link: Refuse non-O_RDWR flags in BPF_OBJ_GET
  ethernet/netronome/nfp: Fix a use after free in nfp_bpf_ctrl_msg_rx
  libbpf: Only create rx and tx XDP rings when necessary
  bpf, sockmap: Fix sk->prot unhash op reset
  net: ensure mac header is set in virtio_net_hdr_to_skb()
  i40e: Fix sparse warning: missing error code 'err'
  i40e: Fix sparse error: 'vsi->netdev' could be null
  i40e: Fix sparse errors in i40e_txrx.c
  net: sched: sch_teql: fix null-pointer dereference
  net: sched: fix action overwrite reference counting
  mac80211: fix TXQ AC confusion
  net: hsr: Reset MAC header for Tx path
  net-ipv6: bugfix - raw & sctp - switch to ipv6_can_nonlocal_bind()
  net: let skb_orphan_partial wake-up waiters.
  usbip: add sysfs_lock to synchronize sysfs code paths
  usbip: stub-dev synchronize sysfs code paths
  usbip: vudc synchronize sysfs code paths
  usbip: synchronize event handler with sysfs code paths
  driver core: Fix locking bug in deferred_probe_timeout_work_func()
  scsi: target: iscsi: Fix zero tag inside a trace event
  i2c: turn recovery error on init to debug
  ice: Refactor DCB related variables out of the ice_port_info struct
  ice: Recognize 860 as iSCSI port in CEE mode
  xfrm: interface: fix ipv4 pmtu check to honor ip header df
  xfrm: Use actual socket sk instead of skb socket for xfrm_output_resume
  regulator: bd9571mwv: Fix AVS and DVFS voltage range
  ARM: OMAP4: Fix PMIC voltage domains for bionic
  ARM: OMAP4: PM: update ROM return address for OSWR and OFF
  net: xfrm: Localize sequence counter per network namespace
  esp: delete NETIF_F_SCTP_CRC bit from features for esp offload
  ASoC: SOF: Intel: HDA: fix core status verification
  ASoC: wm8960: Fix

[Kernel-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x

Just as a heads up: The upstream stable update 5.11.20 for hirsute un-reverts
- "s390/cio: remove pm support from ccw bus driver"
and adds
- "s390/cio: remove invalid condition on IO_SCH_UNREG"

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

Title:
  Hot-unplug of disks leaves broken block devices around in Hirsute on
  s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in systemd source package in Hirsute:
  Invalid
Status in udev source package in Hirsute:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Hot removal of disks under kvm on s390 does not result in the kernel
  removing the block device, which can lead to hung tasks and other
  issues.

  [Test Plan]

  See steps to reproduce the bug in the original description below. To
  test, execute these steps and confirm that the block device gets
  removed as expected.

  [Where problems could occur]

  The fix is a revert of the changes which introduced this regression.
  The original commit was a removal of supposedly unused code, but it
  seems a mistake was made in the logic around unregistering of disks.
  Reverting the changes could have potential to introduce bugs related
  to other virt devices, especially if it interacts badly with
  subsequent driver changes. However, the patch reverted cleanly, and
  reverting restores the code to the state which has been working well
  in previous kernels and seems like the lowest risk option until a
  proper fix is available upstream.

  ---

  Repro:
  #1 Get a guest
  $ uvt-kvm create --disk 5  --password=ubuntu h release=hirsute arch=s390x 
label=daily
  $ uvt-kvm wait h release=hirsute arch=s390x label=daily

  #2 Attach and Detach disk
  $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M
  $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
  $ virsh detach-disk h vdc

  From libvirts POV it is gone at this point
  $ virsh domblklist h
   Target   Source
  --
   vda  /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow
   vdb  /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow

  But the guest thinks still it is present
  $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk
    ...
    vdc252:32   0   20M  0 disk

  This even remains a while after (not a race).

  Any access to it in the guest will hang (as you'd expect of a non-existing 
blockdev)
  4 017581739  20   0  12140  4800 -  S+   pts/0  0:00  |   
\_ sudo mkfs.ext4 /dev/vdc
  4 017591758  20   0   6924  1044 -  D+   pts/0  0:00  |   
\_ mkfs.ext4 /dev/vdc

  The result above was originally found with hirsute-guest@hirsute-host
  on s390x

  I do NOT see the same with  groovy-guest@hirsute-host on s390x
  I DO see the same with hirsute-guest@groovy-host on s390x
    => Guest version dependent not Host/Hipervisor dependent
  I DO see the same with ZFS disks AND LVM disks being added
    => not type dependent
  I do NOT see the same on x86.
    => Arch dependent ??

  ... the evidence slowly points towards an issue in the guest, damn we are so
  close to release - but non-fully detaching disks are critical in my POV :-/

  Filing this as-is for awareness, but certainly this will need more debugging.
  Unsure where this is going to eventually I'll now file it for 
kernel/udev/systemd.
  If there are any known issues/components that are related let me know please!
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: udev
  PackageArchitecture: s390x
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'

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

2021-05-19 Thread Ubuntu Kernel Bot

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

apport-collect 1928921

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

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

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

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

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

Title:
   LRMv5: switch primary version handling to kernel-versions data set

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  In Progress

Bug description:
  Switch fetching dkms-versions data for these packages to the kernel-
  versions dataset.

  Currently the primary dkms-versions data is committed directly to the
  primary kernel packages.  This allows this information to cascade
  reliably to all derivatives and their associated LRM packages.  But
  once the primaries are closed it is increasingly hard to change this
  data.  This makes performing an LRM-only respin very difficult as it
  differs in handling from a primary spin.

  We move the primary version dataset out of the kernel packages into a
  shared external "kernel-versions" dataset.  Each package which needs
  this data then obtains the information it needs directly, with it
  committed locally to that package at update time.

  This renders preparation of am initial (-1) spin and a later LRM-only
  respin identicle.  We simply update the shared dataset and perform a
  no-change rebuild (./update-versions) on them and they will
  automatically get the updated version information.

  We will want to update update-dkms-versions in all primary main
  packages, and introduce same into all LRM packages.  As we already run
  update-dkms-versions in the primary main packages, and are introducing
  update-dkms-versions handling to update-versions in LRM this should
  not change kernel crank proceedure.  The cycle proceedure will need a
  new step to update the shared kernel-versions dataset before cranking
  commences.

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

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

[Kernel-packages] [Bug 1928921] [NEW] LRMv5: switch primary version handling to kernel-versions data set

2021-05-19 Thread Andy Whitcroft

Public bug reported:

Switch fetching dkms-versions data for these packages to the kernel-
versions dataset.

Currently the primary dkms-versions data is committed directly to the
primary kernel packages.  This allows this information to cascade
reliably to all derivatives and their associated LRM packages.  But once
the primaries are closed it is increasingly hard to change this data.
This makes performing an LRM-only respin very difficult as it differs in
handling from a primary spin.

We move the primary version dataset out of the kernel packages into a
shared external "kernel-versions" dataset.  Each package which needs
this data then obtains the information it needs directly, with it
committed locally to that package at update time.

This renders preparation of am initial (-1) spin and a later LRM-only
respin identicle.  We simply update the shared dataset and perform a no-
change rebuild (./update-versions) on them and they will automatically
get the updated version information.

We will want to update update-dkms-versions in all primary main
packages, and introduce same into all LRM packages.  As we already run
update-dkms-versions in the primary main packages, and are introducing
update-dkms-versions handling to update-versions in LRM this should not
change kernel crank proceedure.  The cycle proceedure will need a new
step to update the shared kernel-versions dataset before cranking
commences.

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

** Affects: linux-restricted-modules (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Changed in: linux-restricted-modules (Ubuntu)
   Status: New => In Progress

** Changed in: linux-restricted-modules (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-restricted-modules (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

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

Title:
   LRMv5: switch primary version handling to kernel-versions data set

Status in linux package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  In Progress

Bug description:
  Switch fetching dkms-versions data for these packages to the kernel-
  versions dataset.

  Currently the primary dkms-versions data is committed directly to the
  primary kernel packages.  This allows this information to cascade
  reliably to all derivatives and their associated LRM packages.  But
  once the primaries are closed it is increasingly hard to change this
  data.  This makes performing an LRM-only respin very difficult as it
  differs in handling from a primary spin.

  We move the primary version dataset out of the kernel packages into a
  shared external "kernel-versions" dataset.  Each package which needs
  this data then obtains the information it needs directly, with it
  committed locally to that package at update time.

  This renders preparation of am initial (-1) spin and a later LRM-only
  respin identicle.  We simply update the shared dataset and perform a
  no-change rebuild (./update-versions) on them and they will
  automatically get the updated version information.

  We will want to update update-dkms-versions in all primary main
  packages, and introduce same into all LRM packages.  As we already run
  update-dkms-versions in the primary main packages, and are introducing
  update-dkms-versions handling to update-versions in LRM this should
  not change kernel crank proceedure.  The cycle proceedure will need a
  new step to update the shared kernel-versions dataset before cranking
  commences.

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Still visible on AWS t2.small 4.15.0-1103.110-aws

** Tags added: sru-20210510

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71

Upstream stable patch from 5.11.19 referred to this bug.

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

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

** Changed in: linux (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/1922651

Title:
  r8152 tx status -71

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

Bug description:
  I've bought ThinkPad T14s with a USB-based docking station. Everything
  is working marvelously, but from time to time the ethernet port on the
  docking station won't connect. I've discovered the following messages
  in my dmesg:

  [  400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

  Rebooting the machine doesn't seem to work, turning the ethernet
  connection off and on doesn't seem to work. I have a dualboot
  Linux+Windows (one wants to play games from time to time :-p ) and it
  could be that rebooting from Win to Lin causes this issue, but this
  needs to be confirmed yet. I will try to power off the computer and/or
  the docking station, to see whether that would help.

  I've found numerous bug reports, but they are rather old or may not
  apply to this situation, therefore I figured it's best to open a new
  bug report.

  Thank you so much for your hard work!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 10:00:29 2021
  InstallationDate: Installed on 2021-03-24 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20UH001QMX
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic 
root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2020
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET61W(1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UH001QMX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.30
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UH001QMX
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1928849] Re: Hirsute update: v5.11.18 upstream stable release

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

Title:
  Hirsute update: v5.11.18 upstream stable release

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:

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

  iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
  drm/amd/display: Update modifier list for gfx10_3
  mei: me: add Alder Lake P device id.
  Linux 5.11.18
  UBUNTU: upstream stable to v5.11.18

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

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

[Kernel-packages] [Bug 1928850] Re: Hirsute update: v5.11.19 upstream stable release