[Kernel-packages] [Bug 1876867] Re: [nvidia] Xorg process loads CPU heavily after resuming suspended laptop HP Probook 470 G4
I don't experience this issue anymore, it can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1876867 Title: [nvidia] Xorg process loads CPU heavily after resuming suspended laptop HP Probook 470 G4 Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The issue is triggered by waking my notebook up after suspending. After that CPU is loaded heavily, and I have to re-boot. The computer does not shut down properly and I have to press the button to turn it off. After re-booting I do not have this issue until I suspend my notebook again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Tue May 5 10:21:00 2020 DistUpgraded: 2020-04-24 12:29:55,077 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed wireguard, 1.0.20200413, 5.4.0-26-generic, x86_64: installed (WARNING! Diff between built and installed module!) wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8234] Subsystem: Hewlett-Packard Company GM108M [GeForce 930MX] [103c:8235] InstallationDate: Installed on 2018-01-06 (849 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP ProBook 470 G4 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=5ac056d5-340c-477d-9cd9-1f55a90552ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (10 days ago) dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.08 dmi.board.name: 8234 dmi.board.vendor: HP dmi.board.version: KBC Version 42.6A dmi.chassis.asset.tag: 5CD724DH2V dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.08:bd10/17/2017:svnHP:pnHPProBook470G4:pvr:rvnHP:rn8234:rvrKBCVersion42.6A:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 470 G4 dmi.product.sku: W6R39AV dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon May 4 11:37:08 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1876867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
I have installed them by installed linux-generic, and today i install the latest official 5.4.0-91 kernel, but it is even worse now. mount command: mount -t cifs //192.168.58.13/share /mnt/share/ -o username=guest,password=,noperm,noacl,file_mode=0644,iocharset=utf8,vers=2.1 Server is a windows server 2019 without any changes during the issues. In 5.4.0-91, it seems that cifs is not loaded automatically, and after i modprobe cifs, it still fails with "mount error(13): Permission denied" with dmesg [ 189.086484] CIFS: Attempting to mount //192.168.58.13/share [ 189.090361] CIFS VFS: could not allocate crypto cmac(aes) [ 189.093222] CIFS VFS: could not allocate crypto cmac(aes) [ 189.099002] CIFS VFS: could not allocate crypto md4 [ 189.099789] Status code returned 0xc06d STATUS_LOGON_FAILURE [ 189.099796] CIFS VFS: \\192.168.58.13 Send error in SessSetup = -13 [ 189.099923] CIFS VFS: cifs_mount failed w/return code = -13 If i rollback to 5.4.0-89, everything works fine. > dpkg -l |fgrep -- -89 ii linux-headers-5.4.0-89 5.4.0-89.100 all Header files related to Linux kernel version 5.4.0 ii linux-headers-5.4.0-89-generic 5.4.0-89.100 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-image-5.4.0-89-generic 5.4.0-89.100 amd64Signed kernel image generic ii linux-modules-5.4.0-89-generic 5.4.0-89.100 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-extra-5.4.0-89-generic 5.4.0-89.100 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-tools-5.4.0-89 5.4.0-89.100 amd64Linux kernel version specific tools for version 5.4.0-89 ii linux-tools-5.4.0-89-generic 5.4.0-89.100 amd64Linux kernel version specific tools for version 5.4.0-89 > dpkg -l |fgrep -- -91 ii linux-headers-5.4.0-91 5.4.0-91.102 all Header files related to Linux kernel version 5.4.0 ii linux-headers-5.4.0-91-generic 5.4.0-91.102 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-image-5.4.0-91-generic 5.4.0-91.102 amd64Signed kernel image generic ii linux-modules-5.4.0-91-generic 5.4.0-91.102 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-extra-5.4.0-91-generic 5.4.0-91.102 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-tools-5.4.0-91 5.4.0-91.102 amd64Linux kernel version specific tools for version 5.4.0-91 ii linux-tools-5.4.0-91-generic 5.4.0-91.102 amd64Linux kernel version specific tools for version 5.4.0-91 ii linux-tools-common 5.4.0-91.102 all Linux kernel version specific tools for version 5.4.0 > uname -r 5.4.0-91-generic -- 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/1952094 Title: CIFS mount error: iocharset utf8 not found Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: After i apt upgrade from linux-image-5.4.0-89-generic to linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS mount error: iocharset utf8 not found", and i rollback it and it restores. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 20:16 seq crw-rw 1 root audio 116, 33 Nov 24 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-07 (109 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 hyperv_fb ProcKernelCmdLine:
[Kernel-packages] [Bug 1952568] Re: AMD GPU kernel driver unload error
As far as the patches in other files are concerned, it should have been
as follows.
--
--- /usr/local/src/5.14.0.git/focal/drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c
2021-11-29 22:43:48.637432730 +
+++ uvd_v6_0.c 2021-11-30 06:54:01.572401893 +
@@ -543,30 +543,8 @@
{
struct amdgpu_device *adev = (struct amdgpu_device *)handle;
- /*
-* Proper cleanups before halting the HW engine:
-* - cancel the delayed idle work
-* - enable powergating
-* - enable clockgating
-* - disable dpm
-*
-* TODO: to align with the VCN implementation, move the
-* jobs for clockgating/powergating/dpm setting to
-* ->set_powergating_state().
-*/
cancel_delayed_work_sync(>uvd.idle_work);
- if (adev->pm.dpm_enabled) {
- amdgpu_dpm_enable_uvd(adev, false);
- } else {
- amdgpu_asic_set_uvd_clocks(adev, 0, 0);
- /* shutdown the UVD block */
- amdgpu_device_ip_set_powergating_state(adev,
AMD_IP_BLOCK_TYPE_UVD,
- AMD_PG_STATE_GATE);
- amdgpu_device_ip_set_clockgating_state(adev,
AMD_IP_BLOCK_TYPE_UVD,
- AMD_CG_STATE_GATE);
- }
-
if (RREG32(mmUVD_STATUS) != 0)
uvd_v6_0_stop(adev);
@@ -578,6 +556,30 @@
int r;
struct amdgpu_device *adev = (struct amdgpu_device *)handle;
+ /*
+ * Proper cleanups before halting the HW engine:
+ * - cancel the delayed idle work
+ * - enable powergating
+ * - enable clockgating
+ * - disable dpm
+ *
+ * TODO: to align with the VCN implementation, move the
+ * jobs for clockgating/powergating/dpm setting to
+ * ->set_powergating_state().
+ */
+cancel_delayed_work_sync(>uvd.idle_work);
+
+if (adev->pm.dpm_enabled) {
+amdgpu_dpm_enable_uvd(adev, false);
+} else {
+amdgpu_asic_set_uvd_clocks(adev, 0, 0);
+/* shutdown the UVD block */
+amdgpu_device_ip_set_powergating_state(adev,
AMD_IP_BLOCK_TYPE_UVD,
+ AMD_PG_STATE_GATE);
+amdgpu_device_ip_set_clockgating_state(adev,
AMD_IP_BLOCK_TYPE_UVD,
+ AMD_CG_STATE_GATE);
+}
+
r = uvd_v6_0_hw_fini(adev);
if (r)
return r;
--
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1952568
Title:
AMD GPU kernel driver unload error
Status in linux-oem-5.14 package in Ubuntu:
New
Bug description:
After updating the kernel from 5.14.0-1005 to 5.14.0-1007 on ubuntu20.04, if
you unload the driver with the following command, the command will be forcibly
terminated and the driver cannot be unloaded.
Can be unloaded with 5.14.0-1005 without any problem
sudo modprob -s -r amdgpu
Driver information in lsmod
-
sudo lsmod |grep amdgpu
amdgpu 7049216 -1
iommu_v2 24576 1 amdgpu
gpu_sched 36864 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
ttm73728 2 amdgpu,drm_ttm_helper
drm_kms_helper258048 1 amdgpu
drm 557056 6
gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm
i2c_algo_bit 16384 2 igb,amdgpu
-
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-modules-5.14.0-1007-oem 5.14.0-1007.7
ProcVersionSignature: Ubuntu 5.14.0-1007.7-oem 5.14.14
Uname: Linux 5.14.0-1007-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Mon Nov 29 13:46:48 2021
InstallationDate: Installed on 2019-07-24 (858 days ago)
InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64
(20190416.1)
SourcePackage: linux-oem-5.14
UpgradeStatus: Upgraded to focal on 2020-05-02 (575 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1952568/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
@BinLi This patch will be merged by stable updates in v5.14.19. For 5.13, we didn't have plan to support s2idle in current projects. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
@aaron, Could you help backport the new patches into oem kernel and add the new firmware again? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952568] Re: AMD GPU kernel driver unload error
Confirmed that unloading works fine with PPA mainline kernel 5.14.21 and 5.15.5. Confirmed that unloading works without any problem when driver / gpu / drm / amd of 5.14.0-1006 is imported to 1007. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952568 Title: AMD GPU kernel driver unload error Status in linux-oem-5.14 package in Ubuntu: New Bug description: After updating the kernel from 5.14.0-1005 to 5.14.0-1007 on ubuntu20.04, if you unload the driver with the following command, the command will be forcibly terminated and the driver cannot be unloaded. Can be unloaded with 5.14.0-1005 without any problem sudo modprob -s -r amdgpu Driver information in lsmod - sudo lsmod |grep amdgpu amdgpu 7049216 -1 iommu_v2 24576 1 amdgpu gpu_sched 36864 1 amdgpu drm_ttm_helper 16384 1 amdgpu ttm73728 2 amdgpu,drm_ttm_helper drm_kms_helper258048 1 amdgpu drm 557056 6 gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm i2c_algo_bit 16384 2 igb,amdgpu - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.14.0-1007-oem 5.14.0-1007.7 ProcVersionSignature: Ubuntu 5.14.0-1007.7-oem 5.14.14 Uname: Linux 5.14.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Nov 29 13:46:48 2021 InstallationDate: Installed on 2019-07-24 (858 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.1) SourcePackage: linux-oem-5.14 UpgradeStatus: Upgraded to focal on 2020-05-02 (575 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1952568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952568] Re: AMD GPU kernel driver unload error
The AMGPU patch captured in 5.14.0-1007 was added to uvd_v6_0_hw_fini. but in 5.16-rc3 it is the code added to uvd_v6_0_suspend, so the backport location may be wrong. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952568 Title: AMD GPU kernel driver unload error Status in linux-oem-5.14 package in Ubuntu: New Bug description: After updating the kernel from 5.14.0-1005 to 5.14.0-1007 on ubuntu20.04, if you unload the driver with the following command, the command will be forcibly terminated and the driver cannot be unloaded. Can be unloaded with 5.14.0-1005 without any problem sudo modprob -s -r amdgpu Driver information in lsmod - sudo lsmod |grep amdgpu amdgpu 7049216 -1 iommu_v2 24576 1 amdgpu gpu_sched 36864 1 amdgpu drm_ttm_helper 16384 1 amdgpu ttm73728 2 amdgpu,drm_ttm_helper drm_kms_helper258048 1 amdgpu drm 557056 6 gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm i2c_algo_bit 16384 2 igb,amdgpu - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.14.0-1007-oem 5.14.0-1007.7 ProcVersionSignature: Ubuntu 5.14.0-1007.7-oem 5.14.14 Uname: Linux 5.14.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Nov 29 13:46:48 2021 InstallationDate: Installed on 2019-07-24 (858 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.1) SourcePackage: linux-oem-5.14 UpgradeStatus: Upgraded to focal on 2020-05-02 (575 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1952568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952694] [NEW] battery stuck in "estimating", when unplug the charger the laptop shuts down (the battery was working well with Windows
Public bug reported: battery stuck in "estimating", when unplug the charger the laptop shuts down (the battery was working well with Windows. The battery is not charging and is not possible to get the info about the percentage of battery. Anyway the system can recognize the battery and its capacity. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 30 15:28:40 2021 InstallationDate: Installed on 2021-11-29 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1952694 Title: battery stuck in "estimating", when unplug the charger the laptop shuts down (the battery was working well with Windows Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: battery stuck in "estimating", when unplug the charger the laptop shuts down (the battery was working well with Windows. The battery is not charging and is not possible to get the info about the percentage of battery. Anyway the system can recognize the battery and its capacity. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 30 15:28:40 2021 InstallationDate: Installed on 2021-11-29 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1952694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946174] Re: Trackpad not being detected
This appears to be the same issue I have reported in Bug #1952497 -- 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/1946174 Title: Trackpad not being detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: HP Pavilion - 15-ec1052ax Touchpad manufacturer: Elan Ubuntu version: 21.04 hirsute Hippo ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: abhi 1921 F pulseaudio /dev/snd/controlC0: abhi 1921 F pulseaudio /dev/snd/controlC1: abhi 1921 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 08:38:29 2021 InstallationDate: Installed on 2021-09-21 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=c22aafea-3ec6-436e-a4d4-fd586965dd93 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-37-generic N/A linux-backports-modules-5.11.0-37-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:sku1N1G0PA#ACJ:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1N1G0PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
** Summary changed: - ubuntu_ltp / finit_module02 fails on v4.15 and other kernels + ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
** Tags added: sru-20211108 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1853797 Title: pmu in ubuntu_kvm_unit_tests fails Status in ubuntu-kernel-tests: Triaged Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Status in linux-oracle-5.4 package in Ubuntu: New Bug description: 4 failures: FAIL: rdpmc: fixed cntr-0 FAIL: rdpmc: fixed cntr-1 FAIL: rdpmc: fixed cntr-2 FAIL: all counters Test log: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl enabling apic paging enabled cr0 = 80010011 cr3 = 45a000 cr4 = 20 PMU version: 2 GP counters: 4 GP counter width: 48 Mask length: 7 Fixed counters: 3 Fixed counter width: 48 PASS: core cycles-0 PASS: core cycles-1 PASS: core cycles-2 PASS: core cycles-3 PASS: instructions-0 PASS: instructions-1 PASS: instructions-2 PASS: instructions-3 PASS: ref cycles-0 PASS: ref cycles-1 PASS: ref cycles-2 PASS: ref cycles-3 PASS: llc refference-0 PASS: llc refference-1 PASS: llc refference-2 PASS: llc refference-3 PASS: llc misses-0 PASS: llc misses-1 PASS: llc misses-2 PASS: llc misses-3 PASS: branches-0 PASS: branches-1 PASS: branches-2 PASS: branches-3 PASS: branch misses-0 PASS: branch misses-1 PASS: branch misses-2 PASS: branch misses-3 PASS: fixed-0 PASS: fixed-1 PASS: fixed-2 PASS: rdpmc: cntr-0 PASS: rdpmc: fast-0 PASS: rdpmc: cntr-1 PASS: rdpmc: fast-1 PASS: rdpmc: cntr-2 PASS: rdpmc: fast-2 PASS: rdpmc: cntr-3 PASS: rdpmc: fast-3 FAIL: rdpmc: fixed cntr-0 PASS: rdpmc: fixed fast-0 FAIL: rdpmc: fixed cntr-1 PASS: rdpmc: fixed fast-1 FAIL: rdpmc: fixed cntr-2 PASS: rdpmc: fixed fast-2 FAIL: all counters PASS: overflow: cntr-0 PASS: overflow: status-0 PASS: overflow: status clear-0 PASS: overflow: irq-0 PASS: overflow: cntr-1 PASS: overflow: status-1 PASS: overflow: status clear-1 PASS: overflow: irq-1 PASS: overflow: cntr-2 PASS: overflow: status-2 PASS: overflow: status clear-2 PASS: overflow: irq-2 PASS: overflow: cntr-3 PASS: overflow: status-3 PASS: overflow: status clear-3 PASS: overflow: irq-3 PASS: overflow: cntr-4 PASS: overflow: status-4 PASS: overflow: status clear-4 PASS: overflow: irq-4 PASS: cmask SUMMARY: 67 tests, 4 unexpected failures FAIL pmu (67 tests, 4 unexpected failures) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 04:29:43 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
I note that /dev/input/event7 to event26 are missing with kernel 5.13. The Thunderbolt dock Ethernet seems to be this device (missing with kernel 5.13). r8152 6-1.3.3:1.0 enx3c52821a24c3: renamed from eth0 I see what looks like the laptop's internal ethernet showing up though. I didn't think to move the Ethernet cable to that port to see if it would work. My external monitors (BenQ FP937s and Samsync SyncMaster) show up for both kernels. Interestingly, I don't see the internal panel showing up under either kernel? But it works with 5.11 and not with 5.13. I only see this with 5.11: (II) modeset(G0): using drv /dev/dri/card0 And then some EDID probing, that maybe includes the internal panel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1952674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
** Attachment added: "journal output when booting with kernel 5.11" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1952674/+attachment/5544223/+files/journal-5.11.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1952674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
** Attachment added: "journal output when booting with kernel 5.13" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1952674/+attachment/5544222/+files/journal-5.13.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1952674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952606] Re: Intel I225-IT Ethernet controller is not working during driver probe function
Noticed that the bug has been resolved in kernel 5.11.0-41-generic ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1952606 Title: Intel I225-IT Ethernet controller is not working during driver probe function Status in linux package in Ubuntu: Invalid Bug description: After installing Ubuntu 20.04.3 (Kernel 5.11.0-38-generic) on PXIe controller with I225-IT Ethernet Controller, running dmesg message output the following error thrown by igc driver module: [0.882371] igc: probe of :6d:00.0 failed with error -2 [0.914344] igc: probe of :6e:00.0 failed with error -2 After sending inquiry to Intel, they stated that while kernel 5.15 is the official kernel containing igc driver module to support I225-IT Ethernet Controller, for any official Linux kernel between 5.8 to 5.14, manually adding these 2 patches will address the bug. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7c496de538eebd8212dc2a3c9a468386b264d0d4 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=47bca7de6a4fb8dcb564c7ca14d885c91ed19e03 I would like to request for backporting these 2 patches into the official Ubuntu 20.04.3 (and later) kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951767] Re: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
The patch is in Ubuntu-5.13.0-23.23 ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Incomplete Bug description: [Impact] MAC pass through is not working on new TBT and USB-C docks. [Fix] Enable MAC pass through based on Lenovo USB hub. [Test] Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well. [Where problems could occur] The Realtek USB ethernet in Lenovo USB hub will mess the MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
Passed with Hirsute 5.11.0-42.46 ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534
[Kernel-packages] [Bug 1949029] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544205/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544207/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544217/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544221/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544219/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544215/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544208/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544213/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544216/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544218/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544211/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544206/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544210/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544212/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544220/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544214/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544209/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544204/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544203/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghost 2072 F pulseaudio /dev/snd/controlC0: ghost 2072 F pulseaudio /dev/snd/controlC2: ghost 2072 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-27 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20354 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 Tags: wayland-session impish Uname: Linux 5.13.0-21-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.release: 0.91 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.ec.firmware.release: 0.91 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Re: SSD disappears on Reboot but on cold boot is detected
apport information ** Tags added: apport-collected impish wayland-session ** Description changed: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: ghost 2072 F pulseaudio + /dev/snd/controlC0: ghost 2072 F pulseaudio + /dev/snd/controlC2: ghost 2072 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2021-10-27 (33 days ago) + InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) + MachineType: LENOVO 20354 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=6dee2b9f-b6dc-456a-9ee6-29269acb89f0 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-21-generic N/A + linux-backports-modules-5.13.0-21-generic N/A + linux-firmware 1.201.1 + Tags: wayland-session impish + Uname: Linux 5.13.0-21-generic x86_64 + UpgradeStatus: Upgraded to impish on 2021-10-28 (33 days ago) + UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/21/2015 + dmi.bios.release: 0.91 + dmi.bios.vendor: LENOVO + dmi.bios.version: 9BCN91WW + dmi.board.asset.tag: No Asset Tag + dmi.board.name: Lancer 5A5 + dmi.board.vendor: LENOVO + dmi.board.version: 31900059STD + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo Z50-70 + dmi.ec.firmware.release: 0.91 + dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:br0.91:efr0.91:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70:skuLENOVO_MT_20354_BU_idea_FM_LenovoZ50-70: + dmi.product.family: IDEAPAD + dmi.product.name: 20354 + dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 + dmi.product.version: Lenovo Z50-70 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1949029/+attachment/5544202/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Confirmed Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS
[Kernel-packages] [Bug 1952674] [NEW] Kernel 5.13 fails to work with lots of hardware (HP Zbook)
Public bug reported: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1952674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series
** Tags removed: verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952568] Re: AMD GPU kernel driver unload error
If you replace driver / gpu / drm / amd / with the source of 5.14.0-1005, it can be unloaded normally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952568 Title: AMD GPU kernel driver unload error Status in linux-oem-5.14 package in Ubuntu: New Bug description: After updating the kernel from 5.14.0-1005 to 5.14.0-1007 on ubuntu20.04, if you unload the driver with the following command, the command will be forcibly terminated and the driver cannot be unloaded. Can be unloaded with 5.14.0-1005 without any problem sudo modprob -s -r amdgpu Driver information in lsmod - sudo lsmod |grep amdgpu amdgpu 7049216 -1 iommu_v2 24576 1 amdgpu gpu_sched 36864 1 amdgpu drm_ttm_helper 16384 1 amdgpu ttm73728 2 amdgpu,drm_ttm_helper drm_kms_helper258048 1 amdgpu drm 557056 6 gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm i2c_algo_bit 16384 2 igb,amdgpu - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.14.0-1007-oem 5.14.0-1007.7 ProcVersionSignature: Ubuntu 5.14.0-1007.7-oem 5.14.14 Uname: Linux 5.14.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Nov 29 13:46:48 2021 InstallationDate: Installed on 2019-07-24 (858 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.1) SourcePackage: linux-oem-5.14 UpgradeStatus: Upgraded to focal on 2020-05-02 (575 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1952568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@dianaraz Should be in the next Kernel that's released: https://lkml.org/lkml/2021/11/29/79 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I just saw the update of the new kernel is available, but it doesn't include this bugfix (sob), so my personal laptop keeps having the bug after the update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952666] Re: XPS 9575 auto rotate camera when in tent mode (when laptop is updside down)
I am afraid I cannot provide logs, because this is an observation. I suspect that the issue would need to be resolved at Kernel level. -- 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/1952666 Title: XPS 9575 auto rotate camera when in tent mode (when laptop is updside down) Status in linux package in Ubuntu: Incomplete Bug description: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the video recording output is not rotated. i.e. when conducting a Skype and Zoom call I can see myself upside down. A test in both Skype and Zoom has been conducted, in both instances the video was upside down. This suggests that the driver is not automatically rotating the video recording when the laptop is upside down, in 'tent mode', because the issue occurs in multiple different software. Although a workaround can be conducted in some software by adjusting the settings, this is not ideal, because it requires the user to adjust settings every time the laptop is rotated, which could happen during a meeting for instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952667] Re: XPS 9575 auto switch L-R audio when in tent mode (when laptop is updside down)
I am afraid I cannot provide logs, because this is an observation. However, the issue may involve or require changes to, Pipewire, Pulseaudio, Alsa audio and/or Kernel. My system is currently utilising Pipewire. -- 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/1952667 Title: XPS 9575 auto switch L-R audio when in tent mode (when laptop is updside down) Status in linux package in Ubuntu: Incomplete Bug description: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the Audio output is not rotated/switched. This means, for instance, when listening to spatially orientated audio such as in games, i.e. first person shooters, the audio is the wrong way around. i.e. gunfire sounds like it is coming from the left, when in fact it is to the right, which leads to disorientation. A test has been conducted with the laptop the right way up and this has been compared to the laptop flipped upside down in tent mode, and the audio was identified to be the wrong way around when in tent mode. It is believed that the gyroscope must be linked to the audio drivers to flip the audio output when upside down. Although some software may be able to work around this issue, rotating the laptop on the fly is not possible without adjusting such settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952669] [NEW] package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade
Public bug reported: I was upgrading some packages with Synaptic and the aforementioned one failed claiming that it had some dependency issues. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-470 470.86-0ubuntu0.20.04.1 Uname: Linux 5.15.2-051502-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 29 17:43:14 2021 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-11-15 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1952669 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I was upgrading some packages with Synaptic and the aforementioned one failed claiming that it had some dependency issues. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-470 470.86-0ubuntu0.20.04.1 Uname: Linux 5.15.2-051502-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 29 17:43:14 2021 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-11-15 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952666] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1952666 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952666 Title: XPS 9575 auto rotate camera when in tent mode (when laptop is updside down) Status in linux package in Ubuntu: Incomplete Bug description: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the video recording output is not rotated. i.e. when conducting a Skype and Zoom call I can see myself upside down. A test in both Skype and Zoom has been conducted, in both instances the video was upside down. This suggests that the driver is not automatically rotating the video recording when the laptop is upside down, in 'tent mode', because the issue occurs in multiple different software. Although a workaround can be conducted in some software by adjusting the settings, this is not ideal, because it requires the user to adjust settings every time the laptop is rotated, which could happen during a meeting for instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952667] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1952667 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952667 Title: XPS 9575 auto switch L-R audio when in tent mode (when laptop is updside down) Status in linux package in Ubuntu: Incomplete Bug description: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the Audio output is not rotated/switched. This means, for instance, when listening to spatially orientated audio such as in games, i.e. first person shooters, the audio is the wrong way around. i.e. gunfire sounds like it is coming from the left, when in fact it is to the right, which leads to disorientation. A test has been conducted with the laptop the right way up and this has been compared to the laptop flipped upside down in tent mode, and the audio was identified to be the wrong way around when in tent mode. It is believed that the gyroscope must be linked to the audio drivers to flip the audio output when upside down. Although some software may be able to work around this issue, rotating the laptop on the fly is not possible without adjusting such settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-azure-5.4/5.4.0.1064.44)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1064.44) for bionic have finished running. The following regressions have been reported in tests triggered by the package: asic0x/1.0.1-1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952667] [NEW] XPS 9575 auto switch L-R audio when in tent mode (when laptop is updside down)
Public bug reported: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the Audio output is not rotated/switched. This means, for instance, when listening to spatially orientated audio such as in games, i.e. first person shooters, the audio is the wrong way around. i.e. gunfire sounds like it is coming from the left, when in fact it is to the right, which leads to disorientation. A test has been conducted with the laptop the right way up and this has been compared to the laptop flipped upside down in tent mode, and the audio was identified to be the wrong way around when in tent mode. It is believed that the gyroscope must be linked to the audio drivers to flip the audio output when upside down. Although some software may be able to work around this issue, rotating the laptop on the fly is not possible without adjusting such settings. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952667 Title: XPS 9575 auto switch L-R audio when in tent mode (when laptop is updside down) Status in linux package in Ubuntu: Incomplete Bug description: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the Audio output is not rotated/switched. This means, for instance, when listening to spatially orientated audio such as in games, i.e. first person shooters, the audio is the wrong way around. i.e. gunfire sounds like it is coming from the left, when in fact it is to the right, which leads to disorientation. A test has been conducted with the laptop the right way up and this has been compared to the laptop flipped upside down in tent mode, and the audio was identified to be the wrong way around when in tent mode. It is believed that the gyroscope must be linked to the audio drivers to flip the audio output when upside down. Although some software may be able to work around this issue, rotating the laptop on the fly is not possible without adjusting such settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952665] [NEW] Impish update: upstream stable patchset 2021-11-29
Public bug reported: SRU Justification Impact:    The upstream process for stable tree updates is quite similar    in scope to the Ubuntu SRU process, e.g., each patch has to    demonstrably fix a bug, and each patch is vetted by upstream    by originating either directly from a mainline/stable Linux tree or    a minimally backported form of that patch. The following upstream    stable patches should be included in the Ubuntu kernel:    upstream stable patchset 2021-11-29 Ported from the following upstream stable releases: v5.10.77, v5.14.16 v5.10.78, v5.14.17 v5.10.79, v5.14.18    from git://git.kernel.org/ ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned ARM: 9134/1: remove duplicate memcpy() definition ARM: 9138/1: fix link warning with XIP + frame-pointer ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype ARM: 9141/1: only warn about XIP address when not compile testing usbnet: sanity check for maxpacket usbnet: fix error return code in usbnet_probe() Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" pinctrl: amd: disable and mask interrupts on probe ata: sata_mv: Fix the error handling of mv_chip_id() nfc: port100: fix using -ERRNO as command type mask net/tls: Fix flipped sign in tls_err_abort() calls mmc: vub300: fix control-message timeouts mmc: cqhci: clear HALT state after CQE enable mmc: mediatek: Move cqhci init behind ungate clock mmc: dw_mmc: exynos: fix the finding clock sample value mmc: sdhci: Map more voltage level to SDHCI_POWER_330 mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit ocfs2: fix race between searching chunks and release journal_head from buffer_head nvme-tcp: fix H2CData PDU send accounting (again) cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() cfg80211: fix management registrations locking net: lan78xx: fix division by zero in send path mm, thp: bail out early in collapse_file for writeback page drm/amdgpu: fix out of bounds write cgroup: Fix memory leak caused by missing cgroup_bpf_offline riscv, bpf: Fix potential NULL dereference tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function bpf: Fix potential race in tail call compatibility check bpf: Fix error usage of map_fd and fdget() in generic_map_update_batch() IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields IB/hfi1: Fix abba locking issue with sc_disable() nvmet-tcp: fix data digest pointer calculation nvme-tcp: fix data digest pointer calculation nvme-tcp: fix possible req->offset corruption octeontx2-af: Display all enabled PF VF rsrc_alloc entries. RDMA/mlx5: Set user priority for DCT arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node reset: brcmstb-rescal: fix incorrect polarity of status bit regmap: Fix possible double-free in regcache_rbtree_exit() net: batman-adv: fix error handling net-sysfs: initialize uid and gid before calling net_ns_get_ownership cfg80211: correct bridge/4addr mode check net: Prevent infinite while loop in skb_tx_hash() RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string gpio: xgs-iproc: fix parsing of ngpios property nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST mlxsw: pci: Recycle received packet upon allocation failure net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent net: nxp: lpc_eth.c: avoid hang when bringing interface down net/tls: Fix flipped sign in async_wait.err assignment phy: phy_ethtool_ksettings_get: Lock the phy for consistency phy: phy_ethtool_ksettings_set: Move after phy_start_aneg phy: phy_start_aneg: Add an unlocked version phy: phy_ethtool_ksettings_set: Lock the PHY while changing settings sctp: use init_tag from inithdr for ABORT chunk sctp: fix the processing for INIT_ACK chunk sctp: fix the processing for COOKIE_ECHO chunk sctp: add vtag check in sctp_sf_violation sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_ootb KVM: s390: clear kicked_mask before sleeping again KVM: s390: preserve deliverable_mask in __airqs_kick_single_vcpu scsi: ufs: ufs-exynos: Correct timeout value setting registers riscv: fix misalgned trap vector base address riscv: Fix asan-stack clang build perf script: Check session->header.env.arch before using it mmc: tmio: reenable card irqs after the reset callback mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield block: Fix partition check for host-aware zoned block devices ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub mm: hwpoison: remove the unnecessary THP check mm: filemap: check if THP has hwpoisoned subpage for PMD page fault arm64: dts: imx8mm-kontron: Fix polarity of reg_rst_eth2 arm64:
[Kernel-packages] [Bug 1952666] [NEW] XPS 9575 auto rotate camera when in tent mode (when laptop is updside down)
Public bug reported: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the video recording output is not rotated. i.e. when conducting a Skype and Zoom call I can see myself upside down. A test in both Skype and Zoom has been conducted, in both instances the video was upside down. This suggests that the driver is not automatically rotating the video recording when the laptop is upside down, in 'tent mode', because the issue occurs in multiple different software. Although a workaround can be conducted in some software by adjusting the settings, this is not ideal, because it requires the user to adjust settings every time the laptop is rotated, which could happen during a meeting for instance. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952666 Title: XPS 9575 auto rotate camera when in tent mode (when laptop is updside down) Status in linux package in Ubuntu: New Bug description: When the XPS 9575 laptop is upside down the in-built gyroscope rotates the screen, as correct and expected. However the video recording output is not rotated. i.e. when conducting a Skype and Zoom call I can see myself upside down. A test in both Skype and Zoom has been conducted, in both instances the video was upside down. This suggests that the driver is not automatically rotating the video recording when the laptop is upside down, in 'tent mode', because the issue occurs in multiple different software. Although a workaround can be conducted in some software by adjusting the settings, this is not ideal, because it requires the user to adjust settings every time the laptop is rotated, which could happen during a meeting for instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact]   AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x)   which will not work with existing ACP drivers. [Fix]   Backport the new driver that is now in linux-next (to be in 5.16) [Test]   This is requested by AMD. [Where problems could occur]   Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950013] Re: Add s0i3 RTC wake up for AMD systems
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Â Â RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] Â Â A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Â Â Note this s0i3 RTC wake up also requires new firmware. Â Â The first patch is the prerequisite actual fix (patch 2 and 3). [Test] Â Â This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Â Â Low risk. Â Â First patch only exports Idlemask value. Â Â The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1008.8 --- linux-oem-5.14 (5.14.0-1008.8) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1008.8 -proposed tracker (LP: #1949844) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * Let NVMe with HMB use native power control again (LP: #1950042) - nvme-pci: use attribute group for cmb sysfs - nvme-pci: cmb sysfs: one file, one value - nvme-pci: disable hmb on idle suspend - nvme: allow user toggling hmb usage * Add s0i3 RTC wake up for AMD systems (LP: #1950013) - platform/x86: amd-pmc: Export Idlemask values based on the APU - platform/x86: amd-pmc: adjust arguments for `amd_pmc_send_cmd` - platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - [Config] Enable AMD ACP 6 DMIC Support * Focal update: v5.14.17 upstream stable release (LP: #1950165) - scsi: core: Put LLD module refcnt after SCSI device is released - sfc: Fix reading non-legacy supported link modes - vrf: Revert "Reset skb conntrack connection..." - media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() - Revert "xhci: Set HCD flag to defer primary roothub registration" - Revert "usb: core: hcd: Add support for deferring roothub registration" - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. - drm/i915: Remove memory frequency calculation - Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" - ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" - Revert "wcn36xx: Disable bmps when encryption is disabled" - drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" - drm/amd/display: Revert "Directly retrain link from debugfs" - Revert "drm/i915/gt: Propagate change in error status to children on unhold" - ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table - ALSA: usb-audio: Add Audient iD14 to mixer map quirk table - Linux 5.14.17 * Focal update: v5.14.16 upstream stable release (LP: #1950164) - ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9138/1: fix link warning with XIP + frame-pointer - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ARM: 9148/1: handle CONFIG_CPU_ENDIAN_BE32 in arch/arm/kernel/head.S - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - pinctrl: amd: disable and mask interrupts on probe - ata: sata_mv: Fix the error handling of mv_chip_id() - tipc: fix size validations for the MSG_CRYPTO type - nfc: port100: fix using -ERRNO as command type mask - Revert "net: mdiobus: Fix memory leak in __mdiobus_register" - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: mediatek: Move cqhci init behind ungate clock - mmc: tmio: reenable card irqs after the reset callback - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - block: Fix partition check for host-aware zoned block devices - ocfs2: fix race between searching chunks and release journal_head from buffer_head - nvme-tcp: fix H2CData PDU send accounting (again) - ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - cfg80211: fix management registrations locking - net: lan78xx: fix division
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1008.8 --- linux-oem-5.14 (5.14.0-1008.8) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1008.8 -proposed tracker (LP: #1949844) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * Let NVMe with HMB use native power control again (LP: #1950042) - nvme-pci: use attribute group for cmb sysfs - nvme-pci: cmb sysfs: one file, one value - nvme-pci: disable hmb on idle suspend - nvme: allow user toggling hmb usage * Add s0i3 RTC wake up for AMD systems (LP: #1950013) - platform/x86: amd-pmc: Export Idlemask values based on the APU - platform/x86: amd-pmc: adjust arguments for `amd_pmc_send_cmd` - platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - [Config] Enable AMD ACP 6 DMIC Support * Focal update: v5.14.17 upstream stable release (LP: #1950165) - scsi: core: Put LLD module refcnt after SCSI device is released - sfc: Fix reading non-legacy supported link modes - vrf: Revert "Reset skb conntrack connection..." - media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() - Revert "xhci: Set HCD flag to defer primary roothub registration" - Revert "usb: core: hcd: Add support for deferring roothub registration" - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. - drm/i915: Remove memory frequency calculation - Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" - ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" - Revert "wcn36xx: Disable bmps when encryption is disabled" - drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" - drm/amd/display: Revert "Directly retrain link from debugfs" - Revert "drm/i915/gt: Propagate change in error status to children on unhold" - ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table - ALSA: usb-audio: Add Audient iD14 to mixer map quirk table - Linux 5.14.17 * Focal update: v5.14.16 upstream stable release (LP: #1950164) - ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9138/1: fix link warning with XIP + frame-pointer - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ARM: 9148/1: handle CONFIG_CPU_ENDIAN_BE32 in arch/arm/kernel/head.S - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - pinctrl: amd: disable and mask interrupts on probe - ata: sata_mv: Fix the error handling of mv_chip_id() - tipc: fix size validations for the MSG_CRYPTO type - nfc: port100: fix using -ERRNO as command type mask - Revert "net: mdiobus: Fix memory leak in __mdiobus_register" - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: mediatek: Move cqhci init behind ungate clock - mmc: tmio: reenable card irqs after the reset callback - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - block: Fix partition check for host-aware zoned block devices - ocfs2: fix race between searching chunks and release journal_head from buffer_head - nvme-tcp: fix H2CData PDU send accounting (again) - ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - cfg80211: fix management registrations locking - net: lan78xx: fix division
[Kernel-packages] [Bug 1950160] Re: Focal update: v5.14.15 upstream stable release
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1008.8 --- linux-oem-5.14 (5.14.0-1008.8) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1008.8 -proposed tracker (LP: #1949844) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * Let NVMe with HMB use native power control again (LP: #1950042) - nvme-pci: use attribute group for cmb sysfs - nvme-pci: cmb sysfs: one file, one value - nvme-pci: disable hmb on idle suspend - nvme: allow user toggling hmb usage * Add s0i3 RTC wake up for AMD systems (LP: #1950013) - platform/x86: amd-pmc: Export Idlemask values based on the APU - platform/x86: amd-pmc: adjust arguments for `amd_pmc_send_cmd` - platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - [Config] Enable AMD ACP 6 DMIC Support * Focal update: v5.14.17 upstream stable release (LP: #1950165) - scsi: core: Put LLD module refcnt after SCSI device is released - sfc: Fix reading non-legacy supported link modes - vrf: Revert "Reset skb conntrack connection..." - media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() - Revert "xhci: Set HCD flag to defer primary roothub registration" - Revert "usb: core: hcd: Add support for deferring roothub registration" - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. - drm/i915: Remove memory frequency calculation - Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" - ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" - Revert "wcn36xx: Disable bmps when encryption is disabled" - drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" - drm/amd/display: Revert "Directly retrain link from debugfs" - Revert "drm/i915/gt: Propagate change in error status to children on unhold" - ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table - ALSA: usb-audio: Add Audient iD14 to mixer map quirk table - Linux 5.14.17 * Focal update: v5.14.16 upstream stable release (LP: #1950164) - ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9138/1: fix link warning with XIP + frame-pointer - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ARM: 9148/1: handle CONFIG_CPU_ENDIAN_BE32 in arch/arm/kernel/head.S - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - pinctrl: amd: disable and mask interrupts on probe - ata: sata_mv: Fix the error handling of mv_chip_id() - tipc: fix size validations for the MSG_CRYPTO type - nfc: port100: fix using -ERRNO as command type mask - Revert "net: mdiobus: Fix memory leak in __mdiobus_register" - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: mediatek: Move cqhci init behind ungate clock - mmc: tmio: reenable card irqs after the reset callback - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - block: Fix partition check for host-aware zoned block devices - ocfs2: fix race between searching chunks and release journal_head from buffer_head - nvme-tcp: fix H2CData PDU send accounting (again) - ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - cfg80211: fix management registrations locking - net: lan78xx: fix division
[Kernel-packages] [Bug 1950013] Re: Add s0i3 RTC wake up for AMD systems
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1008.8 --- linux-oem-5.14 (5.14.0-1008.8) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1008.8 -proposed tracker (LP: #1949844) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * Let NVMe with HMB use native power control again (LP: #1950042) - nvme-pci: use attribute group for cmb sysfs - nvme-pci: cmb sysfs: one file, one value - nvme-pci: disable hmb on idle suspend - nvme: allow user toggling hmb usage * Add s0i3 RTC wake up for AMD systems (LP: #1950013) - platform/x86: amd-pmc: Export Idlemask values based on the APU - platform/x86: amd-pmc: adjust arguments for `amd_pmc_send_cmd` - platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - [Config] Enable AMD ACP 6 DMIC Support * Focal update: v5.14.17 upstream stable release (LP: #1950165) - scsi: core: Put LLD module refcnt after SCSI device is released - sfc: Fix reading non-legacy supported link modes - vrf: Revert "Reset skb conntrack connection..." - media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() - Revert "xhci: Set HCD flag to defer primary roothub registration" - Revert "usb: core: hcd: Add support for deferring roothub registration" - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. - drm/i915: Remove memory frequency calculation - Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" - ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" - Revert "wcn36xx: Disable bmps when encryption is disabled" - drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" - drm/amd/display: Revert "Directly retrain link from debugfs" - Revert "drm/i915/gt: Propagate change in error status to children on unhold" - ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table - ALSA: usb-audio: Add Audient iD14 to mixer map quirk table - Linux 5.14.17 * Focal update: v5.14.16 upstream stable release (LP: #1950164) - ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9138/1: fix link warning with XIP + frame-pointer - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ARM: 9148/1: handle CONFIG_CPU_ENDIAN_BE32 in arch/arm/kernel/head.S - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - pinctrl: amd: disable and mask interrupts on probe - ata: sata_mv: Fix the error handling of mv_chip_id() - tipc: fix size validations for the MSG_CRYPTO type - nfc: port100: fix using -ERRNO as command type mask - Revert "net: mdiobus: Fix memory leak in __mdiobus_register" - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: mediatek: Move cqhci init behind ungate clock - mmc: tmio: reenable card irqs after the reset callback - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - block: Fix partition check for host-aware zoned block devices - ocfs2: fix race between searching chunks and release journal_head from buffer_head - nvme-tcp: fix H2CData PDU send accounting (again) - ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - cfg80211: fix management registrations locking - net: lan78xx: fix division
[Kernel-packages] [Bug 1950164] Re: Focal update: v5.14.16 upstream stable release
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1008.8 --- linux-oem-5.14 (5.14.0-1008.8) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1008.8 -proposed tracker (LP: #1949844) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * Let NVMe with HMB use native power control again (LP: #1950042) - nvme-pci: use attribute group for cmb sysfs - nvme-pci: cmb sysfs: one file, one value - nvme-pci: disable hmb on idle suspend - nvme: allow user toggling hmb usage * Add s0i3 RTC wake up for AMD systems (LP: #1950013) - platform/x86: amd-pmc: Export Idlemask values based on the APU - platform/x86: amd-pmc: adjust arguments for `amd_pmc_send_cmd` - platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - [Config] Enable AMD ACP 6 DMIC Support * Focal update: v5.14.17 upstream stable release (LP: #1950165) - scsi: core: Put LLD module refcnt after SCSI device is released - sfc: Fix reading non-legacy supported link modes - vrf: Revert "Reset skb conntrack connection..." - media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() - Revert "xhci: Set HCD flag to defer primary roothub registration" - Revert "usb: core: hcd: Add support for deferring roothub registration" - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. - drm/i915: Remove memory frequency calculation - Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" - ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" - Revert "wcn36xx: Disable bmps when encryption is disabled" - drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" - drm/amd/display: Revert "Directly retrain link from debugfs" - Revert "drm/i915/gt: Propagate change in error status to children on unhold" - ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table - ALSA: usb-audio: Add Audient iD14 to mixer map quirk table - Linux 5.14.17 * Focal update: v5.14.16 upstream stable release (LP: #1950164) - ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9138/1: fix link warning with XIP + frame-pointer - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ARM: 9148/1: handle CONFIG_CPU_ENDIAN_BE32 in arch/arm/kernel/head.S - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - pinctrl: amd: disable and mask interrupts on probe - ata: sata_mv: Fix the error handling of mv_chip_id() - tipc: fix size validations for the MSG_CRYPTO type - nfc: port100: fix using -ERRNO as command type mask - Revert "net: mdiobus: Fix memory leak in __mdiobus_register" - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: mediatek: Move cqhci init behind ungate clock - mmc: tmio: reenable card irqs after the reset callback - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - block: Fix partition check for host-aware zoned block devices - ocfs2: fix race between searching chunks and release journal_head from buffer_head - nvme-tcp: fix H2CData PDU send accounting (again) - ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - cfg80211: fix management registrations locking - net: lan78xx: fix division
[Kernel-packages] [Bug 1950165] Re: Focal update: v5.14.17 upstream stable release
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1008.8 --- linux-oem-5.14 (5.14.0-1008.8) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1008.8 -proposed tracker (LP: #1949844) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * Let NVMe with HMB use native power control again (LP: #1950042) - nvme-pci: use attribute group for cmb sysfs - nvme-pci: cmb sysfs: one file, one value - nvme-pci: disable hmb on idle suspend - nvme: allow user toggling hmb usage * Add s0i3 RTC wake up for AMD systems (LP: #1950013) - platform/x86: amd-pmc: Export Idlemask values based on the APU - platform/x86: amd-pmc: adjust arguments for `amd_pmc_send_cmd` - platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * AMD ACP 6.x DMIC Supports (LP: #1949245) - ASoC: amd: add Yellow Carp ACP6x IP register header - ASoC: amd: add Yellow Carp ACP PCI driver - ASoC: amd: add acp6x init/de-init functions - ASoC: amd: add platform devices for acp6x pdm driver and dmic driver - ASoC: amd: add acp6x pdm platform driver - ASoC: amd: add acp6x irq handler - ASoC: amd: add acp6x pdm driver dma ops - ASoC: amd: add acp6x pci driver pm ops - ASoC: amd: add acp6x pdm driver pm ops - ASoC: amd: enable Yellow carp acp6x drivers build - ASoC: amd: create platform device for acp6x machine driver - ASoC: amd: add YC machine driver using dmic - ASoC: amd: enable Yellow Carp platform machine driver build - [Config] Enable AMD ACP 6 DMIC Support * Focal update: v5.14.17 upstream stable release (LP: #1950165) - scsi: core: Put LLD module refcnt after SCSI device is released - sfc: Fix reading non-legacy supported link modes - vrf: Revert "Reset skb conntrack connection..." - media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() - Revert "xhci: Set HCD flag to defer primary roothub registration" - Revert "usb: core: hcd: Add support for deferring roothub registration" - drm/amdkfd: fix boot failure when iommu is disabled in Picasso. - drm/i915: Remove memory frequency calculation - Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" - ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" - Revert "wcn36xx: Disable bmps when encryption is disabled" - drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8" - drm/amd/display: Revert "Directly retrain link from debugfs" - Revert "drm/i915/gt: Propagate change in error status to children on unhold" - ALSA: usb-audio: Add Schiit Hel device to mixer map quirk table - ALSA: usb-audio: Add Audient iD14 to mixer map quirk table - Linux 5.14.17 * Focal update: v5.14.16 upstream stable release (LP: #1950164) - ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images - ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned - ARM: 9134/1: remove duplicate memcpy() definition - ARM: 9138/1: fix link warning with XIP + frame-pointer - ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype - ARM: 9141/1: only warn about XIP address when not compile testing - ARM: 9148/1: handle CONFIG_CPU_ENDIAN_BE32 in arch/arm/kernel/head.S - usbnet: sanity check for maxpacket - usbnet: fix error return code in usbnet_probe() - Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" - pinctrl: amd: disable and mask interrupts on probe - ata: sata_mv: Fix the error handling of mv_chip_id() - tipc: fix size validations for the MSG_CRYPTO type - nfc: port100: fix using -ERRNO as command type mask - Revert "net: mdiobus: Fix memory leak in __mdiobus_register" - net/tls: Fix flipped sign in tls_err_abort() calls - mmc: vub300: fix control-message timeouts - mmc: cqhci: clear HALT state after CQE enable - mmc: mediatek: Move cqhci init behind ungate clock - mmc: tmio: reenable card irqs after the reset callback - mmc: dw_mmc: exynos: fix the finding clock sample value - mmc: sdhci: Map more voltage level to SDHCI_POWER_330 - mmc: sdhci-pci: Read card detect from ACPI for Intel Merrifield - mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit - block: Fix partition check for host-aware zoned block devices - ocfs2: fix race between searching chunks and release journal_head from buffer_head - nvme-tcp: fix H2CData PDU send accounting (again) - ftrace/nds32: Update the proto for ftrace_trace_function to match ftrace_stub - cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() - cfg80211: fix management registrations locking - net: lan78xx: fix division
[Kernel-packages] [Bug 1923925] Re: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923925 Title: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260 Status in bluez package in Ubuntu: Confirmed Bug description: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933761] Re: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05
*** This bug is a duplicate of bug 1933762 *** https://bugs.launchpad.net/bugs/1933762 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933761 Title: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05 Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. But it's working on windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1933761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC systems with:  # selftests: net: reuseport_bpf_numa  # IPv4 UDP  # send node 0, receive socket 0  # libnuma: Warning: Cannot read node cpumask from sysfs  # ./reuseport_bpf_numa: failed to pin to node: No such file or directory  not ok 3 selftests: net: reuseport_bpf_numa # exit=1 [ Fix ] In some platforms the numa node numbers are not necessarily consecutive, so when reuseport_bpf_numa iterates on the nodes from 0 to the max available node some of those will not be available. The fix is to change the testcase so it checks whether the node is available before trying to send/receive from it. [ Test ] Run reuseport_bpf_numa from selftests/net in one of the affected test nodes. [ Where Problems Could Occur ] This is a very simple fix which relies on the libnuma exported functions and bitmaps to check whether a numa node number is available on the system. If something is not right on how this check is made or on the libnuma code itself only the reuseport_bpf_numa testcase will be affected by reporting false negatives or having a reduced test coverage. [ Original bug report ] This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is:  # selftests: net: reuseport_bpf_numa  # IPv4 UDP  # send node 0, receive socket 0  # send node 1, receive socket 7  # ./reuseport_bpf_numa: node id/receive socket mismatch  not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
This bug is awaiting verification that the linux/5.4.0-92.103 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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! -- 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/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read
[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
This bug is awaiting verification that the linux/5.4.0-92.103 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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! -- 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/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC systems with:  # selftests: net: reuseport_bpf_numa  # IPv4 UDP  # send node 0, receive socket 0  # libnuma: Warning: Cannot read node cpumask from sysfs  # ./reuseport_bpf_numa: failed to pin to node: No such file or directory  not ok 3 selftests: net: reuseport_bpf_numa # exit=1 [ Fix ] In some platforms the numa node numbers are not necessarily consecutive, so when reuseport_bpf_numa iterates on the nodes from 0 to the max available node some of those will not be available. The fix is to change the testcase so it checks whether the node is available before trying to send/receive from it. [ Test ] Run reuseport_bpf_numa from selftests/net in one of the affected test nodes. [ Where Problems Could Occur ] This is a very simple fix which relies on the libnuma exported functions and bitmaps to check whether a numa node number is available on the system. If something is not right on how this check is made or on the libnuma code itself only the reuseport_bpf_numa testcase will be affected by reporting false negatives or having a reduced test coverage. [ Original bug report ] This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is:  # selftests: net: reuseport_bpf_numa  # IPv4 UDP  # send node 0, receive socket 0  # send node 1, receive socket 7  # ./reuseport_bpf_numa: node id/receive socket mismatch  not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC systems with:  # selftests: net: reuseport_bpf_numa  # IPv4 UDP  # send node 0, receive socket 0  # libnuma: Warning: Cannot read node cpumask from sysfs  # ./reuseport_bpf_numa: failed to pin to node: No such file or directory  not ok 3 selftests: net: reuseport_bpf_numa # exit=1 [ Fix ] In some platforms the numa node numbers are not necessarily consecutive, so when reuseport_bpf_numa iterates on the nodes from 0 to the max available node some of those will not be available. The fix is to change the testcase so it checks whether the node is available before trying to send/receive from it. [ Test ] Run reuseport_bpf_numa from selftests/net in one of the affected test nodes. [ Where Problems Could Occur ] This is a very simple fix which relies on the libnuma exported functions and bitmaps to check whether a numa node number is available on the system. If something is not right on how this check is made or on the libnuma code itself only the reuseport_bpf_numa testcase will be affected by reporting false negatives or having a reduced test coverage. [ Original bug report ] This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is:  # selftests: net: reuseport_bpf_numa  # IPv4 UDP  # send node 0, receive socket 0  # send node 1, receive socket 7  # ./reuseport_bpf_numa: node id/receive socket mismatch  not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. 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! -- 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/1947206 Title: Updates to ib_peer_memory requested by Nvidia Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] Nvidia notified me via private email that they'd discovered some issues with the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch intended to resolve them. My knowledge of these changes is limited to what is mentioned in the commit message: - Allow clients to opt out of unmap during invalidation - Fix some bugs in the sequencing of mlx5 MRs - Enable ATS for peer memory [Test Case] ib_write_bw from the perftest package, rebuilt with CUDA support, can be used as a smoke test of this feature. I'll attach a sample test script here. I've verified this test passes with the kernels in the archive, and continues to pass with the provided patch applied. [Fix] Nvidia has emailed me fixes for both trees. They are not currently available in a public tree elsewhere, though I'm told at some point they should end up in a branch here: Â Â https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/ [What could go wrong] The only known use case for ib_peer_memory are Nvidia GPU users making use of the GPU PeerDirect feature where GPUs can share memory with one another over an Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) with such workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947206 Title: Updates to ib_peer_memory requested by Nvidia Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] Nvidia notified me via private email that they'd discovered some issues with the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch intended to resolve them. My knowledge of these changes is limited to what is mentioned in the commit message: - Allow clients to opt out of unmap during invalidation - Fix some bugs in the sequencing of mlx5 MRs - Enable ATS for peer memory [Test Case] ib_write_bw from the perftest package, rebuilt with CUDA support, can be used as a smoke test of this feature. I'll attach a sample test script here. I've verified this test passes with the kernels in the archive, and continues to pass with the provided patch applied. [Fix] Nvidia has emailed me fixes for both trees. They are not currently available in a public tree elsewhere, though I'm told at some point they should end up in a branch here: Â Â https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/ [What could go wrong] The only known use case for ib_peer_memory are Nvidia GPU users making use of the GPU PeerDirect feature where GPUs can share memory with one another over an Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) with such workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases.
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-impish
** Tags added: verification-needed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
 ->adjust_perf() callback") caused intel_pstate to use nonzero HWP
 desired values in certain usage scenarios, but it did not prevent
 them from being leaked into the confugirations in which HWP desired
 is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1: cking 2316 F pulseaudio
 /dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
 /dev/snd/controlC0: cking 2316 F pulseaudio
 /dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic N/A
 linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
This bug is awaiting verification that the linux/5.4.0-92.103 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d
[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series
This bug is awaiting verification that the linux/5.4.0-92.103 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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! -- 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/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
This bug is awaiting verification that the linux/5.4.0-92.103 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
This bug is awaiting verification that the linux/5.11.0-42.46 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists, change the tag 'verification-needed-hirsute' to
'verification-failed-hirsute'.
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!
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
 ->adjust_perf() callback") caused intel_pstate to use nonzero HWP
 desired values in certain usage scenarios, but it did not prevent
 them from being leaked into the confugirations in which HWP desired
 is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1: cking 2316 F pulseaudio
 /dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
 /dev/snd/controlC0: cking 2316 F pulseaudio
 /dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic N/A
 linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951767] Re: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Incomplete Bug description: [Impact] MAC pass through is not working on new TBT and USB-C docks. [Fix] Enable MAC pass through based on Lenovo USB hub. [Test] Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well. [Where problems could occur] The Realtek USB ethernet in Lenovo USB hub will mess the MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
This bug is awaiting verification that the linux/5.13.0-23.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests
** Description changed: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. + + [Other info] + + SF: #00310705 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-signed-azure package in Ubuntu: New Status in linux-azure source package in Hirsute: In Progress Status in linux-meta-azure source package in Hirsute: In Progress Status in linux-signed-azure source package in Hirsute: In Progress Status in linux-azure source package in Impish: New Status in linux-meta-azure source package in Impish: New Status in linux-signed-azure source package in Impish: New Status in linux-azure source package in Jammy: New Status in linux-meta-azure source package in Jammy: New Status in linux-signed-azure source package in Jammy: New Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. [Other info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
 ->adjust_perf() callback") caused intel_pstate to use nonzero HWP
 desired values in certain usage scenarios, but it did not prevent
 them from being leaked into the confugirations in which HWP desired
 is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1: cking 2316 F pulseaudio
 /dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
 /dev/snd/controlC0: cking 2316 F pulseaudio
 /dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic N/A
 linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
Same here, works with kernel 5.13.0-22. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Fix Released Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
I can also confirm that 5.13.0-22 fixes the Wifi problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Fix Released Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
** Changed in: linux-firmware (Ubuntu) Assignee: Seth Forshee (sforshee) => (unassigned) -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
Wifi now works for me with my XPS 9310 when upgrading to new kernel 5.13.0-22. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Confirmed Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
Maybe this is the case of a missing linux-modules-extra installed? nls_utf8 module seems to be shipped on linux-modules-extra, and the missing package would explain the failure. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952094 Title: CIFS mount error: iocharset utf8 not found Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: After i apt upgrade from linux-image-5.4.0-89-generic to linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS mount error: iocharset utf8 not found", and i rollback it and it restores. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 20:16 seq crw-rw 1 root audio 116, 33 Nov 24 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-07 (109 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 12/17/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
@ayanamist - Can you provide some more details about the full mount path and server type (Windows or Linux and versions) ? Upstream is skeptical that the patch I've reverted is involved in a connection attempt, though empirical evidence suggests otherwise. -- 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/1952094 Title: CIFS mount error: iocharset utf8 not found Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: After i apt upgrade from linux-image-5.4.0-89-generic to linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS mount error: iocharset utf8 not found", and i rollback it and it restores. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 20:16 seq crw-rw 1 root audio 116, 33 Nov 24 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-07 (109 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 12/17/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
It does seem to be at least when I just brought my computer out of sleep that the issue somehow is from a conflict with Linux & a webcam being plugged in, because when I saw last night that there seemed to be a link to the webcam, I unplugged my webcam from my computer & it was not frozen like it was always before. It seems like it could be that some webcams are in conflict with Linux when bringing it out of sleep, I have a laptop that also has a webcam on it, but when that is brought out of sleep, the laptop will load up right away, but my desktop computer is not. -- 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/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). Status in linux package in Ubuntu: Invalid Bug description: at each boot I see the messages: 10:34:47 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). 10:34:47 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 1: -32 (exp. 1). 10:34:46 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 2 on unit 1: -32 (exp. 1). this happen on a partition running Ubuntu 18.10 kernel 4.18.0-7-generic but not on the partition running Ubuntu 18.04 kernel 4.15.0-34 on same hardware The integrated webcam works fine and i don't have other webcam connected. corrado@corrado-HP-p6-cc-0904:~$ uname -a Linux corrado-HP-p6-cc-0904 4.18.0-7-generic #8-Ubuntu SMP Tue Aug 28 18:24:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux corrado@corrado-HP-p6-cc-0904:~$ inxi -Fx System:Host: corrado-HP-p6-cc-0904 Kernel: 4.18.0-7-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.0 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 20.9 Wh condition: 20.9/20.9 Wh (100%) model: 13-42 OA03031 status: Full CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 Speed: 1024 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1098 2: 1098 3: 1097 4: 1101 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.5 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.18.0-7-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 v: 2.3LK-NAPI port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 16.78 GiB (3.6%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 5.99 GiB (19.2%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.0 C mobo: 40.0 C Fan Speeds (RPM): N/A Info: Processes: 198 Uptime: 17m Memory: 3.79 GiB used: 1.02 GiB (26.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 inxi: 3.0.22 corrado@corrado-HP-p6-cc-0904:~$ --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado2680 F pulseaudio /dev/snd/controlC1: corrado2680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-05 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) MachineType: Hewlett-Packard HP 250 G3 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=451b1d0c-94ef-4cbc-bc70-c33f546fa75e ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175
[Kernel-packages] [Bug 1949029] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1949029 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] Re: SSD disappears on Reboot but on cold boot is detected
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949029 Title: SSD disappears on Reboot but on cold boot is detected Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949029] [NEW] SSD disappears on Reboot but on cold boot is detected
You have been subscribed to a public bug: I have a dual boot system (Windows 10 and Ubuntu 21) Lenovo Z50-70 I upgraded my storage to Samsung 870 QVO 1TB. When I reboot the machine via Windows, the machine reboots normally and SSD is detected. However, when I reboot the machine via Ubuntu, the machine will reboot but it won't detect my SSD. I have upgraded to the latest Ubuntu distro and have the latest kernels, etc... I have validated that my installation and boot partitions are correct. Other people who faced an issue similar to mine were using SSDs with NVME. However, my SSD is SATA based, not NVME so neither applying the fix I found about setting nvme latency nor upgrading distro have solved the problem. On Windows, I had initially the same problem but on Windows after selecting AHCI Standard SATA mode, the issue was solved. On Ubuntu, I'm already in AHCI mode but the problem persists. I did few times grub boot repair to validate if it was something messed up with my boot configurations but turned out that it's not. I'm able to use Ubuntu 21 at the moment. However, I'm unable to perform a reboot. Every time I have to shut down the machine and then manually push the laptop's button to launch it again because if I accidentally hit reboot via Ubuntu, the machine will not find SSD and on next boot, the BIOS falls back into Windows Boot Manager and I have to run grub boot repair all over again via live USB. I hope that you will find a solution for this problem soon. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- SSD disappears on Reboot but on cold boot is detected https://bugs.launchpad.net/bugs/1949029 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
Patch to revert that commit has been submitted: https://lists.ubuntu.com/archives/kernel-team/2021-November/126144.html -- 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/1952094 Title: CIFS mount error: iocharset utf8 not found Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: After i apt upgrade from linux-image-5.4.0-89-generic to linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS mount error: iocharset utf8 not found", and i rollback it and it restores. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 20:16 seq crw-rw 1 root audio 116, 33 Nov 24 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-07 (109 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 12/17/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
This bug was fixed in the package linux - 5.4.0-91.102 --- linux (5.4.0-91.102) focal; urgency=medium * focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * KVM emulation failure when booting into VM crash kernel with multiple CPUs (LP: #1948862) - KVM: x86: Properly reset MMU context at vCPU RESET/INIT * aufs: kernel bug with apparmor and fuseblk (LP: #1948470) - SAUCE: aufs: bugfix, stop omitting path->mnt * ebpf: bpf_redirect fails with ip6 gre interfaces (LP: #1947164) - net: handle ARPHRD_IP6GRE in dev_is_mac_header_xmit() * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * ACL updates on OCFS2 are not revalidated (LP: #1947161) - ocfs2: fix remounting needed after setfacl command * ppc64 BPF JIT mod by 1 will not return 0 (LP: #1948351) - powerpc/bpf: Fix BPF_MOD when imm == 1 * Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" (LP: #1947709) - Revert "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" * Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference (LP: #1943464) - s390/pci: fix leak of PCI device structure - s390/pci: fix use after free of zpci_dev - s390/pci: fix zpci_zdev_put() on reserve * [SRU][F] USB: serial: pl2303: add support for PL2303HXN (LP: #1948377) - USB: serial: pl2303: add support for PL2303HXN - USB: serial: pl2303: fix line-speed handling on newer chips * Focal update: v5.4.151 upstream stable release (LP: #1947888) - tty: Fix out-of-bound vmalloc access in imageblit - cpufreq: schedutil: Use kobject release() method to free sugov_tunables - cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory - usb: cdns3: fix race condition before setting doorbell - fs-verity: fix signed integer overflow with i_size near S64_MAX - hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field - hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field - hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field - scsi: ufs: Fix illegal offset in UPIU event trace - mac80211: fix use-after-free in CCMP/GCMP RX - x86/kvmclock: Move this_cpu_pvti into kvmclock.h - drm/amd/display: Pass PCI deviceid into DC - ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 - hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs - mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug - mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap - mac80211: mesh: fix potentially unaligned access - mac80211-hwsim: fix late beacon hrtimer handling - sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb - hwmon: (tmp421) report /PVLD condition as fault - hwmon: (tmp421) fix rounding for negative values - net: ipv4: Fix rtnexthop len when RTA_FLOW is present - e100: fix length calculation in e100_get_regs_len - e100: fix buffer overrun in e100_get_regs - selftests, bpf: test_lwt_ip_encap: Really disable rp_filter - scsi: csiostor: Add module softdep on cxgb4 - net: hns3: do not allow call hns3_nic_net_open repeatedly - net: sched: flower: protect fl_walk() with rcu - af_unix: fix races in sk_peer_pid and sk_peer_cred accesses - perf/x86/intel: Update event constraints for ICX - elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings - debugfs: debugfs_create_file_size(): use IS_ERR to check for error - ipack: ipoctal: fix stack information leak - ipack: ipoctal: fix tty registration race - ipack: ipoctal: fix tty-registration error handling - ipack: ipoctal: fix missing allocation-failure check - ipack: ipoctal: fix module reference leak - ext4: fix loff_t overflow in ext4_max_bitmap_size() - ext4: fix reserved space counter leakage - ext4: fix potential infinite loop in ext4_dx_readdir() - HID: u2fzero: ignore incomplete packets without data - net: udp: annotate data race around udp_sk(sk)->corkflag - net: stmmac: don't attach interface until resume finishes - PCI: Fix pci_host_bridge struct device release/free handling - libnvdimm/pmem: Fix crash triggered when I/O in-flight during unbind - hso: fix bailout in error case of probe - usb: hso: fix error handling code of hso_create_net_device - usb: hso: remove the bailout parameter - crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() - HID: betop: fix slab-out-of-bounds Write in betop_probe - netfilter:
[Kernel-packages] [Bug 1947027] Re: hirsute/linux-azure: Backport CIFS patches
This bug was fixed in the package linux-azure - 5.11.0-1022.23 --- linux-azure (5.11.0-1022.23) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1022.23 -proposed tracker (LP: #1949789) * linux-azure: make mana.ko built-in (LP: #1949357) - [Config] CONFIG_MICROSOFT_MANA=y - [Config] remove mana from azure.modules * hirsute/linux-azure: Backport CIFS patches (LP: #1947027) - Revert "CIFS: Fix a potencially linear read overflow" - Revert "smb3: fix posix extensions mount option" - Revert "cifs: create sd context must be a multiple of 8" - Revert "smb3: rc uninitialized in one fallocate path" - Revert "cifs: add missing parsing of backupuid" - Revert "cifs: use helpers when parsing uid/gid mount options and validate them" - Revert "SMB3: fix readpage for large swap cache" - Revert "cifs: fix the out of range assignment to bit fields in parse_server_interfaces" - Revert "cifs: fix fallocate when trying to allocate a hole." - Revert "cifs: only write 64kb at a time when fallocating a small region of a file" - Revert "cifs: prevent NULL deref in cifs_compose_mount_options()" - Revert "cifs: Do not use the original cruid when following DFS links for multiuser mounts" - Revert "cifs: use the expiry output of dns_query to schedule next resolution" - Revert "cifs: handle reconnect of tcon when there is no cached dfs referral" - Revert "smb3: fix uninitialized value for port in witness protocol move" - Revert "cifs: fix check of dfs interlinks" - Revert "cifs: fix missing spinlock around update to ses->status" - Revert "cifs: improve fallocate emulation" - Revert "SMB3: incorrect file id in requests compounded with open" - Revert "cifs: set server->cipher_type to AES-128-CCM for SMB3.0" - Revert "cifs: fix memory leak in smb2_copychunk_range" - Revert "smb3: do not attempt multichannel to server which does not support it" - Revert "smb3: if max_channels set to more than one channel request multichannel" - Revert "smb3: when mounting with multichannel include it in requested capabilities" - Revert "smb2: fix use-after-free in smb2_ioctl_query_info()" - Revert "cifs: fix regression when mounting shares with prefix paths" - Revert "cifs: detect dead connections only when echoes are enabled." - Revert "cifs: fix leak in cifs_smb3_do_mount() ctx" - Revert "cifs: fix out-of-bound memory access when calling smb3_notify() at mount point" - Revert "cifs: Return correct error code from smb2_get_enc_key" - Revert "cifs: On cifs_reconnect, resolve the hostname again." - Revert "cifs: escape spaces in share names" - Revert "cifs: Silently ignore unknown oplock break handle" - Revert "cifs: revalidate mapping when we open files for SMB1 POSIX" - Revert "cifs: Adjust key sizes and key generation routines for AES256 encryption" - Revert "smb3: fix cached file size problems in duplicate extents (reflink)" - Revert "cifs: change noisy error message to FYI" - Revert "cifs: ask for more credit on async read/write code paths" - Revert "cifs: Fix preauth hash corruption" - Revert "cifs: fix allocation size on newly created files" - Revert "cifs: warn and fail if trying to use rootfs without the config option" - Revert "cifs: do not send close in compound create+close requests" - Revert "cifs: return proper error code in statfs(2)" - Revert "cifs: fix credit accounting for extra channel" - Revert "cifs: fix handling of escaped ',' in the password mount argument" - Revert "cifs: fix nodfs mount option" - Revert "cifs: introduce helper for finding referral server to improve DFS target resolution" - Revert "cifs: check all path components in resolved dfs target" - Revert "cifs: fix DFS failover" - Revert "cifs: Fix inconsistent IS_ERR and PTR_ERR" - cifs_debug: use %pd instead of messing with ->d_name - smb3: negotiate current dialect (SMB3.1.1) when version 3 or greater requested - cifs: fix trivial typo - cifs: New optype for session operations. - cifs: Fix in error types returned for out-of-credit situations. - cifs: Identify a connection by a conn_id. - cifs: Reformat DebugData and index connections by conn_id. - cifs: Fix inconsistent IS_ERR and PTR_ERR - cifs: change confusing field serverName (to ip_addr) - cifs: clarify hostname vs ip address in /proc/fs/cifs/DebugData - cifs: Fix cifsacl ACE mask for group and others. - cifs: Retain old ACEs when converting between mode bits and ACL. - cifs: Change SIDs in ACEs while transferring file ownership. - cifs: cleanup a few le16 vs. le32 uses in cifsacl.c - TCON Reconnect during STATUS_NETWORK_NAME_DELETED - cifs: minor simplification to smb2_is_network_name_deleted - cifs: If a corrupted DACL is returned by the
[Kernel-packages] [Bug 1949357] Re: linux-azure: make mana.ko built-in
This bug was fixed in the package linux-azure - 5.11.0-1022.23 --- linux-azure (5.11.0-1022.23) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1022.23 -proposed tracker (LP: #1949789) * linux-azure: make mana.ko built-in (LP: #1949357) - [Config] CONFIG_MICROSOFT_MANA=y - [Config] remove mana from azure.modules * hirsute/linux-azure: Backport CIFS patches (LP: #1947027) - Revert "CIFS: Fix a potencially linear read overflow" - Revert "smb3: fix posix extensions mount option" - Revert "cifs: create sd context must be a multiple of 8" - Revert "smb3: rc uninitialized in one fallocate path" - Revert "cifs: add missing parsing of backupuid" - Revert "cifs: use helpers when parsing uid/gid mount options and validate them" - Revert "SMB3: fix readpage for large swap cache" - Revert "cifs: fix the out of range assignment to bit fields in parse_server_interfaces" - Revert "cifs: fix fallocate when trying to allocate a hole." - Revert "cifs: only write 64kb at a time when fallocating a small region of a file" - Revert "cifs: prevent NULL deref in cifs_compose_mount_options()" - Revert "cifs: Do not use the original cruid when following DFS links for multiuser mounts" - Revert "cifs: use the expiry output of dns_query to schedule next resolution" - Revert "cifs: handle reconnect of tcon when there is no cached dfs referral" - Revert "smb3: fix uninitialized value for port in witness protocol move" - Revert "cifs: fix check of dfs interlinks" - Revert "cifs: fix missing spinlock around update to ses->status" - Revert "cifs: improve fallocate emulation" - Revert "SMB3: incorrect file id in requests compounded with open" - Revert "cifs: set server->cipher_type to AES-128-CCM for SMB3.0" - Revert "cifs: fix memory leak in smb2_copychunk_range" - Revert "smb3: do not attempt multichannel to server which does not support it" - Revert "smb3: if max_channels set to more than one channel request multichannel" - Revert "smb3: when mounting with multichannel include it in requested capabilities" - Revert "smb2: fix use-after-free in smb2_ioctl_query_info()" - Revert "cifs: fix regression when mounting shares with prefix paths" - Revert "cifs: detect dead connections only when echoes are enabled." - Revert "cifs: fix leak in cifs_smb3_do_mount() ctx" - Revert "cifs: fix out-of-bound memory access when calling smb3_notify() at mount point" - Revert "cifs: Return correct error code from smb2_get_enc_key" - Revert "cifs: On cifs_reconnect, resolve the hostname again." - Revert "cifs: escape spaces in share names" - Revert "cifs: Silently ignore unknown oplock break handle" - Revert "cifs: revalidate mapping when we open files for SMB1 POSIX" - Revert "cifs: Adjust key sizes and key generation routines for AES256 encryption" - Revert "smb3: fix cached file size problems in duplicate extents (reflink)" - Revert "cifs: change noisy error message to FYI" - Revert "cifs: ask for more credit on async read/write code paths" - Revert "cifs: Fix preauth hash corruption" - Revert "cifs: fix allocation size on newly created files" - Revert "cifs: warn and fail if trying to use rootfs without the config option" - Revert "cifs: do not send close in compound create+close requests" - Revert "cifs: return proper error code in statfs(2)" - Revert "cifs: fix credit accounting for extra channel" - Revert "cifs: fix handling of escaped ',' in the password mount argument" - Revert "cifs: fix nodfs mount option" - Revert "cifs: introduce helper for finding referral server to improve DFS target resolution" - Revert "cifs: check all path components in resolved dfs target" - Revert "cifs: fix DFS failover" - Revert "cifs: Fix inconsistent IS_ERR and PTR_ERR" - cifs_debug: use %pd instead of messing with ->d_name - smb3: negotiate current dialect (SMB3.1.1) when version 3 or greater requested - cifs: fix trivial typo - cifs: New optype for session operations. - cifs: Fix in error types returned for out-of-credit situations. - cifs: Identify a connection by a conn_id. - cifs: Reformat DebugData and index connections by conn_id. - cifs: Fix inconsistent IS_ERR and PTR_ERR - cifs: change confusing field serverName (to ip_addr) - cifs: clarify hostname vs ip address in /proc/fs/cifs/DebugData - cifs: Fix cifsacl ACE mask for group and others. - cifs: Retain old ACEs when converting between mode bits and ACL. - cifs: Change SIDs in ACEs while transferring file ownership. - cifs: cleanup a few le16 vs. le32 uses in cifsacl.c - TCON Reconnect during STATUS_NETWORK_NAME_DELETED - cifs: minor simplification to smb2_is_network_name_deleted - cifs: If a corrupted DACL is returned by the
