[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1056.66)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1056.66) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-gcp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1933274] Re: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"

[Po-Hsu Lin]

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

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

Title:
  TGL-H skl_dram_get_dimm_info crashes with "Missing case (val ==
  65535)"

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

Bug description:
  Tracing this back, I found the current Ubuntu 5.11 kernel has
  incorrect offsets for some platforms (TGL-H and ADL). I created an
  upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662
  and was directed to a commit, 5d0c938ec9cc, that ought to fix this
  issue. See the attached patch file for this commit applied to the
  current Ubuntu 5.11 kernel.

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


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

[Kernel-packages] [Bug 1940724] Re: 20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

[Launchpad Bug Tracker]

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

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

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back

[Po-Hsu Lin]

** Description changed:

  [Impact]
  We have this test disabled intentionally in the past because of the
  lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from
  l2tp_xmit_skb()" in our kernels.
  
  The way we disable it is to override the executable bit with our
  autotest-client-tests suite [1], but this makes the test suite
  complain about script is not executable. Henceforth we further
  disable it by removing it from the Makefile in the patch "UBUNTU:
  SAUCE: selftests/net -- disable timeout"
  
  Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in
  our test suite [2], we still need to revert that SAUCE patch to get
  it tested.
  
  [1] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16
  [2] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d
  
  [Fix]
- Revert "UBUNTU: SAUCE: selftests/net -- disable timeout"
+ Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"
  
  This test only exists in our tree since Focal.
  
  [Test]
  Run the net test suite in kselftest with patched source tree:
    sudo make -C linux/tools/testing/selftests TARGETS=net run_tests
  
  The l2tp.sh test will be executed.
  
  [Where problems could occur]
  This is only for testing tools, however if commit 27d53323664c54 "l2tp:
  remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we
  might crash our testing node like in bug 1854968. Also, we might see
  new failures caused by this test in the test report.

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

Title:
  Add l2tp.sh in net from ubuntu_kernel_selftests back

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

Bug description:
  [Impact]
  We have this test disabled intentionally in the past because of the
  lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from
  l2tp_xmit_skb()" in our kernels.

  The way we disable it is to override the executable bit with our
  autotest-client-tests suite [1], but this makes the test suite
  complain about script is not executable. Henceforth we further
  disable it by removing it from the Makefile in the patch "UBUNTU:
  SAUCE: selftests/net -- disable timeout"

  Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in
  our test suite [2], we still need to revert that SAUCE patch to get
  it tested.

  [1] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16
  [2] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d

  [Fix]
  Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  This test only exists in our tree since Focal.

  [Test]
  Run the net test suite in kselftest with patched source tree:
    sudo make -C linux/tools/testing/selftests TARGETS=net run_tests

  The l2tp.sh test will be executed.

  [Where problems could occur]
  This is only for testing tools, however if commit 27d53323664c54 "l2tp:
  remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we
  might crash our testing node like in bug 1854968. Also, we might see
  new failures caused by this test in the test report.

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


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

[Kernel-packages] [Bug 1938143] Re: Include product_sku info to modalias

[Po-Hsu Lin]

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

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

Title:
  Include product_sku info to modalias

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

Bug description:
  [Impact]
  When we add DMI quirks for the new platforms, it's hard to prevent from 
leaking its model name. Our customer doesn't like it.

  [Fix]
  Introduce the product sku modalias to DMI table, so that we can use more 
meaningless product sku string to match the platform.

  [Test]
  No real DMI quirk is added in this commit, so need to do any tests.

  [Where problems could occur]
  It's safe to add one more DMI entry, nothing could be affected.

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


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

[Kernel-packages] [Bug 1946216] Re: PL2303GL chips not recognised by 21.10 beta

[Po-Hsu Lin]

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

Hello!
Thanks for your report, this patch has been applied to Impish kernel 
master-next branch via stable update process, it should be available in 
-updates soon.

** This bug has been marked a duplicate of bug 1946242
   Impish update: v5.13.15 upstream stable release

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

Title:
  PL2303GL chips not recognised by 21.10 beta

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  L2303GL usb to serial chips are not recognised by the pl2303 module in
  5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
  x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
  chips are fairly common so it will cause a problem for users.

  I reported this to the upstream maintainer and he confirmed it is a
  known issue and fixed by commit  dcf097e7d21f ("USB: serial: pl2303:
  fix GL type detection"). Please backport for 21.10.

  Email correspondence confirming bug pasted below.

  Johan Hovold 

  9:33 AM (1 hour ago)

  to me, linux-usb
  On Tue, Oct 05, 2021 at 05:28:24PM +0100, Adrian Knagg-Baugh wrote:
  > Hi,
  > As requested in dmesg I'm reporting an unknown device type for the
  > pl2303 driver. Here's the extract from dmesg:
  > 
  > [ 2824.450073] usb 1-2: new full-speed USB device number 5 using xhci_hcd
  > [ 2824.621910] usb 1-2: New USB device found, idVendor=067b,
  > idProduct=23d3, bcdDevice= 4.05
  > [ 2824.621922] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  > [ 2824.621926] usb 1-2: Product: USB-Serial Controller
  > [ 2824.621928] usb 1-2: Manufacturer: Prolific Technology Inc.
  > [ 2824.621931] usb 1-2: SerialNumber: EKCRb19B616
  > [ 2824.630068] pl2303 1-2:1.0: pl2303 converter detected
  > [ 2824.630084] pl2303 1-2:1.0: unknown device type, please report to
  > linux-...@vger.kernel.org
  > 
  > adrian@mononoke:~$ uname -a
  > Linux mononoke 5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC
  > 2021 x86_64 x86_64 x86_64 GNU/Linux
  > 
  > The pl2303 is in a Skywatcher telescope synscan handset, the behaviour
  > is a regression since it was working fine in the 5.11 kernels packaged
  > with Ubuntu 21.04, it's only since updating to 5.13 (which I've had to
  > do to resolve issues with the graphics card in my new laptop) that
  > I've seen the problem.
  > 
  > See below for the output of sudo lsusb -v
  > 
  > I hope this helps.

  Thanks for the report. This should already have been fixed by commit
  dcf097e7d21f ("USB: serial: pl2303: fix GL type detection") which was
  backported to v5.13.15 (released about a month ago).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  adrian 1773 F pulseaudio
   /dev/snd/controlC0:  adrian 1773 F pulseaudio
   /dev/snd/controlC1:  adrian 1773 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  6 10:55:35 2021
  InstallationDate: Installed on 2021-10-02 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513IH_G513IH
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=8a2303d3-7aba-4e56-9501-3d719f7e2f1f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513IH.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513IH
  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: 0.68
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513IH.310:bd07/16/2021:br5.16:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGStrixG513IH_G513IH:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnG513IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513IH_G513IH
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[Jan Johansson]

I have changed DefaultTimeoutStopSec=90s timeout to 20s as personal
choice to make sure that anything running in the background has time to
stop before shutting down, to avoid something braking,

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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


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

[Kernel-packages] [Bug 1947925] [NEW] Seagate IronWolf 125 support

[Mert]

Public bug reported:

This is not a severe bug. (Lack of Firmware for linux on arm)

Seagate's SSD IronWolf 125 (1TB) doesn't work reliable on the raspberry pi 4 
(connected via SATA3 to USB, (Tried out multiple SATA3 to USB Cables)).
After the internal ssds cache is filled the ssd will be locked and is not 
accessible anymore.
FDISK will no longer list the SSD anymore.

The SSD is brand new and is working fine on Mac and Windows. It also works fine 
on Linux (x86).
But Linux on arm will fail on this ssd.
I looked up on their official site to download the firmware but there is 
actually no firmware to download.

I once downloaded the ssd support program on windows to check its
integrity => no hardware errors.

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


** Tags: firmware sata seagate usb

** Tags added: sata seagate

** Tags added: usb

** Description changed:

  This is not a severe bug. (Lack of Firmware for linux on arm)
  
- Seagate's SSD IronWolf 125 (1TB) doesn't work reliable on the raspberry pi 4.
+ Seagate's SSD IronWolf 125 (1TB) doesn't work reliable on the raspberry pi 4 
(connected via SATA3 to USB, (Tried out multiple SATA3 to USB Cables)).
  After the internal ssds cache is filled the ssd will be locked and is not 
accessible anymore.
  FDISK will no longer list the SSD anymore.
  
  The SSD is brand new and is working fine on Mac and Windows. It also works 
fine on Linux (x86).
  But Linux on arm will fail on this ssd.
  I looked up on their official site to download the firmware but there is 
actually no firmware to download.
  
- 
- I once downloaded the ssd support program on windows to check its integrity 
=> no hardware errors.
+ I once downloaded the ssd support program on windows to check its
+ integrity => no hardware errors.

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

Title:
  Seagate IronWolf 125 support

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  This is not a severe bug. (Lack of Firmware for linux on arm)

  Seagate's SSD IronWolf 125 (1TB) doesn't work reliable on the raspberry pi 4 
(connected via SATA3 to USB, (Tried out multiple SATA3 to USB Cables)).
  After the internal ssds cache is filled the ssd will be locked and is not 
accessible anymore.
  FDISK will no longer list the SSD anymore.

  The SSD is brand new and is working fine on Mac and Windows. It also works 
fine on Linux (x86).
  But Linux on arm will fail on this ssd.
  I looked up on their official site to download the firmware but there is 
actually no firmware to download.

  I once downloaded the ssd support program on windows to check its
  integrity => no hardware errors.

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


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

[Kernel-packages] [Bug 1945989] Re: Check for changes relevant for security certifications

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/4.15.0-162.170 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.

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-bionic

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

Title:
  Check for changes relevant for security certifications

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete

Bug description:
  [Impact]

  When producing a new version of some kernels, we need to check for
  changes that might affect FIPS or other certs and justify why a commit
  was kept or removed.

  To simplify this process we can add an automated check that will abort
  the kernel preparation and build when such changes exist without a
  justification.

  [Test Plan]

  Check if the kernel preparation fails (cranky close) when one of a
  security certification changes is added.

  [Where problems could occur]

  No kernels should be affected until we enable this check on each one.
  Even when enabled, that only affects the kernel preparation and not
  the resulting kernel.

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


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

[Kernel-packages] [Bug 1946464] Re: Invalid backport to v4.15: missing pgtable_l5_enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/4.15.0-162.170 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.

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-bionic

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

Title:
  Invalid backport to v4.15: missing pgtable_l5_enabled

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

Bug description:
  [Impact]

  Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at 
runtime") should not be backported to v4.15 because:
  1. It adds pgtable_l5_enabled which does not exist in v4.15,
  2. It is marked as v4.17+
  3. It is marked as fixing commit which does not exist in v4.15 and was not 
backported there.

  allyesconfig in x86_64 fails to build:
  ---
  In file included from ../arch/x86/include/asm/mmu_context.h:12,
   from ../include/linux/mmu_context.h:5,
   from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
  ../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
  ../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’ 
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
    185 |  if (!pgtable_l5_enabled)
    |   ^~
    |   movable_node_enabled

  ---

  [Test Plan]

  Compile the x86_64 KVM code.

  [Where problems could occur]

  If backport commit is actually needed, e.g. when we backport 5-level
  page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table
  layer at runtime"), this could cause double-free and memory
  corruption.

  When backporting x86_64 5-level pages, we need to bring this commit as
  well.

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


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

