[Kernel-packages] [Bug 2042525] [NEW] mlxbf-pmc: Support 64-bit counter and counting cycles

[Shravan Kumar Ramani]

Public bug reported:

SRU Justification:

[Impact]
Currently, there is no method to keep track of the cycle count when an event is 
being monitored. And since cycle count increments quickly, the 32-bit counter 
values could wrap around and hence support for 64-bit counters is also needed 
for the same.

[Fix]
Expose 2 additional sysfs entries: count_clock and use_odd_counter. These 
fields are supported in BlueField-3 PMC hardware and each bit in count_clock 
corresponds to each counter, while each bit in use_odd_counter corresponds to 
an even counter.Exposing these fields will allow the user to program any 
counter of choice to monitor the cycle count for the required duration. 
Similarly, use_odd_counter can be set to couple 2 adjacent odd and even 
counters to form a 64-bit counter.

[Test Case]
1. Verify that count_clock and use_odd_counter sysfs entries are created for 
each BlueField-3 HW block. These are not supported by BlueField-1 or 
BlueField-2 HW.
2. Set any bit in count_clock and check if the corresponding counter values 
increment after enabling.
3. Set any bit in use_odd_counter and check if the cycle count increments on 2 
counters with the odd counter being the lower 32 bits and the even counter 
being the upper 32 bits.

[Regression Potential]
Can be considered minimal.

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

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

Title:
  mlxbf-pmc: Support 64-bit counter and counting cycles

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  Currently, there is no method to keep track of the cycle count when an event 
is being monitored. And since cycle count increments quickly, the 32-bit 
counter values could wrap around and hence support for 64-bit counters is also 
needed for the same.

  [Fix]
  Expose 2 additional sysfs entries: count_clock and use_odd_counter. These 
fields are supported in BlueField-3 PMC hardware and each bit in count_clock 
corresponds to each counter, while each bit in use_odd_counter corresponds to 
an even counter.Exposing these fields will allow the user to program any 
counter of choice to monitor the cycle count for the required duration. 
Similarly, use_odd_counter can be set to couple 2 adjacent odd and even 
counters to form a 64-bit counter.

  [Test Case]
  1. Verify that count_clock and use_odd_counter sysfs entries are created for 
each BlueField-3 HW block. These are not supported by BlueField-1 or 
BlueField-2 HW.
  2. Set any bit in count_clock and check if the corresponding counter values 
increment after enabling.
  3. Set any bit in use_odd_counter and check if the cycle count increments on 
2 counters with the odd counter being the lower 32 bits and the even counter 
being the upper 32 bits.

  [Regression Potential]
  Can be considered minimal.

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


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

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

[Anaggh S]

@koba

sudo apt install autoconf autoconf-archive g++ libglib2.0-dev
libdbus-1-dev libdbus-glib-1-dev libxml2-dev gtk-doc-tools libupower-
glib-dev liblzma-dev libevdev-dev

git clone https://github.com/intel/thermal_daemon.git
cd thermal_daemon

./autogen.sh prefix=/

make

# Stop Default thermald
sudo systemctl stop thermald.service

sudo ./thermald --no-daemon --adaptive

[1698899279][MSG]22 CPUID levels; family:model:stepping 0x6:8e:a (6:142:10)
[1698899279][MSG]22 CPUID levels; family:model:stepping 0x6:8e:a (6:142:10)
[1698899279][MSG]sensor id 13 : No temp sysfs for reading raw temp
[1698899279][MSG]sensor id 13 : No temp sysfs for reading raw temp
[1698899279][MSG]sensor id 13 : No temp sysfs for reading raw temp
*** stack smashing detected ***: terminated
Aborted

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for 

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

[madigal]

Looks like this has been seen in the past:

sudo groupadd power
sudo usermod --groups power --append $USER

https://askubuntu.com/questions/1170790/log-alert-unknown-group-power-
in-message-bus-config-file

But after a reboot, thermald.service is still failing; only the 'power'
warning is gone.

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal 

