[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Kevin Yeh]

** Description changed:

  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
- The last messages displayed on the screen are: 
+ The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9
  
- There are not journal logs existed when I boot with previous kernel.
+ There are no journal logs existed when I boot with the 6.5.0-33 kernel.
  
  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

** Description changed:

  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9
  
- There are no journal logs existed when I boot with the 6.5.0-33 kernel.
+ There are no journal logs existed when it boot with the 6.5.0-33 kernel.
  
  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  New

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

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


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

[Kernel-packages] [Bug 2061940] [NEW] Some DUTs can't boot up after installing the proposed kernel on Mantic

[Kevin Yeh]

Public bug reported:

During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
The last messages displayed on the screen are: 
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9

There are not journal logs existed when I boot with previous kernel.

Here is the list of the impacted machines that I found so far
https://certification.canonical.com/hardware/202106-29206/
https://certification.canonical.com/hardware/202106-29207/
https://certification.canonical.com/hardware/201912-27623/
https://certification.canonical.com/hardware/202007-28059/
https://certification.canonical.com/hardware/202103-28762/
https://certification.canonical.com/hardware/202012-28510/

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


** Tags: cert-sru regression-proposed

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  New

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are: 
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are not journal logs existed when I boot with previous kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

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


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

[Kernel-packages] [Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Kevin Becker]

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

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

Title:
  AWS: arm64: pauth: don't sign leaf functions

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  From our experiments, we found that not signing leaf functions on AWS
  Graviton instances helps improve application performance. We would
  like to have the patch
  
https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8
  backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these
  performance improvements: NGINX 1%, MySQL 2%, PyTorch 2%

  [Test Plan]

  AWS tested.

  [Regression Potential]

  Arm64 binaries may not work correctly.

  [Other Info]

  SF: #00372369

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


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

[Kernel-packages] [Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Kevin Becker]

Confirmed as working by Amazon.

** Tags removed: verification-needed-jammy-linux-aws
** Tags added: verification-done-jammy-linux-aws

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

Title:
  AWS: arm64: pauth: don't sign leaf functions

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  From our experiments, we found that not signing leaf functions on AWS
  Graviton instances helps improve application performance. We would
  like to have the patch
  
https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8
  backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these
  performance improvements: NGINX 1%, MySQL 2%, PyTorch 2%

  [Test Plan]

  AWS tested.

  [Regression Potential]

  Arm64 binaries may not work correctly.

  [Other Info]

  SF: #00372369

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


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

[Kernel-packages] [Bug 2056383] Re: Audio turned to dummy output from 5.15.0-1049-intel-iotg to 5.15.0-1050

[Kevin Yeh]

** Also affects: linux-intel-iotg-5.15 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Audio turned to dummy output from 5.15.0-1049-intel-iotg to
  5.15.0-1050

Status in linux-intel-iotg-5.15 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  [Summary]
  After updated kernel 5.15.0-1049-intel-iotg to 5.15.0-1050

  Sound output device turned to dummy output.

  [Steps to reproduce]
  1. Install OS image to DUT.
  2. Update package from repository(include proposed)
  3. Upgrade package from repository(include proposed)
  4. After upgrade successfully, reboot system.
  5. Audio didn't work functionally.

  [Expected result]
  Audio works normally.

  [Actual result]
  Audio device became dummy output.
  Sound cards are disappeared.

  [Failure rate]
  100%

  Tester comments
  ---
  Audio works fine at kernel 5.15.0-1049-intel-iotg

  [Additional information]
  CID: 202109-29435
  Image: ubuntu-22.04-desktop-amd64+intel-iot.iso
  system-manufacturer: Aaeon
  system-product-name: UPX-TGL01
  CPU: Intel(R) Celeron(R) 6305E @ 1.80GHz
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-1050.56-intel-iotg 5.15.143
  Uname: Linux 5.15.0-1050-intel-iotg x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Wed Mar  6 11:45:08 2024
  InstallationDate: Installed on 2024-03-05 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64+intel-iot (20230316.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 5.19
  dmi.board.asset.tag: Default string
  dmi.board.name: UPX-TGL01
  dmi.board.vendor: AAEON
  dmi.board.version: V1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: AAEON
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd05/14/2021:br5.19:svnAAEON:pnUPX-TGL01:pvrV1.0:rvnAAEON:rnUPX-TGL01:rvrV1.0:cvnAAEON:ct3:cvrV1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: UPX-TGL01
  dmi.product.sku: Default string
  dmi.product.version: V1.0
  dmi.sys.vendor: AAEON

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg-5.15/+bug/2056383/+subscriptions


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

[Kernel-packages] [Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Kevin Becker]

Updated to target Jammy since we're not fixing this in Lunar.

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

** Changed in: linux-aws (Ubuntu Jammy)
   Status: New => In Progress

** No longer affects: linux-aws (Ubuntu Lunar)

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

Title:
  AWS: arm64: pauth: don't sign leaf functions

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  From our experiments, we found that not signing leaf functions on AWS
  Graviton instances helps improve application performance. We would
  like to have the patch
  
https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8
  backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these
  performance improvements: NGINX 1%, MySQL 2%, PyTorch 2%

  [Test Plan]

  AWS tested.

  [Regression Potential]

  Arm64 binaries may not work correctly.

  [Other Info]

  SF: #00372369

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


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

[Kernel-packages] [Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Kevin Becker]

Patches sent to mailing list:

Jammy: https://lists.ubuntu.com/archives/kernel-
team/2024-February/148619.html

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

Title:
  AWS: arm64: pauth: don't sign leaf functions

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Lunar:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  From our experiments, we found that not signing leaf functions on AWS
  Graviton instances helps improve application performance. We would
  like to have the patch
  
https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8
  backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these
  performance improvements: NGINX 1%, MySQL 2%, PyTorch 2%

  [Test Plan]

  AWS tested.

  [Regression Potential]

  Arm64 binaries may not work correctly.

  [Other Info]

  SF: #00372369

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


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

[Kernel-packages] [Bug 2050830] Re: linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with linux-kvm/5.15.0-1050.55

[Kevin Becker]

** Summary changed:

- linux-kvm ADT test failure with linux-kvm/5.15.0-1050.55
+ linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with 
linux-kvm/5.15.0-1050.55

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

Title:
  linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with
  linux-kvm/5.15.0-1050.55

Status in linux-kvm package in Ubuntu:
  New

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

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz

  As part of ubuntu_qrt_apparmor, we get the following error. This also
  seems to lead to further apparmor errors.

  3461s 10:50:40 DEBUG| [stdout] Running test: './test-apparmor.py' distro: 
'Ubuntu 22.04' kernel: '5.15.0-1050.55 (Ubuntu 5.15.0-1050.55-kvm 5.15.136)' 
arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
  3461s 10:50:40 ERROR| [stderr] test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
  3461s 10:50:40 ERROR| [stderr] Test snapd snap ... FAIL
  3461s 10:50:40 ERROR| [stderr] 
  3461s 10:50:40 ERROR| [stderr] 
==
  3461s 10:50:40 ERROR| [stderr] FAIL: test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
  3461s 10:50:40 ERROR| [stderr] Test snapd snap
  3461s 10:50:40 ERROR| [stderr] 
--
  3461s 10:50:40 ERROR| [stderr] Traceback (most recent call last):
  3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 321, in test_snapd_snap_with_vendored_apparmor
  3461s 10:50:40 ERROR| [stderr] self.install_snap("snapd", 
track="latest/stable", classic=False)
  3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/testlib.py",
 line 1339, in install_snap
  3461s 10:50:40 ERROR| [stderr] self.assertEqual(0, rc, "Failed to install 
snap %s from track %s (classic: %s)\nOutput:\n%s" %
  3461s 10:50:40 ERROR| [stderr] AssertionError: 0 != 127 : Failed to install 
snap snapd from track latest/stable (classic: False)
  3461s 10:50:40 ERROR| [stderr] Output:
  3461s 10:50:40 ERROR| [stderr] [Errno 2] No such file or directory: 'snap'

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


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

[Kernel-packages] [Bug 2050830] [NEW] linux-kvm ADT test failure with linux-kvm/5.15.0-1050.55

[Kevin Becker]

Public bug reported:

This is a scripted bug report about ADT failures while running linux-kvm
tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.

Testing failed on:
amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz

As part of ubuntu_qrt_apparmor, we get the following error. This also
seems to lead to further apparmor errors.

3461s 10:50:40 DEBUG| [stdout] Running test: './test-apparmor.py' distro: 
'Ubuntu 22.04' kernel: '5.15.0-1050.55 (Ubuntu 5.15.0-1050.55-kvm 5.15.136)' 
arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
3461s 10:50:40 ERROR| [stderr] test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
3461s 10:50:40 ERROR| [stderr] Test snapd snap ... FAIL
3461s 10:50:40 ERROR| [stderr] 
3461s 10:50:40 ERROR| [stderr] 
==
3461s 10:50:40 ERROR| [stderr] FAIL: test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
3461s 10:50:40 ERROR| [stderr] Test snapd snap
3461s 10:50:40 ERROR| [stderr] 
--
3461s 10:50:40 ERROR| [stderr] Traceback (most recent call last):
3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 321, in test_snapd_snap_with_vendored_apparmor
3461s 10:50:40 ERROR| [stderr] self.install_snap("snapd", 
track="latest/stable", classic=False)
3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/testlib.py",
 line 1339, in install_snap
3461s 10:50:40 ERROR| [stderr] self.assertEqual(0, rc, "Failed to install 
snap %s from track %s (classic: %s)\nOutput:\n%s" %
3461s 10:50:40 ERROR| [stderr] AssertionError: 0 != 127 : Failed to install 
snap snapd from track latest/stable (classic: False)
3461s 10:50:40 ERROR| [stderr] Output:
3461s 10:50:40 ERROR| [stderr] [Errno 2] No such file or directory: 'snap'

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


** Tags: 5.15 amd64 jammy kernel-adt-failure kvm sru-20240108

** Tags added: kernel-adt-failure

** Description changed:

  This is a scripted bug report about ADT failures while running linux-kvm
  tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is caused by
  the dep8 tests of the tested source or the kernel has yet to be
  determined.
  
  Testing failed on:
- amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz
+ amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz
+ 
+ As part of ubuntu_qrt_apparmor, we get the following error. This also
+ seems to lead to further apparmor errors.
+ 
+ 3461s 10:50:40 DEBUG| [stdout] Running test: './test-apparmor.py' distro: 
'Ubuntu 22.04' kernel: '5.15.0-1050.55 (Ubuntu 5.15.0-1050.55-kvm 5.15.136)' 
arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
+ 3461s 10:50:40 ERROR| [stderr] test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
+ 3461s 10:50:40 ERROR| [stderr] Test snapd snap ... FAIL
+ 3461s 10:50:40 ERROR| [stderr] 
+ 3461s 10:50:40 ERROR| [stderr] 
==
+ 3461s 10:50:40 ERROR| [stderr] FAIL: test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
+ 3461s 10:50:40 ERROR| [stderr] Test snapd snap
+ 3461s 10:50:40 ERROR| [stderr] 
--
+ 3461s 10:50:40 ERROR| [stderr] Traceback (most recent call last):
+ 3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 321, in test_snapd_snap_with_vendored_apparmor
+ 3461s 10:50:40 ERROR| [stderr] self.install_snap("snapd", 
track="latest/stable", classic=False)
+ 3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/testlib.py",
 line 1339, in install_snap
+ 3461s 10:50:40 ERROR| [stderr] self.assertEqual(0, rc, "Failed to install 
snap %s from track %s (classic: %s)\nOutput:\n%s" %
+ 3461s 10:50:40 ERROR| [stderr] AssertionError: 0 != 127 : Failed to install 
snap snapd from track latest/stable (classic: False)
+ 3461s 10:50:40 ERROR| [stderr] Output:
+ 3461s 10:50:40 ERROR| [stderr] [Errno 2] No such file or directory: 'snap'

** Tags added: 5.15 amd64 jammy kvm sru-20240108

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.

[Kernel-packages] [Bug 2046444] [NEW] Missing tp_smapi dkms module in 6.5-hwe

[Kevin Yeh]

Public bug reported:

During the 6.5-hwe migration test, I found that there was a missing dkms which 
is tp_smapi.
I just randomly picked some test results for your reference.

https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/
https://certification.canonical.com/hardware/202005-27944/submission/344995/test/71814/result/37864862/
https://certification.canonical.com/hardware/202008-28111/submission/344988/test/71814/result/37863988/

** Affects: linux-signed-hwe-6.5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cert-sru

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

Title:
  Missing tp_smapi dkms module in 6.5-hwe

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

Bug description:
  During the 6.5-hwe migration test, I found that there was a missing dkms 
which is tp_smapi.
  I just randomly picked some test results for your reference.

  
https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/
  
https://certification.canonical.com/hardware/202005-27944/submission/344995/test/71814/result/37864862/
  
https://certification.canonical.com/hardware/202008-28111/submission/344988/test/71814/result/37863988/

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


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

[Kernel-packages] [Bug 2046217] Re: Some machines can't pass the pm-graph test

[Kevin Yeh]

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Some machines can't pass the pm-graph test

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 source package in Jammy:
  New
Status in linux-signed-hwe-6.5 source package in Jammy:
  New

Bug description:
  During the jammy-hwe migration test, I found some machines failed to
  run the pm-graph.
  
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)

  One of machine when I rerun it locally, it passed, but others are
  still failed.

  Following are the machines failed to run pm-graph.
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201702-25401/
  https://certification.canonical.com/hardware/202002-27718/
  https://certification.canonical.com/hardware/201711-25989/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Tue Dec 12 02:48:24 2023
  InstallationDate: Installed on 2023-02-22 (293 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046217] [NEW] Some machines can't pass the pm-graph test

[Kevin Yeh]

Public bug reported:

During the jammy-hwe migration test, I found some machines failed to run
the pm-graph.
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)

One of machine when I rerun it locally, it passed, but others are still
failed.

Following are the machines failed to run pm-graph.
https://certification.canonical.com/hardware/202005-27899/
https://certification.canonical.com/hardware/201702-25401/
https://certification.canonical.com/hardware/202002-27718/
https://certification.canonical.com/hardware/201711-25989/

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: maas
CloudName: maas
CloudPlatform: maas
CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
Date: Tue Dec 12 02:48:24 2023
InstallationDate: Installed on 2023-02-22 (293 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-6.5 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug cert-sru jammy package-from-proposed uec-images

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/bugs/2046217/+attachment/5728540/+files/journal.log

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

Title:
  Some machines can't pass the pm-graph test

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

Bug description:
  During the jammy-hwe migration test, I found some machines failed to
  run the pm-graph.
  
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)

  One of machine when I rerun it locally, it passed, but others are
  still failed.

  Following are the machines failed to run pm-graph.
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201702-25401/
  https://certification.canonical.com/hardware/202002-27718/
  https://certification.canonical.com/hardware/201711-25989/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Tue Dec 12 02:48:24 2023
  InstallationDate: Installed on 2023-02-22 (293 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

[Kevin Yeh]

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

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 16.0
  dmi.bios.vendor: HP
  dmi.bios.version: S12 Ver. 02.16.00
  dmi.board.name: 8810
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.23
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: 

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

[Kevin Yeh]

** Summary changed:

- USB bus error after upgrading to proposed kernel on lunar and jammy
+ USB bus error after upgrading to proposed kernel on lunar, jammy and 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/2043197

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 16.0
  dmi.bios.vendor: HP
  dmi.bios.version: S12 Ver. 02.16.00
  dmi.board.name: 8810
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.23
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
 

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

@smb @kaihengfeng
I also found this regression on 5.4.0-168-generic

Following is the journal log.
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: device descriptor 
read/8, error -71
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: new SuperSpeed Gen 1 
USB device number 7 using xhci_hcd
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: device descriptor 
read/8, error -71
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb usb2-port2: attempt power 
cycle
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: new SuperSpeed Gen 1 
USB device number 8 using xhci_hcd

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

** No longer affects: focal (Ubuntu)

** No longer affects: focal (Ubuntu Jammy)

** No longer affects: focal (Ubuntu Lunar)

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

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

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

** Tags added: regression-proposed

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

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 16.0
  dmi.bios.vendor: HP
  dmi.bios.version: S12 Ver. 02.16.00
  dmi.board.name: 8810
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.23
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: HP ProOne 600 G6
  dmi.product.sku: 123456#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

** Tags removed: verification-needed-done-linux
** Tags added: verification-done-jammy-linux

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

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 16.0
  dmi.bios.vendor: HP
  dmi.bios.version: S12 Ver. 02.16.00
  dmi.board.name: 8810
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.23
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: HP ProOne 600 G6
  dmi.product.sku: 123456#ABA
  dmi.sys.vendor: HP

[Kernel-packages] [Bug 2043333] [NEW] package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

[Kevin Chavanne]

Public bug reported:

I have an AMD Ryzen 7745hx CPU and the iGPU (integrated GPU from the
CPU) is not recognised. It seems to be related to the error I received.

My computer with Mantic only runs on the Nvidia graphic card because it
doesn't take the iGPU into account. I suypposed it is because the CPU is
fairly new to the market and that Igpu drivers are not integrates into
the linux-genereic-6.5

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
 gnome-metronome:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Nov 12 21:58:39 2023
DpkgHistoryLog:
 Start-Date: 2023-11-12  21:58:16
 Commandline: packagekit role='install-packages'
 Requested-By: kevin (1000)
 Install: gnome-metronome:amd64 (1.3.0-0ubuntu4)
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2023-10-24 (19 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=b0f42ab3-3f84-4147-8b10-99e7e7ff4a5e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: dkms
Title: package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/28/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: LPCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Pro 5 16ARX8
dmi.ec.firmware.release: 1.44
dmi.modalias: 
dmi:bvnLENOVO:bvrLPCN44WW:bd06/28/2023:br1.44:efr1.44:svnLENOVO:pn82WM:pvrLegionPro516ARX8:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionPro516ARX8:skuLENOVO_MT_82WM_BU_idea_FM_LegionPro516ARX8:
dmi.product.family: Legion Pro 5 16ARX8
dmi.product.name: 82WM
dmi.product.sku: LENOVO_MT_82WM_BU_idea_FM_Legion Pro 5 16ARX8
dmi.product.version: Legion Pro 5 16ARX8
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package mantic need-duplicate-check

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

Title:
  package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  I have an AMD Ryzen 7745hx CPU and the iGPU (integrated GPU from the
  CPU) is not recognised. It seems to be related to the error I
  received.

  My computer with Mantic only runs on the Nvidia graphic card because
  it doesn't take the iGPU into account. I suypposed it is because the
  CPU is fairly new to the market and that Igpu drivers are not
  integrates into the linux-genereic-6.5

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   gnome-metronome:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Nov 12 21:58:39 2023
  DpkgHistoryLog:
   Start-Date: 2023-11-12  21:58:16
   Commandline: packagekit role='install-packages'
   Requested-By: kevin (1000)
   Install: gnome-metronome:amd64 (1.3.0-0ubuntu4)
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-10-24 (19 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=b0f42ab3-3f84-4147-8b10-99e7e7ff4a5e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.b

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Description changed:

  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.
  
- I found this issue on linux-image-6_2_0-38-generic and linux-
- image-5_15_0-90-generic on some specific machines.
+ I found this issue on linux-image-6.2.0-38-generic and linux-
+ image-5.15.0-90-generic on some specific machines.
  
  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.
  
  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.
  
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
-  Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
+  Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-90-generic N/A
-  linux-backports-modules-5.15.0-90-generic  N/A
-  linux-firmware 20220329.git681281e4-0ubuntu3.22
+  linux-restricted-modules-5.15.0-90-generic N/A
+  linux-backports-modules-5.15.0-90-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 16.0
  dmi.bios.vendor: HP
  dmi.bios.version: S12 Ver. 02.16.00
  dmi.board.name: 8810
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.23
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: HP ProOne 600 G6
  dmi.product.sku: 123456#ABA
  dmi.sys.vendor: HP

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

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

[Kernel-packages] [Bug 2043197] [NEW] USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

Public bug reported:

[Summary]
Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

I found this issue on linux-image-6_2_0-38-generic and linux-
image-5_15_0-90-generic on some specific machines.

Since some of machines are using usb ethernet adapter so after
upgrading, those machines are not accessible.

Following are the machine list I've seen impacted by this issue, I
believe there will be more if I check further.

https://certification.canonical.com/hardware/202005-27899/
https://certification.canonical.com/hardware/201903-26881/
https://certification.canonical.com/hardware/201903-26932/
https://certification.canonical.com/hardware/202005-27944/
https://certification.canonical.com/hardware/202008-28166/
https://certification.canonical.com/hardware/202008-28167/
https://certification.canonical.com/hardware/202102-28728/
https://certification.canonical.com/hardware/202008-28176/
https://certification.canonical.com/hardware/202008-28177/
https://certification.canonical.com/hardware/202202-29946/

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-90-generic 5.15.0-90.100
ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
Uname: Linux 5.15.0-90-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: maas
CloudName: maas
CloudPlatform: maas
CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
Date: Fri Nov 10 12:04:10 2023
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
 Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ProOne 600 G6
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-90-generic N/A
 linux-backports-modules-5.15.0-90-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2023
dmi.bios.release: 16.0
dmi.bios.vendor: HP
dmi.bios.version: S12 Ver. 02.16.00
dmi.board.name: 8810
dmi.board.vendor: HP
dmi.board.version: KBC Version 09.08.23
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 9.8
dmi.modalias: 
dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA:
dmi.product.family: 103C_53307F HP ProOne
dmi.product.name: HP ProOne 600 G6
dmi.product.sku: 123456#ABA
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug cert-sru jammy package-from-proposed uec-images

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/bugs/2043197/+attachment/5717845/+files/journalctl.log

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

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

Status in linux package in Ubuntu:
  New

Bug description:
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6_2_0-38-generic and linux-
  image-5_15_0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  

[Kernel-packages] [Bug 2042092] Re: CIFS module is not included in 6.2.0-1016

[Kevin Klinke]

We are impacted by this as well, and all our new VMs that were spun up
in Azure were failing due to mount issues. We were able to mitigate by
adding the following to our cloud-init:

bootcmd:
  - apt update
  - apt-mark hold linux-image-6.2.0-1016-azure
  - apt-mark hold linux-cloud-tools-6.2.0-1016-azure
  - apt-mark hold linux-headers-6.2.0-1016-azure
  - apt-mark hold linux-tools-6.2.0-1016-azure

This is obviously a temporary fix and if this is not addressed in the
next release we'll regress again and it also prevents us from getting
any bug fixes or security fixes in this most recent version. This feels
like a huge regression in this kernel version and I hope it gets fixed
and we prevent this from happening in future releases.

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.

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


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

[Kernel-packages] [Bug 2040948] Re: USB stick can't be detected

[Kevin Yeh]

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

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

Title:
  USB stick can't be detected

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in linux-signed-oem-6.1 package in Ubuntu:
  New

Bug description:
  [Summary]

  During SRU testing, I found some of devices failed to run the usb
  test, when I re-plugged the usb stick, it can be detected, but after
  rebooting, usb stick is gone again.

  I did some further checks and found that If I power cycle the device,
  it can be detected again.

  It seems to happen on the device plugged with a Sandisk usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Thu Oct 26 10:37:58 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
  InstallationDate: Installed on 2023-09-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2040948] Re: USB stick can't be detected

[Kevin Yeh]

** Tags added: cert-sru

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

Title:
  USB stick can't be detected

Status in linux-signed-oem-6.1 package in Ubuntu:
  New

Bug description:
  [Summary]

  During SRU testing, I found some of devices failed to run the usb
  test, when I re-plugged the usb stick, it can be detected, but after
  rebooting, usb stick is gone again.

  I did some further checks and found that If I power cycle the device,
  it can be detected again.

  It seems to happen on the device plugged with a Sandisk usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Thu Oct 26 10:37:58 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
  InstallationDate: Installed on 2023-09-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.1/+bug/2040948/+subscriptions


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

[Kernel-packages] [Bug 2040948] [NEW] USB stick can't be detected

[Kevin Yeh]

Public bug reported:

[Summary]

During SRU testing, I found some of devices failed to run the usb test,
when I re-plugged the usb stick, it can be detected, but after
rebooting, usb stick is gone again.

I did some further checks and found that If I power cycle the device, it
can be detected again.

It seems to happen on the device plugged with a Sandisk usb stick.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Thu Oct 26 10:37:58 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
InstallationDate: Installed on 2023-09-04 (51 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-oem-6.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-oem-6.1 (Ubuntu)
 Importance: Medium
 Assignee: Kai-Heng Feng (kaihengfeng)
 Status: New


** Tags: amd64 apport-bug jammy package-from-proposed

** Changed in: linux-signed-oem-6.1 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux-signed-oem-6.1 (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  USB stick can't be detected

Status in linux-signed-oem-6.1 package in Ubuntu:
  New

Bug description:
  [Summary]

  During SRU testing, I found some of devices failed to run the usb
  test, when I re-plugged the usb stick, it can be detected, but after
  rebooting, usb stick is gone again.

  I did some further checks and found that If I power cycle the device,
  it can be detected again.

  It seems to happen on the device plugged with a Sandisk usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Thu Oct 26 10:37:58 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
  InstallationDate: Installed on 2023-09-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.1/+bug/2040948/+subscriptions


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

[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete

[Kevin Brierly]

It examines the blkio device tree and sums data as far as i know.
Removed devices do not get deleted from the blkio statistics tree and
are just marked as offline somehow.

In our case racadm lclog created and destroyed usb devices to pull data
and the blkio tree reached over 65000 leafs. It takes time to process a
tree that large. WE believe our issue was caused by accumulation over
time of the usb device leafs from racadm lclog. WE had it running in a
cron which has now been stopped.

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

Title:
  cat /sys/fs/cgroup/blkio/blkio.time_recursive  took 1second to
  complete

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Issue:

  ```console
  # time cat /sys/fs/cgroup/blkio/blkio.time_recursive
  8:16 354721435

  real0m1.297s
  user0m0.000s
  sys 0m1.297s
  ```

  As could be seen from above result, cat blkio took about 1 second to complete 
which
  is much longer than a normal case.

  Kernel Version:

  Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  
  Would be appreciated to know any operations to identify the issue, Thank you 
very much for the help.

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


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

[Kernel-packages] [Bug 2037513] [NEW] HP ProBook 450 G8 Notebook fail to wifi test

[Kevin Yeh]

Public bug reported:

I'm reviewing the SRU test result on this machine.
I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

It's not a regression, since according to previous test run it has failed 
already.
Just because we missed reviewing it for a while.

The journal log is attach, please check further hardware informations at
https://certification.canonical.com/hardware/202106-29176/

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
Uname: Linux 5.15.0-86-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 27 15:47:37 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
InstallationDate: Installed on 2023-09-25 (2 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cert-sru focal package-from-proposed uec-images

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/bugs/2037513/+attachment/5704864/+files/journal.log

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

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

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete

[Kevin Brierly]

the hardware does not seem to be relevant. Do you have anything calling
"racadm lclog" on fairly regular basis? it creates and destroys a usb
device over and over.

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

Title:
  cat /sys/fs/cgroup/blkio/blkio.time_recursive  took 1second to
  complete

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Issue:

  ```console
  # time cat /sys/fs/cgroup/blkio/blkio.time_recursive
  8:16 354721435

  real0m1.297s
  user0m0.000s
  sys 0m1.297s
  ```

  As could be seen from above result, cat blkio took about 1 second to complete 
which
  is much longer than a normal case.

  Kernel Version:

  Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  
  Would be appreciated to know any operations to identify the issue, Thank you 
very much for the help.

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


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

[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete

[Kevin Brierly]

Do you have a lot of blkio devices coming and going? For example
iscsi/usb/etc. We currently believe it's tree bloat due to added/removed
devices. We are still digging into the issue.

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

Title:
  cat /sys/fs/cgroup/blkio/blkio.time_recursive  took 1second to
  complete

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Issue:

  ```console
  # time cat /sys/fs/cgroup/blkio/blkio.time_recursive
  8:16 354721435

  real0m1.297s
  user0m0.000s
  sys 0m1.297s
  ```

  As could be seen from above result, cat blkio took about 1 second to complete 
which
  is much longer than a normal case.

  Kernel Version:

  Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  
  Would be appreciated to know any operations to identify the issue, Thank you 
very much for the help.

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


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

[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete

[Kevin Brierly]

yes. just confirms it takes a while.

** Attachment added: "flame2.html"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+attachment/5700645/+files/flame2.html

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

Title:
  cat /sys/fs/cgroup/blkio/blkio.time_recursive  took 1second to
  complete

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Issue:

  ```console
  # time cat /sys/fs/cgroup/blkio/blkio.time_recursive
  8:16 354721435

  real0m1.297s
  user0m0.000s
  sys 0m1.297s
  ```

  As could be seen from above result, cat blkio took about 1 second to complete 
which
  is much longer than a normal case.

  Kernel Version:

  Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  
  Would be appreciated to know any operations to identify the issue, Thank you 
very much for the help.

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


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

[Kernel-packages] [Bug 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete

[Kevin Brierly]

Was the cause of this ever determined? I am seeing something similar on
some of my systems. Times are usually around 1s, sometimes slightly
higher.

# uname -r
4.15.0-193-generic

# time cat /sys/fs/cgroup/blkio/blkio.time_recursive
8:144 69349171178307
8:128 4718621058
8:112 4604996397
8:96 4625378704
8:80 4873085108
8:64 3777190161
8:48 4749702443
8:32 8346248400
8:16 9260262419
8:0 154939957376379

real0m1.03s
user0m0.00s
sys 0m1.03s

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

Title:
  cat /sys/fs/cgroup/blkio/blkio.time_recursive  took 1second to
  complete

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Issue:

  ```console
  # time cat /sys/fs/cgroup/blkio/blkio.time_recursive
  8:16 354721435

  real0m1.297s
  user0m0.000s
  sys 0m1.297s
  ```

  As could be seen from above result, cat blkio took about 1 second to complete 
which
  is much longer than a normal case.

  Kernel Version:

  Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  
  Would be appreciated to know any operations to identify the issue, Thank you 
very much for the help.

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


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

[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen

[Kevin]

I had a similar issue with a black screen after kernel update to
5.19.0-35. Kernel 5.19.0-32 still worked.

Updating NVIDIA drivers to 525.85.05 fixed 5.19.0-35 and broke 5.19.0-32

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Kevin Yeh]

No regression found.
Test result is available at 
https://docs.google.com/spreadsheets/d/15x8EIBt60Wd2YemL0XrjQnw2VheC0FCbwDGZ37-IpVo/edit?usp=share_link

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Triaged
Status in fabric-manager-525 source package in Jammy:
  Triaged
Status in libnvidia-nscq-515 source package in Jammy:
  Triaged
Status in libnvidia-nscq-525 source package in Jammy:
  Triaged
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Triaged
Status in fabric-manager-515 source package in Kinetic:
  Triaged
Status in fabric-manager-525 source package in Kinetic:
  Triaged
Status in libnvidia-nscq-515 source package in Kinetic:
  Triaged
Status in libnvidia-nscq-525 source package in Kinetic:
  Triaged
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Triaged

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

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain display panels.
  - Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using
VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT to
allocate memory.
  - Disabled Fixed Rate Link (FRL) when using passive DisplayPort
to HDMI dongles, which are incompatible  with FRL.
* debian/templates/control.in:
  - Add Conflicts, Replaces, Provides 

[Kernel-packages] [Bug 2007193] [NEW] One Dell machine won't auto login after installing nvidia-driver-525.85.05

[Kevin Yeh]

Public bug reported:

During the NV driver SRU testing, I found an issue on one dell
machine(https://certification.canonical.com/hardware/202004-27810/).

After installing the latest driver(525.85.05) in proposed, the system won't 
auto login anymore.
I tried many times using reboot command.

Please check journal log in attachment.

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

** Attachment added: "journal.log.27810"
   
https://bugs.launchpad.net/bugs/2007193/+attachment/5646900/+files/journal.log.27810

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

Title:
  One Dell machine won't auto login after installing nvidia-
  driver-525.85.05

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

Bug description:
  During the NV driver SRU testing, I found an issue on one dell
  machine(https://certification.canonical.com/hardware/202004-27810/).

  After installing the latest driver(525.85.05) in proposed, the system won't 
auto login anymore.
  I tried many times using reboot command.

  Please check journal log in attachment.

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


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

[Kernel-packages] [Bug 1996250] [NEW] OEM machine can't install newer version of Nvidia-driver by ubuntu-drivers install

[Kevin Yeh]

Public bug reported:

During the SRU testing, I found a dependency issue when running "ubuntu-drivers 
install".
Although OEM image has preloaded nvidia driver already, but when user want to 
install newer version of nvidia driver will hit this issue.

Using 202002-27718 as an example, after installing oem image, I ran
"ubuntu-drivers install" then I saw following message.

This not only happens on 202002-27718, I checked few oem machines, all
have this issue.

ubuntu-drivers autoinstall
WARNING:root:_pkg_get_support nvidia-driver-515-server: package has invalid 
Support PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-515: package has invalid Support 
PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support 
PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid 
Support PBheader, cannot determine support level

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree


Reading state information... 0%

Reading state information... 0%

Reading state information... Done

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-driver-520 : Depends: libnvidia-gl-520 (= 520.56.06-0ubuntu0.20.04.1) 
but it is not going to be installed
 Depends: libnvidia-compute-520 (= 
520.56.06-0ubuntu0.20.04.1) but it is not going to be installed
 Depends: libnvidia-extra-520 (= 
520.56.06-0ubuntu0.20.04.1) but it is not going to be installed
 Depends: nvidia-compute-utils-520 (= 
520.56.06-0ubuntu0.20.04.1) but it is not going to be installed
 Depends: libnvidia-decode-520 (= 
520.56.06-0ubuntu0.20.04.1) but it is not going to be installed
 Depends: libnvidia-encode-520 (= 
520.56.06-0ubuntu0.20.04.1) but it is not going to be installed
 Depends: nvidia-utils-520 (= 520.56.06-0ubuntu0.20.04.1) 
but it is not going to be installed
 Depends: xserver-xorg-video-nvidia-520 (= 
520.56.06-0ubuntu0.20.04.1) but it is not going to be installed
 Depends: libnvidia-cfg1-520 (= 520.56.06-0ubuntu0.20.04.1) 
but it is not going to be installed
 Depends: libnvidia-fbc1-520 (= 520.56.06-0ubuntu0.20.04.1) 
but it is not going to be installed
 Recommends: libnvidia-compute-520:i386 (= 
520.56.06-0ubuntu0.20.04.1)
 Recommends: libnvidia-decode-520:i386 (= 
520.56.06-0ubuntu0.20.04.1)
 Recommends: libnvidia-encode-520:i386 (= 
520.56.06-0ubuntu0.20.04.1)
 Recommends: libnvidia-fbc1-520:i386 (= 
520.56.06-0ubuntu0.20.04.1)
 Recommends: libnvidia-gl-520:i386 (= 
520.56.06-0ubuntu0.20.04.1)
E: Unable to correct problems, you have held broken packages.

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cert-sru oem-priority

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: 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/1996250

Title:
  OEM machine can't install newer version of Nvidia-driver by ubuntu-
  drivers install

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  During the SRU testing, I found a dependency issue when running 
"ubuntu-drivers install".
  Although OEM image has preloaded nvidia driver already, but when user want to 
install newer version of nvidia driver will hit this issue.

  Using 202002-27718 as an example, after installing oem image, I ran
  "ubuntu-drivers install" then I saw following message.

  This not only happens on 202002-27718, I checked few oem machines, all
  have this issue.

  ubuntu-drivers autoinstall
  WARNING:root:_pkg_get_support nvidia-driver-515-server: package has invalid 
Support PBheader, cannot determine support level
  WARNING:root:_pkg_get_support nvidia-driver-515: package has invalid Support 
PBheader, cannot determine support level
  WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support 
PBheader, cannot determine support level
  WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid 
Support PBheader, cannot determine support level

  Reading package lists... 0%

  Reading 

[Kernel-packages] [Bug 1995618] Re: It seems to not login automatically or get X session after installing Nvidia-driver

[Kevin Yeh]

Hi Alberto
Please find the log and console-log in our test job in the attachment.

** Attachment added: "截圖 2022-11-09 上午11.18.27.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5629770/+files/%E6%88%AA%E5%9C%96%202022-11-09%20%E4%B8%8A%E5%8D%8811.18.27.png

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1995618] Re: It seems to not login automatically or get X session after installing Nvidia-driver

[Kevin Yeh]

** Attachment added: "ubuntu-drivers.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5629769/+files/ubuntu-drivers.log

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1995618] Re: It seems not to auto login or get X session after installing Nvidia-driver

[Kevin Yeh]

** Attachment added: "27810.logs.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5628933/+files/27810.logs.tar.xz

** Summary changed:

- It seems not to auto login or get X session after installing Nvidia-driver
+ It seems to now login automatically or get X session after installing 
Nvidia-driver

** Summary changed:

- It seems to now login automatically or get X session after installing 
Nvidia-driver
+ It seems to not login automatically or get X session after installing 
Nvidia-driver

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

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1995618] Re: It seems not to auto login or get X session after installing Nvidia-driver

[Kevin Yeh]

** Attachment added: "26941.logs.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5628932/+files/26941.logs.tar.xz

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1995618] [NEW] It seems to not login automatically or get X session after installing Nvidia-driver

[Kevin Yeh]

Public bug reported:

During SRU testing, I found some machines kept failing to run switching graphic 
card test.
According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

Now I can't check the status of machines directly, but my guessing is
base on the output from our test case, it showed "Can't open display :0"
and "Gtk couldn't be initialized. Use Gtk.init_check() ".

I met this issue on there different machine which I can get log from
them so far, there are other machines have this issue but I can't get
the log.

Our testing always use ubuntu-driver install to install nvidia-driver.

https://certification.canonical.com/hardware/202004-27810/
https://certification.canonical.com/hardware/202004-27811/
https://certification.canonical.com/hardware/201904-26941/

Kernel version:5.15.0-53-generic
Nvidia driver: nvidia-driver-520-open

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov  3 10:55:26 2022
InstallationDate: Installed on 2020-08-03 (821 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.15 (Ubuntu)
 Importance: High
 Status: New

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


** Tags: amd64 apport-bug focal package-from-proposed uec-images

** Attachment added: "27811.logs.tar.xz"
   
https://bugs.launchpad.net/bugs/1995618/+attachment/5628929/+files/27811.logs.tar.xz

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

[Kevin Pulo]

The only upstream bug that seems potentially related is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024
.  But that's more about ensuring that WPA auth has completed before
starting the DHCP renewal, and it's not clear to me how blocking ICMP
could avoid that problem.  So it might not actually be related.  The fix
for that issue went into development version NM 1.39.9, so I may try
building and trying an upstream version which includes it, to see if
that fixes the problem (but I won't be able to try before next week at
the earliest).

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1024
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associated 
-> 4way_handshake
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key 
negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=]
  Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 
20:11:15.091] [4119] (discord.cpp:551): JS console: 

[Kernel-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

[Kevin Pulo]

I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework
laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device.
Every time wpa-supplicant chooses to associate with a different BSSID
(of the same SSID), the interface ends up being given a new IP address
by the DHCP server (usually the sequentially next address).

I don't have access to the DHCP server or its logs, but I tried the
above suggested workaround of setting net.ipv4.icmp_echo_ignore_all=1
and this prevents the problem from occurring.  So I expect the root
cause is the same.  (And as an aside, there is nothing in the client-
side logs to indicate that ICMP pings could be in any way related;
without this report it would have much more difficult to diagnose and
work around the problem.)

A different laptop running 18.04 on the same network is able to keep its
IP address when roaming, so presumably this is due to a change in
NetworkManager behaviour.

The problem makes it difficult to work in an enterprise office
environment (ie. moving around between desks and meeting rooms), because
all TCP connections are lost when the IP address changes, which is
especially impactful for ssh connections.

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface 

[Kernel-packages] [Bug 1939886] Re: Network connection can't come back after resuming from suspend

[Kevin Yeh]

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

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

Title:
  Network connection can't come back after resuming from suspend

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

Bug description:
  [Summary]
  I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from 
suspend I can't ssh to it.
  When I checked the status of that machine by using command ifconfig, I found 
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. sudo apt update; sudo apt dist-upgrade -y
  3. set a rtc alarm then suspend the system by "date '+%s' -d '+ 1 minutes' | 
sudo tee /sys/class/rtc/rtc0/wakealarm;sudo systemctl suspend" or use 
checkbox-cli run com.canonical.certification::suspend-tp
  4. try to ssh to it

  [Expected result]
  After resuming from suspend, I can ssh to it.

  [Actual result]
  Can't ssh to it.

  [Failure rate]
  5/5

  [Additional information]
  CID: 202012-28554
  SKU: FSB-DVT2-C3
  Network adapter: Qualcomm Atheros - 1969:e0a1
  kernel-version: 5.11.0-27-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 13 08:47:33 2021
  InstallationDate: Installed on 2020-08-03 (374 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

[Kevin Keijzer]

This broke a lot of our servers running Docker, which I all had to
restore by adding the root volume to a different instance and then
changing /boot/grub/grub.cfg in order to boot 5.13.0-1025-aws again.

So another "I can confirm this" from me.

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

Title:
  Docker container creation causes kernel oops on linux-aws
  5.13.0.1028.31~20.04.22

Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  Running the attached script on the latest AWS AMI for Ubuntu 20.04, I
  get a kernel panic and hard reset of the node.

  [   12.314552] VFS: Close: file count is 0
  [   12.351090] [ cut here ]
  [   12.351093] kernel BUG at include/linux/fs.h:3104!
  [   12.355272] invalid opcode:  [#1] SMP PTI
  [   12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws 
#31~20.04.1-Ubuntu
  [   12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
  [   12.371130] RIP: 0010:__fput+0x247/0x250
  [   12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.393425] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.398679] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.419533] FS:  () GS:9153ea90() 
knlGS:
  [   12.426937] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 
007706e0
  [   12.436716] DR0:  DR1:  DR2: 

  [   12.441941] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   12.447170] PKRU: 5554
  [   12.450355] Call Trace:
  [   12.453408]  
  [   12.456296]  fput+0xe/0x10
  [   12.459633]  task_work_run+0x70/0xb0
  [   12.463157]  do_exit+0x37b/0xaf0
  [   12.466570]  do_group_exit+0x43/0xb0
  [   12.470142]  __x64_sys_exit_group+0x18/0x20
  [   12.473989]  do_syscall_64+0x61/0xb0
  [   12.477565]  ? exit_to_user_mode_prepare+0x9b/0x1c0
  [   12.481734]  ? do_user_addr_fault+0x1d0/0x650
  [   12.485665]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   12.489790]  ? irqentry_exit+0x19/0x30
  [   12.493443]  ? exc_page_fault+0x8f/0x170
  [   12.497199]  ? asm_exc_page_fault+0x8/0x30
  [   12.501013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   12.505289] RIP: 0033:0x7f80d42a1bd6
  [   12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac.
  [   12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 
00e7
  [   12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 
7f80d42a1bd6
  [   12.526115] RDX:  RSI: 003c RDI: 

  [   12.531328] RBP:  R08: 00e7 R09: 
fe98
  [   12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 
7f80d45a4740
  [   12.541687] R13: 0002 R14: 7f80d45ad708 R15: 

  [   12.546916]  
  [   12.549829] Modules linked in: xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc 
input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr 
drm ip_tables x_tables autofs4
  [   12.583913] ---[ end trace 77367fed4d782aa4 ]---
  [   12.587963] RIP: 0010:__fput+0x247/0x250
  [   12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.610166] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.615417] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.620635] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.625878] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.631121] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.636358] FS:  () GS:9153ea90() 

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Could you put together a simple instruction for how to perform this
workaround please? I am not sure, if this is what was supposed to be set
by editing dsdt.dsl with above suggestion or if this is a new fix.

In all cases a simple instruction would be much appreciated and I will
test this and get back with the result asap.

Thanks!

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

We have tested with 5.18.0-051800-generic now, unfortunately battery is
still not recognized :(

Anything else we can try? Seems like some has managed to solve this with
identical hardware, but then I must be missing some steps here. Any help
is much appreciated.

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Output of dmesg attached.

** Attachment added: "output dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593690/+files/dmesg.txt

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Please find output of cat /proc/iomem attached.

** Attachment added: "output cat /proc/iomem"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593426/+files/iomem.txt

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATL'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATL
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATL returned object 09af25b3, 
external buffer length 18
 [Integer] = 

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATH'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATH
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATH returned object 3c0aee1f, 
external buffer length 18
 [Integer] = 

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Yes - Disabling Secureboot worked in order to get acpidbg working
(killed my touchpad mouse however that is another topic).

Output from both commands here:

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATD
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATD returned object a3ce38e0, 
external buffer length 18
 [Integer] = 

$ sudo acpidbg -b 'ex \_SB_.BAT1._STA'
Evaluating \_SB_.BAT1._STA
Evaluation of \_SB_.BAT1._STA returned object cb8c88ff, external buffer 
length 18
 [Integer] = 000F

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Unfortunately I get an "Operation not permitted" error when running sudo
acpidbg -b 'ex \_SB_.BAT1._STA' as well.

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Hi,
I left the PC at the office. Will try the new command on Friday when I will be 
there again. Thanks!
Br. Kevin

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Unfortunately I get an "Operation not permitted" error when I try to run
acpidbg here. Is above command exactly as it should be entered? Thanks.

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Hello.
I have tried to follow above instructions carefully, recompiling my own file. 
However for me its not working, unfortunately battery is still not recognized. 

I followed these steps:

1) install acpica-tools
sudo apt-get install acpica-tools

2) Grab the DSDT of your device
sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat

3) Decompile the dsdt.dat
sudo iasl -d dsdt.dat

4) Open the dsdt.dsl with whatever editor tickles your fancy
sudo xed dsdt.dsl

5) Delete everything with a * in front, first line should be "DefinitionBlock"
(For me that include Firmware Error (ACPI) in line 1 and 2 - if that could 
matter:
Could not resolve [^GFX0.CLID], AE_NOT_FOUND (20190509/dswload-388)
Could not resolve [^GFX0.CLID], AE_NOT_FOUND (20190509/dswload2-369)

6) Raise the last number in Definition Block by one
e.g.:
DefinitionBlock ("", "DSDT", 2, "FUJ ", "FJNBB6D ", 0x010C)
   ↓
DefinitionBlock ("", "DSDT", 2, "FUJ ", "FJNBB6D ", 0x010C0001)

7) Search for the string "OperationRegion (ERAM"
for me it was at line 18751; your mileage may vary

8) Replace the entire line with this one:
OperationRegion (ERAM, EmbeddedControl, Zero, 0x0100)

(I had OperationRegion (ERAM, SystemMemory, 0xFE508300, 0x0100) to begin
with)

9) Save and Exit

10) Recompile the dsdt.dsl (Note: This WILL show loads of warnings and 
optimizations
This will give you a dsdt.aml that should work.

I did that with: sudo iasl -ta dsdt.dsl and got the aml file just with
warnings.

11) Proceed as above