[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/4.15.0-162.170 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.

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-bionic

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

Title:
  vrf: fix refcnt leak with vxlan slaves

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

Bug description:
  [Impact]

  There are cases, where deleting a VRF device can hang waiting for the refcnt 
to drop to 0, with the message: 
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1

  This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
  used for dst_alloc with local routes"), included in linux v5.13. The
  original patch, which has introduced the bug, is included in linux
  v4.10.

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

  [Test Case]

  The upstream patch includes a test case, which describe how to
  reproduce the bug.

  [Regression Potential]

  The patch affects ipv4 routing. It is straightforward, it links new
  dst to a vrf device instead of the loopback if needed.

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


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

[Kernel-packages] [Bug 1947174] Re: Add final-checks to check certificates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/4.15.0-162.170 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.

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-bionic

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

Title:
  Add final-checks to check certificates

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * As part of landing builtin revocation certificates work
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has
  been identified that many kernels do not correct enforce newly enfoced
  keys in the derivative flavours. I.e. due to annotations not importing
  parent annotations, due to not having do_enforce_all, or using older
  formats of annotations files.

   * As part fips validation work final-checks got added to check and
  assert that correct things are turned on.

   * It has been agreed that having a final-check for builtin system
  trusted & revocation certificates would be a good thing. If packaging
  declares that certain certificates should be built-in trusted or
  revoked, the kernel must be configured pointing at the packaging
  generated .pem bundle in the config.

  [Test Plan]

   * Kernel should build
   * If trusted or revocation are configured in packaging but the config option 
is misconfigured (i.e. typo or not set), the kernel build and cranky close 
should fail

  
  [Where problems could occur]

   * This is a packaging change only, thus may result in valid kernels
  ftbfs but should be easy to rectify.

  [Other Info]
   
   * Also see

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029

  and kernels that derived from a primary kernel that had that fixed,
  and the subsequently failed boot testing due to not enabling those
  options.

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


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

[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[Kai-Heng Feng]

RBX2,
The fix came along with kernel stable updates, so you don't necessarily need to 
verify it.

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

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

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-67-generic N/A
   linux-backports-modules-5.4.0-67-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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/1920674/+subscriptions


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[elguavas]

you can also just disable the trackpad in the bios settings.

then enable it again when a fixed kernel is available.

bit of a super pita having a laptop with no trackpad though, ;) and for
people running the installer (who would have no reason to know to
disable their trackpad or apply boot params in advance) they just see
that the installer crashes and wont run.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  [impish] Remove the downstream xr-usb-uart driver

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

Bug description:
  [Impact]

  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804

  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above
  patch series.

  [Where problems could occur]
  The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

  [This is a tracking bug, please do not triage]

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


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

[Kernel-packages] [Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was dissabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  Re-enable DEBUG_INFO_BTF where it was dissabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux-hwe-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * pahole used to segfault on 32-bit platforms, which has now been
  fixed

   * pahole used to be too old in focal, which is now being SRUed

   * renable DEBUG_INFO_BTF in all the kernels/arches that had it
  disabled, as otherwise one cannot compile/use advanced BTF features on
  newer kernels.

  
  [Test Plan]

   * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y
   * Check build log that it contains
  ```
BTF .btf.vmlinux.bin.o
  ```

  [Where problems could occur]

   * In the future, kernel may require even newer version of pahole from
  dwarves, making the builds fail to build again, as building BTF debug
  information will now be required. Until either BTF is disabled again
  or pahole is upgraded again.

  [Other Info]
   
   * Latest pahole is available from focal-proposed, hirsute-proposed, impish 
release, builders-extra PPA

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


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

[Kernel-packages] [Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  BCM57800 SRIOV bug causes interfaces to disappear

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

Bug description:
  [Impact]
  bnx2x driver won't add all devices ports/interfaces.

  [Test case]
  Boot system with bnx2x device and verify all ports/interfaces have been added.

  [Potential regression]
  bnx2x devices won't be properly probed. Devices won't be added or SR-IOV 
won't be correctly supported.

  --- Original Description ---

  Works with focal kernel 5.4.0-80
  Broken with focal kernel 5.4.0-88

  On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network
  cards Kernel 5.11.22-3 causes half of the network interfaces to
  disappear specifically the 1gb ports. Commands like "ip link show" and
  "dmesg" no longer show eno3 and eno4 nor any other interface name for
  these ports. I've read the note in the release notes and this does not
  appear to be a case of the interface changing names, the 3rd and 4th
  interface don't show up at all.

  The card is based on the BCM57800 chipset and has two SFP+ and two
  gigabit ports on the same card. Commands like "ip link show" no longer
  show ports 3 and 4. "lspci" still shows four items. dmesg only shows
  the first two interfaces.

  This problem seems to be known upstream, and seems to be a regression.

  More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558

  This is being seen at a customer during an openstack install. It would
  be appreciated if a workaround could be provided or the fix could be
  prioritized. Using standard Focal 20.04 LTS kernel (it installs ok
  with the working kernel then upgrades to the non-working one -- this
  is done through maas and is difficult to control).

  Tested other kernels like hwe-* and all seem to be affected too.

  Client does not want to disable SRIOV on whole card and also cannot
  disable only ports 3/4 (the bios will not allow it).

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


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

[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  Fix A yellow screen pops up in an instant (< 1 second) and then
  disappears before loading the system

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

Bug description:
  [Impact]
  *** this issue happen with secure boot on and issue gone when secure boot is 
off***

  After the BIOS loading screen, a yellow screen pops up in an instant
  (< 1 second) and then disappears. Attached a demo video.

  [Fix]
  do what intel_color_commit() does to make sure the bottom color state
  matches whatever out hardware readout produced.
  Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1

  [Test]
  1. Power on the system
  2. Check if any unusual screen shows before and after the system loading 
screen.
  3. No unusual screen shows before and after the system loading screen

  [Regression Potential]
  Medium, maintainer still not totally sure what should do about color 
management
  features here in general.

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


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

[Kernel-packages] [Bug 1945556] Re: Fix missing HDMI audio on Intel RKL

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  Fix missing HDMI audio on Intel RKL

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

Bug description:
  [Impact]
  HDMI audio is missing on Intel RKL.

  [Fix]
  Also use BIOS provided value for HDA link.

  [Test]
  HDMI audio is back after the fix gets applied.

  [Where problems could occur]
  Because this is a regression, this patch simply brings back the old
  behavior for RKL systems. There could be RKL systems get fixed by
  the offending commit, so this might break those hypothetical systems.

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


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

[Kernel-packages] [Bug 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  USB Type-C hotplug event not handled properly in TGL-H system during
  s2idle

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

Bug description:
  [SRU Justification]

  [Impact]
  The system will be hold by the infinite loop in ACPI method IPCS after 
exiting s2idle in TGL-H systems if the docking station with external display 
connected is unplugged when the system is still in s2idle. It's
  because the system is unaware of the unplug event and it seems keep something 
asserted which will never be released while the system trying to exit s2idle.

  [Fix]
  Disconnect TypeC PHYs during system suspend and shutdown, even with the
  corresponding TypeC sink still plugged to its connector. The HPD event is no 
longer triggered when the system is in s2idle so the resume process will not be 
hindered.

  [Test Case]
  1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the 
NVIDIA GPU is running in either On-Demand mode or Performance mode.
  2. Connect the docking station with the external display connected.
  3. Suspend the system.
  4. Remove the docking station when the system is suspended.
  5. Press power button to wake up the system and wait > 1 minutes to make sure 
if the display comes back.

  [Where problems could occur]
  Low. This will only make a difference in the TypeC DP alternate mode, and the 
display driver will detect the display connector after resume.

  == Original Bug Description ==

  [Summary]
  As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting 
s2idle in TGL-H systems if the USB Type-C docking/dongle with external display 
connected is unplugged when the system is still in s2idle. The system will be 
hold by the infinite loop in ACPI method IPCS and then the PCIe root port of 
NVIDIA gpu fails the power transition from D3cold to D0. It's because the 
display connector hotplug event not handled properly in graphics drivers and 
the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit.

  [ 154.446781]
  [ 154.446783]
  [ 154.446783] Initialized Local Variables for Method [IPCS]:
  [ 154.446784] Local0: 9863e365  Integer 09C5
  [ 154.446790]
  [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments
  defined for method invocation)
  [ 154.446792] Arg0: 25568fbd  Integer 00AC
  [ 154.446795] Arg1: 9ef30e76  Integer 
  [ 154.446798] Arg2: fdf820f0  Integer 0010
  [ 154.446801] Arg3: 9fc2a088  Integer 0001
  [ 154.446804] Arg4: 3a3418f7  Integer 0001
  [ 154.446807] Arg5: 20c4b87c  Integer 
  [ 154.446810] Arg6: 8b965a8a  Integer 
  [ 154.446813]
  [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to
  previous error 

[Kernel-packages] [Bug 1945989] Re: Check for changes relevant for security certifications

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  Check for changes relevant for security certifications

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete

Bug description:
  [Impact]

  When producing a new version of some kernels, we need to check for
  changes that might affect FIPS or other certs and justify why a commit
  was kept or removed.

  To simplify this process we can add an automated check that will abort
  the kernel preparation and build when such changes exist without a
  justification.

  [Test Plan]

  Check if the kernel preparation fails (cranky close) when one of a
  security certification changes is added.

  [Where problems could occur]

  No kernels should be affected until we enable this check on each one.
  Even when enabled, that only affects the kernel preparation and not
  the resulting kernel.

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


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

[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

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

Bug description:
  [Impact]
  The speaker on a coule of Lenovo laptops can't output sound, need
  to do special initialization.

  [Fix]
  Backport a upstream patch, the patch will initialize the speaker
  amplifier with special verbs.

  [Test]
  Booting the patched kernel, output the sound to speaker, could
  heaer the sound.

  [Where problems could occur]
  The patch set the quirk to some lenovo machines with subsystem id,
  there is no regression risk for other machines.

  
  All 3 models need the appropriate HDA verbs sent to properly initialize the 
sound hardware.

  Additionally, the Legion 15IMHG05 needs automute disabled otherwise
  speaker output will not return after removing headphones.

  The good news is that I have working patches for all 3.

  However, the 13s Gen2 reportedly has some weirdness on the volume
  control. I don't have this model of laptop so there's not a lot I can
  do. It seems tuning the volume up and down using the keys on the
  keyboard can jump the volume up and down in large increments. Volume
  adjustments via a GUI do not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7243 F pulseaudio
   /dev/snd/controlC0:  hiryu  7243 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug  5 10:17:57 2021
  InstallationDate: Installed on 2021-04-23 (104 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2021
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

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

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-67-generic N/A
   linux-backports-modules-5.4.0-67-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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/1920674/+subscriptions


-- 
Mailing list: 

[Kernel-packages] [Bug 1945553] Re: It hangs while booting up with AMD W6800 [1002:73A3]

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  It hangs while booting up with AMD W6800 [1002:73A3]

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

Bug description:
  [Impact]
  It hangs when booting up with AMD W6800 [1002:73A3] graphics card.

  [Fix]
  Bisect the kernel and found below fix from v5.15-rc1 mainline kernel
  5810323ba692 drm/amd/pm: Fix a bug communicating with the SMU (v5)

  [Test]
  Verified the patch on a Dell workstation with AMD W6800 graphics card

  [Where problems could occur]
  The code flow doesn't change much, but with better return codes handling and 
print out more meaningful messages. So it should not impact the already working 
devices.

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


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

[Kernel-packages] [Bug 1947174] Re: Add final-checks to check certificates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.13.0-21.21 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

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-impish

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

Title:
  Add final-checks to check certificates

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * As part of landing builtin revocation certificates work
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has
  been identified that many kernels do not correct enforce newly enfoced
  keys in the derivative flavours. I.e. due to annotations not importing
  parent annotations, due to not having do_enforce_all, or using older
  formats of annotations files.

   * As part fips validation work final-checks got added to check and
  assert that correct things are turned on.

   * It has been agreed that having a final-check for builtin system
  trusted & revocation certificates would be a good thing. If packaging
  declares that certain certificates should be built-in trusted or
  revoked, the kernel must be configured pointing at the packaging
  generated .pem bundle in the config.

  [Test Plan]

   * Kernel should build
   * If trusted or revocation are configured in packaging but the config option 
is misconfigured (i.e. typo or not set), the kernel build and cranky close 
should fail

  
  [Where problems could occur]

   * This is a packaging change only, thus may result in valid kernels
  ftbfs but should be easy to rectify.

  [Other Info]
   
   * Also see

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029

  and kernels that derived from a primary kernel that had that fixed,
  and the subsequently failed boot testing due to not enabling those
  options.

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


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

[Kernel-packages] [Bug 1947902] Re: Under particular load, virtio-scsi backed / errors out

[Rich]

I lied, it totally happens on 20.04 (w/5.4.0-89-generic) and 21.04
(5.11.0-37-generic), I just had forgotten I hadn't used virtio-scsi on
them, just SATA.

Oh boy.

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

Title:
  Under particular load, virtio-scsi backed / errors out

Status in linux-signed package in Ubuntu:
  New

Bug description:
  As I often do, I tried running OpenZFS git master's ZFS Test Suite
  against the new Ubuntu 21.10 release, to make sure nothing was
  secretly broken.

  This is on an Ubuntu 21.10 amd64 VM (running 5.13.0-20-generic) inside
  VirtualBox 6.1.26 on Windows 10 x64, using virtio-scsi for the root
  disk. The host is not experiencing any errors or low disk space or
  anything whenever this occurs, and other VMs running on the host and
  same physical disk are unaffected.

  I have seen failures like this happen before when using VirtualBox's
  TRIM/discard functionality, but that has to be very explicitly enabled
  on the VM, and it's not.

  It runs fine for a bit...then suddenly everything crashes and burns, after 
the root disk starts erroring out:
  [ 5281.077557] virtio_scsi virtio1: request:id 869 is not a head!
  [ 5284.066557] sd 2:0:0:0: [sda] tag#390 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.066561] sd 2:0:0:0: [sda] tag#390 CDB: Write(10) 2a 00 01 d4 a3 78 00 
00 a0 00
  [ 5284.066562] blk_update_request: I/O error, dev sda, sector 30712696 op 
0x1:(WRITE) flags 0x800 phys_seg 20 prio class 0
  [ 5284.066575] Aborting journal on device sda3-8.
  [ 5284.066580] sd 2:0:0:0: [sda] tag#391 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.066581] sd 2:0:0:0: [sda] tag#391 CDB: Write(10) 2a 00 01 d4 18 00 00 
00 08 00
  [ 5284.066582] blk_update_request: I/O error, dev sda, sector 30676992 op 
0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
  [ 5284.066584] Buffer I/O error on dev sda3, logical block 3702784, lost sync 
page write
  [ 5284.066586] JBD2: Error -5 detected when updating journal superblock for 
sda3-8.
  [ 5284.070494] EXT4-fs error (device sda3): ext4_journal_check_start:83: comm 
rs:main Q:Reg: Detected aborted journal
  [ 5284.070666] EXT4-fs (sda3): Remounting filesystem read-only
  [ 5284.071033] sd 2:0:0:0: [sda] tag#392 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071036] sd 2:0:0:0: [sda] tag#392 CDB: Read(10) 28 00 02 79 f1 80 00 
00 08 00
  [ 5284.071037] blk_update_request: I/O error, dev sda, sector 41546112 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
  [ 5284.071047] sd 2:0:0:0: [sda] tag#393 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071049] sd 2:0:0:0: [sda] tag#393 CDB: Read(10) 28 00 02 79 f1 a0 00 
00 18 00
  [ 5284.071049] blk_update_request: I/O error, dev sda, sector 41546144 op 
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
  [ 5284.071055] sd 2:0:0:0: [sda] tag#394 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071057] sd 2:0:0:0: [sda] tag#394 CDB: Read(10) 28 00 02 79 f1 d8 00 
00 08 00
  [ 5284.071057] blk_update_request: I/O error, dev sda, sector 41546200 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
  [ 5284.071062] sd 2:0:0:0: [sda] tag#395 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071064] sd 2:0:0:0: [sda] tag#395 CDB: Read(10) 28 00 02 79 f1 f0 00 
00 08 00
  [ 5284.071064] blk_update_request: I/O error, dev sda, sector 41546224 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
  [ 5284.071071] sd 2:0:0:0: [sda] tag#396 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071072] sd 2:0:0:0: [sda] tag#396 CDB: Read(10) 28 00 02 79 f2 00 00 
00 18 00
  [ 5284.071073] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
  [ 5284.071078] sd 2:0:0:0: [sda] tag#397 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071079] sd 2:0:0:0: [sda] tag#397 CDB: Read(10) 28 00 02 79 f2 20 00 
00 08 00
  [ 5284.071080] blk_update_request: I/O error, dev sda, sector 41546272 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
  [ 5284.071085] sd 2:0:0:0: [sda] tag#398 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071086] sd 2:0:0:0: [sda] tag#398 CDB: Read(10) 28 00 02 79 f2 00 00 
00 08 00
  [ 5284.071087] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
  [ 5284.071092] sd 2:0:0:0: [sda] tag#399 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
  [ 5284.071093] sd 2:0:0:0: [sda] tag#399 CDB: Read(10) 28 00 02 79 f2 00 00 
00 08 00
  [ 5284.071094] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
  

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Alvaro]

I have only the buggy kernel 5.13 for booting in my Lenovo laptop, so I
can not boot at all into the system.

If you have the same problem, you can avoid loading the psmouse adding
to the kernel boot params:

modprobe.blacklist=psmouse

and at least you can boot the system and use it to install a new kernel
once the problem is fixed.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1947623] Re: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD

[Diana]

I have a Lenovo ThinkPad T15 with AMD Ryzen 4500 with Radeon graphics
too, and got the same issue.

This happened to me:
- I bought the laptop brand new with no OS installed (per my request)
- When I got it, I created a bootable USB stick with Kubuntu 2021.10 (Image 
that I got from the official page)
 - Kubuntu never started (I did get the menu from the USB stick though), and I 
tried both USB ports.
- I try to boot with the recovering/safe mode and I see that error.
- So I instead format the USB stick to have the bootable version 2021.04 of 
Kubuntu.
- Kubuntu started and I was able to "Try Kubuntu" and install it.
- Once the installation was done, I update all available updates and upgrade 
Kubuntu to 2021.10 from the console. 
- After restart, Kubuntu never started: recover mode showed the same error I 
got with the USB (which is the one reported here).

So if the other Lenovo ThinkPad with Intel setup was able to boot
Kubuntu from USB Stick with no error, I assume it has to do with the AMD
setup.

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

Title:
  Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14
  AMD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can't boot computer after upgrade to Ubuntu 21.10, with kernel
  5.13.0.19.30, because of Kernel Panic Error.

  It seems to be a problem with:
   ETPS/2 Elantech TrackPoint
   ETPS/2 Elantech Touchpad

  Kernel 5.11.0-38 seems to work ok.

  Erorr:

  -
  [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
1.738396] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0xOd. 
  [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7
1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw 
version: 0x4
  [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, 
bcdDevice= 1.00
  [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device
  [ 1.777283] usb 3-3: Manufacturer: Generic
  [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, 
bcdDevice=20.01
  [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, 
SerialNumber=2
  [ 1.788191] usb 1-3: Product: Integrated Camera
  [ 1.790293] usb 1-3: Manufacturer: Azuremaue
  [ 1.792379] usb 1-3: SerialNuMber:
  [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse]
  [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 
5.13.0-19-generic #19 -Ubuntu
1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW 
(1.16 ) 09/06/2021
  [ 1.828936] Workqueue: events long serio handle_event
  [ 1.828936] Call Trace:
  [ 1.828936]  show stack+0x52/0x58
  [ 1.828936]  dump stack+0x7d/0x9c
  [ 1.828936]  panic+0x101/0x2e3
  [ 1.828936]  ? elantech change repurt id+0x1bf/0x1c4 [psmouse]
  [ 1.828936]  __stack_chk_fail+0x14/0x20
  [ 1.828936]  elantech change report id+0x1bf/0x1c4 [psmouse]
  [ 1.828936]  elantech_query_info.cold+0X316/0x594 [psmouse]
  [ 1.828936]  elantech_init*0x34/0x160 [psmouse]
  [ 1.828936]  ? synaptics send cmd*0x60/0x60 Ipsmousel
  [ 1.828936]  psmouse_extensions+0x4b6/0x520 kpsmouse]
  [ 1.828936]  psmouse switch_protocol+0x144/0x190 [psmouse]
  [ 1.828936]  psmouse_connect+0xI85/0x3a0 [psmouse]
  [ 1.828936]  seriodriver_probe+0x86/0x50
  [ 1.828936]  really_probe+0x245/0x4c0
  [ 1.828936]  driver_probe device+0xf0/0x160
  [ 1.828936]  device_driver attach+0xab/0xbO
  [ 1.828936]  __driver_attach+0xbZ/0x140
  [ 1.828936]  ? device_driver_attach+0xbO/0xbO
  [ 1.828936]  bus_foreachdeu+0x7e/0xc0
  [ 1.828936]  driver_attach+0xle/0x20
  [ 1.828936]  serio_handle_event+0xl0f/0x290
  [ 1.828936]  process_one_work+0x220/0x3c0
  [ 1.828936]  worker_thread+0x53/0x420
  [ 1.828936]  kthread+0xl1f/0x140
  [ 1.828936]  ? process_one_work+0x3c0/0x3c0
  [ 1.828936]  ? set_kthread_struct+0x50/0x50
  [ 1.828936]  ret_from_fork+0x22/0x30
  [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation 
range: 0x000-0xbfff)
  [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: 
Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] 
]---
  ---


  Computer:
  -
  Computer
  

  
  Summary
  ---

  -Computer-
  Processor : AMD Ryzen 5 4500U with Radeon Graphics
  Memory: 23817MB (6094MB used)
  Machine Type  : Notebook
  Operating System  

[Kernel-packages] [Bug 1947902] [NEW] Under particular load, virtio-scsi backed / errors out

[Rich]

Public bug reported:

As I often do, I tried running OpenZFS git master's ZFS Test Suite
against the new Ubuntu 21.10 release, to make sure nothing was secretly
broken.

This is on an Ubuntu 21.10 amd64 VM (running 5.13.0-20-generic) inside
VirtualBox 6.1.26 on Windows 10 x64, using virtio-scsi for the root
disk. The host is not experiencing any errors or low disk space or
anything whenever this occurs, and other VMs running on the host and
same physical disk are unaffected.

I have seen failures like this happen before when using VirtualBox's
TRIM/discard functionality, but that has to be very explicitly enabled
on the VM, and it's not.

It runs fine for a bit...then suddenly everything crashes and burns, after the 
root disk starts erroring out:
[ 5281.077557] virtio_scsi virtio1: request:id 869 is not a head!
[ 5284.066557] sd 2:0:0:0: [sda] tag#390 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.066561] sd 2:0:0:0: [sda] tag#390 CDB: Write(10) 2a 00 01 d4 a3 78 00 00 
a0 00
[ 5284.066562] blk_update_request: I/O error, dev sda, sector 30712696 op 
0x1:(WRITE) flags 0x800 phys_seg 20 prio class 0
[ 5284.066575] Aborting journal on device sda3-8.
[ 5284.066580] sd 2:0:0:0: [sda] tag#391 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.066581] sd 2:0:0:0: [sda] tag#391 CDB: Write(10) 2a 00 01 d4 18 00 00 00 
08 00
[ 5284.066582] blk_update_request: I/O error, dev sda, sector 30676992 op 
0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[ 5284.066584] Buffer I/O error on dev sda3, logical block 3702784, lost sync 
page write
[ 5284.066586] JBD2: Error -5 detected when updating journal superblock for 
sda3-8.
[ 5284.070494] EXT4-fs error (device sda3): ext4_journal_check_start:83: comm 
rs:main Q:Reg: Detected aborted journal
[ 5284.070666] EXT4-fs (sda3): Remounting filesystem read-only
[ 5284.071033] sd 2:0:0:0: [sda] tag#392 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071036] sd 2:0:0:0: [sda] tag#392 CDB: Read(10) 28 00 02 79 f1 80 00 00 
08 00
[ 5284.071037] blk_update_request: I/O error, dev sda, sector 41546112 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071047] sd 2:0:0:0: [sda] tag#393 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071049] sd 2:0:0:0: [sda] tag#393 CDB: Read(10) 28 00 02 79 f1 a0 00 00 
18 00
[ 5284.071049] blk_update_request: I/O error, dev sda, sector 41546144 op 
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 5284.071055] sd 2:0:0:0: [sda] tag#394 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071057] sd 2:0:0:0: [sda] tag#394 CDB: Read(10) 28 00 02 79 f1 d8 00 00 
08 00
[ 5284.071057] blk_update_request: I/O error, dev sda, sector 41546200 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071062] sd 2:0:0:0: [sda] tag#395 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071064] sd 2:0:0:0: [sda] tag#395 CDB: Read(10) 28 00 02 79 f1 f0 00 00 
08 00
[ 5284.071064] blk_update_request: I/O error, dev sda, sector 41546224 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071071] sd 2:0:0:0: [sda] tag#396 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071072] sd 2:0:0:0: [sda] tag#396 CDB: Read(10) 28 00 02 79 f2 00 00 00 
18 00
[ 5284.071073] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 5284.071078] sd 2:0:0:0: [sda] tag#397 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071079] sd 2:0:0:0: [sda] tag#397 CDB: Read(10) 28 00 02 79 f2 20 00 00 
08 00
[ 5284.071080] blk_update_request: I/O error, dev sda, sector 41546272 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 5284.071085] sd 2:0:0:0: [sda] tag#398 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071086] sd 2:0:0:0: [sda] tag#398 CDB: Read(10) 28 00 02 79 f2 00 00 00 
08 00
[ 5284.071087] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 5284.071092] sd 2:0:0:0: [sda] tag#399 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5284.071093] sd 2:0:0:0: [sda] tag#399 CDB: Read(10) 28 00 02 79 f2 00 00 00 
08 00
[ 5284.071094] blk_update_request: I/O error, dev sda, sector 41546240 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 5406.093848] scsi_io_completion_action: 2 callbacks suppressed
[ 5406.093857] sd 2:0:0:0: [sda] tag#402 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK cmd_age=0s
[ 5406.093861] sd 2:0:0:0: [sda] tag#402 CDB: Read(10) 28 00 00 24 ff 40 00 00 
08 00
[ 5406.093862] print_req_error: 2 callbacks suppressed
[ 5406.093863] blk_update_request: I/O error, dev sda, sector 2424640 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 5406.093868] Read-error on swap-device (8:0:2424648)
[ 5406.093937] sd 2:0:0:0: [sda] tag#403 FAILED 

[Kernel-packages] [Bug 1944754] Re: linux-tools-aws package does not contain libperf-jvmti.so

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.4.0-1058.61

---
linux-aws (5.4.0-1058.61) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1058.61 -proposed tracker (LP: #1944873)

  *  linux-tools-aws package does not contain libperf-jvmti.so (LP: #1944754)
- [Packaging] aws: Support building libperf-jvmti.so

  [ Ubuntu: 5.4.0-89.100 ]

  * focal/linux: 5.4.0-89.100 -proposed tracker (LP: #1944901)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.27)
  * ext4 journal recovery fails w/ data=journal + mmap (LP: #1847340)
- jbd2: introduce/export functions
  jbd2_journal_submit|finish_inode_data_buffers()
- jbd2, ext4, ocfs2: introduce/use journal callbacks
  j_submit|finish_inode_data_buffers()
- ext4: data=journal: fixes for ext4_page_mkwrite()
- ext4: data=journal: write-protect pages on j_submit_inode_data_buffers()
- ext4: fix mmap write protection for data=journal mode
  * CVE-2021-40490
- ext4: fix race writing to an inline_data file while its xattrs are 
changing
  * Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption" (LP: #1942902)
- Revert "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
  * psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/groovy/hirsute/impish (LP: #1892213)
- selftests/net: remove min gso test in packet_snd
  * Focal update: v5.4.143 upstream stable release (LP: #1944212)
- ext4: fix EXT4_MAX_LOGICAL_BLOCK macro
- x86/fpu: Make init_fpstate correct with optimized XSAVE
- ath: Use safer key clearing with key cache entries
- ath9k: Clear key cache explicitly on disabling hardware
- ath: Export ath_hw_keysetmac()
- ath: Modify ath_key_delete() to not need full key entry
- ath9k: Postpone key cache entry deletion for TXQ frames reference it
- mtd: cfi_cmdset_0002: fix crash when erasing/writing AMD cards
- media: zr364xx: propagate errors from zr364xx_start_readpipe()
- media: zr364xx: fix memory leaks in probe()
- media: drivers/media/usb: fix memory leak in zr364xx_probe
- USB: core: Avoid WARNings for 0-length descriptor requests
- dmaengine: xilinx_dma: Fix read-after-free bug when terminating transfers
- dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe()
- ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218
- dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is 
not
  yet available
- scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry()
- scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach()
- scsi: core: Avoid printing an error if target_alloc() returns -ENXIO
- scsi: core: Fix capacity set to zero after offlinining device
- ARM: dts: nomadik: Fix up interrupt controller node names
- net: usb: lan78xx: don't modify phy_device state concurrently
- drm/amd/display: Fix Dynamic bpp issue with 8K30 with Navi 1X
- Bluetooth: hidp: use correct wait queue when removing ctrl_wait
- iommu: Check if group is NULL before remove device
- cpufreq: armada-37xx: forbid cpufreq for 1.2 GHz variant
- dccp: add do-while-0 stubs for dccp_pr_debug macros
- virtio: Protect vqs list access
- vhost: Fix the calculation in vhost_overflow()
- bpf: Clear zext_dst of dead insns
- bnxt: don't lock the tx queue from napi poll
- bnxt: disable napi before canceling DIM
- net: 6pack: fix slab-out-of-bounds in decode_data
- ptp_pch: Restore dependency on PCI
- bnxt_en: Add missing DMA memory barriers
- vrf: Reset skb conntrack connection on VRF rcv
- virtio-net: support XDP when not more queues
- virtio-net: use NETIF_F_GRO_HW instead of NETIF_F_LRO
- net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32
- net: mdio-mux: Don't ignore memory allocation errors
- net: mdio-mux: Handle -EPROBE_DEFER correctly
- ovs: clear skb->tstamp in forwarding path
- i40e: Fix ATR queue selection
- iavf: Fix ping is lost after untrusted VF had tried to change MAC
- ovl: add splice file read write helper
- mmc: dw_mmc: Fix hang on data CRC error
- ALSA: hda - fix the 'Capture Switch' value change notifications
- tracing / histogram: Fix NULL pointer dereference on strcmp() on NULL 
event
  name
- slimbus: messaging: start transaction ids from 1 instead of zero
- slimbus: messaging: check for valid transaction id
- slimbus: ngd: reset dma setup during runtime pm
- ipack: tpci200: fix many double free issues in tpci200_pci_probe
- ipack: tpci200: fix memory leak in the tpci200_register
- btrfs: prevent rename2 from exchanging a subvol with a directory from
  different parents
- PCI: Increase D3 delay for AMD Renoir/Cezanne XHCI
- ASoC: intel: atom: Fix breakage for PCM buffer address setup
- mm, memcg: avoid stale protection values when cgroup 

[Kernel-packages] [Bug 1945351] Re: hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oracle - 5.11.0-1020.21

---
linux-oracle (5.11.0-1020.21) hirsute; urgency=medium

  * hirsute/linux-oracle: 5.11.0-1020.21 -proposed tracker (LP:
#1944856)

  * hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011 (LP: #1945351)
- [config] oracle: Enable CONFIG_SERIAL_AMBA_PL011

  [ Ubuntu: 5.11.0-38.42 ]

  * hirsute/linux: 5.11.0-38.42 -proposed tracker (LP: #1944863)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.09.27)
  * Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
(LP: #1936708)
- drm/i915/dp: Use max params for panels < eDP 1.4
  * Hirsute update: upstream stable patchset 2021-09-22 (LP: #1944610)
- net: qrtr: fix another OOB Read in qrtr_endpoint_post
- bpf: Fix ringbuf helper function compatibility
- bpf: Fix NULL pointer dereference in bpf_get_local_storage() helper
- ASoC: rt5682: Adjust headset volume button threshold
- ASoC: component: Remove misplaced prefix handling in pin control functions
- ARC: Fix CONFIG_STACKDEPOT
- netfilter: conntrack: collect all entries in one cycle
- once: Fix panic when module unload
- blk-iocost: fix lockdep warning on blkcg->lock
- ovl: fix uninitialized pointer read in ovl_lookup_real_one()
- net: mscc: Fix non-GPL export of regmap APIs
- can: usb: esd_usb2: esd_usb2_rx_event(): fix the interchange of the CAN RX
  and TX error counters
- ceph: correctly handle releasing an embedded cap flush
- riscv: Ensure the value of FP registers in the core dump file is up to 
date
- Revert "btrfs: compression: don't try to compress if we don't have enough
  pages"
- drm/amdgpu: Cancel delayed work when GFXOFF is disabled
- Revert "USB: serial: ch341: fix character loss at high transfer rates"
- USB: serial: option: add new VID/PID to support Fibocom FG150
- usb: renesas-xhci: Prefer firmware loading on unknown ROM state
- usb: dwc3: gadget: Fix dwc3_calc_trbs_left()
- usb: dwc3: gadget: Stop EP0 transfers during pullup disable
- scsi: core: Fix hang of freezing queue between blocking and running device
- RDMA/bnxt_re: Add missing spin lock initialization
- IB/hfi1: Fix possible null-pointer dereference in _extend_sdma_tx_descs()
- RDMA/bnxt_re: Remove unpaired rtnl unlock in bnxt_re_dev_init()
- ice: do not abort devlink info if board identifier can't be found
- net: usb: pegasus: fixes of set_register(s) return value evaluation;
- igc: Use num_tx_queues when iterating over tx_ring queue
- e1000e: Fix the max snoop/no-snoop latency for 10M
- RDMA/efa: Free IRQ vectors on error flow
- ip_gre: add validation for csum_start
- xgene-v2: Fix a resource leak in the error handling path of 'xge_probe()'
- net: marvell: fix MVNETA_TX_IN_PRGRS bit number
- net/sched: ets: fix crash when flipping from 'strict' to 'quantum'
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- cxgb4: dont touch blocked freelist bitmap after free
- rtnetlink: Return correct error on changing device netns
- net: hns3: clear hardware resource when loading driver
- net: hns3: add waiting time before cmdq memory is released
- net: hns3: fix duplicate node in VLAN list
- net: hns3: fix get wrong pfc_en when query PFC configuration
- net: stmmac: add mutex lock to protect est parameters
- net: stmmac: fix kernel panic due to NULL pointer dereference of plat->est
- drm/i915: Fix syncmap memory leak
- usb: gadget: u_audio: fix race condition on endpoint stop
- dt-bindings: sifive-l2-cache: Fix 'select' matching
- perf/x86/intel/uncore: Fix integer overflow on 23 bit left shift of a u32
- clk: renesas: rcar-usb2-clock-sel: Fix kernel NULL pointer dereference
- iwlwifi: pnvm: accept multiple HW-type TLVs
- opp: remove WARN when no valid OPPs remain
- cpufreq: blocklist Qualcomm sm8150 in cpufreq-dt-platdev
- virtio: Improve vq->broken access to avoid any compiler optimization
- virtio_pci: Support surprise removal of virtio pci device
- virtio_vdpa: reject invalid vq indices
- vringh: Use wiov->used to check for read/write desc order
- tools/virtio: fix build
- qed: qed ll2 race condition fixes
- qed: Fix null-pointer dereference in qed_rdma_create_qp()
- Revert "drm/amd/pm: fix workload mismatch on vega10"
- drm/amd/pm: change the workload type for some cards
- blk-mq: don't grab rq's refcount in blk_mq_check_expired()
- drm: Copy drm_wait_vblank to user before returning
- drm/nouveau/disp: power down unused DP links during init
- drm/nouveau/kms/nv50: workaround EFI GOP window channel format differences
- net/rds: dma_map_sg is entitled to merge entries
- btrfs: fix race between marking inode needs to be logged and log syncing
- pipe: 

[Kernel-packages] [Bug 1947699] Re: unmet dependency linux-modules-nvidia-470-generic

[liutianren]

The problem is resolved today.  
linux-modules-nvidia-470-generic no more has unmet dependency.

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

Title:
  unmet dependency linux-modules-nvidia-470-generic

Status in linux-restricted-modules package in Ubuntu:
  New

Bug description:
  # how to reproduce

  apt-get update
  apt-get dist-upgrade
  apt-get autoremove
  apt-get install -s linux-modules-nvidia-470-generic

  The following packages have unmet dependencies:
   linux-modules-nvidia-470-generic : Depends: 
linux-modules-nvidia-470-5.4.0-89-generic (= 5.4.0-89.100) but it is not going 
to be installed
  Depends: nvidia-kernel-common-470 (>= 
470.74) but 470.63.01-0ubuntu0.20.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.

  
  # version

  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  
  I recently upgraded the kernel from 5.11.0-36 to 5.11.0-38, then my lxc 
cannot boot.  The lxc can boot if I remove nvidia dependency.  Then I realized 
that nvidia kernel module was removed during the upgrade.

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


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

[Kernel-packages] [Bug 1946573] Re: Keyboard does not work at all with kernel 5.11.0-37-generic

[Dirk Peter]

"Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:

apport-collect 1946573"

Done. Sorry, that it takes 2 weeks.

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

Title:
  Keyboard does not work at all with kernel 5.11.0-37-generic

Status in linux-hwe-5.11 package in Ubuntu:
  Incomplete

Bug description:
  Version: Linux Mint 20.2 Cinnamon
  Device: Medion S17405
  Version.log says: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22

  Keyboard works under Windows and Grub
  It's a new installation, so it's maybe not a bug of this special kernel 
version

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


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

[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog

[Brian Murray]

** Tags added: rls-jj-incoming

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

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Confirmed
Status in ntfs-3g package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.2
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 1929901] Re: [EHL][TGL][ADL] EDAC support

[Anthony Wong]

** Changed in: linux-intel-5.13 (Ubuntu)
   Status: Confirmed => Fix Committed

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

** Changed in: intel
Milestone: None => sprint2

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

Title:
  [EHL][TGL][ADL] EDAC support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  Fix Released
Status in linux-intel-5.13 package in Ubuntu:
  Fix Committed

Bug description:
  Description
  EDAC driver support on EHL & TGL for reporting ECC error and DIMM location

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1947888] [NEW] Focal update: v5.4.151 upstream stable release

[Kamal Mostafa]

Public bug reported:

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.151 upstream stable release
   from git://git.kernel.org/

tty: Fix out-of-bound vmalloc access in imageblit
cpufreq: schedutil: Use kobject release() method to free sugov_tunables
cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory
usb: cdns3: fix race condition before setting doorbell
fs-verity: fix signed integer overflow with i_size near S64_MAX
hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure 
field
hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure 
field
hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure 
field
scsi: ufs: Fix illegal offset in UPIU event trace
mac80211: fix use-after-free in CCMP/GCMP RX
x86/kvmclock: Move this_cpu_pvti into kvmclock.h
drm/amd/display: Pass PCI deviceid into DC
ipvs: check that ip_vs_conn_tab_bits is between 8 and 20
hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced 
from sysfs
mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug
mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap
mac80211: mesh: fix potentially unaligned access
mac80211-hwsim: fix late beacon hrtimer handling
sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb
hwmon: (tmp421) report /PVLD condition as fault
hwmon: (tmp421) fix rounding for negative values
net: ipv4: Fix rtnexthop len when RTA_FLOW is present
e100: fix length calculation in e100_get_regs_len
e100: fix buffer overrun in e100_get_regs
selftests, bpf: test_lwt_ip_encap: Really disable rp_filter
scsi: csiostor: Add module softdep on cxgb4
net: hns3: do not allow call hns3_nic_net_open repeatedly
net: sched: flower: protect fl_walk() with rcu
af_unix: fix races in sk_peer_pid and sk_peer_cred accesses
perf/x86/intel: Update event constraints for ICX
elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings
debugfs: debugfs_create_file_size(): use IS_ERR to check for error
ipack: ipoctal: fix stack information leak
ipack: ipoctal: fix tty registration race
ipack: ipoctal: fix tty-registration error handling
ipack: ipoctal: fix missing allocation-failure check
ipack: ipoctal: fix module reference leak
ext4: fix loff_t overflow in ext4_max_bitmap_size()
ext4: fix reserved space counter leakage
ext4: fix potential infinite loop in ext4_dx_readdir()
HID: u2fzero: ignore incomplete packets without data
net: udp: annotate data race around udp_sk(sk)->corkflag
net: stmmac: don't attach interface until resume finishes
PCI: Fix pci_host_bridge struct device release/free handling
libnvdimm/pmem: Fix crash triggered when I/O in-flight during unbind
hso: fix bailout in error case of probe
usb: hso: fix error handling code of hso_create_net_device
usb: hso: remove the bailout parameter
crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
HID: betop: fix slab-out-of-bounds Write in betop_probe
netfilter: ipset: Fix oversized kvmalloc() calls
HID: usbhid: free raw_report buffers in usbhid_stop
Linux 5.4.151
UBUNTU: upstream stable to v5.4.151

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- 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:
  
- 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.151 upstream stable release
+    from git://git.kernel.org/
  
-

[Kernel-packages] [Bug 1947886] [NEW] Focal update: v5.4.150 upstream stable release

[Kamal Mostafa]

Public bug reported:

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.150 upstream stable release
   from git://git.kernel.org/

ocfs2: drop acl cache for directories too
usb: gadget: r8a66597: fix a loop in set_feature()
usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave
usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA
usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned()
cifs: fix incorrect check for null pointer in header_assemble
xen/x86: fix PV trap handling on secondary processors
usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c
USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter
USB: cdc-acm: fix minor-number release
binder: make sure fd closes complete
staging: greybus: uart: fix tty use after free
Re-enable UAS for LaCie Rugged USB3-FW with fk quirk
USB: serial: mos7840: remove duplicated 0xac24 device ID
USB: serial: option: add Telit LN920 compositions
USB: serial: option: remove duplicate USB device ID
USB: serial: option: add device id for Foxconn T99W265
mcb: fix error handling in mcb_alloc_bus()
erofs: fix up erofs_lookup tracepoint
btrfs: prevent __btrfs_dump_space_info() to underflow its free space
serial: mvebu-uart: fix driver's tx_empty callback
net: hso: fix muxed tty registration
afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation
platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR()
enetc: Fix illegal access when reading affinity_hint
bnxt_en: Fix TX timeout when TX ring size is set to the smallest
net/smc: add missing error check in smc_clc_prfx_set()
gpio: uniphier: Fix void functions to remove return value
qed: rdma - don't wait for resources under hw error recovery flow
net/mlx4_en: Don't allow aRFS for encapsulated packets
scsi: iscsi: Adjust iface sysfs attr detection
tty: synclink_gt, drop unneeded forward declarations
tty: synclink_gt: rename a conflicting function name
fpga: machxo2-spi: Return an error on failure
fpga: machxo2-spi: Fix missing error code in machxo2_write_complete()
thermal/core: Potential buffer overflow in thermal_build_list_of_policies()
cifs: fix a sign extension bug
scsi: qla2xxx: Restore initiator in dual mode
scsi: lpfc: Use correct scnprintf() limit
irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
irqchip/gic-v3-its: Fix potential VPE leak on error
md: fix a lock order reversal in md_alloc
blktrace: Fix uaf in blk_trace access after removing by sysfs
net: macb: fix use after free on rmmod
net: stmmac: allow CSR clock of 300MHz
m68k: Double cast io functions to unsigned long
ipv6: delay fib6_sernum increase in fib6_add
bpf: Add oversize check before call kvcalloc()
xen/balloon: use a kernel thread instead a workqueue
nvme-multipath: fix ANA state updates when a namespace is not present
sparc32: page align size in arch_dma_alloc
blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd
compiler.h: Introduce absolute_pointer macro
net: i825xx: Use absolute_pointer for memcpy from fixed memory location
sparc: avoid stringop-overread errors
qnx4: avoid stringop-overread errors
parisc: Use absolute_pointer() to define PAGE0
arm64: Mark __stack_chk_guard as __ro_after_init
alpha: Declare virt_to_phys and virt_to_bus parameter as pointer to volatile
net: 6pack: Fix tx timeout and slot time
spi: Fix tegra20 build with CONFIG_PM=n
EDAC/synopsys: Fix wrong value type assignment for edac_mode
thermal/drivers/int340x: Do not set a wrong tcc offset on resume
arm64: dts: marvell: armada-37xx: Extend PCIe MEM space
xen/balloon: fix balloon kthread freezing
qnx4: work around gcc false positive warning bug
Linux 5.4.150
UBUNTU: upstream stable to v5.4.150

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- 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 

[Kernel-packages] [Bug 1947885] [NEW] Focal update: v5.4.149 upstream stable release

[Kamal Mostafa]

Public bug reported:

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.149 upstream stable release
   from git://git.kernel.org/

PCI: pci-bridge-emul: Fix big-endian support
PCI: aardvark: Indicate error in 'val' when config read fails
PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
PCI: aardvark: Fix reporting CRS value
PCI/ACPI: Add Ampere Altra SOC MCFG quirk
KVM: remember position in kvm->vcpus array
console: consume APC, DM, DCS
s390/pci_mmio: fully validate the VMA before calling follow_pte()
ARM: Qualify enabling of swiotlb_init()
apparmor: remove duplicate macro list_entry_is_head()
ARM: 9077/1: PLT: Move struct plt_entries definition to header
ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
ARM: 9079/1: ftrace: Add MODULE_PLTS support
ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
sctp: validate chunk size in __rcv_asconf_lookup
sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
um: virtio_uml: fix memory leak on init failures
dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
9p/trans_virtio: Remove sysfs file on probe failure
prctl: allow to setup brk for et_dyn executables
nilfs2: use refcount_dec_and_lock() to fix potential UAF
profiling: fix shift-out-of-bounds bugs
pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
phy: avoid unnecessary link-up delay in polling mode
net: stmmac: reset Tx desc base address before restarting Tx
Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
thermal/core: Fix thermal_cooling_device_register() prototype
drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
parisc: Move pci_dev_is_behind_card_dino to where it is used
dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
dmaengine: ioat: depends on !UML
dmaengine: xilinx_dma: Set DMA mask for coherent APIs
ceph: request Fw caps before updating the mtime in ceph_write_iter
ceph: lockdep annotations for try_nonblocking_invalidate
btrfs: fix lockdep warning while mounting sprout fs
nilfs2: fix memory leak in nilfs_sysfs_create_device_group
nilfs2: fix NULL pointer in nilfs_##name##_attr_release
nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
pwm: img: Don't modify HW state in .remove() callback
pwm: rockchip: Don't modify HW state in .remove() callback
pwm: stm32-lp: Don't modify HW state in .remove() callback
blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
rtc: rx8010: select REGMAP_I2C
drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
Linux 5.4.149
UBUNTU: upstream stable to v5.4.149

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- 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:
  
- 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.149 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.149 upstream stable release
-from git://git.kernel.org/
+ PCI: pci-bridge-emul: Fix big-endian support
+ PCI: aardvark: Indicate error in 'val' when config read fails
+ PCI: 

[Kernel-packages] [Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was dissabled

[Stefan Bader]

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

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

Title:
  Re-enable DEBUG_INFO_BTF where it was dissabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux-hwe-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * pahole used to segfault on 32-bit platforms, which has now been
  fixed

   * pahole used to be too old in focal, which is now being SRUed

   * renable DEBUG_INFO_BTF in all the kernels/arches that had it
  disabled, as otherwise one cannot compile/use advanced BTF features on
  newer kernels.

  
  [Test Plan]

   * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y
   * Check build log that it contains
  ```
BTF .btf.vmlinux.bin.o
  ```

  [Where problems could occur]

   * In the future, kernel may require even newer version of pahole from
  dwarves, making the builds fail to build again, as building BTF debug
  information will now be required. Until either BTF is disabled again
  or pahole is upgraded again.

  [Other Info]
   
   * Latest pahole is available from focal-proposed, hirsute-proposed, impish 
release, builders-extra PPA

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


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

[Kernel-packages] [Bug 1947880] Re: Bad color profile

[Jairo Serrano]

Nvidia driver photo of monitor

** Attachment added: "Nvidia Driver.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947880/+attachment/5534626/+files/Nvidia%20Driver.jpg

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

Title:
  Bad color profile

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  On a fresh install, with opensource drivers, the colors show shows
  right, but when I install nvidia drivers, any version of that, the
  colors apparently lose gamma or contrast.

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


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

[Kernel-packages] [Bug 1947880] Re: Bad color profile

[Jairo Serrano]

With the open source driver... it looks more vibrant.

I try to adjust the options but it doesn't work.

Until now... I've never needed to touch color calibration or anything.

** Attachment added: "OpenSource Driver.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947880/+attachment/5534627/+files/OpenSource%20Driver.jpg

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

Title:
  Bad color profile

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  On a fresh install, with opensource drivers, the colors show shows
  right, but when I install nvidia drivers, any version of that, the
  colors apparently lose gamma or contrast.

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


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

[Kernel-packages] [Bug 1947880] [NEW] Bad color profile

[Jairo Serrano]

Public bug reported:

On a fresh install, with opensource drivers, the colors show shows
right, but when I install nvidia drivers, any version of that, the
colors apparently lose gamma or contrast.

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Bad color profile

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  On a fresh install, with opensource drivers, the colors show shows
  right, but when I install nvidia drivers, any version of that, the
  colors apparently lose gamma or contrast.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1947853

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

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

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

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

** Tags added: focal

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40

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


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

[Kernel-packages] [Bug 1947853] Re: ubuntu20.04 crash

[Brian Murray]

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

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

Title:
  ubuntu20.04 crash

Status in linux package in Ubuntu:
  New

Bug description:
  [4845314.925034] Call Trace:
  [4845314.925322]  shrink_active_list+0xc1/0x4b0
  [4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
  [4845314.926262]  shrink_node_memcg+0x28a/0x370
  [4845314.926715]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927230]  ? css_next_descendant_pre+0x54/0x70
  [4845314.927733]  shrink_node+0xbd/0x410
  [4845314.928126]  balance_pgdat+0x319/0x590
  [4845314.928538]  kswapd+0x1f8/0x3c0
  [4845314.928898]  ? wait_woken+0x80/0x80
  [4845314.929285]  kthread+0x104/0x140
  [4845314.929645]  ? balance_pgdat+0x590/0x590
  [4845314.930078]  ? kthread_park+0x90/0x90
  [4845314.930484]  ret_from_fork+0x22/0x40

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


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

[Kernel-packages] [Bug 1947853] [NEW] ubuntu20.04 crash

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[4845314.925034] Call Trace:
[4845314.925322]  shrink_active_list+0xc1/0x4b0
[4845314.925768]  ? shrink_inactive_list+0x297/0x3e0
[4845314.926262]  shrink_node_memcg+0x28a/0x370
[4845314.926715]  ? css_next_descendant_pre+0x54/0x70
[4845314.927230]  ? css_next_descendant_pre+0x54/0x70
[4845314.927733]  shrink_node+0xbd/0x410
[4845314.928126]  balance_pgdat+0x319/0x590
[4845314.928538]  kswapd+0x1f8/0x3c0
[4845314.928898]  ? wait_woken+0x80/0x80
[4845314.929285]  kthread+0x104/0x140
[4845314.929645]  ? balance_pgdat+0x590/0x590
[4845314.930078]  ? kthread_park+0x90/0x90
[4845314.930484]  ret_from_fork+0x22/0x40

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


** Tags: bot-comment
-- 
ubuntu20.04 crash
https://bugs.launchpad.net/bugs/1947853
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1941708] Re: BlueZ 5.62 release

[Sebastien Bacher]

uploaded

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

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

Title:
  BlueZ 5.62 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.62 release is out:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

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


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

[Kernel-packages] [Bug 1947851] Re: NFS v2 client fails to mount with timeout on kernel 5.11.0-10-19-aws

[José M . G . Moreira]

This bug report was created in the wrong package, it's related to 
https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.11/

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

Title:
  NFS v2 client fails to mount with timeout on kernel 5.11.0-10-19-aws

Status in linux-aws-5.4 package in Ubuntu:
  New

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  aws-5.4/+bug/1946032, NFS v4 client fails to mount with timeout on
  kernel `5.11.0-10-19-aws`.

  Current workaround, which has ben tested successfully, is to revert
  the kernel to `5.11.0-1017-aws`

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


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

[Kernel-packages] [Bug 1947875] [NEW] NFS v2 client fails to mount with timeout on kernel 5.11.0-10-19-aws Edit

[José M . G . Moreira]

Public bug reported:

Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
aws-5.4/+bug/1946032, NFS v4 client fails to mount with timeout on
kernel `5.11.0-10-19-aws`, Ubuntu 20 Focal.

Current workaround, which has been tested successfully, is to revert the
kernel to `5.11.0-1017-aws`

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


** Tags: focal

** Description changed:

  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  aws-5.4/+bug/1946032, NFS v4 client fails to mount with timeout on
- kernel `5.11.0-10-19-aws`.
+ kernel `5.11.0-10-19-aws`, Ubuntu 20 Focal.
  
- Current workaround, which has ben tested successfully, is to revert the
+ Current workaround, which has been tested successfully, is to revert the
  kernel to `5.11.0-1017-aws`

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

Title:
  NFS v2 client fails to mount with timeout on kernel 5.11.0-10-19-aws
  Edit

Status in linux-aws-5.11 package in Ubuntu:
  New

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  aws-5.4/+bug/1946032, NFS v4 client fails to mount with timeout on
  kernel `5.11.0-10-19-aws`, Ubuntu 20 Focal.

  Current workaround, which has been tested successfully, is to revert
  the kernel to `5.11.0-1017-aws`

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


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

[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics

[Andrew Berry]

Thanks for your prompt work on this.

I enabled the proposed repository and have upgraded the zfs packages. As
this fix is in the zfs kernel module, I thought I would need to update
the kernel packages too:

```
$ dpkg-query -S /lib/modules/5.4.0-89-generic/kernel/zfs/zfs.ko
linux-modules-5.4.0-89-generic: /lib/modules/5.4.0-89-generic/kernel/zfs/zfs.ko
```

I upgraded to `linux-image-5.4.0-90-generic`, but the module version
looks to be old:

```
[4.366482] ZFS: Loaded module v0.8.3-1ubuntu12.12, ZFS pool version 5000, 
ZFS filesystem version 5

$ uname -r
5.4.0-90-generic
```

I would have expected that version to be `0.8.3-1ubuntu12.14`. Any
suggestions?

```
$ dpkg -l | grep zfs
ii  libzfs2linux 0.8.3-1ubuntu12.14
amd64OpenZFS filesystem library for Linux
ii  zfs-auto-snapshot1.2.4-2   
all  ZFS automatic snapshot service
ii  zfs-initramfs0.8.3-1ubuntu12.14
amd64OpenZFS root filesystem capabilities for Linux - initramfs
ii  zfs-zed  0.8.3-1ubuntu12.14
amd64OpenZFS Event Daemon
ii  zfsutils-linux   0.8.3-1ubuntu12.14
amd64command-line tools to manage OpenZFS filesystems
```

```
$ dpkg -l | grep linux- | grep -v '^rc'
ii  linux-base   4.5ubuntu3.6  
all  Linux image base package
ii  linux-firmware   1.187.19  
all  Firmware for Linux kernel drivers
ii  linux-image-5.4.0-88-generic 5.4.0-88.99   
amd64Signed kernel image generic
ii  linux-image-5.4.0-89-generic 5.4.0-89.100  
amd64Signed kernel image generic
ii  linux-image-5.4.0-90-generic 5.4.0-90.101  
amd64Signed kernel image generic
ii  linux-image-generic  5.4.0.89.93   
amd64Generic Linux kernel image
ii  linux-modules-5.4.0-88-generic   5.4.0-88.99   
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-5.4.0-89-generic   5.4.0-89.100  
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-5.4.0-90-generic   5.4.0-90.101  
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-88-generic 5.4.0-88.99   
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-89-generic 5.4.0-89.100  
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
```

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

Title:
  Fix zfs_get_data access to files with wrong generation causing panics

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Committed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  == SRU Focal/Hirsute ==

  [Impact]

  ZFS: Fix a panic while acquiring a lock.

  If TX_WRITE is create on a file, and the file is later deleted and a new
  directory is created on the same object id, it is possible that when
  zil_commit happens, zfs_get_data will be called on the new directory.
  This may result in panic as it tries to do range lock. 

  Upstream ZFS bug #10593, #11682, upstream fix:

  commit 296a4a369bc1078a694f88570972330985b3b1b8
  Author: Chunwei Chen 
  Date: Fri Mar 19 22:53:31 2021 -0700

  Fix zfs_get_data access to files with wrong generation

  This patch fixes this issue by record the generation number during
  zfs_log_write, so zfs_get_data can check if the object is valid.

  The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a
  relatively simple backport with only minor backporting effort required
  in moving some of the module specific upstream changes into the pre-
  renamed module specific os specific parts of the ZFS module.

  [Test Plan]

  This is difficult to reproduce, see
  https://github.com/openzfs/zfs/issues/10593

  The fix has been tested with the complete ubuntu autotest ZFS
  regression tests that exercise ZFS core functionality (smoke tests),
  file system POSIX compliance (fs tests), extra XFS tests and every
  mount option with stress-ng file I/O stress tests.

  [Where problems could occur]

  This fix could regress the ZIL (ZFS intent log) commit writes since it
  modifies this code to now checks for generation numbers. Testing with
  ZFS autotests with intent logs have not 

[Kernel-packages] [Bug 1933248] Re: please drop virtualbox-guest-dkms virtualbox-guest-source

[Tim Gardner]

do_dkms_vbox is not set in Ubuntu-aws-5.4.0-1058.61 debian.aws. Tagging
verification-done-focal

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

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

Title:
  please drop virtualbox-guest-dkms virtualbox-guest-source

Status in linux package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Invalid
Status in virtualbox-hwe source package in Focal:
  Invalid

Bug description:
  [Impact]

   * virtualbox guest modules have graduated into the upstream vanilla
  kernel, since at least v5.4 / Ubuntu 20.04

   * These guest modules are no longer needed in dkms or source form, as
  they are always available from all kernel flavours, including when the
  packages are backported to Ubuntu 20.04.

   * Thus we should stop shipping them, and instead rely on the upstream
  ones.

  [Test Plan]

   * Boot virtualbox images
   * Check that guest-modules based integration still works.

  [Where problems could occur]

   * There might be differences between the linux kernel provided
  modules, guest userspace & host userspace tooling. If there are any
  differences, we would have to resolve the issues as needed to maintain
  backwards & forwards compatibility.

  [Other Info]
   
   * virtualbox guest modules fail to build from source with recent kernels.

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


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

[Kernel-packages] [Bug 1945351] Re: hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011

[Tim Gardner]

>From Ubuntu-oracle-5.11.0-1020.21:

debian.oracle/config/config.common.ubuntu:CONFIG_SERIAL_AMBA_PL011=y

Tagging verification-done-hirsute

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

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

Title:
  hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011

Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  No support for arm64 console currently

  [Fix]

  Add arm64 console support

  [Test]

  Confirm that it boots on desired arm64 hardware, as well as VMs, and
  produces console output.

  [Regression Potential]

  This was never working on arm64 so there should be no risk of
  regression.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1947866

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

Title:
  No Wi-fi device found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  20.4.3/5.11 does not find a Wi-Fi device/driver on the Lenovo P14s Gen 2. 
  Issue not present on 21.4 and 21.10 however as we are in a production 
environment we need to be on LTS version.

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


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

[Kernel-packages] [Bug 1947866] [NEW] No Wi-fi device found

[Rishi Sharda]

Public bug reported:

20.4.3/5.11 does not find a Wi-Fi device/driver on the Lenovo P14s Gen 2. 
Issue not present on 21.4 and 21.10 however as we are in a production 
environment we need to be on LTS version.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1947866

Title:
  No Wi-fi device found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  20.4.3/5.11 does not find a Wi-Fi device/driver on the Lenovo P14s Gen 2. 
  Issue not present on 21.4 and 21.10 however as we are in a production 
environment we need to be on LTS version.

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


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

[Kernel-packages] [Bug 1926892] Re: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Confirmed

Bug description:
  nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-440 450.119.03-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-50-generic
  Date: Sat May  1 07:39:10 2021
  Dependencies: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1 [origin: 
Ubuntu]
  InstallationDate: Installed on 2020-06-01 (335 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 440.100-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-450
  Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1943817] Re: Realtek 8852 wifi kernel module is missing

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1945967
   rtw89 kernel module for Realtek 8852 wifi is missing

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

Title:
  Realtek 8852 wifi kernel module is missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Just got a Thinkpad with Realtek 8852a wifi card. I installed Impish daily 
(kernel 5.13).
  Not recognized.
  The firmware is natively present in firmware folder, /rtw89/rtw8852a_fw.bin .

  But the kernel module is not loaded and in fact no module is loadable!
  sudo modprobe rtw8[completion] does not return this wifi card's module.

  So I did run for:
  https://github.com/lwfinger/rtw89
  and it does work but needs to be done for each kernel upgrade...

  Note that Bluetooth was natively ok.

  I tried 5.14 Ubuntu kernel from unstable ppa but same issue.

  lspci
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  fthx   2333 F pulseaudio
   /dev/snd/controlC1:  fthx   2333 F pulseaudio
   /dev/snd/controlC0:  fthx   2333 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-15 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 21AVFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-9-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9.9-generic 5.14.1
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9-generic N/A
   linux-backports-modules-5.14.0-9-generic  N/A
   linux-firmware1.199
  Tags:  impish
  Uname: Linux 5.14.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET39W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AVFR
  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.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21AVFR
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1947601] Re: Cannot start docker container on ubuntu 21.10 server for 64-bit raspberry pi

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => linux-raspi (Ubuntu)

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

Title:
  Cannot start docker container on ubuntu 21.10 server for 64-bit
  raspberry pi

Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Using the Ubuntu image for Raspberry Pi from here:
  https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-
  server-arm64+raspi.img.xz

  After installing the docker.io package, I cannot start a docker
  container. Example:

  $ sudo docker run --rm hello-world
  docker: Error response from daemon: failed to create endpoint pensive_greider 
on network bridge: failed to add the host (veth2102512) <=> sandbox 
(veth4fb66df) pair interfaces: operation not supported.

  This was working in the previous ubuntu release for 64 bit raspberry
  pi, 21.04.

  This problem is caused by the linux kernel shipped for ubuntu 21.10
  for 64 bit raspberry pi, see post #14.

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


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

[Kernel-packages] [Bug 1947859] [NEW] linux-azure: Updata MANA to 5.15-rc6

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

Microsoft has requested the addition of MANA EQ-sharing patch set which
is essentially everything up through v5.15-rc6.

3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure
Network Adapter (MANA). This saves MSI-X interrupts and allows the host
to offer more virtual ports (network interfaces) to the VM. With the
patches, the MANA driver supports up to 256 virtual ports per VF (it was
16/VF), and support up to 64 queues per vPort (it was 16).

[Test Case]

Microsoft to test and verify.

[Where things might go wrong]

More virtual ports may cause issues in older kernels.

[Other Info]

SF: #00321275

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-azure (Ubuntu Focal)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Impish)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

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

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

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

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

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

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

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

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

** Changed in: linux-azure (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Focal)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure (Ubuntu Hirsute)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure (Ubuntu Impish)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  linux-azure: Updata MANA to 5.15-rc6

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure source package in Impish:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of MANA EQ-sharing patch set
  which is essentially everything up through v5.15-rc6.

  3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure
  Network Adapter (MANA). This saves MSI-X interrupts and allows the
  host to offer more virtual ports (network interfaces) to the VM. With
  the patches, the MANA driver supports up to 256 virtual ports per VF
  (it was 16/VF), and support up to 64 queues per vPort (it was 16).

  [Test Case]

  Microsoft to test and verify.

  [Where things might go wrong]

  More virtual ports may cause issues in older kernels.

  [Other Info]

  SF: #00321275

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


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

[Kernel-packages] [Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function

[Frank Heimes]

Without further details there is no guarantee that this is caused by GPFS (in 
such cases a dump analysis is usually needed to find the root cause).
But scanning this log message for gpfs and mmfs tells me that gpfs is installed,
hence it's user space daemon (mmfsd) is running and (more importantly) the 
kernel module (mmfslinux) is active.
Third party kernel modules can cause issues, since they are usually developed 
towards a certain kernel version, and tend to start failing while the kernel 
evolves, hence the kernel is marked as "Tainted".
So this tells me that not the entire kernel/module combination that's running 
is pristine Ubuntu.

We usually ask to recreate this in a pristine Ubuntu environment (not
having a tainted kernel).

In addition I see the gpfs module listed in the call trace again (in 
combination with (ksys_lseek) which is another indicator:
[645967.290048] ([<001f80a8d2ca>] gpfs_f_llseek+0x4a/0x280 [mmfslinux])
[645967.290053] [<0001d75f5ed2>] ksys_lseek

The error/crash message provides just an overview - a look at the full
logs might be helpful.

Was the folder /var/crash checked for any content as well as the GPFS
logs (/var/adm/ras)?

And as already stated, it needs to be ensured that the system is on the latest 
(supported) level.
If its not the case, the situation needs to be recreated on the latest, hence 
currently supported level:
This "sudo apt update && apt-cache policy linux-generic"
will show your current kernel ('Installed'), but also where you should be 
("Candidate").

( This btw. would also apply to GPFS itself (being on the latest level):
http://files.gpfsug.org/presentations/2017/NERSC/GPFS-Troubleshooting-Apr-2017.pdf
 #22)

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

Title:
  [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic -
  rq_qos_wake_function

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  kernel panic rq_qos_wake_function
   
  ---uname output---
  Linux version 5.4.0-71-generic
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   May 15 20:21:04 data1 kernel: Call Trace:
  May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670)
  May 15 20:21:04 data1 kernel:  [<003e10047e3a>] 
rq_qos_wake_function+0x8a/0xa0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec482>] 
__wake_up_common+0xa2/0x1b0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec984>] 
__wake_up_common_lock+0x94/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec9fa>] __wake_up+0x2a/0x40 
  May 15 20:21:04 data1 kernel:  [<003e1005ee70>] wbt_done+0x90/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e10047f42>] __rq_qos_done+0x42/0x60 
  May 15 20:21:04 data1 kernel:  [<003e10033cb0>] 
blk_mq_free_request+0xe0/0x140 
  May 15 20:21:04 data1 kernel:  [<003e101d46f0>] 
dm_softirq_done+0x140/0x230 
  May 15 20:21:04 data1 kernel:  [<003e100326c0>] 
blk_done_softirq+0xc0/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e103fc084>] __do_softirq+0x104/0x360 
  May 15 20:21:04 data1 kernel:  [<003e0fb9da1e>] irq_exit+0x9e/0xc0 
  May 15 20:21:04 data1 kernel:  [<003e0fb28ae8>] do_IRQ+0x78/0xb0 
  May 15 20:21:04 data1 kernel:  [<003e103fb588>] 
ext_int_handler+0x130/0x134 
  May 15 20:21:04 data1 kernel:  [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 
  May 15 20:21:04 data1 kernel: Last Breaking-Event-Address:
  May 15 20:21:04 data1 kernel:  [<003e0fbce75e>] wake_up_process+0xe/0x20
  May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in 
interrupt
   
  Oops output:
   no
   
  System Dump Info:
The system was configured to capture a dump, however a dump was not 
produced.

  -Attach sysctl -a output output to the bug.

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


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

[Kernel-packages] [Bug 1943817] Re: Realtek 8852 wifi kernel module is missing

[Pirouette Cacahuète]

According to the series in https://patchwork.kernel.org/project/linux-
wireless/list/?series=559649=*, this has been accepted. rtw89 repo
now seems to have this v7 of the driver, and mentions it should be in
the next 5.16 kernel.

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

Title:
  Realtek 8852 wifi kernel module is missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Just got a Thinkpad with Realtek 8852a wifi card. I installed Impish daily 
(kernel 5.13).
  Not recognized.
  The firmware is natively present in firmware folder, /rtw89/rtw8852a_fw.bin .

  But the kernel module is not loaded and in fact no module is loadable!
  sudo modprobe rtw8[completion] does not return this wifi card's module.

  So I did run for:
  https://github.com/lwfinger/rtw89
  and it does work but needs to be done for each kernel upgrade...

  Note that Bluetooth was natively ok.

  I tried 5.14 Ubuntu kernel from unstable ppa but same issue.

  lspci
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  fthx   2333 F pulseaudio
   /dev/snd/controlC1:  fthx   2333 F pulseaudio
   /dev/snd/controlC0:  fthx   2333 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-15 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 21AVFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-9-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9.9-generic 5.14.1
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9-generic N/A
   linux-backports-modules-5.14.0-9-generic  N/A
   linux-firmware1.199
  Tags:  impish
  Uname: Linux 5.14.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET39W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AVFR
  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.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21AVFR
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1947851] [NEW] NFS v2 client fails to mount with timeout on kernel 5.11.0-10-19-aws

[José M . G . Moreira]

Public bug reported:

Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
aws-5.4/+bug/1946032, NFS v4 client fails to mount with timeout on
kernel `5.11.0-10-19-aws`.

Current workaround, which has ben tested successfully, is to revert the
kernel to `5.11.0-1017-aws`

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

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

Title:
  NFS v2 client fails to mount with timeout on kernel 5.11.0-10-19-aws

Status in linux-aws-5.4 package in Ubuntu:
  New

Bug description:
  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  aws-5.4/+bug/1946032, NFS v4 client fails to mount with timeout on
  kernel `5.11.0-10-19-aws`.

  Current workaround, which has ben tested successfully, is to revert
  the kernel to `5.11.0-1017-aws`

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


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

[Kernel-packages] [Bug 1946032] Re: NFS client fails to mount with timeout on kernel 5.4.0-1057-aws

[José M . G . Moreira]

same behavior has been reproduced in Ubuntu 20, kernel 5.11.0-10-19-aws

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

Title:
  NFS client fails to mount with timeout on kernel 5.4.0-1057-aws

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu 18.04.1 server, I mount AWS EFS filesystems with nfsv4.1
  successfully on ec2 instances.

  Mounts work on kernel version 5.4.0-1056-aws but if i upgrade the
  kernel to 5.4.0-1057-aws the mounts stop working with a network
  timeout, due to port 111 being blocked as its not needed for nfsv4

  Issue started to happen when apt daily automatically upgraded the
  kernel version. I reproduced by rolling back kernel version on the
  same instance and doing mounts successfully, then reverting to newer
  kernel (plus reboot) and getting the network timeout issue.

  Mount command is identical in all cases and follows AWS Documentation

  ```
  sudo mount -t nfs -o 
nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport 
mount-target-DNS:/   ~/efs-mount-point  
  ```

  Could it be a kernel bug or misconfiguration, what can i do ?

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


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

[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=212461.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2021-03-28T08:17:23+00:00 dor.askayo wrote:

Issue description

Distinct input events can incorrectly share the same timestamp, even
though they were actually generated a few milliseconds (or even seconds)
apart and a "SYN_REPORT" event occurred between them. See example output
below.

...
Event: time 1616757853.303892, -- SYN_REPORT 
Event: time 1616757853.337911, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.337911, -- SYN_REPORT 
Event: time 1616757853.372886, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.372886, -- SYN_REPORT 
Event: time 1616757853.406914, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.406914, -- SYN_REPORT 
Event: time 1616757853.440892, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.440892, -- SYN_REPORT 
Event: time 1616757853.474907, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.474907, -- SYN_REPORT 
Event: time 1616757853.508886, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.508886, -- SYN_REPORT 
Event: time 1616757853.508886, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e4
Event: time 1616757853.508886, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 0
Event: time 1616757853.508886, -- SYN_REPORT 

Reproduction steps

To reproduce the above:
1. Run evtest and select a device that supports emulated repeat events. (such 
as a keyboard)
2. Press and hold a key for a few seconds and then release.
3. Notice that the "release" event (value 2) incorrectly shares the same 
timestamp as the last repeat event "value 0".

Prior work

* A similar issue was fixed in 6c7e54bd5fda ("Input: reset device timestamp on 
sync") by making sure the timestamp is reset after a "SYN_REPORT" event is 
generated, forcing a new timestamp to be created for following events. However, 
it only handled the case of events that were sent to the input_handle_event() 
function, and didn't cover "SYN_REPORT" events that were generated internally 
in the input core, such as emulated repeat events.
* Another similar issue was fixed by cb5a89cdbaec ("Input: fix stale timestamp 
on key autorepeat events") which made sure that each repeat event got an 
updated timestamp. However, it didn't prevent those timestamps from becoming 
stale and used by following events.

Proposed fix

The attached patch resets the timestamp similarly to 6c7e54bd5fda
("Input: reset device timestamp on sync"), but does so in every case a
"SYN_REPORT" event is generated by the input core. The idea being that
the next event sequence would then be forced to get a new timestamp.

Related issues

* https://bugzilla.kernel.org/show_bug.cgi?id=206929 - The original bug report 
where this issue was reported, which was only partially fixed by cb5a89cdbaec 
("Input: fix stale timestamp on key autorepeat events"). While "repeat" events 
had their timestamps update correctly, the "release" event did not.
* https://gitlab.freedesktop.org/libinput/libinput/-/issues/571#note_83 - 
An issue about errors constantly being printed by libinput about delay in 
handling of events. The investigation of this issue revealed the reported bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/comments/22


On 2021-03-28T09:16:55+00:00 dor.askayo wrote:

Created attachment 296099
0001-Input-reset-timestamp-after-SYN_REPORT-events.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/comments/23


On 2021-06-15T08:10:50+00:00 michel wrote:

I suspect you need to just submit the patch by e-mail according to the
kernel development process. Running

 scripts/get_maintainer.pl 0001-Input-reset-timestamp-after-SYN_REPORT-
events.patch

in a kernel tree prints the maintainers and lists where the patch should
be sent to.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/comments/25


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

** Bug watch added: Linux Kernel Bug Tracker #206929
   https://bugzilla.kernel.org/show_bug.cgi?id=206929

** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #571
   

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

[bugproxy]

--- Comment From kgr...@de.ibm.com 2021-10-20 06:08 EDT---
Hi Frank,

thanks for the summary! Closing this bug now...

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

Title:
  [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Problems occur in IBM z/VM's IUCV (Inter User Communication Vehicle)
  environments and its communication.

  * Errors like "usercopy: Kernel memory overwrite attempt detected to
  SLUB object 'dma-kmalloc-1 k' (offset 0, size 11)!" pop up and cause
  failures.

  * This is because IUCV uses kmalloc() with __GFP_DMA because of memory
  address restrictions.

  * The solution is to mark dma-kmalloc caches as usercopy caches.

  [Fix]

  * 49f2d2419d60a103752e5fbaf158cf8d07c0d884 49f2d2419d60 "usercopy:
  mark dma-kmalloc caches as usercopy caches"

  * Due to changes in the context of the upstream patch,
a cherry-pick was not possible and the following backport was created:

https://bugs.launchpad.net/bugs/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch

  [Test Case]

  * Setup Ubuntu Server 20.04 on s390x system as IBM z/VM guest aka
  virtual machine.

  * Setup IUCV on z/VM: Setting up the (IUCV TCPIP) service machine:
  
https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_tcpservice.html

  * Set up a Linux IUCV instance:
  
https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_scen1_guest.html

  * Set up an IUCV direct:
  
https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_c_iucv_connect.html

  * Make use of IUCV, for example using ssh on a direct connection.

  * Verify if the connections is stable and watch out for messages
  starting with "usercopy".

  [Regression Potential]

  * Problems could occur in case the create_kmalloc_cache call is done wrong,
for example with wrong index, wrong size or just wrong comma separations.

  * Wrong size or index will probably lead to similar instability
  problems that exist today.

  * Problems in the syntax (commas etc.) will be detected at compile
  time.

  * But it's just a single line modification in function
  create_kmalloc_caches of /mm/slab_common.c,

  * so the change is very limited and quite traceable.

  * And it was in depth discussed here:

https://lore.kernel.org/kernel-hardening/1515636190-24061-2-git-send-email-keesc...@chromium.org/

  * a reviewed by a lot of kernel engineers (see provenance)

  * and it was already upstream accepted with kernel 5.8.

  [Other]

  * Since the commit is upstream accepted with 5.8, so it's already in
  impish and hirsute (and groovy).

  * Hence this kernel SRU submission is for Focal only and covers only the 
above single but common code commit/patch.
  __

  When I deployed a Ubuntu20.04 instance with kernel version of
  5.4.0-58-generic under z/VM, I saw below messages from kernel and the
  iucvserv program malfunctioned. Hence it caused some devices like
  network device configuration failure and deployment failure.

  Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from 
IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check 
authorization.
  Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, 
len=7
  Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded 
version is 0.0.0.1
  Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd  2>&1; 
echo iucvcmdrc=$? sent from IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message 
length=14,#012 /#012iucvcmdrc=0
  Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here 
]
  Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy 
whitelist? Kernel memory exposure attempt detected from SLUB object 
'dma-kmalloc-1k' (offset 0, size 20)!
  Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at 
mm/usercopy.c:75 usercopy_warn+0xa0/0xd0
  Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag 
udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT 
nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr
  ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev 
s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm
  _panel_orientation_quirks i2c_core ip_tables x_tables btrfs 

[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!

[Mikko Tanner]

Another data point here:

kernel: [5150033.094216] kernel BUG at lib/string.c:1149!
kernel: [5150033.094224] invalid opcode:  [#1] SMP NOPTI
kernel: [5150033.094229] CPU: 1 PID: 2940890 Comm: mount.ocfs2 Tainted: P   
OE 5.13.12-051312-generic #202108181219-Ubuntu
kernel: [5150033.094233] Hardware name: Gigabyte Technology Co., Ltd. X399 
DESIGNARE EX/X399 DESIGNARE EX-CF, BIOS F12i 09/24/2019
kernel: [5150033.094236] RIP: 0010:fortify_panic+0x13/0x15
kernel: [5150033.094244] Code: 35 37 a8 3b 01 48 c7 c7 93 63 01 b6 e8 c9 c9 fe 
ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 e0 63 01 b6 48 89 e5 e8 b0 c9 fe ff 
<0f> 0b 48 c7 c7 18 dc c8 b5 e8 df ff ff ff 48 c7 c7 10 dc c8 b5 e8
kernel: [5150033.094248] RSP: 0018:b4f1ee523c50 EFLAGS: 00010246
kernel: [5150033.094252] RAX: 0022 RBX: 9cf5639bb000 RCX: 

kernel: [5150033.094254] RDX:  RSI: 9d033e2589c0 RDI: 
9d033e2589c0
kernel: [5150033.094257] RBP: b4f1ee523c50 R08: 9d033e2589c0 R09: 
b4f1ee523a30
kernel: [5150033.094258] R10: 0001 R11: 0001 R12: 
0004
kernel: [5150033.094260] R13: 9cf496853000 R14: 9d00f6a91000 R15: 
9cf5639bb291
kernel: [5150033.094262] FS:  7fb7fd6d3b80() GS:9d033e24() 
knlGS:
kernel: [5150033.094265] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [5150033.094267] CR2: 55f52c08f040 CR3: 00029a09e000 CR4: 
003506e0
kernel: [5150033.094270] Call Trace:
kernel: [5150033.094276]  ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2]
kernel: [5150033.094347]  ? ocfs2_verify_volume+0x143/0x310 [ocfs2]
kernel: [5150033.094410]  ocfs2_fill_super+0x262/0xda0 [ocfs2]
kernel: [5150033.094473]  mount_bdev+0x18d/0x1c0
kernel: [5150033.094478]  ? ocfs2_initialize_super.isra.0+0x1070/0x1070 [ocfs2]
kernel: [5150033.094539]  ocfs2_mount+0x15/0x20 [ocfs2]
kernel: [5150033.094599]  legacy_get_tree+0x2b/0x50
kernel: [5150033.094604]  vfs_get_tree+0x2a/0xc0
kernel: [5150033.094607]  ? capable+0x19/0x20
kernel: [5150033.094612]  path_mount+0x468/0xa60
kernel: [5150033.094617]  do_mount+0x7c/0xa0
kernel: [5150033.094620]  __x64_sys_mount+0x8b/0xe0
kernel: [5150033.094623]  do_syscall_64+0x61/0xb0
kernel: [5150033.094627]  ? syscall_exit_to_user_mode+0x27/0x50
kernel: [5150033.094632]  ? __x64_sys_readlink+0x1f/0x30
kernel: [5150033.094635]  ? do_syscall_64+0x6e/0xb0
kernel: [5150033.094638]  ? irqentry_exit+0x19/0x30
kernel: [5150033.094641]  ? exc_page_fault+0x8f/0x170
kernel: [5150033.094645]  ? asm_exc_page_fault+0x8/0x30
kernel: [5150033.094649]  entry_SYSCALL_64_after_hwframe+0x44/0xae
kernel: [5150033.094651] RIP: 0033:0x7fb7fd88cdde
kernel: [5150033.094679] Code: 48 8b 0d b5 80 0c 00 f7 d8 64 89 01 48 83 c8 ff 
c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 
<48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 82 80 0c 00 f7 d8 64 89 01 48
kernel: [5150033.094682] RSP: 002b:7ffea9610c18 EFLAGS: 0246 ORIG_RAX: 
00a5
kernel: [5150033.094686] RAX: ffda RBX:  RCX: 
7fb7fd88cdde
kernel: [5150033.094688] RDX: 55cd6acb10ae RSI: 55cd6c9a7340 RDI: 
55cd6c9ac140
kernel: [5150033.094689] RBP: 7ffea9610dc0 R08: 55cd6c9ac0e0 R09: 
7ffea960e650
kernel: [5150033.094691] R10:  R11: 0246 R12: 
7ffea9610cb0
kernel: [5150033.094693] R13: 7ffea9610c30 R14: 55cd6c9ac0e0 R15: 

kernel: [5150033.094696] Modules linked in: ocfs2_stack_o2cb ocfs2_dlm ocfs2 
ocfs2_nodemanager ocfs2_stackglue quota_tree nft_reject_inet nf_reject_ipv4 
nf_reject_ipv6 nft_reject nft_ct nft_counter nft_limit nft_meta_bridge bridge 
stp llc snd_seq_dummy vhost_net vhost vhost_iotlb tap rfcomm nf_tables 
ip6table_filter ip6_tables iptable_filter bpfilter wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 
libcurve25519_generic libchacha libblake2s_generic ip6_udp_tunnel udp_tunnel 
nfnetlink_cttimeout nfnetlink cmac algif_hash openvswitch nsh algif_skcipher 
nf_conncount af_alg nf_nat bnep nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common amd64_edac 
edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio crypto_simd 
snd_hda_codec_hdmi cryptd rapl iwlmvm snd_hda_intel snd_intel_dspcfg 
snd_intel_sdw_acpi mac80211 uvcvideo
kernel: [5150033.094758]  snd_hda_codec videobuf2_vmalloc videobuf2_memops 
snd_hda_core snd_seq_midi videobuf2_v4l2 btusb snd_seq_midi_event libarc4 btrtl 
videobuf2_common snd_hwdep snd_rawmidi btbcm btintel videodev snd_seq joydev 
gigabyte_wmi mc input_leds serio_raw snd_pcm snd_seq_device wmi_bmof bluetooth 
iwlwifi snd_timer ecdh_generic efi_pstore snd ecc ccp mxm_wmi cfg80211 k10temp 
soundcore lz4 lz4_compress mac_hid nvidia_uvm(POE) tcp_htcp sch_cake ib_umad 

[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!

[Launchpad Bug Tracker]

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

** Changed in: ocfs2-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  mount.ocfs2 causes kernel BUG at lib/string.c:1149!

Status in corosync package in Ubuntu:
  Confirmed
Status in libaio package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ocfs2-tools package in Ubuntu:
  Confirmed

Bug description:
  the ocfs2-tools autopkgtests for hirsute recently started failing, and
  a local test run shows this kernel bug occurring during the test:

  [  100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E
  [  108.864491] detected buffer overflow in strlen
  [  108.869193] [ cut here ]
  [  108.869196] kernel BUG at lib/string.c:1149!
  [  108.869962] invalid opcode:  [#1] SMP PTI
  [  108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 
5.11.0-11-generic #12-Ubuntu
  [  108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
  [  108.873701] RIP: 0010:fortify_panic+0x13/0x15
  [  108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.882165] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.883474] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 
0004
  [  108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 
926a4cd06291
  [  108.887163] FS:  7f8440b60600() GS:926b77bc() 
knlGS:
  [  108.888626] CS:  0010 DS:  ES:  CR0: 80050033
  [  108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 
06e0
  [  108.890823] Call Trace:
  [  108.891279]  ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2]
  [  108.892603]  ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2]
  [  108.893484]  ? pointer+0x185/0x4d0
  [  108.894079]  ocfs2_fill_super+0x15d/0x7a0 [ocfs2]
  [  108.894965]  mount_bdev+0x18d/0x1c0
  [  108.895570]  ? ocfs2_remount+0x450/0x450 [ocfs2]
  [  108.896518]  ocfs2_mount+0x15/0x20 [ocfs2]
  [  108.897293]  legacy_get_tree+0x2b/0x50
  [  108.897939]  vfs_get_tree+0x2a/0xc0
  [  108.898542]  do_new_mount+0x14b/0x1a0
  [  108.899175]  path_mount+0x1d4/0x4e0
  [  108.899789]  __x64_sys_mount+0x108/0x140
  [  108.900465]  do_syscall_64+0x38/0x90
  [  108.901129]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  108.902376] RIP: 0033:0x7f8441109bce
  [  108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 
0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48
  [  108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 
00a5
  [  108.907610] RAX: ffda RBX:  RCX: 
7f8441109bce
  [  108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 
55eec2b8f060
  [  108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 
7fff92a4bd00
  [  108.912443] R10:  R11: 0246 R12: 
7fff92a4e390
  [  108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: 

  [  108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs 
ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache 
nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev 
bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper 
parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops 
serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg 
sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover 
virtio_blk i2c_piix4 pata_acpi floppy
  [  108.925313] ---[ end trace 72e4f69b08b1a89a ]---
  [  108.927136] RIP: 0010:fortify_panic+0x13/0x15
  [  108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.934468] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.935659] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.936933] R10: a9cf811afa80 R11: 92f53508 

[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!

[Launchpad Bug Tracker]

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

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

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

Title:
  mount.ocfs2 causes kernel BUG at lib/string.c:1149!

Status in corosync package in Ubuntu:
  Confirmed
Status in libaio package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ocfs2-tools package in Ubuntu:
  Confirmed

Bug description:
  the ocfs2-tools autopkgtests for hirsute recently started failing, and
  a local test run shows this kernel bug occurring during the test:

  [  100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E
  [  108.864491] detected buffer overflow in strlen
  [  108.869193] [ cut here ]
  [  108.869196] kernel BUG at lib/string.c:1149!
  [  108.869962] invalid opcode:  [#1] SMP PTI
  [  108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 
5.11.0-11-generic #12-Ubuntu
  [  108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
  [  108.873701] RIP: 0010:fortify_panic+0x13/0x15
  [  108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.882165] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.883474] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 
0004
  [  108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 
926a4cd06291
  [  108.887163] FS:  7f8440b60600() GS:926b77bc() 
knlGS:
  [  108.888626] CS:  0010 DS:  ES:  CR0: 80050033
  [  108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 
06e0
  [  108.890823] Call Trace:
  [  108.891279]  ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2]
  [  108.892603]  ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2]
  [  108.893484]  ? pointer+0x185/0x4d0
  [  108.894079]  ocfs2_fill_super+0x15d/0x7a0 [ocfs2]
  [  108.894965]  mount_bdev+0x18d/0x1c0
  [  108.895570]  ? ocfs2_remount+0x450/0x450 [ocfs2]
  [  108.896518]  ocfs2_mount+0x15/0x20 [ocfs2]
  [  108.897293]  legacy_get_tree+0x2b/0x50
  [  108.897939]  vfs_get_tree+0x2a/0xc0
  [  108.898542]  do_new_mount+0x14b/0x1a0
  [  108.899175]  path_mount+0x1d4/0x4e0
  [  108.899789]  __x64_sys_mount+0x108/0x140
  [  108.900465]  do_syscall_64+0x38/0x90
  [  108.901129]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  108.902376] RIP: 0033:0x7f8441109bce
  [  108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 
0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48
  [  108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 
00a5
  [  108.907610] RAX: ffda RBX:  RCX: 
7f8441109bce
  [  108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 
55eec2b8f060
  [  108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 
7fff92a4bd00
  [  108.912443] R10:  R11: 0246 R12: 
7fff92a4e390
  [  108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: 

  [  108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs 
ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache 
nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev 
bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper 
parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops 
serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg 
sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover 
virtio_blk i2c_piix4 pata_acpi floppy
  [  108.925313] ---[ end trace 72e4f69b08b1a89a ]---
  [  108.927136] RIP: 0010:fortify_panic+0x13/0x15
  [  108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.934468] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.935659] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.936933] R10: a9cf811afa80 R11: 92f53508 R12: 

[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!

[Launchpad Bug Tracker]

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

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

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

Title:
  mount.ocfs2 causes kernel BUG at lib/string.c:1149!

Status in corosync package in Ubuntu:
  Confirmed
Status in libaio package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ocfs2-tools package in Ubuntu:
  Confirmed

Bug description:
  the ocfs2-tools autopkgtests for hirsute recently started failing, and
  a local test run shows this kernel bug occurring during the test:

  [  100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E
  [  108.864491] detected buffer overflow in strlen
  [  108.869193] [ cut here ]
  [  108.869196] kernel BUG at lib/string.c:1149!
  [  108.869962] invalid opcode:  [#1] SMP PTI
  [  108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 
5.11.0-11-generic #12-Ubuntu
  [  108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
  [  108.873701] RIP: 0010:fortify_panic+0x13/0x15
  [  108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.882165] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.883474] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 
0004
  [  108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 
926a4cd06291
  [  108.887163] FS:  7f8440b60600() GS:926b77bc() 
knlGS:
  [  108.888626] CS:  0010 DS:  ES:  CR0: 80050033
  [  108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 
06e0
  [  108.890823] Call Trace:
  [  108.891279]  ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2]
  [  108.892603]  ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2]
  [  108.893484]  ? pointer+0x185/0x4d0
  [  108.894079]  ocfs2_fill_super+0x15d/0x7a0 [ocfs2]
  [  108.894965]  mount_bdev+0x18d/0x1c0
  [  108.895570]  ? ocfs2_remount+0x450/0x450 [ocfs2]
  [  108.896518]  ocfs2_mount+0x15/0x20 [ocfs2]
  [  108.897293]  legacy_get_tree+0x2b/0x50
  [  108.897939]  vfs_get_tree+0x2a/0xc0
  [  108.898542]  do_new_mount+0x14b/0x1a0
  [  108.899175]  path_mount+0x1d4/0x4e0
  [  108.899789]  __x64_sys_mount+0x108/0x140
  [  108.900465]  do_syscall_64+0x38/0x90
  [  108.901129]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  108.902376] RIP: 0033:0x7f8441109bce
  [  108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 
0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48
  [  108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 
00a5
  [  108.907610] RAX: ffda RBX:  RCX: 
7f8441109bce
  [  108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 
55eec2b8f060
  [  108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 
7fff92a4bd00
  [  108.912443] R10:  R11: 0246 R12: 
7fff92a4e390
  [  108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: 

  [  108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs 
ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache 
nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev 
bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper 
parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops 
serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg 
sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover 
virtio_blk i2c_piix4 pata_acpi floppy
  [  108.925313] ---[ end trace 72e4f69b08b1a89a ]---
  [  108.927136] RIP: 0010:fortify_panic+0x13/0x15
  [  108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 
41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 
c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8
  [  108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246
  [  108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: 

  [  108.934468] RDX:  RSI: 926b77bd8ac0 RDI: 
926b77bd8ac0
  [  108.935659] RBP: a9cf811afc90 R08:  R09: 
a9cf811afa88
  [  108.936933] R10: a9cf811afa80 R11: 92f53508 R12: 

[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[RBX2]

As for comment #43, I believe the patch will work. I'm not able, however, to do 
the testing in such a short time. 
Is it possible to extend at least for 2 more weeks? Thank you.

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

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

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-67-generic N/A
   linux-backports-modules-5.4.0-67-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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/1920674/+subscriptions


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

[Kernel-packages] [Bug 1946032] Re: NFS client fails to mount with timeout on kernel 5.4.0-1057-aws

[Launchpad Bug Tracker]

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

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

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

Title:
  NFS client fails to mount with timeout on kernel 5.4.0-1057-aws

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu 18.04.1 server, I mount AWS EFS filesystems with nfsv4.1
  successfully on ec2 instances.

  Mounts work on kernel version 5.4.0-1056-aws but if i upgrade the
  kernel to 5.4.0-1057-aws the mounts stop working with a network
  timeout, due to port 111 being blocked as its not needed for nfsv4

  Issue started to happen when apt daily automatically upgraded the
  kernel version. I reproduced by rolling back kernel version on the
  same instance and doing mounts successfully, then reverting to newer
  kernel (plus reboot) and getting the network timeout issue.

  Mount command is identical in all cases and follows AWS Documentation

  ```
  sudo mount -t nfs -o 
nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport 
mount-target-DNS:/   ~/efs-mount-point  
  ```

  Could it be a kernel bug or misconfiguration, what can i do ?

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


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

[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"

[Daniel van Vugt]

There is a kernel regression that causes some of the problem:

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

But other than that it should be mostly fixed, not entirely, in GNOME
40.

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

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

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

** Bug watch added: Linux Kernel Bug Tracker #212461
   https://bugzilla.kernel.org/show_bug.cgi?id=212461

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=212461
   Importance: Unknown
   Status: Unknown

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

Title:
  libinput says "your system is too slow"

Status in GNOME Shell:
  Unknown
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  During the freeze, the output of the install had a message from "gdm-
  x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr  3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5570
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed quiet splash ---
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[jeremyszu]

** Tags added: originate-from-1936920 stella

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Impish:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Sometimes MT7921 may not be probed due to an endless mcu reset:

[ 5.789548] mt7921 mcu reset 0
[ 5.790625] mt7921 rx type 0x7
[ 5.790625] mt7921 eid 0x1 ext_eid 0x0
[ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0

  [Fix]

  WiFi and Bluetooth firmware updates from mainline:
  * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip 
(MT7921)
  * d34196f5 linux-firmware: update firmware for MT7921 WiFi device

  [Test Case]

  This should fix the mcu reset and wireless/bluetooh devices should be
  probed successfully.

  [Where problems could occur]

  While there is explicit FW API for kernel version compatibility checking,
  this might introduce some hidden glitches that we don't know yet.

  [Other Info]

  MT7921 is supported since Impish 5.13 kernel, and Impish already has the
  latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13
  and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are
  required.

  == original bug report ==

  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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


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

[Kernel-packages] [Bug 1947601] Re: Cannot start docker container on ubuntu 21.10 server for 64-bit raspberry pi

[ianmacs]

** Description changed:

  Using the Ubuntu image for Raspberry Pi from here:
  https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-
  server-arm64+raspi.img.xz
  
  After installing the docker.io package, I cannot start a docker
  container. Example:
  
  $ sudo docker run --rm hello-world
  docker: Error response from daemon: failed to create endpoint pensive_greider 
on network bridge: failed to add the host (veth2102512) <=> sandbox 
(veth4fb66df) pair interfaces: operation not supported.
  
  This was working in the previous ubuntu release for 64 bit raspberry pi,
  21.04.
  
- Searching for this error suggests it could be a problem with linux
- kernel module availability.
- 
- Attaching info generated by ubuntu-bug for package linux-image-raspi. I
- can only attach 1 file, therefore inlining the ubuntu-bug info for
- package docker.io (output is far shorter than for the kernel):
- 
- ProblemType: Bug
- ApportVersion: 2.20.11-0ubuntu70
- Architecture: arm64
- CasperMD5CheckResult: unknown
- Date: Mon Oct 18 14:10:27 2021
- Dependencies:
-  adduser 3.118ubuntu5
-  apparmor 3.0.3-0ubuntu1
-  apt 2.3.9
-  apt-utils 2.3.9
-  bridge-utils 1.7-1ubuntu2
-  ca-certificates 20210119ubuntu1
-  containerd 1.5.5-0ubuntu3
-  dbus 1.12.20-2ubuntu2
-  debconf 1.5.77
-  debconf-i18n 1.5.77
-  dmsetup 2:1.02.175-2.1ubuntu3
-  dns-root-data 2021011101
-  dnsmasq-base 2.85-1ubuntu2
-  dpkg 1.20.9ubuntu2
-  gcc-11-base 11.2.0-7ubuntu2
-  git 1:2.32.0-1ubuntu1
-  git-man 1:2.32.0-1ubuntu1
-  gpgv 2.2.20-1ubuntu4
-  iproute2 5.10.0-4ubuntu1
-  iptables 1.8.7-1ubuntu2
-  less 551-2
-  libacl1 2.2.53-10ubuntu2
-  libapparmor1 3.0.3-0ubuntu1
-  libapt-pkg6.0 2.3.9
-  libatm1 1:2.5.1-4build1
-  libaudit-common 1:3.0-2ubuntu2
-  libaudit1 1:3.0-2ubuntu2
-  libbpf0 1:0.4.0-1ubuntu1
-  libbrotli1 1.0.9-2build3
-  libbsd0 0.11.3-1ubuntu2
-  libbz2-1.0 1.0.8-4ubuntu3
-  libc6 2.34-0ubuntu3
-  libcap-ng0 0.7.9-2.2build1
-  libcap2 1:2.44-1build1
-  libcap2-bin 1:2.44-1build1
-  libcom-err2 1.46.3-1ubuntu3
-  libcrypt1 1:4.4.18-4ubuntu1
-  libcurl3-gnutls 7.74.0-1.3ubuntu2
-  libdb5.3 5.3.28+dfsg1-0.8ubuntu1
-  libdbus-1-3 1.12.20-2ubuntu2
-  libdevmapper1.02.1 2:1.02.175-2.1ubuntu3
-  libelf1 0.185-1build1
-  liberror-perl 0.17029-1
-  libexpat1 2.4.1-2
-  libffi8 3.4.2-1ubuntu5
-  libgcc-s1 11.2.0-7ubuntu2
-  libgcrypt20 1.8.7-5ubuntu2
-  libgdbm-compat4 1.19-2
-  libgdbm6 1.19-2
-  libgmp10 2:6.2.1+dfsg-1ubuntu2
-  libgnutls30 3.7.1-5ubuntu1
-  libgpg-error0 1.38-2build1
-  libgssapi-krb5-2 1.18.3-6
-  libhogweed6 3.7.3-1
-  libidn2-0 2.3.1-1
-  libip4tc2 1.8.7-1ubuntu2
-  libip6tc2 1.8.7-1ubuntu2
-  libk5crypto3 1.18.3-6
-  libkeyutils1 1.6.1-2ubuntu1
-  libkrb5-3 1.18.3-6
-  libkrb5support0 1.18.3-6
-  libldap-2.5-0 2.5.6+dfsg-1~exp1ubuntu1
-  libldap-common 2.5.6+dfsg-1~exp1ubuntu1
-  liblocale-gettext-perl 1.07-4build1
-  liblz4-1 1.9.3-2
-  liblzma5 5.2.5-2
-  libmd0 1.0.3-3build1
-  libmnl0 1.0.4-3
-  libnetfilter-conntrack3 1.0.8-3
-  libnettle8 3.7.3-1
-  libnfnetlink0 1.0.1-3build1
-  libnftnl11 1.1.9-1
-  libnghttp2-14 1.43.0-1
-  libnsl2 1.3.0-2build1
-  libp11-kit0 0.23.22-1build1
-  libpam-cap 1:2.44-1build1
-  libpam-modules 1.3.1-5ubuntu11
-  libpam-modules-bin 1.3.1-5ubuntu11
-  libpam-runtime 1.3.1-5ubuntu11
-  libpam0g 1.3.1-5ubuntu11
-  libpcre2-8-0 10.37-0ubuntu2
-  libperl5.32 5.32.1-3ubuntu3
-  libpsl5 0.21.0-1.2
-  librtmp1 2.4+20151223.gitfa8646d.1-2build3
-  libsasl2-2 2.1.27+dfsg-2.1build1
-  libsasl2-modules 2.1.27+dfsg-2.1build1
-  libsasl2-modules-db 2.1.27+dfsg-2.1build1
-  libseccomp2 2.5.1-1ubuntu1
-  libselinux1 3.1-3build2
-  libsemanage-common 3.1-1ubuntu2
-  libsemanage1 3.1-1ubuntu2
-  libsepol1 3.1-1ubuntu2
-  libssh-4 0.9.6-1
-  libssl1.1 1.1.1l-1ubuntu1
-  libstdc++6 11.2.0-7ubuntu2
-  libsystemd0 248.3-1ubuntu8
-  libtasn1-6 4.16.0-2
-  libtext-charwidth-perl 0.04-10build1
-  libtext-iconv-perl 1.7-7build1
-  libtext-wrapi18n-perl 0.06-9
-  libtinfo6 6.2+20201114-2build1
-  libtirpc-common 1.3.2-2
-  libtirpc3 1.3.2-2
-  libudev1 248.3-1ubuntu8
-  libunistring2 0.9.10-6
-  libxtables12 1.8.7-1ubuntu2
-  libxxhash0 0.8.0-2build1
-  libzstd1 1.4.8+dfsg-2.1
-  lsb-base 11.1.0ubuntu3
-  netbase 6.3
-  openssl 1.1.1l-1ubuntu1
-  passwd 1:4.8.1-1ubuntu9
-  patch 2.7.6-7
-  perl 5.32.1-3ubuntu3
-  perl-base 5.32.1-3ubuntu3
-  perl-modules-5.32 5.32.1-3ubuntu3
-  pigz 2.6-1
-  publicsuffix 20210108.1309-1
-  runc 1.0.1-0ubuntu2
-  tar 1.34+dfsg-1build1
-  ubuntu-fan 0.12.15
-  ubuntu-keyring 2021.03.26
-  xz-utils 5.2.5-2
-  zlib1g 1:1.2.11.dfsg-2ubuntu7
- DistroRelease: Ubuntu 21.10
- ImageMediaBuild: 20211013
- Package: docker.io 20.10.7-0ubuntu5
- PackageArchitecture: arm64
- ProcCpuinfoMinimal:
-  processor: 3
-  BogoMIPS : 108.00
-  Features : fp asimd evtstrm crc32 cpuid
-  CPU implementer  : 0x41
-  CPU architecture: 8
-  CPU variant  : 0x0
-  CPU part : 0xd08
-  CPU revision : 3
-  
-  Hardware : BCM2835
-  Revision : c03111
-  Serial 

[Kernel-packages] [Bug 1944955] Re: Update the 470 NVIDIA driver to 470.74

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.74-0ubuntu0.21.04.1

---
nvidia-graphics-drivers-470 (470.74-0ubuntu0.21.04.1) hirsute; urgency=medium

  * New upstream release (LP: #1944955):
- Updated the nvidia-drm kernel module for compatibility with the
  removal of the DRIVER_PRIME flag in recent Linux kernel
  versions.
- Updated nvidia-bug-report.sh to search the systemd journal for
  gdm-x-session logs.
- Fixed a bug that could prevent nvidia-xconfig from disabling
  the X Composite extension on version 1.20 of the X.org X
  server.
- Fixed a build failure, "too many arguments to function
  'get_user_pages'", when building the NVIDIA kernel module for
  Linux kernel v4.4.168.
- Fixed a build failure, "implicit declaration of function
  do_gettimeofday", when building the NVIDIA kernel module for
  Linux kernel 5.0 release candidates.

 -- Alberto Milone   Fri, 24 Sep 2021
12:16:38 +0200

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

Title:
  Update the 470 NVIDIA driver to 470.74

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released

Bug description:
  Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.74 (470) ==

* New upstream release:
  - Updated the nvidia-drm kernel module for compatibility with the
removal of the DRIVER_PRIME flag in recent Linux kernel
versions.
  - Updated nvidia-bug-report.sh to search the systemd journal for
gdm-x-session logs.
  - Fixed a bug that could prevent nvidia-xconfig from disabling
the X Composite extension on version 1.20 of the X.org X
server.
  - Fixed a build failure, "too many arguments to function
'get_user_pages'", when building the NVIDIA kernel module for
Linux kernel v4.4.168.
  - Fixed a build failure, "implicit declaration of function
do_gettimeofday", when building the NVIDIA kernel module for
Linux kernel 5.0 release candidates.

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


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

[Kernel-packages] [Bug 1944955] Re: Update the 470 NVIDIA driver to 470.74

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.74-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-470 (470.74-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1944955):
- Updated the nvidia-drm kernel module for compatibility with the
  removal of the DRIVER_PRIME flag in recent Linux kernel
  versions.
- Updated nvidia-bug-report.sh to search the systemd journal for
  gdm-x-session logs.
- Fixed a bug that could prevent nvidia-xconfig from disabling
  the X Composite extension on version 1.20 of the X.org X
  server.
- Fixed a build failure, "too many arguments to function
  'get_user_pages'", when building the NVIDIA kernel module for
  Linux kernel v4.4.168.
- Fixed a build failure, "implicit declaration of function
  do_gettimeofday", when building the NVIDIA kernel module for
  Linux kernel 5.0 release candidates.

 -- Alberto Milone   Fri, 24 Sep 2021
12:25:17 +0200

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  Update the 470 NVIDIA driver to 470.74

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released

Bug description:
  Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.74 (470) ==

* New upstream release:
  - Updated the nvidia-drm kernel module for compatibility with the
removal of the DRIVER_PRIME flag in recent Linux kernel
versions.
  - Updated nvidia-bug-report.sh to search the systemd journal for
gdm-x-session logs.
  - Fixed a bug that could prevent nvidia-xconfig from disabling
the X Composite extension on version 1.20 of the X.org X
server.
  - Fixed a build failure, "too many arguments to function
'get_user_pages'", when building the NVIDIA kernel module for
Linux kernel v4.4.168.
  - Fixed a build failure, "implicit declaration of function
do_gettimeofday", when building the NVIDIA kernel module for
Linux kernel 5.0 release candidates.

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


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

[Kernel-packages] [Bug 1944955] Update Released

[Timo Aaltonen]

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

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

Title:
  Update the 470 NVIDIA driver to 470.74

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released

Bug description:
  Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.74 (470) ==

* New upstream release:
  - Updated the nvidia-drm kernel module for compatibility with the
removal of the DRIVER_PRIME flag in recent Linux kernel
versions.
  - Updated nvidia-bug-report.sh to search the systemd journal for
gdm-x-session logs.
  - Fixed a bug that could prevent nvidia-xconfig from disabling
the X Composite extension on version 1.20 of the X.org X
server.
  - Fixed a build failure, "too many arguments to function
'get_user_pages'", when building the NVIDIA kernel module for
Linux kernel v4.4.168.
  - Fixed a build failure, "implicit declaration of function
do_gettimeofday", when building the NVIDIA kernel module for
Linux kernel 5.0 release candidates.

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


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

[Kernel-packages] [Bug 1944955] Re: Update the 470 NVIDIA driver to 470.74

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.74-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-470 (470.74-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1944955):
- Updated the nvidia-drm kernel module for compatibility with the
  removal of the DRIVER_PRIME flag in recent Linux kernel
  versions.
- Updated nvidia-bug-report.sh to search the systemd journal for
  gdm-x-session logs.
- Fixed a bug that could prevent nvidia-xconfig from disabling
  the X Composite extension on version 1.20 of the X.org X
  server.
- Fixed a build failure, "too many arguments to function
  'get_user_pages'", when building the NVIDIA kernel module for
  Linux kernel v4.4.168.
- Fixed a build failure, "implicit declaration of function
  do_gettimeofday", when building the NVIDIA kernel module for
  Linux kernel 5.0 release candidates.

 -- Alberto Milone   Fri, 24 Sep 2021
12:24:19 +0200

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update the 470 NVIDIA driver to 470.74

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released

Bug description:
  Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.74 (470) ==

* New upstream release:
  - Updated the nvidia-drm kernel module for compatibility with the
removal of the DRIVER_PRIME flag in recent Linux kernel
versions.
  - Updated nvidia-bug-report.sh to search the systemd journal for
gdm-x-session logs.
  - Fixed a bug that could prevent nvidia-xconfig from disabling
the X Composite extension on version 1.20 of the X.org X
server.
  - Fixed a build failure, "too many arguments to function
'get_user_pages'", when building the NVIDIA kernel module for
Linux kernel v4.4.168.
  - Fixed a build failure, "implicit declaration of function
do_gettimeofday", when building the NVIDIA kernel module for
Linux kernel 5.0 release candidates.

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


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

[Kernel-packages] [Bug 1944955] Re: Update the 470 NVIDIA driver to 470.74

[Alberto Milone]

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

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

Title:
  Update the 470 NVIDIA driver to 470.74

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released

Bug description:
  Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.74 (470) ==

* New upstream release:
  - Updated the nvidia-drm kernel module for compatibility with the
removal of the DRIVER_PRIME flag in recent Linux kernel
versions.
  - Updated nvidia-bug-report.sh to search the systemd journal for
gdm-x-session logs.
  - Fixed a bug that could prevent nvidia-xconfig from disabling
the X Composite extension on version 1.20 of the X.org X
server.
  - Fixed a build failure, "too many arguments to function
'get_user_pages'", when building the NVIDIA kernel module for
Linux kernel v4.4.168.
  - Fixed a build failure, "implicit declaration of function
do_gettimeofday", when building the NVIDIA kernel module for
Linux kernel 5.0 release candidates.

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


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

[Kernel-packages] [Bug 1947012] Re: ubuntu_kernel_selftests.net times out with hirsute/linux-realtime

[Stefan Bader]

I had this as well for sru-20211018 but for generic. This was host rizzo
(maybe it is the host).

** Tags added: sru-20211018

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

Title:
  ubuntu_kernel_selftests.net times out with hirsute/linux-realtime

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

Bug description:
  ubuntu_kernel_selftests.net consistently times out with hirsute/linux-
  realtime.

  The last testcase which runs is usually fib_nexthops.sh, although
  there doesn't seem to be any problems with this particular testcase as
  looking at the log timestamp it is usually not running for too long
  when the timeout happens (this testcase takes around 10min to run on
  hirsute/linux).

  06:00:07 INFO | STARTubuntu_kernel_selftests.net
ubuntu_kernel_selftests.nettimestamp=1634018407timeout=1800
localtime=Oct 12 06:00:07
  [...]
  06:22:58 DEBUG| [stdout] # selftests: net: fib_nexthops.sh
  06:23:00 DEBUG| [stdout] # 
  06:23:00 DEBUG| [stdout] # Basic functional tests
  06:23:00 DEBUG| [stdout] # --
  06:23:00 DEBUG| [stdout] # TEST: List with nothing defined
 [ OK ]
  [...]
  06:28:52 DEBUG| [stdout] # IPv6 runtime torture
  06:28:52 DEBUG| [stdout] # 
  06:30:09 INFO | Timer expired (1800 sec.), nuking pid 30045
  06:30:10 INFO | ERRORubuntu_kernel_selftests.net
ubuntu_kernel_selftests.nettimestamp=1634020210localtime=Oct 12 
06:30:10Test timeout expired, rc=15

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


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

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

[bugproxy]

--- Comment From aleksandra.pa...@de.ibm.com 2021-09-16 04:22 EDT---
Hi, we have hit the same problem:

vmcore/dvtc2b-2.gpfs.net_202106240332/dmesg.202106240332:
...
[645967.289658] Unable to handle kernel pointer dereference in virtual kernel 
address space
[645967.289665] Failing address: 001ffc004bf14000 TEID: 001ffc004bf14403
[645967.289668] Fault in home space mode while using kernel ASCE.
[645967.289671] AS:0001d839c00b R2:00038bbec00b R3:0003010c0007 
S:00030226 P:0400
[645967.289715] Oops: 0011 ilc:2 [#1] SMP
[645967.289721] Modules linked in: mmfs26(OE) mmfslinux(OE) tracedev(OE) nfsv3 
nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp 
mrp stp llc bonding binfmt_misc dm_service_time dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua pkey zcrypt s390_trng ghash_s390 prng aes_s390 
des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 
sha_common chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 
sch_fq_codel drm drm_panel_orientation_quirks i2c_core sunrpc ip_tables 
x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
linear crc32_vx_s390 zfcp scsi_transport_fc qeth_l2 dasd_eckd_mod dasd_mod qeth 
qdio ccwgroup [last unloaded: tracedev]
[645967.289791] CPU: 4 PID: 1891047 Comm: kgnrdwr_dvtc2b Kdump: loaded Tainted: 
G   OE 5.4.0-74-generic #83-Ubuntu
[645967.289795] Hardware name: IBM 3906 M05 710 (LPAR)
[645967.289798] Krnl PSW : 0404e0018000 0001d73e20ce 
(try_to_wake_up+0x4e/0x700)
[645967.289809]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
[645967.289814] Krnl GPRS: 000370d32488 001ffc00 001ffc05 
0003
[645967.289817] 0005 041ffbff80bcb9e0 
0003
[645967.289858]0003 001ffc004bf141bc  
001ffc004bf13878
[645967.289860]9519 0001d7c1aa40 001ffbff80bcba10 
001ffbff80bcb990
[645967.289872] Krnl Code: 0001d73e20c2: 41902944   la  
%r9,2372(%r2)
0001d73e20c6: 582003ac   l   %r2,940
#0001d73e20ca: a718   lhi %r1,0
>0001d73e20ce: ba129000   cs  %r1,%r2,0(%r9)
0001d73e20d2: a77401c9   brc 7,0001d73e2464
0001d73e20d6: e310b0080004   lg  %r1,8(%r11)
0001d73e20dc: b9800018   ngr %r1,%r8
0001d73e20e0: a774001f   brc 7,0001d73e211e
[645967.289894] Call Trace:
[645967.289899] ([<>] 0x0)
[645967.289906]  [<0001d785c83a>] rq_qos_wake_function+0x8a/0xa0
[645967.289913]  [<0001d74004c2>] __wake_up_common+0xa2/0x1b0
[645967.289915]  [<0001d74009c4>] __wake_up_common_lock+0x94/0xe0
[645967.289918]  [<0001d7400a3a>] __wake_up+0x2a/0x40
[645967.289923]  [<0001d7873870>] wbt_done+0x90/0xe0
[645967.289925]  [<0001d785c942>] __rq_qos_done+0x42/0x60
[645967.289928]  [<0001d78486c0>] blk_mq_free_request+0xe0/0x140
[645967.289949]  [<001f801bf18a>] dasd_request_done+0x2a/0x40 [dasd_mod]
[645967.289951]  [<0001d7848938>] blk_mq_complete_request+0xb8/0x160
[645967.289957]  [<001f801c43c8>] dasd_block_tasklet+0x148/0x470 [dasd_mod]
[645967.289962]  [<0001d73b12d2>] tasklet_action_common.isra.0+0x82/0x160
[645967.289968]  [<0001d7c117b4>] __do_softirq+0x104/0x360
[645967.289971]  [<0001d73b1a4e>] irq_exit+0x9e/0xc0
[645967.289974]  [<0001d733cb28>] do_IRQ+0x78/0xb0
[645967.289977]  [<0001d7c10a20>] io_int_handler+0x12c/0x294
[645967.289985]  [<001f805f3c30>] _DTrace3+0x10/0xb0 [tracedev]
[645967.290048] ([<001f80a8d2ca>] gpfs_f_llseek+0x4a/0x280 [mmfslinux])
[645967.290053]  [<0001d75f5ed2>] ksys_lseek+0x92/0xe0
[645967.290055]  [<0001d7c10498>] system_call+0xdc/0x2c8
[645967.290056] Last Breaking-Event-Address:
[645967.290060]  [<0001d73e278e>] wake_up_process+0xe/0x20

If I should upload the data for this bug or open a new please tell.

--- Comment From aleksandra.pa...@de.ibm.com 2021-09-16 04:27 EDT---
dvtc2b-2.gpfs.net:  OS: Debian Linux: Ubuntu 20.04.2 LTS  =>  Kernel: 
5.4.0-74-generic on s390x

--- Comment From boris.m...@de.ibm.com 2021-09-17 09:36 EDT---
I double-checked with Canonical regarding the current / in-service release 
level of 20.04 LTS. The current level is 20.04.3, to be more precise 20.04.3 
with Kernel 5.4.0.84. Therefore, you should try to re-produce the bug on the 
20.04.3 release.

Apart from the (not supported anymore) 20.04.2 release level, a first
look on the error messages strongly hints to a GPFS error.
("vmcore/dvtc2b-2.gpfs.net_202106240332/dmesg.202106240332")

@Aleksandra: can you please confirm if GPFS is running on the system?

--- Comment From aleksandra.pa...@de.ibm.com 2021-09-20 05:29 EDT---
Yes, gpfs is running on the system.

But 

[Kernel-packages] [Bug 1947568] Re: cannot promote clone: "not a cloned filesystem"

[James Dingwall]

** Description changed:

  I have a zvol containing a Windows image for a virtual machine.  After
  restarting the system a node under /dev/zvol/... was not created for the
  virtual disk and no amount of prompting by `udevadm trigger` helped.
  Instead I created a snapshot from the most recent hourly backup:
  
  # zfs clone rpool/vm/windows/windows10/hda@hourly07 
rpool/vm/windows/windows10/hda-new
  # zfs promote rpool/vm/windows/windows10/hda-new
  cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem
  (didn't work here but carried on assuming something can be sorted later)
  # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old
  # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda
  
  Entries in /dev appeared and I could start the virtual machine.  Trying
  to promote the clone gives 'not a cloned filesystem' message.  I later
  renamed the old zvol and tried to cleanup:
  
  # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted
  #  zfs destroy rpool/to-be-deleted@hourly07
  cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones
  use '-R' to destroy the following datasets:
  rpool/vm/windows/windows10/hda@hourly09
  rpool/vm/windows/windows10/hda@hourly10
  rpool/vm/windows/windows10/hda
  # zfs promote rpool/vm/windows/windows10/hda
  cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem
  
  # zfs get origin rpool/vm/windows/windows10/hda
  NAMEPROPERTY  VALUE SOURCE
  rpool/vm/windows/windows10/hda  originrpool/to-be-deleted@hourly07  -
  
  # zfs get clones rpool/to-be-deleted@hourly07
  NAME  PROPERTY  VALUE   SOURCE
  rpool/to-be-deleted@hourly07  clonesrpool/vm/windows/windows10/hda  -
  
  The dependency between seems to be as expected.  This small test fails
  in the same way:
  
  # zfs create -V1G rpool/vm/test
  # zfs snapshot rpool/vm/test@test2
  # zfs clone rpool/vm/test@test2 rpool/vm/test3
  # zfs promote rpool/vm/test3
  cannot promote 'rpool/vm/test3': not a cloned filesystem
  # zfs get origin rpool/vm/test3
  NAMEPROPERTY  VALUESOURCE
  rpool/vm/test3  originrpool/vm/test@test2  -
  # zfs get clones rpool/vm/test@test2
  NAME PROPERTY  VALUE   SOURCE
  rpool/vm/test@test2  clonesrpool/vm/test3  -
  
  All the zpool members are ONLINE and no errors are reported.
  
  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal
  
  # uname -r
  5.11.0-37-generic
  
  # modinfo zfs | grep -i version
  version:2.0.2-1ubuntu5.1
  srcversion: F267DF7B3FFB43AFE76257D
  vermagic:   5.11.0-37-generic SMP mod_unload modversions
+ 
+ # apt-cache policy zfsutils-linux
+ zfsutils-linux:
+   Installed: 0.8.3-1ubuntu12.12
+   Candidate: 0.8.3-1ubuntu12.13
+   Version table:
+  0.8.3-1ubuntu12.13 500
+ 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
+  *** 0.8.3-1ubuntu12.12 100
+ 100 /var/lib/dpkg/status
+  0.8.3-1ubuntu12.9 500
+ 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
+  0.8.3-1ubuntu12 500
+ 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  cannot promote clone: "not a cloned filesystem"

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have a zvol containing a Windows image for a virtual machine.  After
  restarting the system a node under /dev/zvol/... was not created for
  the virtual disk and no amount of prompting by `udevadm trigger`
  helped.  Instead I created a snapshot from the most recent hourly
  backup:

  # zfs clone rpool/vm/windows/windows10/hda@hourly07 
rpool/vm/windows/windows10/hda-new
  # zfs promote rpool/vm/windows/windows10/hda-new
  cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem
  (didn't work here but carried on assuming something can be sorted later)
  # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old
  # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda

  Entries in /dev appeared and I could start the virtual machine.
  Trying to promote the clone gives 'not a cloned filesystem' message.
  I later renamed the old zvol and tried to cleanup:

  # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted
  #  zfs destroy rpool/to-be-deleted@hourly07
  cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones
  use '-R' to destroy the following datasets:
  rpool/vm/windows/windows10/hda@hourly09
  

[Kernel-packages] [Bug 1947326] Re: [Dell Latitude 7320] Clipping and pointer lag after update to kernel 5.13 (fixed by i915.enable_psr=0)

[Daniel van Vugt]

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/intel/-/issues/4318
   Importance: Unknown
   Status: Unknown

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

Title:
  [Dell Latitude 7320] Clipping and pointer lag after update to kernel
  5.13 (fixed by i915.enable_psr=0)

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

Bug description:
  Graphics were working perfectly until update to 21.10.
  Now I experience graphics lag when typing and moving the pointer, and 
clipping when scrolling or playing video.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 15 10:42:19 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago)

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


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

[Kernel-packages] [Bug 1947326] Re: [Dell Latitude 7320] Clipping and pointer lag after update to kernel 5.13 (fixed by i915.enable_psr=0)

[Krister Swenson]

Thanks vanvugt!
Here is the upstream bug report: 
https://gitlab.freedesktop.org/drm/intel/-/issues/4318

** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4318
   https://gitlab.freedesktop.org/drm/intel/-/issues/4318

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

Title:
  [Dell Latitude 7320] Clipping and pointer lag after update to kernel
  5.13 (fixed by i915.enable_psr=0)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Graphics were working perfectly until update to 21.10.
  Now I experience graphics lag when typing and moving the pointer, and 
clipping when scrolling or playing video.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 15 10:42:19 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago)

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


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

[Kernel-packages] [Bug 1947498] Re: zfs/zpool encryption crash on server 21.10

[Hadmut Danisch]

Even more trouble: The machine, although freshly installed, can't even
properly mount the filesystems received by zfs send|zfs receive from a
20.04 machine, and hangs in shutdown, does not even turn itself off.
Several PANICs.


ZFS for 21.10 is really broken.

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

Title:
  zfs/zpool encryption crash on server 21.10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,

  just installed a new HPE microserver with SSD and four harddisks with
  new 21.10 server and tried to create a zpool with

  zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O
  encryption=on -O keyformat=passphrase

  
  which reproducably crashed twice with the attached kernel message. 

  
  The zpool then exists, but is not encrypted. 

  zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd 
  without the option works 

  and a subsequent

  zfs create pool1/sub -o encryption=on -o keyformat=passphrase

  works as well. Which is, however, not a real workaround for a fully
  encrypted pool (which worked under 20.04).

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: zfsutils-linux 2.0.6-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Oct 17 12:44:15 2021
  InstallationDate: Installed on 2021-10-17 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 
(20211013)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1946444] Re: ath11k_pci firmware crashes under regular usage on Dell XPS 13 9310 (no suspend and resume)

[Launchpad Bug Tracker]

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

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

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

Title:
  ath11k_pci  firmware crashes under regular usage on Dell XPS 13 9310
  (no suspend and resume)

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  While I was normally working on my Dell XPS 13 9310 Laptop, noticed
  that WiFi suddenly got disconnected. Looking at dmesg, noticed that
  the firmware crashed.

  (I am also attaching the entire dmesg output as a file to this bug. )

  $ dmesg | grep ath11_k

  [   13.826871] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0
  [35908.890709] ath11k_pci :72:00.0: firmware crashed: MHI_CB_SYS_ERROR
  [36170.055770] ath11k_pci :72:00.0: wmi command 12290 timeout
  [36170.055776] ath11k_pci :72:00.0: failed to send WMI_STOP_SCAN_CMDID
  [36170.055783] ath11k_pci :72:00.0: failed to stop wmi scan: -11
  [36170.055786] ath11k_pci :72:00.0: failed to stop scan: -11
  [36170.055788] ath11k_pci :72:00.0: failed to start hw scan: -110
  ...
  ...
  [36305.230431] ath11k_pci :72:00.0: wmi command 16387 timeout
  [36305.230436] ath11k_pci :72:00.0: failed to send WMI_PDEV_SET_PARAM cmd
  [36305.230445] ath11k_pci :72:00.0: failed to enable PMF QOS: (-11

  I had to reboot the machine at least 2 times before WiFi started
  working. In the past, I had noticed WiFi would not work after boot a
  couple of times, but this is the first time I am seeing it breaking
  under normal, continuous usage. This is a major reliability issue if
  WiFi connection keeps breaking in the middle of work like this.

  Also, this is somewhat similar to the following bugs, but not exactly
  the same:

  https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018
  (here there is no message 'firmware crashed' but rather some failures
  from ath11k_pci. Moreover it occurred during suspend and resume.
  Whereas in my case, the last suspend + resume was at least 3 and half
  hours before the firmware crash)

  https://bugs.launchpad.net/ubuntu/+source/linux-signed-
  oem-5.10/+bug/1942060 (here there is 'firmware crashed' message, but
  all the error messages after that seem to be different. Moreover it
  seems to have occurred 56 seconds after system booted, when WiFi
  network was connected. Whereas I had a uptime of 9 hours and about 6
  hours after the last WiFi connection).

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


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

[Kernel-packages] [Bug 1947326] Re: [Dell Latitude 7320] Clipping and pointer lag after update to kernel 5.13 (fixed by i915.enable_psr=0)

[Daniel van Vugt]

I think the current advice is to report bugs at
https://gitlab.freedesktop.org/drm/intel/-/issues

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

Title:
  [Dell Latitude 7320] Clipping and pointer lag after update to kernel
  5.13 (fixed by i915.enable_psr=0)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Graphics were working perfectly until update to 21.10.
  Now I experience graphics lag when typing and moving the pointer, and 
clipping when scrolling or playing video.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 15 10:42:19 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago)

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


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

[Kernel-packages] [Bug 1947326] Re: [Dell Latitude 7320] Clipping and pointer lag after update to kernel 5.13 (fixed by i915.enable_psr=0)

[Krister Swenson]

@vanvugt Do you know where the best place is to report this regression
upstream?

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

Title:
  [Dell Latitude 7320] Clipping and pointer lag after update to kernel
  5.13 (fixed by i915.enable_psr=0)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Graphics were working perfectly until update to 21.10.
  Now I experience graphics lag when typing and moving the pointer, and 
clipping when scrolling or playing video.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 15 10:42:19 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago)

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


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[You-Sheng Yang]

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ Sometimes MT7921 may not be probed due to an endless mcu reset:
+ 
+   [ 5.789548] mt7921 mcu reset 0
+   [ 5.790625] mt7921 rx type 0x7
+   [ 5.790625] mt7921 eid 0x1 ext_eid 0x0
+   [ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0
+ 
+ [Fix]
+ 
+ WiFi and Bluetooth firmware updates from mainline:
+ * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip 
(MT7921)
+ * d34196f5 linux-firmware: update firmware for MT7921 WiFi device
+ 
+ [Test Case]
+ 
+ This should fix the mcu reset and wireless/bluetooh devices should be
+ probed successfully.
+ 
+ [Where problems could occur]
+ 
+ While there is explicit FW API for kernel version compatibility checking,
+ this might introduce some hidden glitches that we don't know yet.
+ 
+ [Other Info]
+ 
+ MT7921 is supported since Impish 5.13 kernel, and Impish already has the
+ latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13
+ and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are
+ required.
+ 
+ == original bug report ==
+ 
  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.
  
  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Impish:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Sometimes MT7921 may not be probed due to an endless mcu reset:

[ 5.789548] mt7921 mcu reset 0
[ 5.790625] mt7921 rx type 0x7
[ 5.790625] mt7921 eid 0x1 ext_eid 0x0
[ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0

  [Fix]

  WiFi and Bluetooth firmware updates from mainline:
  * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip 
(MT7921)
  * d34196f5 linux-firmware: update firmware for MT7921 WiFi device

  [Test Case]

  This should fix the mcu reset and wireless/bluetooh devices should be
  probed successfully.

  [Where problems could occur]

  While there is explicit FW API for kernel version compatibility checking,
  this might introduce some hidden glitches that we don't know yet.

  [Other Info]

  MT7921 is supported since Impish 5.13 kernel, and Impish already has the
  latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13
  and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are
  required.

  == original bug report ==

  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2021-October/125084.html (focal)
* https://lists.ubuntu.com/archives/kernel-team/2021-October/125085.html 
(impish)

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Impish:
  In Progress

Bug description:
  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[You-Sheng Yang]

[5.656047] mt7921e :02:00.0: enabling device ( -> 0002)
[5.656529] mt7921e :02:00.0: ASIC revision: 79610010
[5.787109] mt7921 mcu reset 0
[5.788869] mt7921 rx type 0x7
[5.788877] mt7921 eid 0x4 ext_eid 0x2
[5.70] mt76_rx_event eid 0x4 ext_eid 0x2
[5.789545] mt7921e :02:00.0: HW/SW Version: 0x8a108a10, Build Time: 
20210612122717a
[5.789548] mt7921 mcu reset 0
[5.790625] mt7921 rx type 0x7
[5.790625] mt7921 eid 0x1 ext_eid 0x0
[5.790626] mt76_rx_event eid 0x1 ext_eid 0x0
[5.790737] mt7921 mcu reset 0
[5.795575] mt7921 rx type 0x7
[5.795577] mt7921 eid 0x1 ext_eid 0x0
[5.795579] mt76_rx_event eid 0x1 ext_eid 0x0
[5.795591] mt7921 mcu reset 0
[5.795671] mt7921 rx type 0x7
[5.795671] mt7921 eid 0x4 ext_eid 0x3
[5.795672] mt76_rx_event eid 0x4 ext_eid 0x3
[5.796374] mt7921e :02:00.0: WM Firmware Version: 01, Build 
Time: 20210612122753
[5.796376] mt7921 mcu reset 0
[5.797540] mt7921 rx type 0x7
[5.797547] mt7921 eid 0x1 ext_eid 0x0
[5.797550] mt76_rx_event eid 0x1 ext_eid 0x0
[5.797966] mt7921 mcu reset 0
[5.802381] mt7921 rx type 0x7
[5.802382] mt7921 eid 0x1 ext_eid 0x0
[5.802383] mt76_rx_event eid 0x1 ext_eid 0x0
[5.802696] mt7921 mcu reset 0
[5.806039] mt7921 rx type 0x7
[5.806041] mt7921 eid 0x1 ext_eid 0x0
[5.806041] mt76_rx_event eid 0x1 ext_eid 0x0
[5.806075] mt7921 mcu reset 0
[5.807652] mt7921 rx type 0x7
[5.807656] mt7921 eid 0x1 ext_eid 0x0
[5.807659] mt76_rx_event eid 0x1 ext_eid 0x0
[5.808067] mt7921 mcu reset 0
[5.827134] mt7921 rx type 0x7
[5.827137] mt7921 eid 0x1 ext_eid 0x0
[5.827138] mt76_rx_event eid 0x1 ext_eid 0x0
[5.827172] mt7921e :02:00.0: Firmware init done
[5.827177] mt7921 mcu reset 0
[5.831100] mt7921 rx type 0x7
[5.831103] mt7921 eid 0xec ext_eid 0x0
[5.831104] mt76_rx_event eid 0xec ext_eid 0x0

then repeatedly reset mcu forever.

** Attachment added: "dmesg_20210915"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947829/+attachment/5534519/+files/dmesg_20210915

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Impish:
  In Progress

Bug description:
  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[You-Sheng Yang]

MT7921 is supported starting from Impish. Impish has already the latest
MT7921 bluetooth fw, but still misses the WiFi one, commit d34196f5
("linux-firmware: update firmware for MT7921 WiFi device").

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

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

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

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

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

** Changed in: linux-firmware (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Impish)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Impish)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Impish:
  In Progress

Bug description:
  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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


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

[Kernel-packages] [Bug 1947829] [NEW] Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[You-Sheng Yang]

Public bug reported:

[Reproduce Steps]
1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

[Results]
Expected Result:The wireless settings should be exists and wifi can be used
Actual Result:The wireless settings not exists and wifi can not be used

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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


** Tags: hwe-networking-wifi oem-priority originate-from-1941014 somerville

** Tags added: oem-priority originate-from-1941014 somerville

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

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

Bug description:
  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

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


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