Re: [Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

[koba]

hi, would you mind to help on checking, if upstream thermald also
happens?


#git clone https://github.com/intel/thermal_daemon.git
#As per README.md,
#./autogen prefix=/
#make

Before run the upstream thermald, stop the original daemon
#systemctl stop thermald.service
#sudo ./thermald --no-daemon --adaptive

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service 

[Kernel-packages] [Bug 2041006] Re: WARNING CPU: 2 PID: 3763 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197 dcn32_calculate_dccg_k1_k2_values

[Lawrence A Fossi]

I can confirm everything I'm seeing is fixed in mainline/v6.5.6 6.7.7
could not be tested due to a bad signature error.

The lone exception was amd_gpio AMDI0030 0: Invalid config param 0014. That is 
fixed in mainline/6.6.rc5
I did not test the earlier 6.6rc candidates.

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

Title:
  WARNING CPU: 2 PID: 3763 at
  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hwseq.c:1197
  dcn32_calculate_dccg_k1_k2_values

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-hwe-6.2 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-hwe-6.2 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-6.2 source package in Noble:
  Invalid

Bug description:
  darkfoss@Tardis-2:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  Clean install just apt-get update and apt-get dist-upgrade 
  During the installation process when intramfs is run the following error is 
being generated:
  Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu

  darkfoss@Tardis-2:~$ apt-cache policy linux-firmware
  linux-firmware:
Installed: 20220329.git681281e4-0ubuntu3.21
Candidate: 20220329.git681281e4-0ubuntu3.21
Version table:
   *** 20220329.git681281e4-0ubuntu3.21 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20220329.git681281e4-0ubuntu3.14 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   20220329.git681281e4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  All of the above do not work even though the driver is installed
  correctly. The above error prevents radeonsi from loading.

  The good news is when I installed Both 23.04 and 23.10 they had 1 working 
firmware each they are:
  From Lunar Lobster
  20230323.gitbcdcfbcf-0ubuntu1.2 security (main)   2023-07-06
  Publishing details

  Created on 2023-07-06 by Andy Whitcroft
  Published on 2023-07-06

  Changelog

  linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium

* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug 
(LP: #1968604)
  - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922
  - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922

   -- Juerg Haefliger   Mon, 05 Jun 2023
  09:22:50 +0200

  Available diffs

  diff from 20230323.gitbcdcfbcf-0ubuntu1.1 to
  20230323.gitbcdcfbcf-0ubuntu1.2 (653 bytes)

  Builds

  [FULLYBUILT] amd64

  Built packages

  linux-firmware Firmware for Linux kernel drivers

  Package files

  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.debian.tar.xz (3.4 MiB)
  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2.dsc (2.0 KiB)
  linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2_all.deb (268.0 MiB)
  linux-firmware_20230323.gitbcdcfbcf.orig.tar.xz (254.0 MiB)


  From The Mantic Minotaur  (current stable release)
  20230919.git3672ccab-0ubuntu2.1  release (main)   2023-10-09
  Publishing details

  Created on 2023-10-09 by Ubuntu Archive Auto-Sync
  Published on 2023-10-09

  Changelog

  linux-firmware (20230919.git3672ccab-0ubuntu2.1) mantic;
  urgency=medium

* /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 (LP: 
#2038546)
  - [Packaging] config: Don't exclude cypress fw link targets

   -- Juerg Haefliger   Mon, 09 Oct 2023
  16:16:20 +0200

  Available diffs

  diff from 20230919.git3672ccab-0ubuntu2 to
  20230919.git3672ccab-0ubuntu2.1 (992 bytes)

  Builds

  [FULLYBUILT] amd64
  [FULLYBUILT] arm64
  [FULLYBUILT] armhf
  [FULLYBUILT] ppc64el
  [FULLYBUILT] riscv64
  [FULLYBUILT] s390x

  Built packages

  linux-firmware Firmware for Linux kernel drivers

  Package files

  linux-firmware_20230919.git3672ccab-0ubuntu2.1.debian.tar.xz (3.3 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1.dsc (2.0 KiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb (389.5 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_arm64.deb (386.5 MiB)
  linux-firmware_20230919.git3672ccab-0ubuntu2.1_armhf.deb (384.5 MiB)
  

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

[Anaggh S]

+1 Happening on fresh install.

* Xubuntu 23.10 amd64 on every boot.
* CPU Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
* Linux home 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 
13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
* thermald 2.5.4-2

sudo systemctl status thermald

× thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; preset: 
enabled)
 Active: failed (Result: core-dump) since Thu 2023-11-02 07:50:42 IST; 6min 
ago
   Duration: 146ms
Process: 8439 ExecStart=/usr/sbin/thermald --systemd --dbus-enable 
--adaptive (code=dumped, signal=ABRT)
   Main PID: 8439 (code=dumped, signal=ABRT)
CPU: 28ms

Nov 02 07:50:42 home systemd[1]: thermald.service: Scheduled restart job, 
restart counter is at 5.
Nov 02 07:50:42 home systemd[1]: Stopped thermald.service - Thermal Daemon 
Service.
Nov 02 07:50:42 home systemd[1]: thermald.service: Start request repeated too 
quickly.
Nov 02 07:50:42 home systemd[1]: thermald.service: Failed with result 
'core-dump'.
Nov 02 07:50:42 home systemd[1]: Failed to start thermald.service - Thermal 
Daemon Service.


journalctl -u thermald

Nov 02 06:45:54 home systemd[1]: Starting thermald.service - Thermal Daemon 
Service...
Nov 02 06:45:54 home systemd[1]: Started thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:54 home thermald[608]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:54 home thermald[608]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:54 home thermald[608]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:54 home thermald[608]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:54 home thermald[608]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:54 home thermald[608]: *** stack smashing detected ***: terminated
Nov 02 06:45:54 home systemd[1]: thermald.service: Main process exited, 
code=killed, status=6/ABRT
Nov 02 06:45:54 home systemd[1]: thermald.service: Failed with result 'signal'.
Nov 02 06:45:54 home systemd[1]: thermald.service: Scheduled restart job, 
restart counter is at 1.
Nov 02 06:45:55 home systemd[1]: Stopped thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:55 home systemd[1]: Starting thermald.service - Thermal Daemon 
Service...
Nov 02 06:45:55 home thermald[738]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:55 home systemd[1]: Started thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:55 home thermald[738]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:55 home thermald[738]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:55 home thermald[738]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:55 home thermald[738]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:55 home thermald[738]: *** stack smashing detected ***: terminated
Nov 02 06:45:55 home systemd[1]: thermald.service: Main process exited, 
code=killed, status=6/ABRT
Nov 02 06:45:55 home systemd[1]: thermald.service: Failed with result 'signal'.
Nov 02 06:45:55 home systemd[1]: thermald.service: Scheduled restart job, 
restart counter is at 2.
Nov 02 06:45:55 home systemd[1]: Stopped thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:55 home systemd[1]: Starting thermald.service - Thermal Daemon 
Service...
Nov 02 06:45:55 home systemd[1]: Started thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:55 home thermald[779]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:55 home thermald[779]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:55 home thermald[779]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:55 home thermald[779]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:55 home thermald[779]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:55 home thermald[779]: *** stack smashing detected ***: terminated
Nov 02 06:45:56 home systemd[1]: thermald.service: Main process exited, 
code=dumped, status=6/ABRT
Nov 02 06:45:56 home systemd[1]: thermald.service: Failed with result 
'core-dump'.
Nov 02 06:45:56 home systemd[1]: thermald.service: Scheduled restart job, 
restart counter is at 3.
Nov 02 06:45:56 home systemd[1]: Stopped thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:56 home systemd[1]: Starting thermald.service - Thermal Daemon 
Service...
Nov 02 06:45:56 home systemd[1]: Started thermald.service - Thermal Daemon 
Service.
Nov 02 06:45:56 home thermald[1105]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:56 home thermald[1105]: 22 CPUID levels; family:model:stepping 
0x6:8e:a (6:142:10)
Nov 02 06:45:56 home thermald[1105]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:56 home thermald[1105]: sensor id 13 : No temp sysfs for reading 
raw temp
Nov 02 06:45:56 home thermald[1105]: sensor id 13 : No temp 

[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on

[koba]

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

** Also affects: linux-oem-6.5 (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => koba (kobako)

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

Title:
  Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle
  screen on

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.

  [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814

  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

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


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

[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed

[koba]

** Description changed:

  [Impact]
  checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
  
  [Fix]
+ Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
+ for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
+ due to a regression that caused resume from suspend to fail on certain
+ systems. However, we never added this capability back and this is now
+ causing systems fail to enter low power CPU states, drawing more power
+ from the battery.
+ 
+ The original revert mentioned that we restore L1 PM substate configuration
+ even though ASPM L1 may already be enabled. This is due the fact that
+ the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
+ 
+ Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
+ more closely by:
+ 
+ 1) Do not restore ASPM configuration in pci_restore_pcie_state() but
+do that after PCIe capability is restored in pci_restore_aspm_state()
+following PCIe r6.0, sec 5.5.4.
+ 
+ 2) ASPM is first enabled on the upstream component and then downstream
+(this is already forced by the parent-child ordering of Linux
+Device Power Management framework).
+ 
+ 3) Program ASPM L1 PM substate configuration before L1 enables.
+ 
+ 4) Program ASPM L1 PM substate enables last after rest of the fields
+in the capability are programmed.
+ 
+ 5) Add denylist that skips restoring on the ASUS and TUXEDO systems
+where these regressions happened, just in case. For the TUXEDO case
+we only skip restore if the BIOS is involved in system suspend
+(that's forcing "mem_sleep=deep" in the command line). This is to
+avoid possible power regression when the default suspend to idle is
+used, and at the same time make sure the devices continue working
+after resume when the BIOS is involved.
  
+ [Test Case]
+ 1. suspend and resume.
+ 2. check if the error appears in dmesg
+ ~~~
+  pcieport :00:1c.0: pciehp: Slot(5): Card not present
+  rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device 
inaccessible
+  rtsx_pci :05:00.0: Unable to change power state from D3cold to D0, 
device inaccessible
+ ~~~
  
  [where the issue could happen]
- low,
+ low, the patch works well on the reported malfunctioned ASUS platform too.

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

Title:
  Fix after-suspend-mediacard/sdhc-insert test failed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  [Impact]
  checkbox test case, after-suspend-mediacard/sdhc-insert, failed.

  [Fix]
  Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
  for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
  due to a regression that caused resume from suspend to fail on certain
  systems. However, we never added this capability back and this is now
  causing systems fail to enter low power CPU states, drawing more power
  from the battery.
  
  The original revert mentioned that we restore L1 PM substate configuration
  even though ASPM L1 may already be enabled. This is due the fact that
  the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
  
  Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
  more closely by:
  
  1) Do not restore ASPM configuration in pci_restore_pcie_state() but
 do that after PCIe capability is restored in pci_restore_aspm_state()
 following PCIe r6.0, sec 5.5.4.
  
  2) ASPM is first enabled on the upstream component and then downstream
 (this is already forced by the parent-child ordering of Linux
 Device Power Management framework).
  
  3) Program ASPM L1 PM substate configuration before L1 enables.
  
  4) Program ASPM L1 PM substate enables last after rest of the fields
 in the capability are programmed.
  
  5) Add denylist that skips restoring on the ASUS and TUXEDO systems
 where these regressions happened, just in case. For the TUXEDO case
 we only skip restore if the BIOS is involved in system suspend
 (that's forcing "mem_sleep=deep" in the command line). This is to
 avoid possible power regression when the default suspend to idle is
 used, and at the same time make sure the devices continue working
 after resume when the BIOS is involved.

  [Test Case]
  1. suspend 

[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0

[Matthew Ruffell]

Performing verification for Jammy. I checked out the
Ubuntu-5.15.0-90.100 git tag from the source repository on an arm64
system, and made sure that pahole was removed. I completed a build and
looked at the build log, and there were no more pahole warnings.

Marking verified for jammy.

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

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

Title:
  scripts/pahole-flags.sh change return to exit 0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux-bluefield source package in Jammy:
  Fix Committed

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

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

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


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

[Kernel-packages] [Bug 2042500] [NEW] Fix after-suspend-mediacard/sdhc-insert test failed

[koba]

Public bug reported:

[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.

[Fix]


[where the issue could happen]
low,

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

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

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

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

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-6.1 (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.5 (Ubuntu Noble)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-2035307 stella

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

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

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

** Also affects: linux-oem-6.1 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => koba (kobako)

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

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

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

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

** Tags added: oem-priority originate-from-2035307 stella

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

Title:
  Fix after-suspend-mediacard/sdhc-insert test failed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  [Impact]
  checkbox test case, after-suspend-mediacard/sdhc-insert, failed.

  [Fix]


  [where the issue could happen]
  low,

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


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

[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs

[AceLan Kao]

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

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

Title:
  Infinite systemd loop when power off the machine with multiple MD
  RAIDs

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:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The system with multiple MD RAIDs sometimes hangs while rebooting, that's 
because of the systemd can't stop and close the MD disk.

  [Fix]
  This commit fixes the issue, and this issue has been introduced by 
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed") 
after v6.0

  https://patchwork.kernel.org/project/linux-
  raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/

  [Test case]
  1. Reboot the system with multiple MD RAIDs at least 10 times.
  2. Make sure the system can reboot successfully every time.
  3. You should not see error messages like below.

  [ 205.360738] systemd-shutdown[1]: Stopping MD devices.
  [ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
  [ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
  [ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
  [ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
  [ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127, 
ignoring: Input/output error
  [ 205.404975] md: md127 stopped.
  [ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
  [ 205.770179] md: md126: resync interrupted.
  [ 205.776258] md126: detected capacity change from 1900396544 to 0
  [ 205.783349] md: md126 stopped.
  [ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
  [ 205.862435] md: md126 stopped.
  [ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125, 
ignoring: Input/output error
  [ 205.872845] block device autoloading is deprecated and will be removed.
  [ 205.880955] md: md125 stopped.
  [ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
  [ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or 
resource busy
  [ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
  [ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or 
resource busy
  [ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
  [ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or 
resource busy
  [ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.

  [Where problems could occur]
  It fixes the data race issue, should not introduce any regression.

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


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

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

[Kai-Heng Feng]

** Changed in: linux-signed-oem-6.1 (Ubuntu)
   Status: New => In Progress

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

Title:
  USB stick can't be detected

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

Bug description:
  [Summary]

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

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

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

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

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


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

[Kernel-packages] [Bug 2039782] Re: Stalls on CPUs/tasks on VisionFive 2 with external GPU

[Opvolger]

@xypron

I know, https://rvspace.org/en/project/JH7110_Upstream_Plan

Can't wait until everything is green on this site :)

Good to know that NVMe support is working correctly.

I was very surprised to see that an external GPU worked "out of the box"
with Ubuntu 23.10. But then it crashed a lot :(

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

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


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

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1026.26
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-oem-6.1' to 'verification-done-
jammy-linux-oem-6.1'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy-
linux-oem-6.1'.


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-oem-6.1-v2 
verification-needed-jammy-linux-oem-6.1

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
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:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1026.26
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-oem-6.1' to 'verification-done-
jammy-linux-oem-6.1'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy-
linux-oem-6.1'.


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-oem-6.1-v2 
verification-needed-jammy-linux-oem-6.1

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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


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

[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1026.26
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-oem-6.1' to 'verification-done-
jammy-linux-oem-6.1'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy-
linux-oem-6.1'.


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-oem-6.1-v2 
verification-needed-jammy-linux-oem-6.1

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

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
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 Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  New
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

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


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

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

[JS]

Looking to https://forums.linuxmint.com/viewtopic.php?t=406953, this
issue might not be limited to 5.15.0-88 but could affect also 6.2.0-36.

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 
3: 1000 4: 794
  5: 796 6: 3156 7: 799 8: 758 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 
v: kernel ports:
  active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI 
driver: nvidia
  v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 
10de:1d10
Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 
chip-ID: 0408:a030
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm 
(27")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 
23.0.4-0ubuntu1~22.04.1
  direct render: Yes
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
v: kernel pcie:
  speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
IF: wlp3s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Acer Incorporated ALI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 
04:00.1
  chip-ID: 10ec:8168
IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
Local Storage: total: 1.36 TiB used: 143.29 GiB (10.3%)
ID-1: /dev/sda model: SD Ultra 3D 1TB size: 931.51 GiB speed: 6.0 Gb/s 
serial: 
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB 
speed: 6.0 Gb/s
  serial: 
  Partition:
ID-1: / size: 915.32 GiB used: 143.28 GiB (15.7%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
  Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: 
/swapfile
  Sensors:
System Temperatures: cpu: 48.0 C pch: 37.0 C mobo: N/A
Fan Speeds (RPM): N/A
  Repos:
Packages: 3240 apt: 3217 flatpak: 23
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-jammy.list
  1: deb [signed-by=/etc/apt/keyrings/audio-recorder-ppa-jammy.gpg] https: 
//ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu jammy main
Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
  1: deb http: 

[Kernel-packages] [Bug 2039782] Re: Stalls on CPUs/tasks on VisionFive 2 with external GPU

[Heinrich Schuchardt]

@opvolger

Thank you for confirming the issue.

The upstreaming of PCIe for the StarFive VisionFive 2 board is not
finalized yet. The kernel team will revisit this issue once there is
proper upstream support. They picked up what was available on the kernel
list which brought us NVMe support for which I am grateful.

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

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


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

[Kernel-packages] [Bug 2039782] Re: Stalls on CPUs/tasks on VisionFive 2 with external GPU

[Heinrich Schuchardt]

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

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

Title:
  Stalls on CPUs/tasks on VisionFive 2 with external GPU

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am trying to install Ubuntu Mantic on the StarFive VisionFive 2 1.3B
  board using
  https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-live-
  server-riscv64.img.gz

  I have connected an Nvidia GT710 graphics card to the NVMe connector
  and see rcu_sched stalls. I have not  observed this behavior on
  StarFive VisionFive 2 1.3B boards without an external GPU.

  The U-Boot installed on SPI flash is
  
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/release/+files/u-boot-starfive_2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa5_riscv64.deb

  [   93.102845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
  [   93.114452] rcu: 0-...!: (1 GPs behind) idle=c69c/1/0x4002 
softirq=2431/2431 fqs=41
  [   93.128724] rcu: (detected by 2, t=15008 jiffies, g=4353, q=2369 
ncpus=4)
  [   93.140996] Task dump for CPU 0:
  [   93.149549] task:swapper/0   state:R  running task stack:0 
pid:0 ppid:0  flags:0x
  [   93.164907] Call Trace:
  [   93.172715] [] __schedule+0x27a/0x82e
  [   93.183385] rcu: rcu_sched kthread timer wakeup didn't happen for 14937 
jiffies! g4353 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200
  [   93.200202] rcu: Possible timer handling issue on cpu=0 
timer-softirq=890
  [   93.212733] rcu: rcu_sched kthread starved for 14945 jiffies! g4353 f0x0 
RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0
  [   93.228777] rcu: Unless rcu_sched kthread gets sufficient CPU time, 
OOM is now expected behavior.
  [   93.243573] rcu: RCU grace-period kthread stack dump:
  [   93.254522] task:rcu_sched   state:R stack:0 pid:15ppid:2  
flags:0x
  [   93.268895] Call Trace:
  [   93.277340] [] __schedule+0x27a/0x82e
  [   93.288646] [] schedule+0x4e/0xde
  [   93.299623] [] schedule_timeout+0x8c/0x15e
  [   93.311380] [] rcu_gp_fqs_loop+0x2fc/0x3d4
  [   93.323170] [] rcu_gp_kthread+0x11a/0x142
  [   93.334901] [] kthread+0xc4/0xe4
  [   93.345833] [] ret_from_fork+0xe/0x20

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


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

[Kernel-packages] [Bug 2039782] Re: Stalls on CPUs/tasks on VisionFive 2 with external GPU

[Opvolger]

I have the same problem

[   14.873826] Console: switching to colour frame buffer device 240x67
[   15.120436] radeon 0001:01:00.0: [drm] fb0: radeondrmfb frame buffer device
[   75.138845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   75.145779] rcu: 0-...0: (2 ticks this GP) 
idle=ae24/1/0x4002 softirq=881/882 fqs=7501   
[   75.156363] rcu:  hardirqs   softirqs   csw/system
[   75.162878] rcu:  number: 17595499  00
[   75.169396] rcu: cputime:0  00   ==> 
30016(ms)
[   75.177538] rcu: (detected by 3, t=15011 jiffies, g=121, q=273 ncpus=4)
[   75.185375] Task dump for CPU 0:
[   75.189151] task:swapper/0   state:R  running task stack:0 pid:0 
ppid:0  flags:0x0008
[   75.200753] Call Trace:
[   75.203615] [] __schedule+0x27a/0x82e
Timed out for waiting the udev queue being empty.
[  198.633202] watchdog: Watchdog detected hard LOCKUP on cpu 0
[  198.639832] Modules linked in: radeon(+) hid_generic usbhid hid motorcomm 
video drm_suballoc_helper i2c_algo_bit drm_ttm_helper ttm drm_display_helper 
dwmac_starfive stmmac_platform cec rc_core stmmac drm_kms_helper drm 
axp20x_regulator pcs_xpcs xhci_pci dw_mmc_starfive dw_mmc_pltfm phylink 
backlight xhci_pci_renesas pinctrl_starfive_jh7110_aon dw_mmc 
clk_starfive_jh7110_aon axp20x_i2c jh7110_trng clk_starfive_jh7110_isp 
clk_starfive_jh7110_vout axp20x spi_cadence_quadspi phy_jh7110_usb
[  242.654895] INFO: task kworker/1:2:83 blocked for more than 120 seconds.
[  242.662754]   Not tainted 6.5.0-10-generic #10.1-Ubuntu
[  242.669286] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  242.678454] task:kworker/1:2 state:D stack:0 pid:83ppid:2  
flags:0x
[  242.688246] Workqueue: events output_poll_execute [drm_kms_helper]
[  242.695736] Call Trace:
[  242.698600] [] __schedule+0x27a/0x82e
[  242.704733] [] schedule+0x4e/0xde
[  242.710452] [] schedule_preempt_disabled+0x18/0x20
[  242.717901] [] __mutex_lock.constprop.0+0x3ce/0x6e0
[  242.725452] [] __mutex_lock_slowpath+0x1a/0x26
[  242.732495] [] mutex_lock+0x48/0x58
[  242.738419] [] drm_client_dev_hotplug+0x7c/0x10a [drm]
[  242.746934] [] output_poll_execute+0x1e2/0x21c 
[drm_kms_helper]
[  242.755890] [] process_one_work+0x1dc/0x3b4
[  242.762628] [] worker_thread+0x88/0x456
[  242.768959] [] kthread+0xc4/0xe4
[  242.774576] [] ret_from_fork+0xe/0x20
[  242.780717] INFO: task (udev-worker):117 blocked for more than 120 seconds.
[  242.788875]   Not tainted 6.5.0-10-generic #10.1-Ubuntu
[  242.795410] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  242.804577] task:(udev-worker)   state:D stack:0 pid:117   ppid:111
flags:0x0006
[  242.814360] Call Trace:
[  242.817230] [] __schedule+0x27a/0x82e
[  242.823366] [] schedule+0x4e/0xde
[  242.829088] [] schedule_timeout+0x128/0x15e
[  242.835831] [] __wait_for_common+0x17c/0x24a
[  242.897655] [] wait_for_completion+0x26/0x36
[  242.959630] [] __wait_rcu_gp+0xec/0x192
[  243.021222] [] synchronize_rcu+0x118/0x126
[  243.083262] [] __sysrq_swap_key_ops+0xa2/0xf4
[  243.145935] [] register_sysrq_key+0x1a/0x26
[  243.208817] [] 
__drm_fb_helper_initial_config_and_unlock+0x1ae/0x24a [drm_kms_helper]  
[  243.276529] [] drm_fb_helper_initial_config+0x3a/0x46 
[drm_kms_helper]
[  243.342843] [] radeon_fbdev_client_hotplug+0xb4/0xba 
[radeon]
[  243.410095] [] drm_client_register+0x4c/0x92 [drm]
[  243.475748] [] radeon_fbdev_setup+0xaa/0xf8 [radeon]
[  243.542662] [] radeon_pci_probe+0xe8/0x158 [radeon]
[  243.609846] [] local_pci_probe+0x40/0x88
[  243.675177] [] pci_call_probe+0x60/0x17a
[  243.740214] [] pci_device_probe+0x7c/0xdc
[  243.804828] [] call_driver_probe+0x22/0x142
[  243.869782] [] really_probe+0x9a/0x2a2
[  243.934343] [] __driver_probe_device+0x7e/0x146
[  243.999560] [] driver_probe_device+0x38/0xd0
[  244.064017] [] __driver_attach+0xee/0x1e8
[  244.128136] [] bus_for_each_dev+0x6c/0xc4
[  244.192404] [] driver_attach+0x26/0x34
[  244.256463] [] bus_add_driver+0x112/0x21e
[  244.321058] [] driver_register+0x52/0x106
[  244.385902] [] __pci_register_driver+0x4c/0x60
[  244.451082] [] radeon_module_init+0x6c/0x1000 [radeon]
[  244.518090] [] do_one_initcall+0x5c/0x1e2
[  244.582278] [] do_init_module+0x5e/0x224
[  244.645610] [] load_module+0x7b4/0x8de
[  244.708029] [] init_module_from_file+0x82/0xd4
[  244.771181] [] sys_finit_module+0x194/0x330
[  244.834148] [] do_trap_ecall_u+0xd6/0x154
[  244.896674] [] ret_from_exception+0x0/0x64
[  255.222845] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  255.285167] rcu: 0-...0: (2 ticks this GP) 
idle=ae24/1/0x4002 softirq=881/882 fqs=2  
[  255.351454] rcu:  hardirqs   softirqs   csw/system
[  255.414129] rcu:  number: 122510523  00
[  255.476719] rcu: cputime:0  00   ==> 
210144(ms)
[  

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

[Souvik Kumar]

or anydesk please ? talking regarding #106 & #108

-- 
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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Souvik Kumar]

Giuliano, can you please guide me through teamviewer? That issue is
still not getting fixed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

** Changed in: ipu6-drivers (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: ipu6-drivers (Ubuntu Mantic)
   Status: New => Triaged

** Changed in: ipu6-drivers (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: ivsc-driver (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: ivsc-driver (Ubuntu Mantic)
   Status: New => Triaged

** Changed in: ivsc-driver (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in ipu6-drivers source package in Mantic:
  Triaged
Status in ivsc-driver source package in Mantic:
  Triaged
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA 

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

[Kevin Klinke]

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

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

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

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

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

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

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

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in ipu6-drivers source package in Mantic:
  New
Status in ivsc-driver source package in Mantic:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come according to Intel.

  These two fixes are therefore for related components for not-yet fully
  upstreamed IPU6 as needed for out-of-tree dkms drivers.

  [Test Case]

  ```
  $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU"
  $ sudo dmesg | grep int3472
  # 

[Kernel-packages] [Bug 2042455] [NEW] Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init

[William Tu]

Public bug reported:

Summary:
Machine hangs when loading OFED 2310 mlx5 driver at BlueField

How to reproduce:
# load the OFED driver

Reason:
BF got stuck and observed call trace "mlx5_sf_hw_table_init+0xf4/0x2d0 
[mlx5_core]

dmesg from minicom:
[  726.569928] INFO: task systemd-udevd:297 blocked for more than 604 seconds.
[  726.576895]   Tainted: G   OE 5.15.0-1029-bluefield 
#31-Ubuntu
[  726.584101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  726.591913] task:systemd-udevd   state:D stack:0 pid:  297 ppid:   280 
flags:0x000d
[  726.600248] Call trace:
[  726.602680]  __switch_to+0xf8/0x150
[  726.606159]  __schedule+0x2b8/0x790
[  726.609634]  schedule+0x64/0x140
[  726.612850]  schedule_preempt_disabled+0x18/0x24
[  726.617453]  __mutex_lock.constprop.0+0x1a0/0x680
[  726.622141]  __mutex_lock_slowpath+0x40/0x90
[  726.626396]  mutex_lock+0x64/0x70
[  726.629695]  devlink_resource_register+0x50/0x1a0
[  726.634386]  mlx5_sf_hw_table_init+0xf4/0x2d0 [mlx5_core]
[  726.639882]  mlx5_init_one_devl_locked+0x1c8/0x784 [mlx5_core]
[  726.645791]  probe_one+0x300/0x5f0 [mlx5_core]
[  726.650307]  local_pci_probe+0x48/0xb4
[  726.654043]  pci_device_probe+0x18c/0x200
[  726.658039]  really_probe+0xd0/0x490
[  726.661600]  __driver_probe_device+0x148/0x190
[  726.666029]  driver_probe_device+0x48/0x180
[  726.670198]  __driver_attach+0x104/0x240
[  726.674106]  bus_for_each_dev+0x78/0xdc
[  726.677927]  driver_attach+0x2c/0x40
[  726.681486]  bus_add_driver+0x154/0x270
[  726.685307]  driver_register+0x80/0x13c
[  726.689129]  __pci_register_driver+0x4c/0x60
[  726.693386]  __init_backport+0xf0/0x1000 [mlx5_core]
[  726.698425]  do_one_initcall+0x4c/0x250
[  726.702248]  do_init_module+0x50/0x260
[  726.705983]  load_module+0x9fc/0xbe0
[  726.709543]  __do_sys_finit_module+0xa8/0x114
[  726.713885]  __arm64_sys_finit_module+0x28/0x3c
[  726.718401]  invoke_syscall+0x78/0x100
[  726.722137]  el0_svc_common.constprop.0+0x54/0x184
[  726.726913]  do_el0_svc+0x30/0xac
[  726.730215]  el0_svc+0x48/0x160
[  726.733341]  el0t_64_sync_handler+0xa4/0x130
[  726.737597]  el0t_64_sync+0x1a4/0x1a8
[  847.401924] INFO: task systemd-udevd:297 blocked for more than 724 seconds.
[  847.408891]   Tainted: G   OE 5.15.0-1029-bluefield 
#31-Ubuntu

How to fix:
This is related to
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039869
and we need to backport/cherry-pick more patches from the series

Patches are below
Backport: f655dacb59ac net: devlink: remove unused locked functions
Backport: 012ec02ae441 netdevsim: convert driver to use unlocked devlink API 
during init/fini
Cherry-pick: eb0e9fa2c635 net: devlink: add unlocked variants of 
devlink_region_create/destroy() functions
SKIP: 72a4c8c94efa mlxsw: convert driver to use unlocked devlink API during 
init/fini
Backport: 70a2ff89369d net: devlink: add unlocked variants of devlink_dpipe*() 
functions
Cherry-pick: 755cfa69c4ec net: devlink: add unlocked variants of devlink_sb*() 
functions
Cherry-pick: c223d6a4bf6d net: devlink: add unlocked variants of 
devlink_resource*() functions
Cherry-pick: 852e85a704c2 net: devlink: add unlocked variants of 
devling_trap*() functions
Cherry-pick: e26fde2f5bef net: devlink: avoid false DEADLOCK warning reported 
by lock

Thanks!

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

** Summary changed:

- Devlink backport: Fix mlx5 driver hangs
+ Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init

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

Title:
  Devlink backport: Fix mlx5 driver hangs due to mlx5_sf_hw_table_init

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  Summary:
  Machine hangs when loading OFED 2310 mlx5 driver at BlueField

  How to reproduce:
  # load the OFED driver

  Reason:
  BF got stuck and observed call trace "mlx5_sf_hw_table_init+0xf4/0x2d0 
[mlx5_core]

  dmesg from minicom:
  [  726.569928] INFO: task systemd-udevd:297 blocked for more than 604 seconds.
  [  726.576895]   Tainted: G   OE 5.15.0-1029-bluefield 
#31-Ubuntu
  [  726.584101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.591913] task:systemd-udevd   state:D stack:0 pid:  297 ppid:   280 
flags:0x000d
  [  726.600248] Call trace:
  [  726.602680]  __switch_to+0xf8/0x150
  [  726.606159]  __schedule+0x2b8/0x790
  [  726.609634]  schedule+0x64/0x140
  [  726.612850]  schedule_preempt_disabled+0x18/0x24
  [  726.617453]  __mutex_lock.constprop.0+0x1a0/0x680
  [  726.622141]  __mutex_lock_slowpath+0x40/0x90
  [  726.626396]  mutex_lock+0x64/0x70
  [  726.629695]  devlink_resource_register+0x50/0x1a0
  [  726.634386]  mlx5_sf_hw_table_init+0xf4/0x2d0 [mlx5_core]
  [  726.639882]  

[Kernel-packages] [Bug 2042075] Re: Black screen at login after updating to this kernel

[Mario Limonciello]

Can you please share the kernel log from a failed kernel?  To get it:
1) Boot the failed kernel and reproduce failure
2) Boot a good kernel
3) run "journalctl -k -b-1 > journal_bad.txt"
4) run "journalctl -k > journal_good.txt"

Then attach both of those to this bug.


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

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

Title:
  Black screen at login after updating to this kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Inspiron  AMD A10 Laptop
  Linux Mint Mate O/S

  After updating the kernel I restarted the laptop. After entering my
  password and logging in the screen goes black with occasional flashes
  of, I guess i'd call it static.

  The same thing happened with the previous kernel I installed, ending
  .87, when I was running Zorin OS.

  After un-installing the system returns to opening as usual.

  System:
Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working 
correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco
  dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

  Machine:
Type: Portable System: Dell product: Inspiron  v: A12 serial: 
 Chassis:
  type: 8 v: A12 serial: 
Mobo: Dell model: 0CX84K v: A00 serial:  UEFI: Dell v: 
A12
  date: 08/30/2016

  CPU:
Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 
64 type: MT MCP
  arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 
1: 2673 2: 2680
  3: 3053 4: 2700 bogomips: 14374
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu 
v: kernel ports:
  active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 
Mobile]
  vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 
bus-ID: 03:00.0
  chip-ID: 1002:6660
Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 
2-4:3
  chip-ID: 0c45:6712
Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: 
X:
  loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu 
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96
Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9")
OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 
5.15.0-76-generic)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  I don't have a lot of experience with reporting errors so I hope this
  helps!

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


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

[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Fix unstable audio at low levels on Thinkpad P1G4

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 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 source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The audio at low levels is not stable with fluctuating levels.

  [Fix]
  Forcibly assign NID 0x03 to HP while NID 0x02 to SPK.

  [Test]
  Tested on hardware, the audio output is OK at all levels.

  [Where problems could occur]
  It may break audio output on Thinkpad P1G4/5.

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


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

[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  PCI BARs larger than 128GB are disabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux-bluefield package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Current linux-bluefield kernel reports that PCI BARs larger than 128GB
  are disabled.

  Increase the maximum PCI BAR size from 128GB to 8TB for future
  expansion.

  [Test Plan]

  Use updated kernel with PCI device with PCI BARs larger than 128GB.

  [Where problems could occur]

  No potential problems are expected.

  [Other Info]

  Testing has been provided by the customer. This patch is a cherry-pick
  from the upstream 5.18 kernel. It is intended for linux-bluefield
  kernel re-spin but it may be also suitable for the generic kernel
  (separate submission).

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


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

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

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-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/1945989

Title:
  Check for changes relevant for security certifications

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

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

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

  [Test Plan]

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

  [Where problems could occur]

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

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


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

[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Fix suspend hang on Lenovo workstation

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 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The system hang after resume from S3.
  Error logs:
  kernel: igb :02:00.0: disabling already-disabled device
  kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 
pci_disable_device+0xc4/0xf0
  kernel: RIP: 0010:pci_disable_device+0xc4/0xf0
  kernel: Call Trace:
  kernel:  
  kernel:  igb_io_error_detected+0x3e/0x60
  kernel:  report_error_detected+0xd6/0x1c0
  kernel:  ? __pfx_report_normal_detected+0x10/0x10
  kernel:  report_normal_detected+0x16/0x30
  kernel:  pci_walk_bus+0x74/0xa0
  kernel:  pcie_do_recovery+0xb9/0x340
  kernel:  ? __pfx_aer_root_reset+0x10/0x10
  kernel:  aer_process_err_devices+0x168/0x220
  kernel:  aer_isr+0x1b5/0x1e0
  kernel:  ? __pfx_irq_thread_fn+0x10/0x10
  kernel:  irq_thread_fn+0x21/0x70
  kernel:  irq_thread+0xf8/0x1c0
  kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
  kernel:  ? __pfx_irq_thread+0x10/0x10
  kernel:  kthread+0xef/0x120
  kernel:  ? __pfx_kthread+0x10/0x10
  kernel:  ret_from_fork+0x29/0x50
  kernel:  
  kernel: ---[ end trace  ]---

  [Fix]
  The pci io error detected ops is called before the driver resumed.
  Avoid this race condition to fix the issue.

  [Test]
  Tested on hardware, the system suspend/resume OK.

  [Where problems could occur]
  It may break igb driver.

  The commit is included in 6.5-rc1 and merged by stable update in
  oem-6.1, SRU for Jammy and Lunar.

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


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

[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-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/2034745

Title:
  [regression] Unable to initialize SGX enclaves with XFRM other than 3

Status in linux package in Ubuntu:
  Fix Released
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 Released

Bug description:
  SRU Justification

  [Impact]

  In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
  sgx_encl_init returns EINVAL. The only reason this wouldn't work
  properly is if sgx_drv_init thinks XSAVE isn't enabled. This works
  fine in 5.15.0-1043.

  Likely cause:
  1045 adds this patch: 
https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4
 . This later patch indicates that the former patch introduced some ordering 
problems. 
https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5
 . That later patch isn't applied to 1045.

  [Test Plan]

  User test results pending, but its a fix commit so should likely be
  applied regardless.

  [Regression Potential]

  SGX could continue to fail.

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


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

[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  allow io_uring to be disabled in runtime

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  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 source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  io_uring has been an important attack vector in the recent years in local 
privilege escalation attacks. Allowing admins that don't use io_uring to 
disable it in their systems allows them to reduce their attack surface.

  [Test case]
  sysctl -w kernel.io_uring_disabled=1
  then try to use io_uring from an unprivileged user, then try it with 
privileges (CAP_SYS_ADMIN)

  Actually also tried setting kernel.io_uring_disabled=2 and checking that
  neither (privileged or unprivileged worked).

  Then testing setting it back to 0.

  Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and
  that it worked for group 1000, then set it to 1001 and verified that it
  didn't work anymore for group 1000.

  
  [Potential regression]
  Uses can be denied from using io_uring.

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


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

[Kernel-packages] [Bug 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-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/2035166

Title:
  NULL Pointer Dereference During KVM MMU Page Invalidation

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

Bug description:
  [Impact]
  During VM live migration, there is a potential risk of dereferencing a NULL 
pointer,
  which can lead to memory access issues and result in an unstable environment.

  [Fix]
  The call trace is as follows:

  kernel: BUG: kernel NULL pointer dereference, address: 0008
  kernel: #PF: supervisor write access in kernel mode
  kernel: #PF: error_code(0x0002) - not-present page
  kernel: PGD 0 P4D 0 
  kernel: Oops: 0002 [#1] SMP NOPTI
  kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G  IOE 
5.15.0-53-generic #59~20.04.1-Ubuntu
  kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021
  kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm]
  kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 
0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 
89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de
  kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246
  kernel: RAX:  RBX: a0fe29e94c38 RCX: 0027
  kernel: RDX:  RSI: 0004 RDI: b5801e24ba58
  kernel: RBP: b58032027930 R08:  R09: 0004
  kernel: R10: 0001 R11:  R12: 0003
  kernel: R13: 0004 R14:  R15: b5801e235000
  kernel: FS:  7f1553fff700() GS:a20eff78() 
knlGS:
  kernel: CS:  0010 DS:  ES:  CR0: 80050033
  kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0
  kernel: PKRU: 5554
  kernel: Call Trace:
  kernel:  
  kernel:  ? __switch_to_xtra+0x109/0x510
  kernel:  zap_gfn_range+0x218/0x360 [kvm]
  kernel:  ? __smp_call_single_queue+0x59/0x90
  kernel:  ? alloc_cpumask_var_node+0x1/0x30
  kernel:  ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm]
  kernel:  kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm]
  kernel:  kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm]
  --
  kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab
  kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f
  kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470
  kernel: R10:  R11: 0246 R12: 7f1553ffe050
  kernel: R13: 7f1553ffe160 R14:  R15: 0080
  kernel:  

  The error occurred randomly in different production environments of the 
customer, all with the same call trace.
  Therefore, the likelihood of other processes contaminating memory is low.
  After analyzing the call trace with the help of debug symbols, we can 
pinpoint the source of the error.

  root@focal:~/ddeb# eu-addr2line -ifae 
./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko 
__handle_changed_spte+0x3a9
  0x00068109
  __list_del inlined at 
/build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 
in __handle_changed_spte
  /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13
  __list_del_entry
  /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2
  list_del
  /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2
  tdp_mmu_unlink_page
  
/build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2
  handle_removed_tdp_mmu_page
  
/build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2
  __handle_changed_spte
  
/build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3

  The error occurred when the kernel attempted to delete an entry from a list.
  This issue may potentially be related to timing and has proven challenging to 
reproduce consistently, making it difficult for us to pinpoint the cause.
  

[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Avoid address overwrite in kernel_connect

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-gkeop package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  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
Status in linux-gke source package in Jammy:
  Fix Released
Status in linux-gkeop source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-gcp source package in Lunar:
  Fix Released
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  This fix is requested to resolve an issue with NFS-backed mounts when
  used with BPF-load-balancing:

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

  
  Testing:
   - GCP has confirmed the fix works before proposing it upstream. I have 
verified basic network sanity with fix applied.

  
  Regression potenial:
   - The fix modifies kernel_connect() which can have an effect on all kinds of 
network connections. The change itself is very minor though and simply converts 
a pass-by-reference to a pass-by-value - so the risk is considered minimal.

  More information at:
  https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view

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


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

[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Timo Aaltonen]

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

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

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

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

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

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

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

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

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

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

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
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 Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  New
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

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


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

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

[Luke Dearden]

Ran into this issue just now.

Looks like new VMs in Azure North Europe are now being deployed with
6.2.0-1016-azure whereas earlier today it was 6.2.0-1015-azure

Our cifs mounts obviously fail now.

Is there a way to manually switch to 6.2.0-1015-azure?

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

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

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


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

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

[Ubuntu SRU Bot]

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

network-manager/1.44.2-1ubuntu1.2 (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/mantic/update_excuses.html#linux-meta

[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 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Timo Aaltonen]

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

Status in HWE Next:
  New
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

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


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

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

[JS]

Same issue here with 3.5 mm audio output - no issue via HDMI.

For sake of completeness: The workaround to add in /etc/modprobe.d/alsa-
base.conf a new last line "options snd-hda-intel power_save=0
power_save_controller=N" is not resolving but avoiding only the issue -
still presenting twice popping during shutdown.

---

My affected system:

System:
  Kernel: 5.15.0-88-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Intel Client Systems product: NUC8i5BEH v: J72747-302
serial:  Chassis: Intel Corporation type: 3 v: 2.0
serial: 
  Mobo: Intel model: NUC8BEB v: J72692-303 serial: 
UEFI: Intel v: BECFL357.86A.0094.2023.0612.1527 date: 06/12/2023
CPU:
  Info: quad core model: Intel Core i5-8259U bits: 64 type: MT MCP
smt: enabled arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB
L3: 6 MiB
  Speed (MHz): avg: 600 min/max: 400/3800 cores: 1: 600 2: 600 3: 600
4: 600 5: 600 6: 600 7: 600 8: 600 bogomips: 36799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
[...]
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9dc8 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-88-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
[...]

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 
3: 1000 4: 794
  5: 796 6: 3156 7: 799 8: 758 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 
v: kernel ports:
  active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI 
driver: nvidia
  v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 
10de:1d10
Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 
chip-ID: 0408:a030
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm 
(27")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 
23.0.4-0ubuntu1~22.04.1
  direct render: Yes
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
v: kernel pcie:
  speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb

[Kernel-packages] [Bug 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

[Luis Alberto Pabón]

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

Found it thank you, I was tripped up by the fact it doesn't show as an
update but of course it doesn't.

The kernel does seem to fix the nvme problem, but it introduces issues
potentially with the graphics stack (half size Plymouth spinner and
ubuntu logo on a 4k display and GDM hangs forever)

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

Title:
  [ kernel 6.5 regression ] nvme not working on some laptops

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

Bug description:
  With the update to Ubuntu 23.10 my nvme drive ceased to function.
  Booting the old 6.2 kernel from 23.04 works, but not the newer
  6.5.0-9.

  This is a kernel bug that's been fixed in 6.5.6, any chance it could
  possibly be backported?

  More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luis   3036 F wireplumber
   /dev/snd/controlC1:  luis   3036 F wireplumber
   /dev/snd/seq:luis   3029 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:05:29 2023
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2039755] ProcCpuinfo.txt

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 

[Kernel-packages] [Bug 2039755] RfKill.txt

[Alex Ball]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/2039755/+attachment/5714990/+files/RfKill.txt

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 R12: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 R12: 

[Kernel-packages] [Bug 2039755] IwConfig.txt

[Alex Ball]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/2039755/+attachment/5714978/+files/IwConfig.txt

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

[Kernel-packages] [Bug 2039755] Re: lernel crashes in CIFS code

[Alex Ball]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ab318  2365 F pulseaudio
 /dev/snd/controlC0:  ab318  2365 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: KDE neon 22.04
HibernationDevice: RESUME=UUID=51ff5047-545a-4d60-bce1-cb029fc539f1
InstallationDate: Installed on 2019-02-07 (1727 days ago)
InstallationMedia: neon user "Bionic" - Build amd64 LIVE Binary 20190124-05:42
MachineType: Dell Inc. Latitude 5591
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=a05625f1-a3f6-4856-8b6f-5ba0fb066079 ro quiet splash dis_ucode_ldr 
nosgx resume=UUID=51ff5047-545a-4d60-bce1-cb029fc539f1 vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-36-generic N/A
 linux-backports-modules-6.2.0-36-generic  N/A
 linux-firmware20220329.git681281e4-0ubuntu3.21
Tags:  jammy
Uname: Linux 6.2.0-36-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-10-25 (372 days ago)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.28
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.28.0
dmi.board.name: 0DVVG1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.28.0:bd07/04/2023:br1.28:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:sku0819:
dmi.product.family: Latitude
dmi.product.name: Latitude 5591
dmi.product.sku: 0819
dmi.sys.vendor: Dell Inc.


** Tags added: apport-collected

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm 

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

[Alex Ball]

apport information

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

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 R12: 

[Kernel-packages] [Bug 2039755] AlsaInfo.txt

[Alex Ball]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2039755/+attachment/5714975/+files/AlsaInfo.txt

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Chris Chiu]

** Changed in: linux (Ubuntu Jammy)
   Status: Invalid => In Progress

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

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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


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

[Kernel-packages] [Bug 2039755] Re: lernel crashes in CIFS code

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  lernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 

[Kernel-packages] [Bug 2039755] Re: lernel crashes in CIFS code

[Alex Ball]

This has started happening for me since upgrading linux-image-generic-
hwe-22.04 from 6.2.0.31.31~22.04.8 to 6.2.0.32.32~22.04.9. It is still
happening currently with 6.2.0.36.37~22.04.14.

I get this issue typically when (auto-) mounting or unmounting a CIFS
share that has VFS, resulting in a NULL pointer dereference in the
kernel and a soft lockup in the CPU. A recent example:

Oct 31 14:46:04 lipc-carsus kernel: [ cut here ]
Oct 31 14:46:04 lipc-carsus kernel: WARNING: CPU: 4 PID: 29475 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
Oct 31 14:46:04 lipc-carsus kernel: Modules linked in: nls_utf8 cifs cifs_arc4 
cifs_md4 fscache netfs authenc echainiv esp4 ccm rfcomm nft_masq xfrm_user 
xfrm_algo nft_chain_nat nf_nat bridge stp llc vhost_vsock 
vmw_vsock_virtio_transp>
Oct 31 14:46:04 lipc-carsus kernel:  soundwire_generic_allocation 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led 
snd_soc_acpi_intel_match snd_soc_a>
Oct 31 14:46:04 lipc-carsus kernel:  hid_multitouch mei intel_rapl_common 
intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone 
int3400_thermal dell_smo8800 intel_hid acpi_thermal_rel mac_hid acpi_pad 
sparse_keymap >
Oct 31 14:46:04 lipc-carsus kernel: CPU: 4 PID: 29475 Comm: umount Tainted: P   
OE  6.2.0-35-generic #35~22.04.1-Ubuntu
Oct 31 14:46:04 lipc-carsus kernel: Hardware name: Dell Inc. Latitude 
5591/0DVVG1, BIOS 1.28.0 07/04/2023
Oct 31 14:46:04 lipc-carsus kernel: RIP: 0010:__cifs_put_smb_ses+0x3dd/0x4d0 
[cifs]
Oct 31 14:46:04 lipc-carsus kernel: Code: e8 48 c7 c1 70 82 d5 c1 48 c7 c2 30 
34 d8 c1 41 89 c1 48 c7 c6 68 cf d6 c1 48 c7 c7 d0 97 dc c1 e8 a8 65 98 c8 e9 
21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 f7 1c c9 48 c7 c6
Oct 31 14:46:04 lipc-carsus kernel: RSP: 0018:a923d8067d20 EFLAGS: 00010286
Oct 31 14:46:04 lipc-carsus kernel: RAX:  RBX: 8a8d13f0eee8 
RCX: 
Oct 31 14:46:04 lipc-carsus kernel: RDX:  RSI:  
RDI: 
Oct 31 14:46:04 lipc-carsus kernel: RBP: a923d8067d50 R08:  
R09: 
Oct 31 14:46:04 lipc-carsus kernel: R10:  R11:  
R12: 8a8ddf627000
Oct 31 14:46:04 lipc-carsus kernel: R13: 8a8ddf627038 R14:  
R15: 8a8ddf627000
Oct 31 14:46:04 lipc-carsus kernel: FS:  7f7c7b2ac800() 
GS:8a906c30() knlGS:
Oct 31 14:46:04 lipc-carsus kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Oct 31 14:46:04 lipc-carsus kernel: CR2: 55b1b50e4400 CR3: 00039631e002 
CR4: 003706e0
Oct 31 14:46:04 lipc-carsus kernel: DR0:  DR1:  
DR2: 
Oct 31 14:46:04 lipc-carsus kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
Oct 31 14:46:04 lipc-carsus kernel: Call Trace:
Oct 31 14:46:04 lipc-carsus kernel:  
Oct 31 14:46:04 lipc-carsus kernel:  ? show_regs+0x72/0x90
Oct 31 14:46:04 lipc-carsus kernel:  ? __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  ? __warn+0x8d/0x160
Oct 31 14:46:04 lipc-carsus kernel:  ? __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  ? report_bug+0x1bb/0x1d0
Oct 31 14:46:04 lipc-carsus kernel:  ? handle_bug+0x46/0x90
Oct 31 14:46:04 lipc-carsus kernel:  ? exc_invalid_op+0x19/0x80
Oct 31 14:46:04 lipc-carsus kernel:  ? asm_exc_invalid_op+0x1b/0x20
Oct 31 14:46:04 lipc-carsus kernel:  ? __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  tconInfoFree+0x9b/0x110 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  cifs_put_tcon.part.0+0x109/0x2d0 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  cifs_put_tlink+0x4a/0x90 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  cifs_umount+0x59/0xb0 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  cifs_kill_sb+0x50/0x60 [cifs]
Oct 31 14:46:04 lipc-carsus kernel:  deactivate_locked_super+0x32/0xb0
Oct 31 14:46:04 lipc-carsus kernel:  deactivate_super+0x4a/0x60
Oct 31 14:46:04 lipc-carsus kernel:  cleanup_mnt+0x105/0x170
Oct 31 14:46:04 lipc-carsus kernel:  __cleanup_mnt+0x12/0x20
Oct 31 14:46:04 lipc-carsus kernel:  task_work_run+0x5e/0xa0
Oct 31 14:46:04 lipc-carsus kernel:  exit_to_user_mode_loop+0x111/0x140
Oct 31 14:46:04 lipc-carsus kernel:  exit_to_user_mode_prepare+0xb9/0xd0
Oct 31 14:46:04 lipc-carsus kernel:  syscall_exit_to_user_mode+0x2a/0x60
Oct 31 14:46:04 lipc-carsus kernel:  do_syscall_64+0x69/0x90
Oct 31 14:46:04 lipc-carsus kernel:  ? do_syscall_64+0x69/0x90
Oct 31 14:46:04 lipc-carsus kernel:  ? exc_page_fault+0x92/0x1b0
Oct 31 14:46:04 lipc-carsus kernel:  entry_SYSCALL_64_after_hwframe+0x73/0xdd
Oct 31 14:46:04 lipc-carsus kernel: RIP: 0033:0x7f7c7b125c2b
Oct 31 14:46:04 lipc-carsus kernel: Code: 0b 32 0f 00 f7 d8 64 89 01 48 83 c8 
ff c3 90 f3 0f 1e fa 31 f6 e9 05 00 00 00 0f 1f 

[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

[Luis Alberto Pabón]

I have tested linux/6.5.0-12 and it's been a mixed bag:


 * The nvme fix seems to work, I can see my services loading and whatnot on the 
boot log 
 * The Plymouth theme displays at half the size than with other kernels (I have 
a 4k display with intel integrated graphics and nvidia gtx 1050 which I never 
use) 
 * GDM fails to load and hangs forever. I can't switch to any TTYs. The system 
isn't hard-blocked though, it reacts to ctrl+alt+del and reboots 

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

  
  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

[Launchpad Bug Tracker]

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

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

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 
3: 1000 4: 794
  5: 796 6: 3156 7: 799 8: 758 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 
v: kernel ports:
  active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI 
driver: nvidia
  v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 
10de:1d10
Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 
chip-ID: 0408:a030
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm 
(27")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 
23.0.4-0ubuntu1~22.04.1
  direct render: Yes
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
v: kernel pcie:
  speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
IF: wlp3s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Acer Incorporated ALI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 
04:00.1
  chip-ID: 10ec:8168
IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
Local Storage: total: 1.36 TiB used: 143.29 GiB (10.3%)
ID-1: /dev/sda model: SD Ultra 3D 1TB size: 931.51 GiB speed: 6.0 Gb/s 
serial: 
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB 
speed: 6.0 Gb/s
  serial: 
  Partition:
ID-1: / size: 915.32 GiB used: 143.28 GiB (15.7%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
  Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: 
/swapfile
  Sensors:
System Temperatures: cpu: 48.0 C pch: 37.0 C mobo: N/A
Fan Speeds (RPM): N/A
  Repos:
Packages: 3240 apt: 3217 flatpak: 23
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-jammy.list
  1: deb [signed-by=/etc/apt/keyrings/audio-recorder-ppa-jammy.gpg] https: 
//ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu jammy main
Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
  1: deb http: //packages.linuxmint.com 

[Kernel-packages] [Bug 2033869] Re: linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-iotg-b

[Ionut Nechita]

** Summary changed:

- linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-iotg-b
+ linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-iotg-b

** Description changed:

- linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-
+ linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-
  iotg-b

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

Title:
  linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-
  iotg-b

Status in linux-intel-iotg package in Ubuntu:
  New

Bug description:
  linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-
  iotg-b

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


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

[Kernel-packages] [Bug 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

[Luis Alberto Pabón]

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

The newest kernel available for mantic, including "proposed", is
6.5.0-10, where did you see -12?

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

Title:
  [ kernel 6.5 regression ] nvme not working on some laptops

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

Bug description:
  With the update to Ubuntu 23.10 my nvme drive ceased to function.
  Booting the old 6.2 kernel from 23.04 works, but not the newer
  6.5.0-9.

  This is a kernel bug that's been fixed in 6.5.6, any chance it could
  possibly be backported?

  More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luis   3036 F wireplumber
   /dev/snd/controlC1:  luis   3036 F wireplumber
   /dev/snd/seq:luis   3029 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:05:29 2023
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 2040157
   Unable to use nvme drive to install Ubuntu 23.10

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

Title:
  [ kernel 6.5 regression ] nvme not working on some laptops

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

Bug description:
  With the update to Ubuntu 23.10 my nvme drive ceased to function.
  Booting the old 6.2 kernel from 23.04 works, but not the newer
  6.5.0-9.

  This is a kernel bug that's been fixed in 6.5.6, any chance it could
  possibly be backported?

  More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luis   3036 F wireplumber
   /dev/snd/controlC1:  luis   3036 F wireplumber
   /dev/snd/seq:luis   3029 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:05:29 2023
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Juerg Haefliger]

Installed linux-tools-common 6.2.0-38.39 from lunar-proposed and
verified that hwdata is installed as a dependency.


** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Juerg Haefliger]

Installed linux-tools-common 5.15.0-90.100 from jammy-proposed and
verified that hwdata is installed as a dependency.


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

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Juerg Haefliger]

Installed linux-tools-common 6.5.0-12.12 from mantic-proposed and
verified that hwdata is installed as a dependency.

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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

[Kernel-packages] [Bug 2042428] [NEW] 10–20 second hang/freeze after resume from S3 sleep

[Mikko Rantalainen]

Public bug reported:

I'm using XFCE + picom for my graphical desktop and the system is using
Nvidia GTX 1060 3 GB graphics adapter. Whenever the system is waking
from S3 sleep, the graphical desktop freezes once for 10–20 seconds when
I resize any existing window or launch a new program.

$ apt policy nvidia-driver-535
nvidia-driver-535:
  Installed: 535.113.01-0ubuntu0.22.04.3
  Candidate: 535.113.01-0ubuntu0.22.04.3
  Version table:
 *** 535.113.01-0ubuntu0.22.04.3 500
500 http://fi.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 
Packages
100 /var/lib/dpkg/status

It seems that Nvidia has published new version 535.129.03 at
https://www.nvidia.com/download/driverResults.aspx/213194/en-us/ and its
changelog mentions following:

- Fixed a bug that intermittently caused the display to freeze when
resuming from suspend on some Ada GPUs.

The 1060 shouldn't be included in Ada family but I wouldn't be surprised
if the underlying problem were the same.

Here's the picom command line I'm using in case it makes a difference:

picom --config /dev/null  --log-file /dev/null --shadow -o 0.20 -r 8 -l
-8 -t -8  --corner-radius 4 --backend glx --glx-no-stencil --glx-no-
rebind-pixmap --no-use-damage --vsync --vsync-use-glfinish --shadow-
exclude '_GTK_FRAME_EXTENTS@:c' --shadow-exclude "name ?= 'Thunderbird'
&& (window_type = 'utility' || window_type = 'popup_menu')" --no-fading-
openclose --unredir-if-possible --unredir-if-possible-delay 500

The problem seems to happen even without using picom, but the use of
picom seems to trigger the issue after every resume from S3. The problem
is big enough to increase the S3 resume time for ~30 seconds in practice
because the system is unusable until the freeze goes away.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-535 535.113.01-0ubuntu0.22.04.3
ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-lowlatency 6.2.16
Uname: Linux 6.2.0-1015-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Nov  1 11:58:39 2023
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1760 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: Upgraded to jammy on 2023-08-11 (82 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158

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


** Tags: amd64 apport-bug jammy

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

Title:
  10–20 second hang/freeze after resume from S3 sleep

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

Bug description:
  I'm using XFCE + picom for my graphical desktop and the system is
  using Nvidia GTX 1060 3 GB graphics adapter. Whenever the system is
  waking from S3 sleep, the graphical desktop freezes once for 10–20
  seconds when I resize any existing window or launch a new program.

  $ apt policy nvidia-driver-535
  nvidia-driver-535:
Installed: 535.113.01-0ubuntu0.22.04.3
Candidate: 535.113.01-0ubuntu0.22.04.3
Version table:
   *** 535.113.01-0ubuntu0.22.04.3 500
  500 http://fi.archive.ubuntu.com/ubuntu jammy-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  It seems that Nvidia has published new version 535.129.03 at
  https://www.nvidia.com/download/driverResults.aspx/213194/en-us/ and
  its changelog mentions following:

  - Fixed a bug that intermittently caused the display to freeze when
  resuming from suspend on some Ada GPUs.

  The 1060 shouldn't be included in Ada family but I wouldn't be
  surprised if the underlying problem were the same.

  Here's the picom command line I'm using in case it makes a difference:

  picom --config /dev/null  --log-file /dev/null --shadow -o 0.20 -r 8
  -l -8 -t -8  --corner-radius 4 --backend glx --glx-no-stencil --glx-
  no-rebind-pixmap --no-use-damage --vsync --vsync-use-glfinish
  --shadow-exclude '_GTK_FRAME_EXTENTS@:c' --shadow-exclude "name ?=
  'Thunderbird' && (window_type = 'utility' || window_type =
  'popup_menu')" --no-fading-openclose --unredir-if-possible --unredir-
  if-possible-delay 500

  The problem seems to happen even without using picom, but the use of
  picom seems to trigger the issue after every resume from S3. The
  problem is big enough to increase the S3 resume time for ~30 seconds
  in practice because the system is unusable until the freeze 

[Kernel-packages] [Bug 2042426] [NEW] Introduce the new NVIDIA 545 driver series

[Alberto Milone]

Public bug reported:

Introduce the new NVIDIA 545 driver series.

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Medium
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-535 (Ubuntu Focal)
 Importance: Medium
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-535 (Ubuntu Jammy)
 Importance: Medium
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-535 (Ubuntu Lunar)
 Importance: Medium
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-535 (Ubuntu Mantic)
 Importance: Medium
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  Introduce the new NVIDIA 545 driver series

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Lunar:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Mantic:
  In Progress

Bug description:
  Introduce the new NVIDIA 545 driver series.

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


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

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

[Timo Aaltonen]

..but instead wait until they get applied via upstream stable

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
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:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

[Timo Aaltonen]

I mean that there's no need to add hwe-* as being affected, because the
parent kernel for hwe-6.2 is lunar, and it's already covered here.

And I'm actually reluctant to add these to oem kernels, because they'd
need to be tested as well.

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
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:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions


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

[Kernel-packages] [Bug 2042074] Re: missing mei_vsc firmware for HM2172 and OV02E sensor

[Juerg Haefliger]

** Tags added: kern-8451

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

Title:
  missing mei_vsc firmware for HM2172 and OV02E sensor

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

Bug description:
  [ 5.880936] mei_vsc spi-INTC10D0:00: Direct firmware load for 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin failed with error -2
  [ 5.880940] mei_vsc spi-INTC10D0:00: file not found 
vsc/soc_a1_prod/ivsc_pkg_ovti02e1_0_a1_prod.bin
  [ 5.880958] mei_vsc spi-INTC10D0:00: hw_reset failed ret = -19
  [ 5.880959] mei_vsc spi-INTC10D0:00: reset failed ret = -19
  [ 5.880960] mei_vsc spi-INTC10D0:00: link layer initialization failed.
  [ 5.880974] mei_vsc spi-INTC10D0:00: init hw failure.

  Upstream commit in https://github.com/intel/ivsc-
  firmware/commit/4f15196c0dcb7b71981cfe24015336eefd9a7bc8

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


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

[Kernel-packages] [Bug 2042088] Re: package linux-headers-6.2.0-36-generic 6.2.0-36.37 failed to install/upgrade: installed linux-headers-6.2.0-36-generic package post-installation script subprocess r

[Juerg Haefliger]

That DKMS modules is unsupported and breaks kernel header installation.
Please remove it.

$ dkms remove rtl88x2bu/git


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

Title:
  package linux-headers-6.2.0-36-generic 6.2.0-36.37 failed to
  install/upgrade: installed linux-headers-6.2.0-36-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Building module:
  Cleaning build area...
  'make' -j2 KVER=6.2.0-36-generic 
KSRC=/lib/modules/6.2.0-36-generic/build(bad
 exit status: 2)
  ERROR (dkms apport): binary package for rtl88x2bu: git not found
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/rtl88x2bu/git/build/make.log for more information.
  dkms autoinstall on 6.2.0-36-generic/x86_64 failed for rtl88x2bu(10)
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
   * dkms: autoinstall for kernel 6.2.0-36-generic
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: hiba a csomag feldolgozásakor: linux-headers-6.2.0-36-generic 
(--configure):
   installed linux-headers-6.2.0-36-generic package post-installation script 
subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-36-generic 6.2.0-36.37
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  judit  1646 F wireplumber
   /dev/snd/controlC1:  judit  1646 F wireplumber
   /dev/snd/seq:judit  1633 F pipewire
  CasperMD5CheckResult: unknown
  Date: Tue Oct 31 13:22:38 2023
  ErrorMessage: installed linux-headers-6.2.0-36-generic package 
post-installation script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=10cf95da-595a-4987-b599-d61cbfc17ca1
  InstallationDate: Installed on 2016-10-16 (2570 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUSTeK Computer INC. VM40B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=9f5d1bb4-4b33-449e-a155-45aba2c59da2 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.2.0-36-generic 6.2.0-36.37 failed to 
install/upgrade: installed linux-headers-6.2.0-36-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-14 (108 days ago)
  dmi.bios.date: 12/09/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: VM40B
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd12/09/2014:br4.6:svnASUSTeKComputerINC.:pnVM40B:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnVM40B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: VM40B
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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


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

[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Timo Aaltonen]

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

** No longer affects: linux-oem-6.1 (Ubuntu)

** No longer affects: linux (Ubuntu Jammy)

** No longer affects: linux-oem-6.5 (Ubuntu Jammy)

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

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

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

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

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => Fix Committed

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

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

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => Fix Committed

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

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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 Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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


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

[Kernel-packages] [Bug 2031287] Re: sysdig-dkms failed to build with J-6.5

[Po-Hsu Lin]

This is affecting other J-6.5 variants as well (jammy-linux-ibm-gt-opt,
jammy-linux-aws)


** Summary changed:

- sysdig-dkms failed to build with J-oem-6.5
+ sysdig-dkms failed to build with J-6.5

** Tags added: aws

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

Title:
  sysdig-dkms failed to build with J-6.5

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Confirmed

Bug description:
  ubuntu_sysdig_smoke_test failed because of sysdig DKMS build failed
  with J-oem-6.5

   Error! Bad return status for module build on kernel: 6.5.0-1002-oem (x86_64)
   Consult /var/lib/dkms/sysdig/0.27.1/build/make.log for more information.
   dpkg: error processing package sysdig-dkms (--configure):
installed sysdig-dkms package post-installation script subprocess returned 
error exit status 10
   Processing triggers for man-db (2.10.2-1) ...
   Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
   Errors were encountered while processing:
sysdig-dkms
   needrestart is being skipped since dpkg has failed
   W: --force-yes is deprecated, use one of the options starting with --allow 
instead.
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   Running 'dkms status -m sysdig | grep installed'
   Running 'cat /var/lib/dkms/sysdig/*/build/make.log'
   DKMS make.log for sysdig-0.27.1 for kernel 6.5.0-1002-oem (x86_64)
   Thu Aug 10 12:17:20 UTC 2023
   make: Entering directory '/usr/src/linux-headers-6.5.0-1002-oem'
   warning: the compiler differs from the one used to build the kernel
 The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 
12.3.0-1ubuntu1~22.04) 12.3.0
 You are using:   gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
 CC [M]  /var/lib/dkms/sysdig/0.27.1/build/main.o
 CC [M]  /var/lib/dkms/sysdig/0.27.1/build/dynamic_params_table.o
 CC [M]  /var/lib/dkms/sysdig/0.27.1/build/fillers_table.o
 CC [M]  /var/lib/dkms/sysdig/0.27.1/build/flags_table.o
 CC [M]  /var/lib/dkms/sysdig/0.27.1/build/ppm_events.o
   In file included from ./include/linux/linkage.h:7,
from ./arch/x86/include/asm/cache.h:5,
from ./include/linux/cache.h:6,
from ./arch/x86/include/asm/current.h:9,
from ./include/linux/sched.h:12,
from ./arch/x86/include/asm/syscall.h:14,
from /var/lib/dkms/sysdig/0.27.1/build/main.c:19:
   /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘sysdig_init’:
   ./include/linux/export.h:29:22: error: passing argument 1 of ‘class_create’ 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  29 | #define THIS_MODULE (&__this_module)
 | ~^~~
 |  |
 |  struct module *
   /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:36: note: in expansion of 
macro ‘THIS_MODULE’
2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME);
 |^~~
   In file included from ./include/linux/device.h:31,
from ./include/linux/cdev.h:8,
from /var/lib/dkms/sysdig/0.27.1/build/main.c:26:
   ./include/linux/device/class.h:230:54: note: expected ‘const char *’ but 
argument is of type ‘struct module *’
 230 | struct class * __must_check class_create(const char *name);
 |  ^~~~
   /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:23: error: too many arguments 
to function ‘class_create’
2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME);
 |   ^~~~
   ./include/linux/device/class.h:230:29: note: declared here
 230 | struct class * __must_check class_create(const char *name);
 | ^~~~
   cc1: some warnings being treated as errors
   make[2]: *** [scripts/Makefile.build:251: 
/var/lib/dkms/sysdig/0.27.1/build/main.o] Error 1
   make[2]: *** Waiting for unfinished jobs
   make[1]: *** [/usr/src/linux-headers-6.5.0-1002-oem/Makefile:2037: 
/var/lib/dkms/sysdig/0.27.1/build] Error 2
   make: *** [Makefile:234: __sub-make] Error 2
   make: Leaving directory '/usr/src/linux-headers-6.5.0-1002-oem'

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


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

[Kernel-packages] [Bug 2039405] Re: Unable to power off the system with MTL CPU

[AceLan Kao]

** Tags removed: verification-needed-jammy-linux-oem-6.5 
verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux-oem-6.5 
verification-done-mantic-linux

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

Title:
  Unable to power off the system with MTL CPU

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:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The commit introduced from v6.4 leads to the power off issue
  45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible

  [Fix]
  The problematic commit has been reverted since v6.6
  fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible"

  [Test case]
  1. Power up the MTL system
  2. Power off the system and make sure it shutdown correctly

  [Where problems could occur]
  From the origin commit log, revert the commit may have a protential security 
issue.

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


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

[Kernel-packages] [Bug 2039405] Re: Unable to power off the system with MTL CPU

[Timo Aaltonen]

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Unable to power off the system with MTL CPU

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:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The commit introduced from v6.4 leads to the power off issue
  45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible

  [Fix]
  The problematic commit has been reverted since v6.6
  fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible"

  [Test case]
  1. Power up the MTL system
  2. Power off the system and make sure it shutdown correctly

  [Where problems could occur]
  From the origin commit log, revert the commit may have a protential security 
issue.

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


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

[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Timo Aaltonen]

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  New

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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


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

[Kernel-packages] [Bug 2042000] Re: 6.2.0-36 kills usb wifi

[Juerg Haefliger]

Can you attach the journal log from one of the runs with kernel 6.2.0-36?
$ sudo journalctl -b -1

Adjust the '-1' (previous boot) above to find a boot of kernel -36.


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

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

Title:
  6.2.0-36 kills usb wifi

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed the kernel update from 6.2.0-35 to 6.2.0-36 today (Oct 30,
  2023). After reboot, USB WiFi dongle was no longer recognised.
  Rebooted into previous kernel (6.2.0-35) and have no issue. Not sure
  what broke, or if it is a regression of some sort. Also, how to upload
  the bug as stated below, when booting into that kernel does not allow
  WiFi connection.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Timo Aaltonen]

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in ipu6-drivers source package in Mantic:
  New
Status in ivsc-driver source package in Mantic:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come according to Intel.

  These two fixes are therefore for related components for not-yet fully
  upstreamed IPU6 as needed for out-of-tree dkms drivers.

  [Test Case]

  ```
  $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU"
  $ sudo dmesg | grep int3472
  # should 

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in ipu6-drivers source package in Mantic:
  New
Status in ivsc-driver source package in Mantic:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, 

[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

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


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

[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

[Ubuntu Kernel Bot]

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


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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

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


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

[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  allow io_uring to be disabled in runtime

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  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 source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  io_uring has been an important attack vector in the recent years in local 
privilege escalation attacks. Allowing admins that don't use io_uring to 
disable it in their systems allows them to reduce their attack surface.

  [Test case]
  sysctl -w kernel.io_uring_disabled=1
  then try to use io_uring from an unprivileged user, then try it with 
privileges (CAP_SYS_ADMIN)

  Actually also tried setting kernel.io_uring_disabled=2 and checking that
  neither (privileged or unprivileged worked).

  Then testing setting it back to 0.

  Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and
  that it worked for group 1000, then set it to 1001 and verified that it
  didn't work anymore for group 1000.

  
  [Potential regression]
  Uses can be denied from using io_uring.

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


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

[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Infinite systemd loop when power off the machine with multiple MD
  RAIDs

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:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The system with multiple MD RAIDs sometimes hangs while rebooting, that's 
because of the systemd can't stop and close the MD disk.

  [Fix]
  This commit fixes the issue, and this issue has been introduced by 
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed") 
after v6.0

  https://patchwork.kernel.org/project/linux-
  raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/

  [Test case]
  1. Reboot the system with multiple MD RAIDs at least 10 times.
  2. Make sure the system can reboot successfully every time.
  3. You should not see error messages like below.

  [ 205.360738] systemd-shutdown[1]: Stopping MD devices.
  [ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
  [ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
  [ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
  [ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
  [ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127, 
ignoring: Input/output error
  [ 205.404975] md: md127 stopped.
  [ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
  [ 205.770179] md: md126: resync interrupted.
  [ 205.776258] md126: detected capacity change from 1900396544 to 0
  [ 205.783349] md: md126 stopped.
  [ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
  [ 205.862435] md: md126 stopped.
  [ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125, 
ignoring: Input/output error
  [ 205.872845] block device autoloading is deprecated and will be removed.
  [ 205.880955] md: md125 stopped.
  [ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
  [ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or 
resource busy
  [ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
  [ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or 
resource busy
  [ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
  [ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or 
resource busy
  [ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.

  [Where problems could occur]
  It fixes the data race issue, should not introduce any regression.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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

[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
  multimedia and PCIE peripherals

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]
  IOMMU related peripherals cannot work.

  [Fix]
  CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency.

  [Test Case]
  build test.
  this is the first step to enable the platform on generic kernel. to fully 
enable the platform, there are some modifications still needed, so only the 
build test is performed at this stage.

  [Where problems could occur]
  to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be 
built-in. the risk would be low because it's not used by default and it needs 
the driver to allocate by demand.

  [Other info]
  the purpose of this is to make ubuntu as an arm systemready ir distribution 
for mediatek platform.

  https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady-
  IR/Test-installation-of-Linux-distributions?lang=en

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


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

[Kernel-packages] [Bug 2036377] Re: Fix RCU warning on AMD laptops

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Fix RCU warning on AMD laptops

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:
  Won't Fix
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 Released
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 Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Scary kernel splat about RCU can be observed everytime laptop resumes
  from suspend.

  [Fix]
  Use non-atomic notifier for power supply change to relax the constraint.

  [Test]
  Once the fix is applied, no more RCU warning can be found after several
  suspend/resume cycle.

  [Where problems could occur]
  Essentially no regression potential. Atomic notifier should be used by
  core kernel, and things like power supply doesn't need to be atomic
  anyway.

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


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

[Kernel-packages] [Bug 2037273] Re: Realtek 8852CE WiFi 6E country code udpates

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Realtek 8852CE WiFi 6E country code udpates

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:
  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:
  [SRU Justification]

  [Impact]

  Missing WiFi 6G band for interested countries.

  [Fix]

  Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
  regulatory map to R64-R43").

  [Test Case]

  Use `iw list` to check if 6G bands are then enabled.

  [Where problems could occur]

  This enables corresponding 6G bands for rtw89 driven devices. There
  should be no other side effects.

  [Other Info]

  Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable
  is skipped.

  = original bug report ==

  Proposed fix: 
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
  Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update 
regulatory map to R64-R43") and is in v6.6-rc1 now.

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


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

[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Fix unstable audio at low levels on Thinkpad P1G4

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 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 source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The audio at low levels is not stable with fluctuating levels.

  [Fix]
  Forcibly assign NID 0x03 to HP while NID 0x02 to SPK.

  [Test]
  Tested on hardware, the audio output is OK at all levels.

  [Where problems could occur]
  It may break audio output on Thinkpad P1G4/5.

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


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

[Kernel-packages] [Bug 2039405] Re: Unable to power off the system with MTL CPU

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Unable to power off the system with MTL CPU

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:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The commit introduced from v6.4 leads to the power off issue
  45e34c8af58f x86/smp: Put CPUs into INIT on shutdown if possible

  [Fix]
  The problematic commit has been reverted since v6.6
  fbe1bf1e5ff1 Revert "x86/smp: Put CPUs into INIT on shutdown if possible"

  [Test case]
  1. Power up the MTL system
  2. Power off the system and make sure it shutdown correctly

  [Where problems could occur]
  From the origin commit log, revert the commit may have a protential security 
issue.

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


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

[Kernel-packages] [Bug 2038522] Re: disable shiftfs

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  disable shiftfs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Now that all the filesystems that we officially support have the
  idmapped mounts capability we can get rid of shiftfs.

  The benefit of this change is that we don't have to maintain an out-
  of-tree filesystem anymore and we can completely rely on upstream
  features.

  [Test case]

  lxd was the main user of shiftfs to compensate the lack of idmapped
  mounts capability of certain filesystems, such as zfs / ceph, but now
  in mantic also these two filesystem received the support for idmapped
  mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see
  LP: #2032959).

  The lxd team provided a positive feedback, testing the latest 6.5
  Mantic kernel across all the supported filesystems with shiftfs
  disabled.

  [Fix]

  Disable shiftfs in the kernel config and enable unsafe idmapped mounts
  by default (default=on).

  [Regression potential]

  The support for idmapped mounts for the ceph filesystem is not applied
  upstream yet, so we may experience regressions in systems that are
  using this filesystem. Moreover disabling shiftfs may trigger failures
  in our testing (testing shiftfs capabilities will obviously fail) or
  break any other user-space application that is relying on shiftfs
  (however to our knowledge lxd was the only "official" user or shiftfs;
  for this reason we may also see potential regressions in lxd).

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


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

[Kernel-packages] [Bug 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5

[Ubuntu Kernel Bot]

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


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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  drop all references to is_rust_module.sh in kernels >= 6.5

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  The script tools/is_rust_module.sh has been dropped by this commit:

079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
  is_rust_module.sh")

  And upstream as well (in 6.6):

41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")

  But we still have a reference of it in debian.master/reconstruct and
  that generates the following warning during the build:

chmod: cannot access 'scripts/is_rust_module.sh': No such file or
  directory

  [Fix]

  Drop the reference to is_rust_module.sh from reconstruct to prevent
  unnecessary warnings during the build.

  [Test case]

  The following command ran from the kernel source directory is enough
  to trigger the warning:

   $ fakeroot debian/rules clean

  [Regression potential]

  This change is affecting only our packaging. The change is trivial but
  it might affect our kernel build process in case of regressions.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Ubuntu Kernel Bot]

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


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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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