date:20240228

For the slow boots, try experimenting with kernel parameters like
acpi_backlight=vendor and for more detailed info see
https://wiki.ubuntu.com/Kernel/Debugging/Backlight

For the failed boots I would also recommend trying the kernel parameter:
nvidia-drm.modeset=0

For both issues try the new experimental Nvidia driver version 550:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

So how can I fix it?

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11)
  00:1f.5 Serial bus controller: Intel Corporation Raptor Lake SPI (flash) 
Controller (rev 11)
  01:00.0

[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

** Tags added: flickerfreeboot

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

Title:
  Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

Status in gdm:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Confirmed
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Released
Status in linux package in Fedora:
  Fix Released

Bug description:
  [ Impact ]

  The fbdev subsystem has been deprecated for a long time. We should
  drop it in favour of using simpledrm with fbdev emulation layer.

  This requires Kernel config changes:

  FB_EFI=n
  FB_VESA=n

  fbcon will still require FB to be available, but will use the fbdev
  emulation layer

  [ Test Plan ]

  * Ensure that systems currently relying on fbdev (and therefore only
  allowing Xorg logins) such as some virtual machine types, boot with
  working Wayland support.

  [ Where Problems could occur ]

  * When this stack is enabled, it changes boot timing such that some drivers 
may take a longer time to boot and GDM may hang in a black screen (bug 2039757).
  * Race conditions could be exposed to DE environments
  * Software that expects to find DRM device at /dev/dri/card0 may have a 
problem.
  * Some older versions of NVIDIA driver might not work properly.

  [ Other Info ]

  * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385

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


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

[Kernel-packages] [Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages

2024-02-28 Thread Andrea Righi

I don't see these messages with the latest Noble using the kernel from
the proposed pocket (6.8.0-11-generic). Can you also give it a try (if
you can)?

Hopefully we'll be able to promote a 6.8 in release soon, we are
currently blocked by a glibc regression (that doesn't seem to be a
kernel regression). If we can unblock/hint this one (hopefully this
week, or worst case next week) we'll have a new 6.8 in release.

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

Title:
  dmesg spammed by virtui-fs and 9pnet-virtio messages

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu noble, as of 28 Feb 2024, on amd64, s390x, ppc64, seeing kernel
  messages after boot (running instances in a VM using virt-manager)

  uname -a
  Linux noble-amd64-efi 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 
30 10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  [   30.638354] virtio-fs: tag  not found
  [   30.642316] 9pnet_virtio: no channels available for device config
  [   35.897615] virtio-fs: tag  not found
  [   35.901568] 9pnet_virtio: no channels available for device config
  [   41.141860] virtio-fs: tag  not found
  [   41.145513] 9pnet_virtio: no channels available for device config
  [   46.382040] virtio-fs: tag  not found
  [   46.386141] 9pnet_virtio: no channels available for device config
  [   51.632229] virtio-fs: tag  not found
  [   51.635727] 9pnet_virtio: no channels available for device config

  These are annoying when logging in via the console.

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


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

[Kernel-packages] [Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

Gabriel help me find one X1C9. I will try to reproduce the issue after I
got it.

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

Title:
  Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When you connect the headset which is based on Bluetooth LE it
  connects and then almost immediately disconnects.  This does not
  happen when using the 6.5.0-1009-oem kernel  Can you poirt whatever
  changes to bluetooth from the oem kernel to the generic as the cutomer
  will not use the oem kernels

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.15.0.1053.49)

2024-02-28 Thread Ubuntu SRU Bot

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

systemd/249.11-0ubuntu3.12 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

2024-02-28 Thread Hui Wang

** Description changed:

- This is for tracking purpose
+ BugLink: https://bugs.launchpad.net/bugs/2055283
+ 
+ [Impact]
+ 
+ We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image
+ and booting up, the bluetooth couldn't work at all. Checking the dmesg,
+ the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi,
+ but there is no this firmware in the linux-firmware of Jammy, and I
+ also checked the Mantic and Noble, Mandic doesn't have this firmware too,
+ Noble already has the firmware since the upstream linux-firmware integrated
+ the intel/ibt-0180-4150.sfi last year.
+ 
+ 
+ [Fix]
+ 
+ Backport 4 commits from upstream linux-firmware, these 4 commits are all
+ on intel/ibt-0180-4150.sfi|ddc
+ 
+ 
+ [Test Case]
+ 
+ Put the firmware into the /lib/firmware/intel/, reboot the machine,
+ check dmesg, the bluetooth driver loads the firmware successfully,
+ 
+ run hciconfig, the hci0 shows up.
+ 
+ run checkbox testcase, it could pass.
+ [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]
+ 
+ 
+ [Where problems could occur]
+ 
+ Probably could make the Intel AX201 BT adapter couldn't work, but the 
possibility
+ is very low, we tested the firmware on different lenovo machines with the BT 
adapter
+ AX201, all worked well.

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

Title:
  Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress

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

  [Impact]

  We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image
  and booting up, the bluetooth couldn't work at all. Checking the dmesg,
  the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi,
  but there is no this firmware in the linux-firmware of Jammy, and I
  also checked the Mantic and Noble, Mandic doesn't have this firmware too,
  Noble already has the firmware since the upstream linux-firmware integrated
  the intel/ibt-0180-4150.sfi last year.

  
  [Fix]

  Backport 4 commits from upstream linux-firmware, these 4 commits are all
  on intel/ibt-0180-4150.sfi|ddc

  
  [Test Case]

  Put the firmware into the /lib/firmware/intel/, reboot the machine,
  check dmesg, the bluetooth driver loads the firmware successfully,

  run hciconfig, the hci0 shows up.

  run checkbox testcase, it could pass.
  [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]

  
  [Where problems could occur]

  Probably could make the Intel AX201 BT adapter couldn't work, but the 
possibility
  is very low, we tested the firmware on different lenovo machines with the BT 
adapter
  AX201, all worked well.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1108.104)

2024-02-28 Thread Ubuntu SRU Bot

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

dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
evdi/1.9.1-1ubuntu4~20.04.2 (amd64)
lttng-modules/2.12.5-1ubuntu2~20.04.5 (amd64)
oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4 (amd64)
rtl8821ce/5.5.2.1-0ubuntu4~20.04.5 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
virtualbox/6.1.50-dfsg-1~ubuntu1.20.04.1 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2052640] Re: New NVIDIA release 470.239.06

This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.239.06-0ubuntu1

---
nvidia-graphics-drivers-470-server (470.239.06-0ubuntu1) noble; urgency=medium

  * New upstream release (LP: #2052640)
  * Make ERD & UDA orig tarballs reproducible for same upstream releases
  * Make orig tarballs reproducible
  * Drop unused and obsolete patches

 -- Dimitri John Ledkov   Fri, 09 Feb 2024
11:49:19 +

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Noble)
   Status: In Progress => Fix Released

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

Title:
  New NVIDIA release 470.239.06

Status in fabric-manager-470 package in Ubuntu:
  In Progress
Status in libnvidia-nscq-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  In Progress
Status in libnvidia-nscq-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in fabric-manager-470 source package in Noble:
  In Progress
Status in libnvidia-nscq-470 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Noble:
  Fix Released

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.

  Note as this is a legacy driver, the QA team available hardware might
  be limited if not existent. Tests on GKE might be suitable, as they
  still default to 470 series.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

The only explanations I can see for the failed boots is:

Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(WW) NVIDIA(G0): Failed to set the display configuration
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(WW) NVIDIA(G0):  - Setting a mode on head 0 failed: Insufficient permissions
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(WW) NVIDIA(G0):  - Setting a mode on head 1 failed: Insufficient permissions
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(WW) NVIDIA(G0):  - Setting a mode on head 2 failed: Insufficient permissions
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(WW) NVIDIA(G0):  - Setting a mode on head 3 failed: Insufficient permissions
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(II) NVIDIA(GPU-0): Deleting GPU-0
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]: 
(II) Server terminated successfully (0). Closing log file.

The slow boots still seem to be the backlight issue in comment #10.

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: Incomplete => New

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Incomplete => New

** Changed in: nvidia-graphics-drivers-545 (Ubuntu)
   Status: Incomplete => New

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2