sudo cp dsdt.aml /boot/
sudo cp 01_acpi /etc/grub.d/
chmod 755 01_acpi
sudo update-grub
reboot

Still just the same :/
Can anyone point me in the right direction?

PS. BIOS v. 1.12 (freshly update through Windows, Fujitsu DeskUpdate).

Br. Kevin

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-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: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish

[Kevin Yeh]

Test results for 510 are available at 
https://docs.google.com/spreadsheets/d/1VjZ1Jx9vuQPFtmTU-r9hJYDWlrA5dyopHQfQ9LWitlg/edit?usp=sharing
Test results for 390 are available at 
https://docs.google.com/spreadsheets/d/1hZrugw1J2oNKFf4ZZzhBE5wmE1HWjZGSOqk6Llt_0ZM/edit?usp=sharing

No regression found for both.

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

Title:
  Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in
  Bionic, Focal, and Impish

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Impish:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

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

  === 510 impish/focal/bionic ===

    * New upstream release (LP: #1966093):
  - Added support for the following GPUs:
  NVIDIA RTX A4000H
  NVIDIA RTX A5500
  - Fixed a bug that could cause displays with HDMI or DisplayPort
    audio to be deselected as the default audio output device after
    resuming from suspend.
  - Fixed a regression that could cause OpenGL applications to hang
    or render incorrectly after suspend/resume cycles or VT-
    switches
  - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:"
    in /proc/driver/nvidia/gpus//information
    to be "Unknown" for some GPUs.

  === 390 impish/focal/bionic ===

* New upstream release (LP: #1966093):
  - Fixed a bug where vkCreateSwapchain could cause the X Server to
crash when an invalid imageFormat was provided.
  - Fixed a driver installation failure on Linux kernel 5.11
release candidates, where the NVIDIA kernel module failed to
build with error "fatal error: asm/kmap_types.h: No such file
or directory".

[ Dimitri John Ledkov ]
* debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch:
  - Fix armhf builds.
* debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch:
  - Fix build failure with Linux 5.17.

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


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

[Kernel-packages] [Bug 1967977] [NEW] Can't boot up after installing nvidia-driver-510 on Jammy beta

[Kevin Yeh]

Public bug reported:

[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.

[Expected result]

system should boot into desktop.

[Actual result]

system stuck in boot stage and monitor keeps blinking.
please see the attachment.

[Info]

OS version: Ubuntu Jammy Jellyfish (development branch)
Device: Dell Precision 5760
CID: 202103-28844

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


** Tags: jaiyi jammy nvidia-driver-510 oem-priority

** Attachment added: "IMG_6022.mp4"
   
https://bugs.launchpad.net/bugs/1967977/+attachment/5577445/+files/IMG_6022.mp4

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

Title:
  Can't boot up after installing nvidia-driver-510 on Jammy beta

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

Bug description:
  [Reproduce step]
  1. install ubuntu-22.04 beta.
  2. run "apt update" and "ubuntu-driver install"
  3. reboot the system.

  [Expected result]

  system should boot into desktop.

  [Actual result]

  system stuck in boot stage and monitor keeps blinking.
  please see the attachment.

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: Dell Precision 5760
  CID: 202103-28844

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


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

[Kernel-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox

[Kevin Yeh]

I tried glxgear before, it will use nvidia-driver, I can see it by nvidia-smi.
Since we define our test scope using firefox to check, so I report this bug.
Or should I add firefox as impacted package and remove linux package.

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

Title:
  Jammy didn't use nvidia driver when executing firefox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z2 Mini G5 Workstation
  dmi.product.sku: 9JD38AV
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox

[Kevin Yeh]

** Summary changed:

- Jammy didn't use nvidia driver whne executing firefox
+ Jammy didn't use nvidia driver when executing firefox

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

Title:
  Jammy didn't use nvidia driver when executing firefox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z2 Mini G5 Workstation
  dmi.product.sku: 9JD38AV
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1967456] [NEW] Jammy didn't use nvidia driver whne executing firefox

[Kevin Yeh]

Public bug reported:

[Reproduce step]

1. Install Jammy beta.
2. Install Nvidia driver by ubuntu-driver install.
3. Connect monitor to dGPU output port.
4. Run firefox, type "about:support" in url, and check column "GPU #1"

[Expected result]

should see nvidia driver info.

[Actual result]

still use llvmpipe

[Info]

OS version: Ubuntu Jammy Jellyfish (development branch)
Device: HP Z2 Mini G5 workstation
CID: 202008-28179

Wayland in use.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-23-generic 5.15.0-23.23
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1186 F pulseaudio
 /dev/snd/controlC1:  u  1186 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 00:07:47 2022
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: HP HP Z2 Mini G5 Workstation
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-23-generic N/A
 linux-backports-modules-5.15.0-23-generic  N/A
 linux-firmware 20220314.gitcd01f857-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2020
dmi.bios.release: 0.1
dmi.bios.vendor: HP
dmi.bios.version: S50 Ver. 01.00.01
dmi.board.name: 8754
dmi.board.vendor: HP
dmi.board.version: KBC Version 09.08.03
dmi.chassis.type: 2
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 9.8
dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z2 Mini G5 Workstation
dmi.product.sku: 9JD38AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug jammy jiayi oem-priority wayland-session

** Attachment added: "Screenshot from 2022-03-31 23-57-25.png"
   
https://bugs.launchpad.net/bugs/1967456/+attachment/5575464/+files/Screenshot%20from%202022-03-31%2023-57-25.png

** Tags added: jiayi oem-priority

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

Title:
  Jammy didn't use nvidia driver whne executing firefox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  

[Kernel-packages] [Bug 1961075] Re: Introduce 510-server NVIDIA driver and update the 510 UDA driver series in Bionic, Focal, and Impish

[Kevin Yeh]

Please find test results at 
https://docs.google.com/spreadsheets/d/1VtJNgxFU4sO8foPgzP2Q-g-flo2sSELecOJnS9pGKXM/edit?usp=sharing.
No regressions were found.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

  [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]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961596] Re: Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor

[Kevin Karl]

Thanks for the solution. I removed "nomodeset" from grub config and now
it detects external monitor.

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

Title:
  Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external
  monitor

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

Bug description:
  Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)"

  $ lspci | grep -E 'VGA|Display'
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)

  $ glxinfo -B
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Mesa/X.org (0x)
  Device: llvmpipe (LLVM 12.0.0, 256 bits) (0x)
  Version: 21.2.6
  Accelerated: no
  Video memory: 31887MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.1
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  OpenGL vendor string: Mesa/X.org
  OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.2.6
  OpenGL core profile shading language version string: 4.50
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 3.1 Mesa 21.2.6
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)

  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.6
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 21 14:42:46 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.9.1, 5.13.0-28-generic, x86_64: installed
   evdi, 1.9.1, 5.13.0-30-generic, x86_64: installed
   virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed
   virtualbox, 6.1.26, 5.13.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:8784]
  InstallationDate: Installed on 2021-03-03 (355 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ZBook Fury 15 G7 Mobile Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nomodeset vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: HP
  dmi.bios.version: S92 Ver. 01.04.01
  dmi.board.name: 8783
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3D.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 22.61
  dmi.modalias: 
dmi:bvnHP:bvrS92Ver.01.04.01:bd01/05/2021:br4.1:efr22.61:svnHP:pnHPZBookFury15G7MobileWorkstation:pvr:sku26F75AV:rvnHP:rn8783:rvrKBCVersion16.3D.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Fury 15 G7 Mobile Workstation
  dmi.product.sku: 26F75AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0

[Kevin Yeh]

According to test result at 
https://certification.canonical.com/hardware/202002-27718/submission/245770/test-results/pass/?term=media.
This problem has been solved.

** 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-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1951784

Title:
  Can't read/write SD card after running CPU offline test in 5.11.0 and
  5.13.0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.11 package in Ubuntu:
  New
Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  [Summary]
  I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard 
test always fails.
  I found that after CPU offline test, I can't read/write SD card.
  After checking dmesg, I got those error msgs.
  [  232.577510] __common_interrupt: 7.34 No irq handler for vector
  [  234.354327] mmc0: error -110 doing runtime resume

  I found the same issue on Dell Precision 3551(202002-27718) and Dell
  Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36

  Before I didn't think it's a bug since I re-run mediacard test then
  it's pass. But this cycle there are more systems failed to the test, I
  just started digging into that.

  [Step to reproduce]
  1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04
  2. sudo apt update; sudo apt dist-upgrade -y
  3. run cpu offline test via checkbox-cli or execute following command
     for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done;
     cd $mount_point_of_sd_card
     sudo dd if=/dev/urandom of=test bs=1M count=10

  [Expected result]
  Can read/write SD card.

  [Actual result]
  Can't read/write SD card.

  [Failure rate]
  5/5

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 22 01:28:59 2021
  InstallationDate: Installed on 2020-08-03 (475 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1957018] Re: System hangs on reboot and shutdown

[Kevin Watts]

Also same issue with Asus PN50 Ryzen 5 4500U Bios 0623 (latest Bios) and
Mint version 20.3

Everything fine using version 5.11.0.46 but can't shut down/restart with
5.13.0.25 (even after waiting over ten minutes). sudo shutdown -h now
also doesn't work. Seems to reach (message) [OK] Reached Target Power-
off but then nothing except periodic [UFW Block] messages.

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

Title:
  System hangs on reboot and shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 5.13.0-22-generic to 5.13.0-25-generic,
  the system cannot be powered down or rebooted, just hangs
  indefinitely.

   This is a possible duplicate of the link below

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

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


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

[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal

[Kevin Yeh]

Test results for 495 are available at
https://docs.google.com/spreadsheets/d/14Kc4yMyGIqUr6oMGzqddlVcMMoY4qpq99crILaH58Os/edit?usp=sharing

Test results for 470 are available at
https://docs.google.com/spreadsheets/d/1kAo_Y8LFIDYY6skpkPGDCrNErG8-rN_ziQ0eJwmYDZ4/edit?usp=sharing

No regression were found.

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

Title:
  Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
  and 470 in Focal

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
  Fix Committed

Bug description:
  [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 (focal only) ==

  nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
  urgency=medium

    * debian/{nvidia_supported|pm-aliases-gen}:
  - Drop the following IDs in favour of the 495 series (LP: #1954818):
    1fbc, 249c, 249d, 24b6, 24b7, 24b8,
    25a0, 25b8.

  == 495 (bionic, focal, hirsute, impish) ==

  nvidia-graphics-drivers-495 (495.46-0ubuntu*)

[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
  - Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.

[ Alberto Milone ]
    * debian/additional_card_ids,
  debian/additional_runtimepm_ids:
  - Add the following IDs:
    1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8

    * New upstream release (LP: #1954818):
  - Added support for the GBM API. This adds the new symlink
    nvidia-drm_gbm.so pointing to the file libnvidia-
    allocator.so.VERSION to implement a GBM backend driver usable
    with the GBM loader from the Mesa project version 21.2 and
    above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
    15_nvidia_gbm.json, which implement EGL support for the GBM
    platform (EGL_KHR_platform_gbm).
  - Add indicator for Resizable BAR support on compatible systems.
  - Fixed a bug that could cause the X server to crash when
    starting a new server generation on PRIME configurations.
  - Removed support for NvIFROpenGL. This functionality was
    deprecated in the 470.xx driver release.
  - Removed libnvidia-cbl.so from the driver package. This
    functionality is now provided by other driver libraries.
  - Changed the minimum required Linux kernel version from 2.6.32
    to 3.10.
  - Updated nvidia.ko to load even if no supported NVIDIA GPUs are
    present when an NVIDIA NVSwitch device is detected in the
    system. Previously, nvidia.ko would fail to load into the
    kernel if no supported GPUs were present.
  - Fixed a bug in the Vulkan driver where unused input attributes
    to a vertex shader would corrupt the interpolation qualifiers
    for the shader.
  - Fixed a bug in the Vulkan driver where individual components of
    barycentric inputs could not be read.
  - Added support for the VK_KHR_present_id extension.
  - Added support for the VK_KHR_present_wait extension.
  - Added support for the
    VK_KHR_shader_subgroup_uniform_control_flow extension.
  - Fixed a bug where VK_NVX_binary_import was advertised as
    supported on unsupported platforms. This caused calls to
    vkCreateDevice to fail if applications attempted to enable
    

[Kernel-packages] [Bug 1950665] Re: Update the 470 NVIDIA driver to 470.86

[Kevin Yeh]

You can find test results at 
https://docs.google.com/spreadsheets/d/1bjCjuBFXykVvCb_NuxepUjJthqSiiiDQY854-Tqffyw/edit?usp=sharing
No regression were found.

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

Title:
  Update the 470 NVIDIA driver to 470.86

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the 470 NVIDIA series in Bionic, Focal, Hirsute, and Impish.

  [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 ==
    * New upstream release (LP: #1950665):
  - Fixed a regression which prevented DisplayPort and HDMI 2.1
    variable refresh rate (VRR) G-SYNC Compatible monitors from
    functioning correctly in variable refresh rate mode, resulting
    in issues such as flickering.

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


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

[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0

[Kevin Yeh]

** Summary changed:

- Can't read/write SD card after running CPU offline test in 5.11.0-41.45
+ Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0

** Changed in: linux-signed-hwe-5.11 (Ubuntu)
   Importance: High => Medium

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Importance: High => Medium

** Description changed:

  [Summary]
  I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard 
test always fails.
  I found that after CPU offline test, I can't read/write SD card.
  After checking dmesg, I got those error msgs.
  [  232.577510] __common_interrupt: 7.34 No irq handler for vector
  [  234.354327] mmc0: error -110 doing runtime resume
  
- Also I found the same issue on Dell Precision 3551(202002-27718) in
- 5.13.0-21(both Focal/Impish), but this system don't have issue in
- 5.11.0-41.
+ I found the same issue on Dell Precision 3551(202002-27718) and Dell
+ Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36
+ 
+ Before I didn't think it's a bug since I re-run mediacard test then it's
+ pass. But this cycle there are more systems failed to the test, I just
+ started digging into that.
  
  [Step to reproduce]
- 1. install ubuntu-20.04.2
+ 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04
  2. sudo apt update; sudo apt dist-upgrade -y
  3. run cpu offline test via checkbox-cli or execute following command
-for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done; 
-cd $mount_point_of_sd_card
-sudo dd if=/dev/urandom of=test bs=1M count=10
- 
+    for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done;
+    cd $mount_point_of_sd_card
+    sudo dd if=/dev/urandom of=test bs=1M count=10
  
  [Expected result]
  Can read/write SD card.
  
  [Actual result]
  Can't read/write SD card.
  
  [Failure rate]
  5/5
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 22 01:28:59 2021
  InstallationDate: Installed on 2020-08-03 (475 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Can't read/write SD card after running CPU offline test in 5.11.0 and
  5.13.0

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

Bug description:
  [Summary]
  I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard 
test always fails.
  I found that after CPU offline test, I can't read/write SD card.
  After checking dmesg, I got those error msgs.
  [  232.577510] __common_interrupt: 7.34 No irq handler for vector
  [  234.354327] mmc0: error -110 doing runtime resume

  I found the same issue on Dell Precision 3551(202002-27718) and Dell
  Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36

  Before I didn't think it's a bug since I re-run mediacard test then
  it's pass. But this cycle there are more systems failed to the test, I
  just started digging into that.

  [Step to reproduce]
  1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04
  2. sudo apt update; sudo apt dist-upgrade -y
  3. run cpu offline test via checkbox-cli or execute following command
     for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done;
     cd $mount_point_of_sd_card
     sudo dd if=/dev/urandom of=test bs=1M count=10

  [Expected result]
  Can read/write SD card.

  [Actual result]
  Can't read/write SD card.

  [Failure rate]
  5/5

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 22 01:28:59 2021
  InstallationDate: Installed on 2020-08-03 (475 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1951784] [NEW] Can't read/write SD card after running CPU offline test in 5.11.0-41.45

[Kevin Yeh]

Public bug reported:

[Summary]
I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test 
always fails.
I found that after CPU offline test, I can't read/write SD card.
After checking dmesg, I got those error msgs.
[  232.577510] __common_interrupt: 7.34 No irq handler for vector
[  234.354327] mmc0: error -110 doing runtime resume

Also I found the same issue on Dell Precision 3551(202002-27718) in
5.13.0-21(both Focal/Impish), but this system don't have issue in
5.11.0-41.

[Step to reproduce]
1. install ubuntu-20.04.2
2. sudo apt update; sudo apt dist-upgrade -y
3. run cpu offline test via checkbox-cli or execute following command
   for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done; 
   cd $mount_point_of_sd_card
   sudo dd if=/dev/urandom of=test bs=1M count=10


[Expected result]
Can read/write SD card.

[Actual result]
Can't read/write SD card.

[Failure rate]
5/5

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Nov 22 01:28:59 2021
InstallationDate: Installed on 2020-08-03 (475 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: High
 Status: New

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug cert-sru focal package-from-proposed uec-images

** Attachment added: "journalctl-27131.log"
   
https://bugs.launchpad.net/bugs/1951784/+attachment/5542566/+files/journalctl-27131.log

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

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Can't read/write SD card after running CPU offline test in
  5.11.0-41.45

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

Bug description:
  [Summary]
  I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard 
test always fails.
  I found that after CPU offline test, I can't read/write SD card.
  After checking dmesg, I got those error msgs.
  [  232.577510] __common_interrupt: 7.34 No irq handler for vector
  [  234.354327] mmc0: error -110 doing runtime resume

  Also I found the same issue on Dell Precision 3551(202002-27718) in
  5.13.0-21(both Focal/Impish), but this system don't have issue in
  5.11.0-41.

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. sudo apt update; sudo apt dist-upgrade -y
  3. run cpu offline test via checkbox-cli or execute following command
 for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done; 
 cd $mount_point_of_sd_card
 sudo dd if=/dev/urandom of=test bs=1M count=10

  
  [Expected result]
  Can read/write SD card.

  [Actual result]
  Can't read/write SD card.

  [Failure rate]
  5/5

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 22 01:28:59 2021
  InstallationDate: Installed on 2020-08-03 (475 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021

[Kevin Yeh]

Nvidia SRU testing for 470.82 and 495.44 are completed, no regressions were 
found.
Test results are available at 
https://docs.google.com/spreadsheets/d/1QGCG0fSR9NV7SkURqcJG31nkwob9q4oRxcBni4lZL0w/edit?usp=sharing
 and 
https://docs.google.com/spreadsheets/d/1ABUVyn1zZcj4bsTpEJ9pdkVsJeyyfadtFQDwOtBa8Uk/edit?usp=sharing

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


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

[Kevin Yeh]

The test results are available at 
https://docs.google.com/spreadsheets/d/10rgG0qyrMdhwjrpHdPecCeDk4MGVZs7iPJdAZcHZZkk/edit#gid=1527963777
No regressions were found.

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

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed

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 1943913] Re: touchpad and keyboard are not working in 5.11.0-35

[Kevin Yeh]

After installing hirsute kernel -36 in Focal, touch pad and keyboard are
still not working. I also tried to install -36 kernel only without dist-
upgrade and disabled proposed then they're working, so I guess it's not
a kernel regression.

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

Title:
  touchpad and keyboard are not working in 5.11.0-35

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

Bug description:
  [Summary]
  Touchpad and keyboard are not working after installing 5.11.0-35 from 
proposed.
  I tried to use 5.11.0-34, keyboard and touchpad are working.

  I found there are some error msg through dmesg, not sure are they related to 
this issue?
  [   14.586201] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: 
-5
  [   15.069933] psmouse serio1: Failed to enable mouse on isa0060/serio1
  [   19.558182] psmouse serio1: Failed to enable mouse on isa0060/serio1

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. enable proposed.
  3. sudo apt update; sudo apt dist-upgrade -y
  4. reboot.

  [Expected result]
  touchpad and keyboard are working.

  [Actual result]
  Can't get any response from both.

  [Failure rate]
  5/5

  [Additional information]
  CID: 201807-26321
  SKU: BKN4-DVT2-C1
  kernel-version: 5.11.0-35-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-35-generic 5.11.0-35.37~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-35.37~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 01:41:01 2021
  InstallationDate: Installed on 2020-08-03 (409 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working

[kevin flynn]

NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu

Keychron K1 keyboard

Bluetooth connection:
Loss of most chars, numbers and some symbols show. 

Using: echo 'options hid_apple fnmode=0' | sudo tee
/etc/modprobe.d/hid_apple.conf

fixes the issue

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

Title:
  Keychron K1 keyboard not working

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

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1943913] Re: touchpad and keyboard are not working in 5.11.0-35

[Kevin Yeh]

ii  linux-modules-5.11.0-35-generic5.11.0-35.37~20.04.1 
 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 
SMP
ii  linux-modules-extra-5.11.0-35-generic  5.11.0-35.37~20.04.1 
 amd64Linux kernel extra modules for version 5.11.0 on 64 bit x86 
SMP

modules and modules-extra are installed.

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

Title:
  touchpad and keyboard are not working in 5.11.0-35

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

Bug description:
  [Summary]
  Touchpad and keyboard are not working after installing 5.11.0-35 from 
proposed.
  I tried to use 5.11.0-34, keyboard and touchpad are working.

  I found there are some error msg through dmesg, not sure are they related to 
this issue?
  [   14.586201] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: 
-5
  [   15.069933] psmouse serio1: Failed to enable mouse on isa0060/serio1
  [   19.558182] psmouse serio1: Failed to enable mouse on isa0060/serio1

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. enable proposed.
  3. sudo apt update; sudo apt dist-upgrade -y
  4. reboot.

  [Expected result]
  touchpad and keyboard are working.

  [Actual result]
  Can't get any response from both.

  [Failure rate]
  5/5

  [Additional information]
  CID: 201807-26321
  SKU: BKN4-DVT2-C1
  kernel-version: 5.11.0-35-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-35-generic 5.11.0-35.37~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-35.37~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 01:41:01 2021
  InstallationDate: Installed on 2020-08-03 (409 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1943913] [NEW] touchpad and keyboard are not working in 5.11.0-35

[Kevin Yeh]

Public bug reported:

[Summary]
Touchpad and keyboard are not working after installing 5.11.0-35 from proposed.
I tried to use 5.11.0-34, keyboard and touchpad are working.

I found there are some error msg through dmesg, not sure are they related to 
this issue?
[   14.586201] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
[   15.069933] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   19.558182] psmouse serio1: Failed to enable mouse on isa0060/serio1

[Step to reproduce]
1. install ubuntu-20.04.2
2. enable proposed.
3. sudo apt update; sudo apt dist-upgrade -y
4. reboot.

[Expected result]
touchpad and keyboard are working.

[Actual result]
Can't get any response from both.

[Failure rate]
5/5

[Additional information]
CID: 201807-26321
SKU: BKN4-DVT2-C1
kernel-version: 5.11.0-35-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-35-generic 5.11.0-35.37~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-35.37~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Sep 17 01:41:01 2021
InstallationDate: Installed on 2020-08-03 (409 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug cert-sru focal package-from-proposed uec-images

** Attachment added: "output of journalctl"
   
https://bugs.launchpad.net/bugs/1943913/+attachment/5525845/+files/journalctl-26321.log

** Tags removed: cert-su
** Tags added: cert-sru

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

Title:
  touchpad and keyboard are not working in 5.11.0-35

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

Bug description:
  [Summary]
  Touchpad and keyboard are not working after installing 5.11.0-35 from 
proposed.
  I tried to use 5.11.0-34, keyboard and touchpad are working.

  I found there are some error msg through dmesg, not sure are they related to 
this issue?
  [   14.586201] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: 
-5
  [   15.069933] psmouse serio1: Failed to enable mouse on isa0060/serio1
  [   19.558182] psmouse serio1: Failed to enable mouse on isa0060/serio1

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. enable proposed.
  3. sudo apt update; sudo apt dist-upgrade -y
  4. reboot.

  [Expected result]
  touchpad and keyboard are working.

  [Actual result]
  Can't get any response from both.

  [Failure rate]
  5/5

  [Additional information]
  CID: 201807-26321
  SKU: BKN4-DVT2-C1
  kernel-version: 5.11.0-35-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-35-generic 5.11.0-35.37~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-35.37~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 01:41:01 2021
  InstallationDate: Installed on 2020-08-03 (409 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04

[kevin mwangi]

Hello Alejandro,

I notified them about the bug & they are aware of it.

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

Title:
  [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04

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

Bug description:
  Just installed ubuntu 20.04 and the screen has been flickering all
  through. tried applying the ubuntu on Wayland solution but no change.
  Please help with a solution on workaround for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 22 21:39:46 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
  InstallationDate: Installed on 2021-08-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP EliteBook Folio G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.release: 1.10
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.10
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.68
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 41.104
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: Z5Z39US#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

Re: [Kernel-packages] [Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04

[kevin mwangi]

Find the videos attached,
Thank you.


Regards,
On Wed, Aug 25, 2021 at 5:15 AM Daniel van Vugt <1940...@bugs.launchpad.net>
wrote:

> Please:
>
> 1. Tell us the contents of /proc/cmdline
>
> 2. Attach a video of the problem so we can better understand what you
> are seeing.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1940780
>
> Title:
>   [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
>
> Status in linux-hwe-5.11 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Just installed ubuntu 20.04 and the screen has been flickering all
>   through. tried applying the ubuntu on Wayland solution but no change.
>   Please help with a solution on workaround for this.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
>   Uname: Linux 5.11.0-27-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Aug 22 21:39:46 2021
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: I just need to know a workaround
>   GraphicsCard:
>Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA
> controller])
>  Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
>   InstallationDate: Installed on 2021-08-22 (0 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   MachineType: HP HP EliteBook Folio G1
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic
> root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/19/2016
>   dmi.bios.release: 1.10
>   dmi.bios.vendor: HP
>   dmi.bios.version: N91 Ver. 01.10
>   dmi.board.name: 8170
>   dmi.board.vendor: HP
>   dmi.board.version: KBC Version 29.68
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.ec.firmware.release: 41.104
>   dmi.modalias:
> dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr:
>   dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
>   dmi.product.name: HP EliteBook Folio G1
>   dmi.product.sku: Z5Z39US#ABA
>   dmi.sys.vendor: HP
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.105-3~20.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1940780/+subscriptions
>
>

-- 
*Maina Kelvin Mwangi*


** Attachment added: "Screencast from 08-31-2021 10:40:38 PM.webm"
   
https://bugs.launchpad.net/bugs/1940780/+attachment/5522436/+files/Screencast%20from%2008-31-2021%2010%3A40%3A38%20PM.webm

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

Title:
  [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04

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

Bug description:
  Just installed ubuntu 20.04 and the screen has been flickering all
  through. tried applying the ubuntu on Wayland solution but no change.
  Please help with a solution on workaround for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 22 21:39:46 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
  InstallationDate: Installed on 2021-08-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP EliteBook Folio G1
  

[Kernel-packages] [Bug 1942271] [NEW] Spontaneous NVIDIA panic

[Kevin McMurtrie]

Public bug reported:

All graphics and USB devices spontaneously halted.
SSH, networking, and filesystems remained working.
Xorg stuck and can not exit even after ABRT signal.
"shutdown" command never completed.


Aug 31 18:17:12 fuel kernel: [ 3494.973431] BUG: unable to handle page fault 
for address: 00020018
Aug 31 18:17:12 fuel kernel: [ 3494.973436] #PF: supervisor read access in 
kernel mode
Aug 31 18:17:12 fuel kernel: [ 3494.973438] #PF: error_code(0x) - 
not-present page
Aug 31 18:17:12 fuel kernel: [ 3494.973439] PGD 0 P4D 0 
Aug 31 18:17:12 fuel kernel: [ 3494.973442] Oops:  [#1] SMP NOPTI
Aug 31 18:17:12 fuel kernel: [ 3494.973444] CPU: 2 PID: 33911 Comm: chrome 
Tainted: P   OE 5.11.0-31-generic #33-Ubuntu
Aug 31 18:17:12 fuel kernel: [ 3494.973447] Hardware name: Gigabyte Technology 
Co., Ltd. Default string/X99P-SLI-CF, BIOS F25b 03/13/2018
Aug 31 18:17:12 fuel kernel: [ 3494.973448] RIP: 0010:_nv028963rm+0x35/0x90 
[nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.973792] Code: 57 10 31 c0 48 85 d2 74 2e 48 
8b 4f 08 31 c0 48 85 c9 74 0d 48 63 41 14 48 89 d6 48 29 c6 48 89 f0 48 3b 57 
18 48 89 07 74 1b <48> 8b 42 08 48 89 47 10 b8 01 00 00 00 48 83 c4 08 c3 66 0f 
1f 84
Aug 31 18:17:12 fuel kernel: [ 3494.973795] RSP: 0018:b11742f43bd0 EFLAGS: 
00010203
Aug 31 18:17:12 fuel kernel: [ 3494.973797] RAX: 00020010 RBX: 
9c819c336c30 RCX: 9c7e48cec978
Aug 31 18:17:12 fuel kernel: [ 3494.973798] RDX: 00020010 RSI: 
00020010 RDI: 9c7cf6695d20
Aug 31 18:17:12 fuel kernel: [ 3494.973800] RBP: 9c7cf6695d20 R08: 
0020 R09: 9c7cf6695d28
Aug 31 18:17:12 fuel kernel: [ 3494.973801] R10:  R11: 
 R12: 9c7d3d867738
Aug 31 18:17:12 fuel kernel: [ 3494.973802] R13: 9c7e1c027060 R14: 
9c7cf6695d98 R15: 9c819c336c30
Aug 31 18:17:12 fuel kernel: [ 3494.973804] FS:  () 
GS:9c8bcfc8() knlGS:
Aug 31 18:17:12 fuel kernel: [ 3494.973806] CS:  0010 DS:  ES:  CR0: 
80050033
Aug 31 18:17:12 fuel kernel: [ 3494.973807] CR2: 00020018 CR3: 
0006dcc10005 CR4: 003706e0
Aug 31 18:17:12 fuel kernel: [ 3494.973809] DR0:  DR1: 
 DR2: 
Aug 31 18:17:12 fuel kernel: [ 3494.973810] DR3:  DR6: 
fffe0ff0 DR7: 0400
Aug 31 18:17:12 fuel kernel: [ 3494.973811] Call Trace:
Aug 31 18:17:12 fuel kernel: [ 3494.973814]  ? _nv035844rm+0xa8/0xe0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.974111]  ? _nv014655rm+0x2ee/0x770 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.974414]  ? _nv037695rm+0xb3/0x150 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.974719]  ? _nv037694rm+0x297/0x4e0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975018]  ? _nv037689rm+0x60/0x70 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975317]  ? _nv037690rm+0x7b/0xb0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975618]  ? _nv036056rm+0x40/0xe0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975840]  ? _nv000699rm+0x68/0x80 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976092]  ? 
rm_cleanup_file_private+0xea/0x160 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976341]  ? fsnotify+0x23c/0x2f0
Aug 31 18:17:12 fuel kernel: [ 3494.976347]  ? nvidia_close+0x156/0x320 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976539]  ? nvidia_frontend_close+0x2f/0x50 
[nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976728]  ? __fput+0x9f/0x250
Aug 31 18:17:12 fuel kernel: [ 3494.976731]  ? fput+0xe/0x10
Aug 31 18:17:12 fuel kernel: [ 3494.976733]  ? task_work_run+0x6d/0xa0
Aug 31 18:17:12 fuel kernel: [ 3494.976738]  ? do_exit+0x233/0x3e0
Aug 31 18:17:12 fuel kernel: [ 3494.976742]  ? do_group_exit+0x3b/0xb0
Aug 31 18:17:12 fuel kernel: [ 3494.976744]  ? __x64_sys_exit_group+0x18/0x20
Aug 31 18:17:12 fuel kernel: [ 3494.976747]  ? do_syscall_64+0x38/0x90
Aug 31 18:17:12 fuel kernel: [ 3494.976749]  ? 
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 31 18:17:12 fuel kernel: [ 3494.976754] Modules linked in: ipt_REJECT 
nf_reject_ipv4 xt_multiport nft_compat nft_counter nf_tables libcrc32c 
nfnetlink ccm md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc 
snd_hda_codec_hdmi intel_rapl_msr intel_rapl_common snd_hda_codec_realtek 
snd_hda_codec_generic zfs(PO) ledtrig_audio snd_hda_intel snd_intel_dspcfg 
soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec 
x86_pkg_temp_thermal zunicode(PO) intel_powerclamp snd_hda_core zzstd(O) 
snd_hwdep coretemp soundwire_bus zlua(O) snd_soc_core kvm_intel nls_iso8859_1 
zavl(PO) icp(PO) snd_compress ac97_bus snd_pcm_dmaengine snd_pcm kvm 
snd_seq_midi zcommon(PO) snd_seq_midi_event znvpair(PO) crct10dif_pclmul spl(O) 
joydev input_leds snd_rawmidi ghash_clmulni_intel snd_seq snd_seq_device 
aesni_intel snd_timer crypto_simd cryptd glue_helper snd rapl mei_me 
intel_cstate efi_pstore mxm_wmi mei soundcore intel_wmi_thunderbolt mac_hid 

[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

[Kevin Yeh]

Test results are available at 
https://drive.google.com/drive/u/1/folders/1ZHwi-YQZUR7pGIo-QcT9NbupnUk5GJPp.
No regressions were found.

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released

Bug description:
  Update the 470 (UDA) and 470-server (ERD) 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.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04

[kevin mwangi]

The issue is still persistent,


** Attachment added: "Screenshot-20210824184650-558x19.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1940780/+attachment/5520277/+files/Screenshot-20210824184650-558x19.png

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

Title:
  [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04

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

Bug description:
  Just installed ubuntu 20.04 and the screen has been flickering all
  through. tried applying the ubuntu on Wayland solution but no change.
  Please help with a solution on workaround for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 22 21:39:46 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
  InstallationDate: Installed on 2021-08-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP EliteBook Folio G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.release: 1.10
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.10
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.68
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 41.104
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: Z5Z39US#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1939886] Re: Network connection can't come back after resuming from suspend

[Kevin Yeh]

** Description changed:

  [Summary]
  I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from 
suspend I can't ssh to it.
  When I checked the status of that machine by using command ifconfig, I found 
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.
  
  [Step to reproduce]
  1. install ubuntu-20.04.2
- 2. enable proposed repo
- 3. sudo apt update; sudo apt dist-upgrade -y
- 4. set a rtc alarm then suspend the system by "date '+%s' -d '+ 1 minutes' | 
sudo tee /sys/class/rtc/rtc0/wakealarm;sudo systemctl suspend" or use 
checkbox-cli run com.canonical.certification::suspend-tp
- 5. try to ssh to it
+ 2. sudo apt update; sudo apt dist-upgrade -y
+ 3. set a rtc alarm then suspend the system by "date '+%s' -d '+ 1 minutes' | 
sudo tee /sys/class/rtc/rtc0/wakealarm;sudo systemctl suspend" or use 
checkbox-cli run com.canonical.certification::suspend-tp
+ 4. try to ssh to it
  
  [Expected result]
  After resuming from suspend, I can ssh to it.
  
  [Actual result]
  Can't ssh to it.
  
  [Failure rate]
  5/5
  
  [Additional information]
  CID: 202012-28554
  SKU: FSB-DVT2-C3
  Network adapter: Qualcomm Atheros - 1969:e0a1
  kernel-version: 5.11.0-27-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 13 08:47:33 2021
  InstallationDate: Installed on 2020-08-03 (374 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Network connection can't come back after resuming from suspend

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

Bug description:
  [Summary]
  I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from 
suspend I can't ssh to it.
  When I checked the status of that machine by using command ifconfig, I found 
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. sudo apt update; sudo apt dist-upgrade -y
  3. set a rtc alarm then suspend the system by "date '+%s' -d '+ 1 minutes' | 
sudo tee /sys/class/rtc/rtc0/wakealarm;sudo systemctl suspend" or use 
checkbox-cli run com.canonical.certification::suspend-tp
  4. try to ssh to it

  [Expected result]
  After resuming from suspend, I can ssh to it.

  [Actual result]
  Can't ssh to it.

  [Failure rate]
  5/5

  [Additional information]
  CID: 202012-28554
  SKU: FSB-DVT2-C3
  Network adapter: Qualcomm Atheros - 1969:e0a1
  kernel-version: 5.11.0-27-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 13 08:47:33 2021
  InstallationDate: Installed on 2020-08-03 (374 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1939886] [NEW] Network connection can't come back after resuming from suspend

[Kevin Yeh]

Public bug reported:

[Summary]
I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from 
suspend I can't ssh to it.
When I checked the status of that machine by using command ifconfig, I found 
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.

[Step to reproduce]
1. install ubuntu-20.04.2
2. enable proposed repo
3. sudo apt update; sudo apt dist-upgrade -y
4. set a rtc alarm then suspend the system by "date '+%s' -d '+ 1 minutes' | 
sudo tee /sys/class/rtc/rtc0/wakealarm;sudo systemctl suspend" or use 
checkbox-cli run com.canonical.certification::suspend-tp
5. try to ssh to it

[Expected result]
After resuming from suspend, I can ssh to it.

[Actual result]
Can't ssh to it.

[Failure rate]
5/5

[Additional information]
CID: 202012-28554
SKU: FSB-DVT2-C3
Network adapter: Qualcomm Atheros - 1969:e0a1
kernel-version: 5.11.0-27-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Aug 13 08:47:33 2021
InstallationDate: Installed on 2020-08-03 (374 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: Critical
 Status: New


** Tags: amd64 apport-bug cert-sru focal package-from-proposed uec-images

** Attachment added: "output of journalctl"
   
https://bugs.launchpad.net/bugs/1939886/+attachment/5517764/+files/journal-201801-26082.log

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

Title:
  Network connection can't come back after resuming from suspend

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

Bug description:
  [Summary]
  I'm running SRU testing on Dell G7 7588(201801-26082), after resuming from 
suspend I can't ssh to it.
  When I checked the status of that machine by using command ifconfig, I found 
there wasn't LAN card exist and LED indicator of RJ-45 port didn't blink.

  [Step to reproduce]
  1. install ubuntu-20.04.2
  2. enable proposed repo
  3. sudo apt update; sudo apt dist-upgrade -y
  4. set a rtc alarm then suspend the system by "date '+%s' -d '+ 1 minutes' | 
sudo tee /sys/class/rtc/rtc0/wakealarm;sudo systemctl suspend" or use 
checkbox-cli run com.canonical.certification::suspend-tp
  5. try to ssh to it

  [Expected result]
  After resuming from suspend, I can ssh to it.

  [Actual result]
  Can't ssh to it.

  [Failure rate]
  5/5

  [Additional information]
  CID: 202012-28554
  SKU: FSB-DVT2-C3
  Network adapter: Qualcomm Atheros - 1969:e0a1
  kernel-version: 5.11.0-27-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 13 08:47:33 2021
  InstallationDate: Installed on 2020-08-03 (374 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series

[Kevin Yeh]

Test results of nvidia-driver-460 are available at 
https://docs.google.com/spreadsheets/d/1OvcC1jFqSrm3fWTDh7HXIxy1uVdrRxfIyrMU8hYp5A4/edit#gid=312612113.
Test results of nvidia-driver-465 are available at 
https://docs.google.com/spreadsheets/d/1JCQCO92T_6WOVV3KfpRQjDFsWytVhbscny50bhrld8o/edit#gid=1527963777.
No regressions were found for both.

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

Title:
  Update the 465 and the 460 NVIDIA driver series

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Committed
Status in nvidia-settings source package in Hirsute:
  Fix Committed

Bug description:
  Update the 465 and the 460 NVIDIA driver series, and add support for
  Linux 5.13 to all the driver series.

  [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]

  == 460.84 ==

* New upstream release (LP: #1931131):
  - Added support for the following GPUs:
  GeForce RTX 3080 Ti
* debian/additional_card_ids:
  - Drop the additional IDs.
* debian/rules:
  - Skip lines that start with "#"
in debian/additional_card_ids.
* 

[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

[Kevin Blicharski]

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

Same issue. Ubuntu 20.04 on a Lenovo P50. Recently upgraded from 18.04
to 20.04 and would have thought this would make my system more stable,
not less.

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1930354] [NEW] package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error

[Kevin Remisoski]

Public bug reported:

Pretty sure this bug is more related to my kernel version, but there
doesn't seem to be any information about what the latest supported
kernel is.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1
Uname: Linux 5.12.8-051208-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun  1 00:17:36 2021
ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2021-06-01 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.3
SourcePackage: nvidia-graphics-drivers-460
Title: package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy

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

Title:
  package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to
  install/upgrade: installed nvidia-dkms-460 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  Pretty sure this bug is more related to my kernel version, but there
  doesn't seem to be any information about what the latest supported
  kernel is.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1
  Uname: Linux 5.12.8-051208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  1 00:17:36 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-06-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  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-460/+bug/1930354/+subscriptions

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

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

[Kevin Hester]

Though this problem also just appeared for me on ubuntu 20.10, when I
tried to upgrade my working mainline kernel from 5.11.16 to 5.11.17.

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

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

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

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

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

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

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

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

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11

[Kevin Yeh]

The link of Nvidia SRU testing results are following, no regressions
were found.

460.56: https://docs.google.com/spreadsheets/d/13fPRPMELE6Fal2xNE-
dTDZFJXJ0djH7W3tq0dJa0nB0/edit?usp=sharing

450.102.04: https://docs.google.com/spreadsheets/d
/17BZZANxJgWXXX0B6OnNY37NI7zMU6F-qTOQybA7Izbk/edit?usp=sharing

390.141: https://docs.google.com/spreadsheets/d/1c8ITvWs2zyBttt9m-
dLmHHYzpfQMbRoHxx0Re8-6Fzw/edit?usp=sharing

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

Title:
  Update the 460 driver, make switching between driver series more
  robust, and add support for Linux 5.11

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Update the 460 driver, make switching between driver series more
  robust (LP: #1915935), and add support for Linux 5.11

  [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]

  == 460 ==

    * New upstream release (LP: #1916908):
  - Added support for the following GPUs:
  GeForce RTX 3060
  - Fixed a bug with indexed ray payloads in Vulkan.
  - Fixed a bug where calls to vkCreateDevice could fail on Ampere
    GPUs when ray tracing extensions were enabled and the
    application was running within the Steam Linux Runtime.
  - Fixed a regression that could cause display corruption when
    using a scaled resolution after resuming from power management
    suspend.
    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
  - Advertise support for cuda-11.2-1.

  == 460-server ==

    * debian/templates/control.in:
  - Add missing conflict/replace/provide for libnvidia-common,
    nvidia-compute-utils, libnvidia-compute, and nvidia-headless
    (LP: #1915935).
    * debian/templates/dkms_nvidia.conf.in,
  

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Kevin Hester]

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=202541
   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/1667750

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 

[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Kevin Hester]

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=202541
   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/1749961

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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

[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Kevin Hester]

Btw - I just checked 20.10 even using kernel 5.11.8 (latest via
"mainline --install 5.11.8" and that current kernel shows the same
problem and error message "ERROR Transfer event TRB DMA ptr not part of
current TD ep_index 1"

Test hardware: Lenovo Thunderbolt Dock Gen 2" shows these same problems
with a high speed USB (Samsung SSD T7) disk on Ubuntu 20.10. No need to
involve the gige port to see the problem.

This is probably still a bug in the kernel but I'm not sure how you want
to report it upstream so it is linked here...

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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

[Kernel-packages] [Bug 1918024] [NEW] ZFS/fwupd infinite loop

[Kevin McMurtrie]

Public bug reported:

Infinite loop of ZFS/fwupd events slowing system to a crawl after
waking.

Mar  6 12:37:56 fuel zed: eid=3668 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:56 fuel zed: eid=3669 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:56 fuel zed: eid=3670 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:56 fuel zed: eid=3671 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:57 fuel zed: eid=3672 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:57 fuel zed: eid=3673 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:57 fuel zed: eid=3674 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:57 fuel zed: eid=3675 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
Mar  6 12:37:57 fuel fwupd[9611]: 20:37:57:0979 FuEngine ata failed 
to change udev device 
/sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb: 
cannot ensure ID: FuUdevDevice:
Mar  6 12:37:57 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0
Mar  6 12:37:57 fuel fwupd[9611]:   Serial:   WD-WCC7K5PENUZC
Mar  6 12:37:57 fuel fwupd[9611]:   Flags:none
Mar  6 12:37:57 fuel fwupd[9611]:   Version:  80.00A80
Mar  6 12:37:57 fuel fwupd[9611]: 20:37:57:0985 FuEngine ata failed 
to change udev device 
/sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb/sdb9:
 cannot ensure ID: FuUdevDevice:
Mar  6 12:37:57 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0
Mar  6 12:37:57 fuel fwupd[9611]:   Serial:   WD-WCC7K5PENUZC
Mar  6 12:37:57 fuel fwupd[9611]:   Flags:none
Mar  6 12:37:57 fuel fwupd[9611]:   Version:  80.00A80
Mar  6 12:37:58 fuel fwupd[9611]: 20:37:58:0070 FuEngine ata failed 
to change udev device 
/sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb/sdb1:
 cannot ensure ID: FuUdevDevice:
Mar  6 12:37:58 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0
Mar  6 12:37:58 fuel fwupd[9611]:   Serial:   WD-WCC7K5PENUZC
Mar  6 12:37:58 fuel fwupd[9611]:   Flags:none
Mar  6 12:37:58 fuel fwupd[9611]:   Version:  80.00A80

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-44-generic 5.8.0-44.50
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mcmurtri   8333 F pulseaudio
 /dev/snd/controlC0:  mcmurtri   8333 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sat Mar  6 12:38:40 2021
InstallationDate: Installed on 2018-10-28 (860 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash mitigations=off 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-44-generic N/A
 linux-backports-modules-5.8.0-44-generic  N/A
 linux-firmware1.190.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-12-14 (82 days ago)
dmi.bios.date: 03/13/2018
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F25b
dmi.board.asset.tag: Default string
dmi.board.name: X99P-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25b:bd03/13/2018:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug groovy

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

Title:
  ZFS/fwupd infinite loop

Status in linux package in Ubuntu:
  New

Bug description:
  Infinite loop of ZFS/fwupd events slowing system to a crawl after
  waking.

  Mar  6 12:37:56 fuel zed: eid=3668 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
  Mar  6 12:37:56 fuel zed: eid=3669 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
  Mar  6 12:37:56 fuel zed: eid=3670 class=config_sync 
pool_guid=0x2D095FFB2B65A8E6  
  Mar  

[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Kevin Hester]

I can confirm @lamalas "Lenovo Thunderbolt Dock Gen 2" shows these same
problems with a high speed USB (Samsung SSD T7) disk on Ubuntu 20.10. No
need to involve the gige port to see the problem.

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Kevin Yeh]

The link of Nvidia SRU testing result is following, no regression was found.
https://docs.google.com/spreadsheets/d/1-efzhthwiePkABHBgVGw8qBQwr8v0wznSEWcA52pjzs/edit#gid=1694297374

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

Title:
  Introduce the new NVIDIA 460-server series and update the 460 series

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Introduce the new NVIDIA 460-server series and update the 460 series.

  [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]

  == 460-server ==

    * Initial release:
  - Added support for the following GPUs:
  NVIDIA A40
  NVIDIA RTX A6000
  - Added support for CUDA 11.2.

  == 460 ==

    * New upstream release:
  - Added support for the following GPUs:
  GeForce RTX 3080 Laptop GPU
  GeForce RTX 3070 Laptop GPU
  GeForce RTX 3060 Laptop GPU
  GeForce GT 1010
  - Updated the NVIDIA driver to restore functionality of some
    features, including runtime power management, hotplugging
    audio-capable display devices, and S0ix-based system suspend,
    with recent kernels such as Linux 5.10.
  - Fixed a bug that caused bindless texture samplers to be
    incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS
    limit.
  - Fixed a bug that could cause the GPU to hang when attempting to
    perform link training on an HDMI 2.1 Fixed Rate Link (FRL)
    display, while the display is powered off.
  - Fixed a bug that could intermittently cause NvFBC applications
    to fail with the error message "Unable to send exported fds".

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

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

[Kernel-packages] [Bug 1833281] Re: System freeze when memory is put on SWAP in Linux >4.10.x

[Kevin Wortman]

I am experiencing this bug on a stock Dell Inspiron 5000 (5482) with 8
GB RAM and the factory SSD. It is completely debilitating. Having 1-2
completely unpredictable, 30-minute-plus, hard freezes per day is a
showstopper. I can't trust this environment for professional work, or
even to take notes in gedit during a phone call.

I've been an Ubuntu user and advocate at work and home for 10+ years,
but I guess I have to quit :(

I tried different flavors, and the bug manifested under all of them:
Ubuntu LTS 20.04, Ubuntu 20.10, Ubuntu MATE 20.10, and Debian 10.

Fedora 33 does not suffer from this bug, so I'm using that. I get
frequent "Gah! Your tab just crashed" errors in Firefox any time I have
more than about 5 tabs open. I conjecture there is some difference
between the Redhat-based and Debian-based kernels, that causes the
Redhat-based ones to kill a tab process in the circumstance that causes
the Debian-based ones to lock up. The Fedora experience is acceptable,
though it's still disappointing that Linux performance is has regressed
to be inadequate for basic web browsing.

Takeaway: Fedora seems to be an acceptable workaround for people
experiencing this bug.

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

Title:
  System freeze when memory is put on SWAP in Linux >4.10.x

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

Bug description:
  I'm reporting this since it's reproduceable the 70% of the time.
  Summary:

  In different circumstances, when the systems starts to swap out RAM
  memory, even small amounts, the system becomes completely unusuable
  and the screen freezes up, no mouse movement, no TTY access or SSH
  access can be made, only SYSRQ keys seem to do something (only reboot,
  so REISUB worked so far though, OOM is useless since the memory/swap
  is not even full)

  The I/O Disk led is stuck to 100% in ALL the following cases when this
  happens.

  So far:
  - This happens even when only ZRAM is enabled, and no swap partition is used.
  - Happens when ZSWAP is used with a swap partition
  - Happens also when a partition without zram or zswap is used
  - Maybe it's AMD specific? 

  However, I'm not experiencing this on my laptop using the same tests.

  My laptop is an Intel one, while my desktop is an AMD Ryzen platform.

  Here are the specs:
  CPU: AMD Ryzen 5 1600 no OC
  GPU: AMD RX 580 8GB
  SSD: Crucial MX500 500GB
  MOBO: MSI B350M Grenade
  RAM: 8GB HyperX Kingston 2667Mhz

  Ubuntu version: 18.04 LTS, backports repo enabled
  Kernel version: 4.18.0-18, official ubuntu repo
  Bios settings: Default

  Additional info: Maybe I'm not 100% sure, but I noticed when using the
  5.0.0-17 generic kernel, the lockups seem to still happen, but they
  recover eventually. Happened only a few times though...

  But will always be frozen for at least 30 seconds, differently from my
  intel laptop where those do occur.

  The SSD make is the same. I bought two of these, they got also the
  same amount of RAM.

  In my laptop those do not occur at all. Swapping memory even huge
  quantities like 1GB or more, do not produce any issues.

  Tests made:
  For testing this behaviour I tried:

  - Compiling the chromium-browser source code (takes up a lot of system
  RAM)

  - Used the "stress" command, using a specific amount of memory to
  decide how many it will be swapped, and here I noticed that even small
  quantities like a couple of megabytes will cause the system to freeze
  the 70% of the times

  Example: "stress --vm 1 --vm-bytes=7G"

  What should happen:
  I expect system slowdowns when swapping out memory since I do not have enough 
RAM, but unlikely when using Windows or my laptop with the same Linux version, 
not a completely unusuable environment. The swap partition is in both cases on 
an SSD.

  Reproduceability: 70% of the times

  Additional info again:
  I'm not sure this is due to any hardware failure, my SSD health is fine, as 
my CPU and RAM. As I said swapping in Windows works fine...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  haru   2076 F pulseaudio
   /dev/snd/controlC2:  haru   2076 F pulseaudio
   /dev/snd/controlC0:  haru   2076 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic 
root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   

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

[Kevin Tang]

System: HP Convertible x360 11-ab0XX
$ cat /sys/class/dmi/id/chassis_type
31

Keyboard was working in 5.4.0-42.
Broken with update to 5.4.0-54.
Still broken in 5.9.10.
Working in 5.4.75.

Is 5.9.10 missing the fix that was included in 5.4.75 for chassis_type
31?

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

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The laptop keyboard doesn't work at login or in the de. If I
  ctrl+alt+F3 from an external usb keyboard to a terminal the laptop
  keyboard works. An external usb keyboard works everywhere. The
  laptop's keyboard does work everywhere with the previous kernel
  5.4.0.42.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
  Uname: Linux 5.4.0-45-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Sep  3 03:09:49 2020
  InstallationDate: Installed on 2019-08-07 (392 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency 
root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-lowlatency N/A
   linux-backports-modules-5.4.0-45-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.57
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.sku: M0B61EA#ACQ
  dmi.product.version: 097710405F00010420180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series

[Kevin Yeh]

The link of test results is as follows.

https://docs.google.com/spreadsheets/d/1ga7U4PUHjV2TF8ihcsDaEUdoGp7M7Iz11zVs442ZARw/edit?usp=sharing

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

Title:
  Introduce the new NVIDIA 455 series

Status in linux package in Ubuntu:
  Confirmed
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Confirmed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-455 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Confirmed
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-455 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed
Status in linux-restricted-modules source package in Groovy:
  Confirmed
Status in nvidia-graphics-drivers-455 source package in Groovy:
  Fix Committed

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

    * New upstream release:
  - Added support for the following GPUs:
  GeForce RTX 3070
  - Added support for using an NVIDIA-driven display as a PRIME
    Display Offload sink with a PRIME Display Offload source driven
    by the xf86-video-intel driver.
  - Fixed a bug in a Vulkan barrier optimization that allowed some
    back-to-back copies to run unordered.
  - Fixed a performance regression in the NVIDIA X driver which
    affected some X11 RENDER extension use cases.
  - Added AMD Secure Memory Encryption compatibility.
    * debian/templates/control.in:
  - Set support level to NFB instead of Beta.
  - Add support for CUDA 11.

  Note: this will be the initial release for Bionic and Focal.

  
  Changelog entries for the linux-restricted-modules:

  UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel
  virtual package

  Make all the NVIDIA drivers, except for 390, provide the 
nvidia-prebuilt-kernel
  virtual package.

  This allows adding a generic dependency on the signed modules.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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

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

[Kevin K]

apport information

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

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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