[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  Description of problem:

  Observed device_dax related probe errors in dmesg when HBM CPU is set
  to flat mode.  Duplicate device_dax ids were created and hence probing
  is failing.

  How reproducible:
  Frequently

  Version-Release
  Release:22.04.2, 22.10

  [Test Case]

  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.

  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.

  Expected results:
  Dummy/duplicate devices should not create.

  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/

  
  [Where problems could occur]

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2

  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].

  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"devdax" ---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    }
  ]
  root@ubuntu:/home/ubuntu# dmesg | grep -i error
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748902] device_dax: probe of dax3.0 failed with error -16

  After reconfig-device devdax to system-ram below are the results:
  ---
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
  {
    "chardev":"dax0.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":2,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
  {
    "chardev":"dax1.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":3,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax4.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax1.0",

[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Change in trace file leads to test timeout in ftrace tests on 5.15
  ARM64

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc,
  event-pid.tc in linux/tools/testing/selftests/ftrace will take too
  much time to run and consequently leads to test timeout.

  The culprit is the `cat` command on the changing trace file.

  [Fix]
  * 25b9513872 selftests/ftrace: Stop tracing while reading the trace
    file by default

  This patch can be cherry-picked into Jammy. I didn't see this issue in
  our 5.4 kernels. And it's already landed in newer kernels.

  [Test]
  On an ARM64 testing node, apply this patch to the kernel tree and run
  event-pid.tc test in linux/tools/testing/selftests/ftrace with:

    sudo ./ftracetest -vvv test.d/event/event-pid.tc

  The test should finish within a few minutes.

  [Regression Potential]
  Change limited to testing tools, it should not have any actual impact
  to kernel functions.

  == Original Bug Report ==
  First time seen this since ftrace refactor out from ubuntu_kernel_selftests 
to ubuntu-kselftests-ftrace

  Issue found on ARM64 nodes with both generic / generic-64k kernel.

  Partial test log:
   Running './ftracetest -vvv test.d/event/subsystem-enable.tc'
   === Ftrace unit tests ===
   
   [1] event tracing - enable/disable with event level files
   + [ 2 -eq 1 ]
   + [ -f set_event_pid ]
   + echo
   + [ -f set_ftrace_pid ]
   + echo
   + [ -f set_ftrace_notrace ]
   + echo
   + [ -f set_graph_function ]
   + echo
   + tee set_graph_function set_graph_notrace
   + [ -f stack_trace_filter ]
   + echo
   + [ -f kprobe_events ]
   + echo
   + [ -f uprobe_events ]
   + echo
   + [ -f synthetic_events ]
   + echo
   + [ -f snapshot ]
   + echo 0
   + clear_trace
   + echo
   + enable_tracing
   + echo 1
   + . 
/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc
   + echo sched:sched_switch
   + yield
   + ping 127.0.0.1 -c 1
   PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
   64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms

   --- 127.0.0.1 ping statistics ---
   1 packets transmitted, 1 received, 0% packet loss, time 0ms
   rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms
   + cat trace
   + grep sched_switch
   + wc -l
   Timer expired (600 sec.), nuking pid 20982

  From the code (tools/testing/selftests/ftrace/test.d/event/event-
  enable.tc) this test is trying to run:

  count=`cat trace | grep sched_switch | wc -l`

  This command caused the timeout as `cat trace` seems to be never
  ending.

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


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

[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System can't enter suspend on AHCI mode,
  the CPU FAN and System FAN is running, PSU LED is on.
  When fail to enter suspend, remove ODD, the system can successfully enter 
suspend again.

  [Fix]
  Enable LPM on Alder Lake-P AHCI.

  [Test Cases]
  1. enabled AHCI on target machine.
  2. boot with kernel applied fix.
  3. suspend then check slp_s0_residency_usec_cstate_show
  ~~~
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  4951200
  Package C2 : 63571033
  Package C3 : 6212
  Package C6 : 5633477
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 5255561
  u@ubuntu:~$ sudo rtcwake -m mem -s 10
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  12965280
  Package C2 : 75052691
  Package C3 : 46989
  Package C6 : 8108332
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 13628111
  ~~~

  [where the issue could happen]
  Medium, Intel promise there's no issue of ADL AHCI and
  they will take responsibility after regression.
  Intel also take LPM as POR so they will fix any issues.

  [Misc]
  Because the board_ahci_mobile is still not modified to board_ahci_low_power 
on Jammy,
  provide a single patch for Jammy.

  For generic J/M, passed the all arch compilations on cbd,
  Jammy,
  ~~~
  $ git push j_cbd
  Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ
  remote: * 0/1 workers busy, 0 builds queued
  remote: 2023-11-17 19:50:25  kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK
  remote: 2023-11-17 20:18:29  kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK
  remote: 2023-11-17 20:01:41  kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK
  remote: 2023-11-17 20:31:51  kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK
  remote: 2023-11-17 20:37:25  kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK
  remote: 

  To cbd.kernel:jammy.git
   * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next
  ~~~

  Lunar,
  $ git push l_cbd
  Enumerating objects: 9, done.
  Counting objects: 100% (9/9), done.
  Delta compression using up to 8 threads
  Compressing objects: 100% (5/5), done.
  Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done.
  Total 5 (delta 4), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-915de03d6ecf-V1nm
  remote: * 9/9 workers busy, 0 builds queued
  remote: 2023-11-20 16:00:11

[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  linux tools packages for derived kernels refuse to install
  simultaneously due to libcpupower name collision

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple kernel flavours are conflicting with each on .deb / file
  level via their tools packages

   * Resolve the conflicting private libcpupower.so by statically
  linking it into the only C binary that uses said library in the linux-
  tools

  [ Test Plan ]

   * co-install tools packages from multiple kernel flavours of the same
  major version and abi, it should be successful

  [ Where problems could occur ]

   * If one tries really hard to find the private location of
  libcpupower.so and dlopen it by ever changing abi name, that will not
  be possible, until the separate bug report is fixed to introduce the
  public stable libcpupower.so.1 which so far ubuntu has never yet
  provided.

  [ Other Info ]
   
   * original bug report

  Taking linux-kvm and linux-gcp for example:

  $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103384 2023-07-25 20:00 
./usr/lib/libcpupower.so.6.2.0-1011
  $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103392 2023-08-16 15:08 
./usr/lib/libcpupower.so.6.2.0-1011

  linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
  a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
  utilities, and yet files of the same full path cannot be installed
  from two distinct debian packages, which follows we won't be able to
  install two linux-tools packages of two different derived kernels on
  the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
  Uname: Linux 6.5.0-9004-generic x86_64
  NonfreeKernelModules: zfs wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicamo 6331 F wireplumber
   /dev/snd/controlC0:  vicamo 6331 F wireplumber
   /dev/snd/seq:vicamo 6315 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Sep 14 23:31:16 2023
  InstallationDate: Installed on 2022-04-10 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic 
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-generic N/A
   linux-backports-modules-6.5.0-9004-generic  N/A
   linux-firmware  20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version:

[Kernel-packages] [Bug 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better
  performance

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can 
only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 
6.2.0-1014-azure kernel in Ubuntu 22.04.

  After I pick up the upstream patch(es) to enable PCI relaxed ordering
  (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps.

  [Fix]

  [1]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02

  [2]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76

  [3]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2

  [4]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Mellanox connections could be corrupted or run slower.

  [Other Info]

  SF: #00370735

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


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

[Kernel-packages] [Bug 2041842] Re: Kernel doesn't compile with CONFIG_IMA

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Kernel doesn't compile with CONFIG_IMA

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Because of typo error in function declaration kernel doesn't compile
  with specific configuration

  Steps to reproduce:

  make defconfig
  ./scripts/config --file .config \
   -d SECURITY_SELINUX \
   -e IMA
  make olddefconfig
  grep -E "CONFIG_IMA=|CONFIG_IMA_LSM_RULES" .config
  make bzImage

  Grep should return "CONFIG_IMA=y" but not "CONFIG_IMA_LSM_RULES=y"

  Error:

  In file included from security/integrity/ima/ima_fs.c:25:
  security/integrity/ima/ima.h:440:41: error: unknown type name 'strcut'; did 
you mean 'struct'?
440 | static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 
field, u32 op,
| ^~
| struct
  make[3]: *** [scripts/Makefile.build:297: security/integrity/ima/ima_fs.o] 
Error 1
  make[2]: *** [scripts/Makefile.build:560: security/integrity/ima] Error 2
  make[1]: *** [scripts/Makefile.build:560: security/integrity] Error 2

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


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

[Kernel-packages] [Bug 2044192] Re: Patches needed for AmpereOne (arm64)

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Patches needed for AmpereOne (arm64)

Status in linux package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * Google requested patches for AmpereOne machine type

  [Fix]

  * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 GCP and Focal 5.4 GCP for now
  * Also submitting to Jammy 5.15 generic
  * Cherry-picks from upstream

  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the 
TVAL programming interface")
  012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
  30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to 
the core code")
  8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer 
programming over to CVAL")
  72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs 
callback ordering issue")
  ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from 
erratum function names")
  a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer 
programming over to CVAL")
  1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer 
register accessors to u64")
  d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read 
accessors")
  4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for 
unhandled register accesses")

  [Test Case]

  * Compile tested
  * Boot tested on GCP AmpereOne instance

  [Where things could go wrong]

  * Low chance of regression. Changes isolated to ARM timers.

  [Other Info]

  * SF #00372821

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


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

[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  AppArmor patch for mq-posix interface is missing in jammy

Status in linux package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  New

Bug description:
  [ Impact ]

  mq-posix snapd interface does not work on Ubuntu Core 22. It results
  in permission denied even all interfaces are connected.

  Our brandstore customer is using posix message queue for IPC between
  snaps. They added mq-posix interface and connected them properly but
  getting permission denied error.

  The AppArmor patch for posix message queue created for other customer
  did not land in the standard jammy kernel.

  Userspace support for AppArmor message queue handling is already
  present in Ubuntu Core 22, it is just missing from the kernel.

  [ Test Plan ]

   * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or 
Classic 22.04 with the standard kernel.
   * Example snaps for testing: 
https://code.launchpad.net/~itrue/+git/mqtest-provider and 
https://code.launchpad.net/~itrue/+git/mqtest-client

  [ Where problems could occur ]

   * The patches already exist for 5.15 and have been used on other
  private customer kernels and all kernels released after 22.04, so
  there is already a good track record for this patchset and it
  shouldn't create any issues.

  [ Other Info ]
   
   * This is a time-sensitive issue for a paying customer

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


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

[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Add ODM driver rtc-pcf85263

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

Bug description:
  From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:43:41 +0100
  Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver

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

  
  [ Impact ]
  rtc-pcf85263 driver needed for ODM partner

  [ Test Plan ]

  Load the driver setting the timestamp level to 0 (default to 1) :
  modprobe rtc-pcf85263 tsl=0

  export the rtc device:
  echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device

  RTC device should act as a standard RTC,
  hwclock -r -f /dev/rtc1 #for reading
  hwclock -w -f /dev/rtc1 #for writing

  This driver has anti-tampering function.
  Get the current tamper timestamp:
  cat /sys/class/rtc/rtc1/device/timestamp1

  unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the 
anti-tampering goes in open state.
  The timestamp should be updated to the current time.

  [ Where problems could occur ]

  Events could occur on the I2C bus communication.

  [ Other Info ]

  X-HWE-Bug: Bug #2046985

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


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

[Kernel-packages] [Bug 2042568] Re: Azure - Kernel crashes when removing gpu from pci

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.

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

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

** Tags added: kernel-spammed-jammy-linux-azure-fips-v2
verification-needed-jammy-linux-azure-fips

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

Title:
Azure - Kernel crashes when removing gpu from pci

Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure source package in Jammy:
Fix Released
Status in linux-azure source package in Lunar:
Fix Committed

Bug description:
[Description]

On a VM on Azure with a Tesla gpu it was noticed that when removing
the gpu from the pci the vm would crash. In case the nvidia drivers
are loaded, the machine won't crash. Instead the removing process will
hang and the machine will crash on reboot.

This is related to bug [1].
The bug reported in [1] regards another driver but the root cause is the same.
It is still investigated whether this is a bug in pci, or it is a bug of
various drivers on how they use pci.

For this case we have identified that removing commit [2] prevents the
kernel crashes.

Azure has requested to revert this commit, at least for the time being.
This commit is not in upstream, so it just need to be reverted from Ubuntu
kernels.

[Test Case]

On an Azure vm with a gpu :

# echo '1' > /sys/bus/pci/devices/0001:00:00.0/remove

where '0001:00:00.0' the pci address of the gpu.
The vm will crash.

[Where things could go wrong]

The commit to be reverted was included in a patchset to address lp
bugs https://bugs.launchpad.net/bugs/2023071 and
https://bugs.launchpad.net/bugs/2023594

However this commit just reduces boot time and removing shall not introduce
any regressions.
Side effects will be increase in the boot time.

[Other]

Only Ubuntu azure kernels are affected :

- Jammy 5.15
- Lunar 6.2

Focal is also affected since it's using 5.15 kernel.
This commit does not appear in Mantic 6.5 kernel.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=215515
[2]
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/jammy/commit/?h=Ubuntu-azure-5.15.0-1043.50=75af0c10b3703400890d314d1d91d25294234a81

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

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

[Kernel-packages] [Bug 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Azure: Deprecate Netvsc and implement MANA direct

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Committed
Status in linux-azure source package in Mantic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Microsoft has asked for the inclusion of 3 patches that deprecate the
  use of netvsc in favor of MANA direct.

  hv_netvsc: Mark VF as slave before exposing it to user-mode:
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8

  hv_netvsc: Fix race of register_netdevice_notifier and VF register:
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db

  hv_netvsc: fix race of netvsc and VF register_netdevice:
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837

  [Test Plan]

  Microsoft tested

  [Regression potential]

  User space that relies on netvsc will likely fail

  [Other Info]

  SF: #00374570

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


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

[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  [Debian] autoreconstruct - Do not generate chmod -x for deleted  files

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Debian source format 1.0 cannot remove files, create symlinks and change
  permission in the .diff.gz tarball. Therefore any changes in these 3
  categories cannot be represented without any tricks. To solve this,
  the `reconstruct` script is used every time we build the source package.
  The script is generated by `gen-auto-reconstruct` script during `cranky
  close`. It checks if there has been any changes in the 3 categories
  mentioned above between the upstream version (i.e v6.5) and the current one.
  The problem with the script is that in case a file A was removed since the
  upstream version was released, the `reconstruct` script will contains
  these commands in this exact order:
  rm -f A
  chmod -x A
  The second command will fail because file A does not exist anymore.
  This is solved by generating the `chmod +/-x` commands before `rm`.
  Which results in:
  chmod -x A
  rm -f A
  But because the reconstruct script is used during `clean` rule which is
  triggered pretty much during every cranky step which is run in the
  source repo, the first command will always file because file A is not
  present anymore in the tree. To solved this, any `chmod` change is added
  only if the file has not been deleted. Therefore if file A has been
  deleted, the `reconstruct` script will contain only this:
  rm -f A

  [Fix]
  Generate chmod commands first.
  And when generating chmod -x command, first check if the file has been 
deleted. If yes, no need for a chmod command.

  [Test Plan]
  It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and 
it reconstruct script looked correct.

  [Other Info]
  An example of this is #lp2038611 where `script/is_rust_module.sh` was 
removed, but we keep seeing
  "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory"
  because `rm -f` and `chmod -x` command were generated.

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


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

[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Add ODM driver gpio-m058ssan

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

Bug description:
  From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:45:07 +0100
  Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver

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

  [ Impact ]
  gpio-m058ssan driver needed for ODM partner

  [ Test Plan ]

  Connect the loopback GPIO connector to the ReliaCOR-40-13 system and
  connect the power supply of the GPIO connector.

  insert the "m058ssan" module:
  modprobe m058ssan

  create GPIOchip:
  echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device

  get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs ,
  the latter 8 are GPIs.

  Set and reset all of the GPOs one at a time and check that the
  corresponding GPI is set and reset accordingly.

  [ Where problems could occur ]

  Make sure that the power supply of the GPIO connector is correctly connected, 
otherwise the GPI will always report 0.
  Events could occur on the i2c bus communication that may cause miss-behavior 
of the driver.

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Add ODM driver f81604 usb-can

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

Bug description:
  From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:46:08 +0100
  Subject: [PATCH 3/3] Add f81604 usb-can kernel driver

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

  [ Impact ]
  f81604  driver needed for ODM partner

  [ Test Plan ]

  Install can-utils

  apt install can-utils

  insert the driver:
  modprobe f81604

  two socket can interfaces will be created, can0 and can1

  connect the DB9 cable and termination provided.
  Set up the two interfaces:
  ip link set can1 up type can bitrate 50
  ip link set can1 up type can bitrate 50
  candump can0

  In another shell run:
  cansend can1 123#DEADBEEF

  The first shell should report the received frame. Switch the
  interfaces in the last commands to test the frame flow in the other
  way around.

  [ Where problems could occur ]
  USB bus miss-behavior could cause issues to the driver.

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2046105] Re: Sound: Add rtl quirk of M90-Gen5

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

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


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

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

-- 
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 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-6.5 source package in Jammy:
  Fix Released
Status in linux-signed-hwe-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Fix Released
Status in linux-hwe-6.5 source package in Mantic:
  New
Status in linux-signed-hwe-6.5 source package in Mantic:
  New
Status in linux source package in Noble:
  Confirmed
Status in linux-hwe-6.5 source package in Noble:
  New
Status in linux-signed-hwe-6.5 source package in Noble:
  In Progress

Bug description:
  == SRU Justification ==
  [Impact]
  When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system
  resume, NULL pointer dereference occurs and the system stops working.

  [Fix]
  Rescan the bus in order to reprobe the device to avoid mac80211 layer
  gets messed up.

  [Test]
  With the fix in place, system keeps working after firmware issue occurs.
  Verified with thousand times of suspend.

  [Where problems could occur]
  If the firmware/hardware is really dead and beyond recoverable, the same
  process can be triggered again and again.

  == Original bug report ==
  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/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Hotplugging SCSI disk in QEMU VM fails

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
  Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest 
kernels >= 6.5 might be broken.
  The inconsistency suggests a potential race condition.

  [Fix]
  Reverting the two specified commits appears to restore reliability.
  ==
  cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only 
for non-root bus
  40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  Upstream has resolved the issue by reverting both commits through a commit 
placed below.
  ==
  5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  [Test Plan]
  1. Create a VM
  virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk 
path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio
  -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0
  2. Prepare two XMLs for adding two disk devices
  # cat disk_X.xml
  
    
    
    
  
  3. Hotplug disks and check for success
  virsh attach-device scsi_test disk_X.xml

  [Where problems could occur]
  The patch reverts two commits that previously addressed long-standing issues 
related to hotplugging devices with large BARs.
  While this reversion may reintroduce legacy issues, it does not introduce new 
problems.
  The associated risks are deemed low, making it worthwhile to address timing 
issues during the hotplugging of SCSI disks in QEMU VM.

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


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

[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B PC

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Add quirk to disable i915 fastboot on B PC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Some displays connect to the B PC device got the garbled display

  [Fix]
  The issue will disappear after commit 
5ac860cc52540df8bca27e0bb25b6744df67e8f0,
  but these patches cannot be backported from 5.19 to 5.15. So add quirk
  to force disable the i915 fastboot on the device to fix the abnormal display

  [Test Case]
  1. Connect the display and power on the B PC device
  2. Check the display for boot up

  [Where problems could occur]
  Quirk only on the B PCs. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2052453] Re: Azure: Fix regression introduced in LP: #2045069

This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 
verification-needed-jammy-linux-azure-fips

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

Title:
  Azure: Fix regression introduced in LP: #2045069

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Mantic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Microsoft requested the addition of 3 patches in LP: #2045069. A
  regression was discovered in Focal.

  [Fix]

  hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed

  hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove

  [Test Case]

  Microsoft tested

  [Regression Potential]

  hv_netvsc could still have a modprobe race.

  [Other Info]

  SF: #00374570

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


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

[Kernel-packages] [Bug 2055147] Re: Kernel upgrade to 6.5.0-21-generic fails to boot

2024-02-28 Thread Matthew Ruffell

Hi Sly,

Your evdi kernel module for DisplayLink docks failed to compile. It
likely couldn't generate your initramfs, leaving your 6.5.0-21-generic
not able to boot.

Your logs say its trying to build version 1.11.0:

ERROR (dkms apport): binary package for evdi: 1.11.0 not found
Error! Bad return status for module build on kernel: 6.5.0-21-generic (x86_64)
Consult /var/lib/dkms/evdi/1.11.0/build/make.log for more information.

This is a bit old and outdated. You can re-install the DisplayLink
drivers from the upstream source, that has a newer version of evdi:

https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu

That will probably remove the old evdi and install a newer one.

Alternatively, you can remove the old evdi dkms entry and install evdi-
dkms from the Ubuntu repositories which has a evdi compatible with
6.5.0-21-generic.

DisplayLink support is kinda bad on Ubuntu, but its what we must do to
have working displays with our docks.

Thanks,
Matthew

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

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

Title:
  Kernel upgrade to 6.5.0-21-generic fails to boot

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After automatic update to kernel 6.5.0-21-generic my laptop fails to
  complete booting with a kernel panic. Safe mode did not work. Booting
  to previous kernel 6.5.0-17-generic is fine.

  Errors during failed boot include:
  ```
  VFS Cannot open root device /dev/mapper/vgubuntu-root or unknown-block(0.0) 
error -6
  Please append a correct root= boot option
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0.0)

  ```

  Trying clean up, I see the following error with the kernel
  installation:

  ```
  sly@sigil:~$ sudo apt-get autoremove
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 6 not to upgrade.
  3 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up linux-headers-6.5.0-21-generic (6.5.0-21.21) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.5.0-21-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j16 KERNELRELEASE=6.5.0-21-generic all 
INCLUDEDIR=/lib/modules/6.5.0-21-generic/build/include 
KVERSION=6.5.0-21-generic DKMS_BUILD=1...(bad exit status: 2)
  ERROR (dkms apport): binary package for evdi: 1.11.0 not found
  Error! Bad return status for module build on kernel: 6.5.0-21-generic (x86_64)
  Consult /var/lib/dkms/evdi/1.11.0/build/make.log for more information.
  dkms autoinstall on 6.5.0-21-generic/x86_64 succeeded for nvidia
  dkms autoinstall on 6.5.0-21-generic/x86_64 failed for evdi(10)
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
   * dkms: autoinstall for kernel 6.5.0-21-generic
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.5.0-21-generic (--configure):
   installed linux-headers-6.5.0-21-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.5.0-21-generic; however:
Package linux-headers-6.5.0-21-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.
dpkg: dependency problems prevent 
configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.5.0.21.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for linux-image-6.5.0-21-generic (6.5.0-21.21) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.5.0-21-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j16 KERNELRELEASE=6.5.0-21-generic all

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2024-02-28 Thread Daniel Tang

@arman-nm I converted your gist into a bash script:
https://askubuntu.com/a/1506007/1004020

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer

[Kernel-packages] [Bug 2054571] Re: New NVIDIA release 535.161.07

This bug was fixed in the package fabric-manager-535 -
535.161.07-0ubuntu1

---
fabric-manager-535 (535.161.07-0ubuntu1) noble; urgency=medium

  * New upstream release (LP: #2054571)

 -- Dimitri John Ledkov   Thu, 22 Feb 2024
18:31:23 +

** Changed in: fabric-manager-535 (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New NVIDIA release 535.161.07

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  In Progress
Status in fabric-manager-535 source package in Bionic:
  In Progress
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  In Progress

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.

  Note as this is a legacy driver, the QA team available hardware might
  be limited if not existent. Tests on GKE might be suitable, as they
  still default to 470 series.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2024-02-28 Thread Daniel Tang

Is there any progress upstreaming this patch?

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06

[Kernel-packages] [Bug 2052640] Re: New NVIDIA release 470.239.06

This bug was fixed in the package libnvidia-nscq-470 -
470.239.06-0ubuntu1

---
libnvidia-nscq-470 (470.239.06-0ubuntu1) noble; urgency=medium

  * New upstream release (LP: #2052640)

 -- Dimitri John Ledkov   Wed, 21 Feb 2024
09:12:56 +

** Changed in: libnvidia-nscq-470 (Ubuntu Noble)
   Status: In Progress => Fix Released

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

Title:
  New NVIDIA release 470.239.06

Status in fabric-manager-470 package in Ubuntu:
  In Progress
Status in libnvidia-nscq-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in fabric-manager-470 source package in Bionic:
  In Progress
Status in libnvidia-nscq-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in fabric-manager-470 source package in Noble:
  In Progress
Status in libnvidia-nscq-470 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Noble:
  In Progress

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.

  Note as this is a legacy driver, the QA team available hardware might
  be limited if not existent. Tests on GKE might be suitable, as they
  still default to 470 series.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2054571] Re: New NVIDIA release 535.161.07

This bug was fixed in the package libnvidia-nscq-535 -
535.161.07-0ubuntu1

---
libnvidia-nscq-535 (535.161.07-0ubuntu1) noble; urgency=medium

  * New upstream release (LP: #2054571)

 -- Dimitri John Ledkov   Thu, 22 Feb 2024
18:47:08 +

** Changed in: libnvidia-nscq-535 (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New NVIDIA release 535.161.07

Status in fabric-manager-535 package in Ubuntu:
  New
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  In Progress
Status in fabric-manager-535 source package in Bionic:
  In Progress
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  New
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  In Progress

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.

  Note as this is a legacy driver, the QA team available hardware might
  be limited if not existent. Tests on GKE might be suitable, as they
  still default to 470 series.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2024-02-28 Thread FL140

Sorry hedrick if a left a wrong impression. Looks, like my comment was
not clear enough, I was recommending the 2.2.2 version for systems which
came with a 2.2.x package, e.g. 23.10 (mantic). There the bugs started
to make real problems (happening much more often) because a bunch of
things came together (IIRC the enabled block cloning feature, new
packages of tools like cp which used the new features, etc.) and could
be triggered much easier. I wasn't following older branches too close,
so no recommendations on those from my side, but IIRC the origin of the
"clone feature bug" was much much older.

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Jammy:
  Fix Committed
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  Fix Released
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

   * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
 only makes it stronger and not weaker, thus if it were incorrect, likely
 only performance would be impacted (and it is unlikely to be incorrect
 given upstream reviews and attention to data corruption issues; also,
 there are no additional changes to that function upstream)

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2024-02-28 Thread Charles Hedrick

Since I was just referenced, note that I wouldn't favor putting 2.2 into
Jammy. I would, however, prefer to see the latest 2.1.x.

2.2 is still seeing a substantial number of bug fixes. It will probably
be ok by the release date of 24.04, but I still wouldn't change major
versions for Jammy.

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Jammy:
  Fix Committed
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  Fix Released
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

   * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
 only makes it stronger and not weaker, thus if it were incorrect, likely
 only performance would be impacted (and it is unlikely to be incorrect
 given upstream reviews and attention to data corruption issues; also,
 there are no additional changes to that function upstream)

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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


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

[Kernel-packages] [Bug 2055310] [NEW] dmesg spammed by virtui-fs and 9pnet-virtio messages

2024-02-28 Thread Colin Ian King

Public bug reported:

Ubuntu noble, as of 28 Feb 2024, on amd64, s390x, ppc64, seeing kernel
messages after boot (running instances in a VM using virt-manager)

uname -a
Linux noble-amd64-efi 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 
30 10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

[   30.638354] virtio-fs: tag  not found
[   30.642316] 9pnet_virtio: no channels available for device config
[   35.897615] virtio-fs: tag  not found
[   35.901568] 9pnet_virtio: no channels available for device config
[   41.141860] virtio-fs: tag  not found
[   41.145513] 9pnet_virtio: no channels available for device config
[   46.382040] virtio-fs: tag  not found
[   46.386141] 9pnet_virtio: no channels available for device config
[   51.632229] virtio-fs: tag  not found
[   51.635727] 9pnet_virtio: no channels available for device config

These are annoying when logging in via the console.

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

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

** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-24.04-beta

** Description changed:

  Ubuntu noble, as of 28 Feb 2024, on amd64, s390x, ppc64, seeing kernel
- messages after boot:
+ messages after boot (running instances in a VM using virt-manager)
  
  uname -a
  Linux noble-amd64-efi 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 
30 10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
- 
  
  [   30.638354] virtio-fs: tag  not found
  [   30.642316] 9pnet_virtio: no channels available for device config
  [   35.897615] virtio-fs: tag  not found
  [   35.901568] 9pnet_virtio: no channels available for device config
  [   41.141860] virtio-fs: tag  not found
  [   41.145513] 9pnet_virtio: no channels available for device config
  [   46.382040] virtio-fs: tag  not found
  [   46.386141] 9pnet_virtio: no channels available for device config
  [   51.632229] virtio-fs: tag  not found
  [   51.635727] 9pnet_virtio: no channels available for device config
  
  These are annoying when logging in via the console.

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

Title:
  dmesg spammed by virtui-fs and 9pnet-virtio messages

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu noble, as of 28 Feb 2024, on amd64, s390x, ppc64, seeing kernel
  messages after boot (running instances in a VM using virt-manager)

  uname -a
  Linux noble-amd64-efi 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 
30 10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  [   30.638354] virtio-fs: tag  not found
  [   30.642316] 9pnet_virtio: no channels available for device config
  [   35.897615] virtio-fs: tag  not found
  [   35.901568] 9pnet_virtio: no channels available for device config
  [   41.141860] virtio-fs: tag  not found
  [   41.145513] 9pnet_virtio: no channels available for device config
  [   46.382040] virtio-fs: tag  not found
  [   46.386141] 9pnet_virtio: no channels available for device config
  [   51.632229] virtio-fs: tag  not found
  [   51.635727] 9pnet_virtio: no channels available for device config

  These are annoying when logging in via the console.

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


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

[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load

2024-02-28 Thread Colin Ian King

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  OpenZFS writing stalls, under load

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry
  Pi 8GB. ZFS deduplication, and LZJB compression is enabled.

  This issue seems to occur, intermittently, after some time (happens
  with both SMB access, via Samba, and when interacting with the system,
  via SSH), and never previously occurred, until a few months ago, and I
  sometimes have to force a reboot of the system (at the cost of some
  data loss), in order to use it again.

  The "dmesg" log reports:

  [25375.911590] z_wr_iss_h  D0  2161  2 0x0028
  [25375.911606] Call trace:
  [25375.911627]  __switch_to+0x104/0x170
  [25375.911639]  __schedule+0x30c/0x7c0
  [25375.911647]  schedule+0x3c/0xb8
  [25375.911655]  io_schedule+0x20/0x58
  [25375.911668]  rq_qos_wait+0x100/0x178
  [25375.911677]  wbt_wait+0xb4/0xf0
  [25375.911687]  __rq_qos_throttle+0x38/0x50
  [25375.911700]  blk_mq_make_request+0x128/0x610
  [25375.911712]  generic_make_request+0xb4/0x2d8
  [25375.911722]  submit_bio+0x48/0x218
  [25375.911960]  vdev_disk_io_start+0x670/0x9f8 [zfs]
  [25375.912181]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
  [25375.912400]  zio_nowait+0xd4/0x170 [zfs]
  [25375.912617]  vdev_mirror_io_start+0xa8/0x1b0 [zfs]
  [25375.912839]  zio_vdev_io_start+0x248/0x2b8 [zfs]
  [25375.913057]  zio_execute+0xac/0x110 [zfs]
  [25375.913096]  taskq_thread+0x2f8/0x570 [spl]
  [25375.913108]  kthread+0xfc/0x128
  [25375.913119]  ret_from_fork+0x10/0x1c
  [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds.
  [25375.919916]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.934835] txg_syncD0  2333  2 0x0028
  [25375.934850] Call trace:
  [25375.934869]  __switch_to+0x104/0x170
  [25375.934879]  __schedule+0x30c/0x7c0
  [25375.934887]  schedule+0x3c/0xb8
  [25375.934899]  schedule_timeout+0x9c/0x190
  [25375.934908]  io_schedule_timeout+0x28/0x48
  [25375.934946]  __cv_timedwait_common+0x1a8/0x1f8 [spl]
  [25375.934982]  __cv_timedwait_io+0x3c/0x50 [spl]
  [25375.935205]  zio_wait+0x130/0x2a0 [zfs]
  [25375.935423]  dsl_pool_sync+0x3fc/0x498 [zfs]
  [25375.935650]  spa_sync+0x538/0xe68 [zfs]
  [25375.935867]  txg_sync_thread+0x2c0/0x468 [zfs]
  [25375.935911]  thread_generic_wrapper+0x74/0xa0 [spl]
  [25375.935924]  kthread+0xfc/0x128
  [25375.935935]  ret_from_fork+0x10/0x1c
  [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds.
  [25375.942780]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.957702] zbackup D0 75339   5499 0x
  [25375.957716] Call trace:
  [25375.957732]  __switch_to+0x104/0x170
  [25375.957742]  __schedule+0x30c/0x7c0
  [25375.957750]  schedule+0x3c/0xb8
  [25375.957789]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.957823]  __cv_wait+0x30/0x40 [spl]
  [25375.958045]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.958263]  zil_commit+0x48/0x70 [zfs]
  [25375.958481]  zfs_create+0x544/0x7d0 [zfs]
  [25375.958698]  zpl_create+0xb8/0x178 [zfs]
  [25375.958711]  lookup_open+0x4ec/0x6a8
  [25375.958721]  do_last+0x260/0x8c0
  [25375.958730]  path_openat+0x84/0x258
  [25375.958739]  do_filp_open+0x84/0x108
  [25375.958752]  do_sys_open+0x180/0x2b0
  [25375.958763]  __arm64_sys_openat+0x2c/0x38
  [25375.958773]  el0_svc_common.constprop.0+0x80/0x218
  [25375.958781]  el0_svc_handler+0x34/0xa0
  [25375.958791]  el0_svc+0x10/0x2cc
  [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds.
  [25375.965564]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.980479] zbackup D0 95187   5499 0x
  [25375.980493] Call trace:
  [25375.980514]  __switch_to+0x104/0x170
  [25375.980525]  __schedule+0x30c/0x7c0
  [25375.980536]  schedule+0x3c/0xb8
  [25375.980578]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.980612]  __cv_wait+0x30/0x40 [spl]
  [25375.980834]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.981052]  zil_commit+0x48/0x70 [zfs]
  [25375.981280]  zfs_write+0xa3c/0xb90 [zfs]
  [25375.981498]  zpl_write_common_iovec+0xac/0x120 [zfs]
  [25375.981726]  zpl_iter_write+0xe4/0x150 [zfs]
  [25375.981766]  new_sync_write+0x100/0x1a8
  [25375.981776]  __vfs_write+0x74/0x90
  [25375.981784]  vfs_write+0xe4/0x1c8
  [25375.981794]  ksys_write+0x78/0x100
  [25375.981803]

Re: [Kernel-packages] [Bug 2055162] Re: linux-headers package not being pulled in with linux-image-generic

2024-02-28 Thread Walter Tautz

I had removed the linux-generic package in the past since, presumably, it
is "optional". I have made a point of reinstalling it. Hopefully this will
correct the issue where
I had to install the correct header package AFTER the kernel package had
been updated. Unfortunately this causes the nvidia kernel module to be not
available which,
of course, prevents gnome from launching. I would suggest that you find a
way to force the linux-generic package to be required and warn people that
removing it
will remove it's dependencies also. As soon as the header package was
installed dkms immediately started building and the desktop started.

==
apt show linux-generic
Package: linux-generic
Version: 5.15.0.97.92
Priority: optional
Section: kernel
Source: linux-meta
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 21.5 kB
Provides: kernel-testing--linux--full--generic,
kernel-testing--linux--full--preferred
Depends: linux-image-generic (= 5.15.0.97.92), linux-headers-generic (=
5.15.0.97.92)
Download-Size: 1,696 B
APT-Manual-Installed: yes
APT-Sources: http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
Description: Complete Generic Linux kernel and headers
 This package will always depend on the latest complete generic Linux kernel
 and headers.

--
 Roger Federer Fanatic Extraordinaire :-)

On Wed, 28 Feb 2024 at 03:35, Juerg Haefliger <2055...@bugs.launchpad.net>
wrote:

> > does not pull in the correct linux-header package
>
> What is installed that you think is wrong? Can you post the relevant apt
> logs (/var/log/apt/{history,term}.log*)?
>
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2055162
>
> Title:
>   linux-headers package not being pulled in with linux-image-generic
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   linux-image-5.15.0-97-generic definitely exists in Ubuntu and it does
>   not pull in the correct linux-header package which is required to
>   rebuilt nvidia kernel modules.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136
>   Uname: Linux 5.15.0-97-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp
> zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: GNOME
>   Date: Tue Feb 27 08:29:48 2024
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>   InstallationDate: Installed on 2023-06-16 (256 days ago)
>   InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
> (20230223)
>   ProcEnviron:
>LANGUAGE=en_CA:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ubiquity
>   Symptom: installation
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055162/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> status=Incomplete; importance=Undecided; assignee=None;
> Launchpad-Bug-Tags: amd64 apport-bug jammy ubiquity-22.04.19
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: juergh vorlon wtautz
> Launchpad-Bug-Reporter: Walter Tautz (wtautz)
> Launchpad-Bug-Modifier: Juerg Haefliger (juergh)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: wtautz
>
>

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

Title:
  linux-headers package not being pulled in with linux-image-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  linux-image-5.15.0-97-generic definitely exists in Ubuntu and it does
  not pull in the correct linux-header package which is required to
  rebuilt nvidia kernel modules.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136
  Uname: Linux 5.15.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Feb 27 08:29:48 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2023-06-16 (256 days ago)

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "failboot case#7"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2055153/+attachment/5750187/+files/failedboot6.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "slowboot case#7"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750185/+files/slowboot6.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "slowboot case#8"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750186/+files/slowboot7.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "slowboot case#6"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750184/+files/slowboot5.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "slowboot case#5"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750183/+files/slowboot4.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "failboot case#6"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750182/+files/failedboot5.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "failboot case#5"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750179/+files/failedboot4.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

** Attachment added: "failboot case#4"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750178/+files/failedboot3.txt

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus:

[Kernel-packages] [Bug 2055283] [NEW] Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

2024-02-28 Thread Hui Wang

Public bug reported:

This is for tracking purpose

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

** Affects: linux-firmware (Ubuntu Jammy)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: linux-firmware (Ubuntu Mantic)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress


** Tags: oem-priority originate-from-2054554 sutton

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

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

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

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

** Changed in: linux-firmware (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: linux-firmware (Ubuntu Mantic)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

** Tags added: oem-priority originate-from-2054554 sutton

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

Title:
  Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Mantic:
  In Progress

Bug description:
  This is for tracking purpose

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


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

[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

2024-02-28 Thread Georgia Garcia

The mqueue patches are present in linux-nvidia-tegra: commits
6e7ff802c7b10 and b4ebbcfebd4d3

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

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

Title:
  AppArmor patch for mq-posix interface is missing in jammy

Status in linux package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  New

Bug description:
  [ Impact ]

  mq-posix snapd interface does not work on Ubuntu Core 22. It results
  in permission denied even all interfaces are connected.

  Our brandstore customer is using posix message queue for IPC between
  snaps. They added mq-posix interface and connected them properly but
  getting permission denied error.

  The AppArmor patch for posix message queue created for other customer
  did not land in the standard jammy kernel.

  Userspace support for AppArmor message queue handling is already
  present in Ubuntu Core 22, it is just missing from the kernel.

  [ Test Plan ]

   * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or 
Classic 22.04 with the standard kernel.
   * Example snaps for testing: 
https://code.launchpad.net/~itrue/+git/mqtest-provider and 
https://code.launchpad.net/~itrue/+git/mqtest-client

  [ Where problems could occur ]

   * The patches already exist for 5.15 and have been used on other
  private customer kernels and all kernels released after 22.04, so
  there is already a good track record for this patchset and it
  shouldn't create any issues.

  [ Other Info ]
   
   * This is a time-sensitive issue for a paying customer

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


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

[Kernel-packages] [Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

@David,

Could you provide the dmesg of 6.5 generic kernel after reproduced the
issue?

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

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

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

Title:
  Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When you connect the headset which is based on Bluetooth LE it
  connects and then almost immediately disconnects.  This does not
  happen when using the 6.5.0-1009-oem kernel  Can you poirt whatever
  changes to bluetooth from the oem kernel to the generic as the cutomer
  will not use the oem kernels

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


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

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

I tried to run the command

ubuntu-bug /var/crash/YOURFILE.crash

as you proposed but it is not working.
It shows 'The application Files has closed unexpectedly'

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus: Intel

[Kernel-packages] [Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

Ubuntu Jammy 6.5 kernel is located in:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy 
hwe-6.5-next

Ubuntu Jammy oem kernel is located in:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/jammy 
oem-6.5-next

the only diff from Ubuntu 6.5.0-17 to the kernel oem-6.5.0-1009 is following:
git diff Ubuntu-6.5.0-17.17..Ubuntu-oem-6.5-6.5.0-1009.10  drivers/bluetooth/
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index cc1a1315e478..b99befd9d1f5 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -631,24 +631,9 @@ static const struct usb_device_id blacklist_table[] = {
{ USB_DEVICE(0x0489, 0xe0e4), .driver_info = BTUSB_MEDIATEK |
 BTUSB_WIDEBAND_SPEECH |
 BTUSB_VALID_LE_STATES },
-   { USB_DEVICE(0x0489, 0xe0f1), .driver_info = BTUSB_MEDIATEK |
-BTUSB_WIDEBAND_SPEECH |
-BTUSB_VALID_LE_STATES },
{ USB_DEVICE(0x0489, 0xe0f2), .driver_info = BTUSB_MEDIATEK |
 BTUSB_WIDEBAND_SPEECH |
 BTUSB_VALID_LE_STATES },
-   { USB_DEVICE(0x0489, 0xe0f5), .driver_info = BTUSB_MEDIATEK |
-BTUSB_WIDEBAND_SPEECH |
-BTUSB_VALID_LE_STATES },
-   { USB_DEVICE(0x0489, 0xe0f6), .driver_info = BTUSB_MEDIATEK |
-BTUSB_WIDEBAND_SPEECH |
-BTUSB_VALID_LE_STATES },
-   { USB_DEVICE(0x0489, 0xe102), .driver_info = BTUSB_MEDIATEK |
-BTUSB_WIDEBAND_SPEECH |
-BTUSB_VALID_LE_STATES },
-   { USB_DEVICE(0x04ca, 0x3804), .driver_info = BTUSB_MEDIATEK |
-BTUSB_WIDEBAND_SPEECH |
-BTUSB_VALID_LE_STATES },
 
/* Additional Realtek 8723AE Bluetooth devices */
{ USB_DEVICE(0x0930, 0x021d), .driver_info = BTUSB_REALTEK },

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

Title:
  Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

Status in linux package in Ubuntu:
  New

Bug description:
  When you connect the headset which is based on Bluetooth LE it
  connects and then almost immediately disconnects.  This does not
  happen when using the 6.5.0-1009-oem kernel  Can you poirt whatever
  changes to bluetooth from the oem kernel to the generic as the cutomer
  will not use the oem kernels

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


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

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

Enabled debug in /etc/gdm3/custom.conf
I will collect more failed logs and upload here. Thanks! 

** Attachment removed: "_usr_bin_nautilus.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2055153/+attachment/5750086/+files/_usr_bin_nautilus.1000.crash

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device

[Kernel-packages] [Bug 2049938] Re: Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

** Changed in: linux (Ubuntu)
 Assignee: The Sutton Team (sutton-team) => AaronMa (mapengyu)

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

Title:
  Bang & Olufsen Cisco 980 loses connection on 6.5 generic kernel

Status in linux package in Ubuntu:
  New

Bug description:
  When you connect the headset which is based on Bluetooth LE it
  connects and then almost immediately disconnects.  This does not
  happen when using the 6.5.0-1009-oem kernel  Can you poirt whatever
  changes to bluetooth from the oem kernel to the generic as the cutomer
  will not use the oem kernels

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


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

[Kernel-packages] [Bug 2049838] Re: Mute/mic LEDs no function on HP ZBook

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  Mute/mic LEDs no function on HP ZBook

Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  The mute LEDS are not work properly on some newer HP ZBooks.

  [Fix]
  It needs the specific quirk for the hardware layout. Add it accordingly. 

  [Test]
  Install the patched kernel and click the mute button. Confirm that the LED on 
the mute key turns on an off according to mute status.

  [Where problems could occur]
  This quirk only works if design of the board w.r.t. the same subsystem ID is 
unchanged. Otherwise the quirk will not work (the mute LEDs won't function 
normally).

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


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

[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device

This bug is awaiting verification that the linux-aws-
fips/5.15.0-1055.60+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
'verification-done-jammy-linux-aws-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-aws-fips' to
'verification-failed-jammy-linux-aws-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-aws-fips-v2 
verification-needed-jammy-linux-aws-fips

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

Title:
  partproke is broken on empty loopback device

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


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

[Kernel-packages] [Bug 2051846] Re: Mute/mic LEDs no function on HP ZBook Power

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  Mute/mic LEDs no function on HP ZBook Power

Status in OEM Priority Project:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP ZBook Power

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

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

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

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


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

[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

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

  Currently this patch is in the linux-next, and will be in the
  mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
  kernel, Noble kernel will have this patch automatically.

  [Impact]
  In the gnome audio setting, if we adjust balancing setting, it doesn't
  work at all on a Dell machine with cirrus codec, that is because with
  the current driver, the exported amixer controls can't be handled by
  pulseaudio.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  Booted with the patched kernel, move the bar to the left or right to
  adjust the balance, we could hear the sound from left channel or right
  channel accordingly.

  [Where problems could occur]
  This change will not create "Master Volume" amixer controls, probably
  will make the audio control malfunction, that is we couldn't control
  playback or capture volume correctly, but this regression possibility
  is very low, we already tested the patch on the machines with cirrus
  codec, they all worked well as before.

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


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

[Kernel-packages] [Bug 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  black screen when wake up from s3 with AMD W7600 gfx

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H 
monitor

  [Fix]
  Mario points out the commit in 6.7 may help
  3b401e30c249 drm/ttm: Reorder sys manager cleanup step

  [Test]
  1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS.
  2. Boot OS, put SUT to suspend.
  3. Wake up the System from suspend.
  4. Right away reboot the system from Ubuntu OS.
  5. Put SUT to suspend and wake up the system.
  6. After wake up Suspend, SUT should not be black screen.
  7. Repetition Step 2~6 30 cycles

  [Where problems could occur]
  Handling the system memory manager after the workqueue is destroyed prevents 
from the pointer beeing used after free. Should be pretty safe to include it.

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


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

[Kernel-packages] [Bug 2051334] Re: There is sound from the speakers and headphones at the same time on one dell platform

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

Title:
  There is sound from the speakers and headphones at the same time on
  one dell platform

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  After headphone is plugged, the sound plays from both headphone and speaker.

  [Fix]
  Cirrus provides a fix for this issue and currently, the patch is in sound 
subsystem tree
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=fcfc9f711d1e2fc7876ac12b1b16c509404b9625

  [Verify]
  Plugin headphone and play sounds, the sound should be from headphone only.

  [Where problems could occur]
  The fix is only for 2 specific models, and has been verfied.

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


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

[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  Sound: Add rtl quirk of M70-Gen5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

  This commit is merged by stable updates in noble kernel,
  5.15 doesn't support this platform,
  SRU for mantic and oem-6.5.

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


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

[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1015.16

---
linux-oem-6.5 (6.5.0-1015.16) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1015.16 -proposed tracker (LP: #2052289)

  * Mute/mic LEDs no function on HP ZBook Power (LP: #2051846)
- ALSA: hda/realtek: fix mute/micmute LEDs for HP ZBook Power

  * Sound: Add rtl quirk of M70-Gen5 (LP: #2051947)
- ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5

  * Fix spurious wakeup caused by Cirque touchpad (LP: #2051896)
- HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk
- HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines
- HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend

  * There is sound from the speakers and headphones at the same time on one dell
platform (LP: #2051334)
- ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker 
platform

  * black screen when wake up from s3 with AMD W7600 gfx (LP: #2051341)
- drm/ttm: Reorder sys manager cleanup step

  * Mute/mic LEDs no function on HP ZBook  (LP: #2049838)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on HP 
ZBook

  * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050)
- ALSA: hda/cs8409: Suppress vmaster control for Dolphin models

  [ Ubuntu: 6.5.0-21.21 ]

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)
  * The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events
  * partproke is broken on empty loopback device (LP: #2049689)
- block: Move checking GENHD_FL_NO_PART to bdev_add_partition()
  * CVE-2023-51781
- appletalk: Fix Use-After-Free in atalk_ioctl
  * CVE-2023-51780
- atm: Fix Use-After-Free in do_vcc_ioctl
  * CVE-2023-6915
- ida: Fix crash in ida_free when the bitmap is empty
  * CVE-2024-0565
- smb: client: fix OOB in receive_encrypted_standard()
  * CVE-2024-0582
- io_uring: enable io_mem_alloc/free to be used in other parts
- io_uring/kbuf: defer release of mapped buffer rings
  * CVE-2024-0646
- net: tls, update curr on splice as well

 -- Timo Aaltonen   Tue, 13 Feb 2024
11:55:49 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

Title:
  Fix spurious wakeup caused by Cirque touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Spurious wakeup event caused by Cirque touchpad, prevent the system from
  sleep properly.

  [Fix]
  Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad.

  [Test]
  Suspend the system 100 times and make sure non of the wakeup event is
  caused by the touchpad and its IRQ line.

  [Where problems could occur]
  Logically the power consumption can increase slightly, but in reality
  there isn't any noticeable change. Since the quirk only applies to one
  device, there isn't much regression risk.

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


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

[Kernel-packages] [Bug 2054560] Re: Xorg freeze: i915 flips and commits are timing out

2024-02-28 Thread Xavier

Hi Daniel, thank you for your advice : in fact, moving to Wayland seems to 
solve the issue.
However, I am not ready to switch to Wayland because it has some annoying side 
effects :  a few application/functionalities that I use on a daily basis work 
differently or not with wayland.

I have realized also that with x.org, there is no freeze when using
PowerSave mode (might be related to the log you mentioned in your last
post).

I will try  to stay on kernel 6.2 or 6.5 with PowerSave mode for now.

Thank you for your help. For my concern this issue can be closed.
Xavier

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

Title:
  Xorg freeze: i915 flips and commits are timing out

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

Bug description:
  Random freezes occur since the installation of 6.5.x kernel. 
  Freeze occur several times a day, probably after touching the mouse or 
keyboard, but I'm not sure.
  App continue to work sound is OK, there is just no dispay updated.

  Booting to old 6.2 kernel solves the problem. I have tried all 6.5
  updates since the first released, but each time, I had a freeze after
  a few hours.

  Example of last mesg in dmesg when freeze occur :

  Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out

  or :
  Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), 
lowering kernel.perf_event_max_sample_rate to 79750
  Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR*

[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

2024-02-28 Thread Roxana Nicolescu

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

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

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Daan De Meyer (daandemeyer)

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Daan De Meyer (daandemeyer)

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

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

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

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

Title:
  linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from
  linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
  modules-extra. This makes it hard to pull in via the linux-virtual
  package, it can only come from the linux-generic one that also pulls
  in the firmware and everything else needed for baremetal, and that
  serves no purpose in a qemu VM. This stops VMs using these kernels
  from using the erofs filesystem. Erofs is a modern alternative to
  squashfs that supports more features such as ACLs. The following LPC
  presentation has more details on erofs and its advantages over
  squashfs: https://youtu.be/jt-hp_LtSBc.

  A user launching a VM using the linux-virtual kernel image is not able
  to mount erofs filesystems due to the lack of this kconfig. We make
  extensive use of erofs in systemd's upstream CI, which is running on
  Github Actions, which uses Jammy, so it would be great to have this
  backported.

  [Fix]

  Please consider moving this module to linux-modules.

  These are already enabled in the 'main' kernel config, and in other
  distros. In Debian/Archlinux/Fedora it is a (core) module that is
  built by default.

  To verify this works, it is sufficient to create an erofs filesystem
  with mkfs.erofs and verify that it can be mounted:

  $ mkdir sources
  $ echo abcde > sources/file
  $ mkfs.erofs erofs sources
  $ mount erofs mnt --mkdir
  $ ls mnt
  file

  Without this module installed and loaded, the mount will fail. Once
  enabled, it will succeed.

  [Test]

  1. pull built linux-modules packages for architectures with do_extras_package
 set to true;
  2. extract the deb and check if erofs kernel module file exists:

 $ dpkg-deb -R linux-modules-*.deb .
 $ find . -name erofs.ko\*

  [Regression Potential]

  Moving a module from a less-common to a more-common package should not
  have any negative side effects. The main effect will be a little more
  disk space used by the more common package, whether the module is in
  use or not. There will also be more functionality available in the
  default installation, which means a slightly increased surface and
  possibility of new bugs in case it gets used.

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

It looks like the above code might not need /dev/console at all. It
should be possible to modify it to use a private pipe for fsck's stdout.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

I'm starting to suspect our patch (comment #39) isn't directly to blame
for the systemd issue. Disabling or otherwise breaking systemd-
fsckd.service doesn't stop fsck output from polluting the console and
triggering this bug. Only skipping fsck avoids it. You can skip fsck
using 'fastboot' or 'fsck.mode=skip' on the kernel command line.

The fact that fsck prints a useless success message to its stdout is the
issue, but it's upstream systemd asking for that:

  https://github.com/systemd/systemd/blob/main/src/fsck/fsck.c#L336

and there doesn't seem to be any simple fsck parameter to tell it to run
more quietly (systemd already uses fsck -T).

I think maybe Red Hat unwittingly works around the problem by starting
the Plymouth splash earlier in initrd because they have SimpleDRM
enabled.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 2055259] [NEW] Zoom H4n Pro not seen as recording device in Audacity but works with arecord

2024-02-28 Thread Mint Platz

Public bug reported:

Hi!

This is a weird one: I wanted to use my Zoom H4n Pro as a recording
device with Linux Mint Mate 21.2 and kernel 6.5.0-14-generic. lusb tells
me

Bus 002 Device 009: ID 1686:0045 ZOOM Corporation Handy Recorder stereo
mix

, cat /proc/asound/cards shows

2 [H4]: USB-Audio - H4
ZOOM Corporation H4 at usb-:00:1d.0-1.4.2, full speed

and I can even record from it using the terminal with

arecord -D hw:2 -f cd foo.wav

. So from a hardware/driver perspective, things seem fine.

However the device only sporadically shows up in the "Sound Preferences"
applet,

pulseaudio -k

typically helps to refresh. But once I click some radio buttons in
"Choose a device for sound input" in the "Input" tab, the entries
related to my Zoom H4n Pro disappear and I'm left with "Monitor of
Built-in Audio Analog Stereo" being the only available option.

If Audacity is already open and I immediately start a recording after
pulseaudio -k, the first attempt succeeds but as soon as I click "Play",
the H4n device is gone.

So there obviously is something going on (could be how Audacity handles
input devices as well) that makes Pulse Audio revert to some default
setting whenever I try to record. arecord from the console works every
time, but it is quite tedious if you're used to an Audacity workflow. I
don't have pavucontrol installed because I don't really need it and I
also worry that it might interfere with the Sound Preferences applet
that comes with Linux Mint by default.

I also tested the Jabra Speak 410 handsfree station I had available.
This seems to reliably work as an input/microphone device and as on
output device/loudspeaker. For as long as the device is attached, the
sound preferences dialog shows "Jabra SPEAK 410 Mono" in the input tab
and "Jabra SPEAK Analog Stereo" in the output tab. I can record from and
play with it as often as I want in Audacity.

The Zoom H4n Pro on the other hand always shows up in the sound
preferences dialog after executing pulseaudio -k. I can then start
Audacity, start/stop monitoring and record from the Zoom H4n Pro (shown
as "Handy Recorder stereo mix Analog Stereo" in the input tab of sound
preferences) as often as I want.

But the moment I hit the "Play" button in Audacity, the Zoom device is
gone from the list of input devices in sound preferences and not coming
back unless I run pulseaudio -k again.

Updated the Zoom's firmware to 1.10, did not change anything. Using
different USB cables or ports did not make a difference either. So the
issue could also be how Audacity adresses input devices or what it does
to play audio which sort of messes things up in conjunction with the
Zoom's firmware.

And finally: The issue does not seem to show up on Linux Mint 19.1 Tessa
with Kernel 4.15.0-20-generic #21-Ubuntu. That is a different
motherboard (ASUS B365M-K instead of P7P55D) but I doubt that it makes a
difference at that level.

If you want me to test something or provide more logs, just go ahead.
Any help highly appreciated. Thank you.

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

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

Title:
  Zoom H4n Pro not seen as recording device in Audacity but works with
  arecord

Status in linux package in Ubuntu:
  New

Bug description:
  Hi!

  This is a weird one: I wanted to use my Zoom H4n Pro as a recording
  device with Linux Mint Mate 21.2 and kernel 6.5.0-14-generic. lusb
  tells me

  Bus 002 Device 009: ID 1686:0045 ZOOM Corporation Handy Recorder
  stereo mix

  , cat /proc/asound/cards shows

  2 [H4]: USB-Audio - H4
  ZOOM Corporation H4 at usb-:00:1d.0-1.4.2, full speed

  and I can even record from it using the terminal with

  arecord -D hw:2 -f cd foo.wav

  . So from a hardware/driver perspective, things seem fine.

  However the device only sporadically shows up in the "Sound
  Preferences" applet,

  pulseaudio -k

  typically helps to refresh. But once I click some radio buttons in
  "Choose a device for sound input" in the "Input" tab, the entries
  related to my Zoom H4n Pro disappear and I'm left with "Monitor of
  Built-in Audio Analog Stereo" being the only available option.

  If Audacity is already open and I immediately start a recording after
  pulseaudio -k, the first attempt succeeds but as soon as I click
  "Play", the H4n device is gone.

  So there obviously is something going on (could be how Audacity
  handles input devices as well) that makes Pulse Audio revert to some
  default setting whenever I try to record. arecord from the console
  works every time, but it is quite tedious if you're used to an
  Audacity workflow. I don't have pavucontrol installed because I don't
  really need it and I also worry that it might interfere with the Sound
  Preferences applet that comes with Linux Mint by default.

  I also tested the Jabra Speak 410

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

The nautilus crash is not relevant here, thanks.

Yes please enable debug in /etc/gdm3/custom.conf

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
  00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11)

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

I submitted new bug report(#2055257) using ubuntu-bug command but attach
the file here also Thanks!

** Attachment added: "_usr_bin_nautilus.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2055153/+attachment/5750086/+files/_usr_bin_nautilus.1000.crash

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Incomplete

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 
(rev 11)
  00:1f.0 ISA bridge: Intel Corporation Device

[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed