[Kernel-packages] [Bug 1979030] Re: Multiple error and bugs during boot on Ubuntu 22.04 LTS
** Changed in: linux (Ubuntu) Assignee: Mohammad Mahdi (taiwbi) => (unassigned) -- 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/1979030 Title: Multiple error and bugs during boot on Ubuntu 22.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Since I update my ubuntu to 22.04 LTS, I get these errors during boot: Jun 13 14:37:55 ubuntu kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Jun 13 14:37:55 ubuntu kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Jun 13 14:37:55 ubuntu kernel: ACPI: Skipping parse of AML opcode: Method (0x0014) above error repeated many times. Jun 13 14:37:55 ubuntu kernel: nvme nvme0: failed to set APST feature (2) Jun 13 14:37:55 ubuntu kernel: ACPI BIOS Error (bug): Could not resolve symbol [\DPPP], AE_NOT_FOUND (20210730/psargs-330) Jun 13 14:37:55 ubuntu kernel: Jun 13 14:37:55 ubuntu kernel: No Local Variables are initialized for Method [IDSP] Jun 13 14:37:55 ubuntu kernel: Jun 13 14:37:55 ubuntu kernel: No Arguments are initialized for method [IDSP] Jun 13 14:37:55 ubuntu kernel: Jun 13 14:37:55 ubuntu kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 13 14:37:55 ubuntu kernel: ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20210730/nsprepkg-94) Jun 13 14:37:58 ubuntu thermald[679]: Unsupported condition 50 (User_presence) Jun 13 14:37:58 ubuntu thermald[679]: Unsupported condition 50 (User_presence) Jun 13 14:37:58 ubuntu thermald[679]: Unsupported condition 9 (Aggregate_power_percentage) Jun 13 14:37:58 ubuntu thermald[679]: Unsupported condition 9 (Aggregate_power_percentage) Jun 13 14:37:58 ubuntu thermald[679]: Unsupported condition 9 (Aggregate_power_percentage) Jun 13 14:37:58 ubuntu thermald[679]: Unsupported conditions are present Jun 13 14:37:58 ubuntu thermald[679]: Polling mode is enabled: 4 Jun 13 14:37:58 ubuntu gdm-launch-environment][1073]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=126) by (uid=0) Jun 13 14:37:58 ubuntu kernel: ACPI BIOS Error (bug): Could not resolve symbol [\DPPP], AE_NOT_FOUND (20210730/psargs-330) Jun 13 14:37:58 ubuntu kernel: Jun 13 14:37:58 ubuntu kernel: No Local Variables are initialized for Method [IDSP] Jun 13 14:37:58 ubuntu kernel: Jun 13 14:37:58 ubuntu kernel: No Arguments are initialized for method [IDSP] Jun 13 14:37:58 ubuntu kernel: Jun 13 14:37:58 ubuntu kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 13 14:37:58 ubuntu kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 13 17:00:10 ubuntu nm-openvpn[15506]: AEAD Decrypt error: bad packet ID (may be a replay): [ #59175 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings * This report may be duplicated by #1978917. I just tried to send the report with the 'ubuntu-bug linux' command to provide you with more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-39-generic 5.15.0-39.42 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mahdi 2413 F pulseaudio CasperMD5CheckResult: pass Date: Fri Jun 17 09:44:14 2022 HibernationDevice: RESUME=UUID=f56ee4ed-58ac-49d4-a438-3ca75f08397a InstallationDate: Installed on 2022-03-02 (106 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56dd IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 13d3:3491 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FLC_R564FL ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2d8fb36c-c4c1-48be-b649-9fffa7a1440c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2
[Kernel-packages] [Bug 1986168] Re: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS
@vanvugt (comment from 2022-08-15): I'm using 'Ubuntu on Xorg' with following configuration (see below) in '/usr/share/X11/xorg.conf.d/40-libinput.conf' with follwing result: - forward & back buttons work fine - left & right button work fine - 'MiddleEmulation' work fine - but scrolling the page - click and hold button 3 (back) (see https://help.ubuntu.com/community/Logitech_Marblemouse_USB) + rolling the ball doesn't work - 'back function' intervenes faster... In the 20.04 all functions worked fine... Section "InputClass" Identifier "Marble Mouse" MatchProduct "Logitech USB Trackball" MatchIsPointer "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "ScrollMethod" "button" Option "ScrollButton" "8" Option "MiddleEmulation" "true" EndSection -- 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/1986168 Title: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: 1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf etc according to https://help.ubuntu.com/community/Logitech_Marblemouse_USB 2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are still in place but the Marble Mouse buttons I configured previously are not working. Expected behavior is they should still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1986168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Same problem here. Thinkpad P14s Gen1, 32GB Ram. Was working fine on 20.04 - and after the upgrade to 22.04.1, everything is totally laggy, CPU consumption almost always at 100%. iommu=off made it slightly better, but still not acceptable... -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
We are now running a Dell platform certification with the module, it has an issue about no signal, we are collaborating with ODM to clarify it. Could we leave the bug for a while, I'll notify here once everything is clear. Thanks, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi Jaejeon, Please let us know if there are any further opens in this ticket and if not, can we close the ticket. Thanks and Best Regards, Murali -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988494] Re: ubuntu display error
*** This bug is a duplicate of bug 1969959 *** https://bugs.launchpad.net/bugs/1969959 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1969959, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: nouveau ** This bug has been marked a duplicate of bug 1969959 [nouveau] Weird colors after startup (Ubuntu 22.04) -- 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/1988494 Title: ubuntu display error Status in linux package in Ubuntu: New Bug description: Booting from T7 Samsung SSD "trying Ubuntu" my display on Ubuntu seems to have a red/orange filter enabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 02:10:23 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GA102 [GeForce RTX 3080 Lite Hash Rate] [1028:c890] LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware Aurora Ryzen Edition ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2022 dmi.bios.release: 2.3 dmi.bios.vendor: Alienware dmi.bios.version: 2.3.1 dmi.board.name: 0TYR0X dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr2.3.1:bd07/11/2022:br2.3:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.3.1:rvnAlienware:rn0TYR0X:rvrA01:cvnAlienware:ct3:cvrNotSpecified:sku0A8B: dmi.product.family: Alienware dmi.product.name: Alienware Aurora Ryzen Edition dmi.product.sku: 0A8B dmi.product.version: 2.3.1 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988494] [NEW] ubuntu display error
You have been subscribed to a public bug: Booting from T7 Samsung SSD "trying Ubuntu" my display on Ubuntu seems to have a red/orange filter enabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 2 02:10:23 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GA102 [GeForce RTX 3080 Lite Hash Rate] [1028:c890] LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware Aurora Ryzen Edition ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2022 dmi.bios.release: 2.3 dmi.bios.vendor: Alienware dmi.bios.version: 2.3.1 dmi.board.name: 0TYR0X dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr2.3.1:bd07/11/2022:br2.3:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.3.1:rvnAlienware:rn0TYR0X:rvrA01:cvnAlienware:ct3:cvrNotSpecified:sku0A8B: dmi.product.family: Alienware dmi.product.name: Alienware Aurora Ryzen Edition dmi.product.sku: 0A8B dmi.product.version: 2.3.1 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- ubuntu display error https://bugs.launchpad.net/bugs/1988494 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 1969086] Re: Enable swiotlb to avoid untrusted devices errors on AMD platforms
As dependency bug 1969091 was covered by v5.15.33 this is really just two patches, and the more important one is 5.15.y already. The other one is just messaging: f316ba0a8814f4c91e80a435da3421baf0ddd24c. # git describe --contains 9e53c25f326604c838d528b430b8e603944b9e28 v5.15.46~190 It's landed in ubuntu's Jammy kernel too and OEM kernel too: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/drivers/iommu/amd?h=master-next=a0468da388126aece4c989eee5a6cd83945cf731 https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/jammy/commit/drivers/iommu/amd?h=oem-5.17-next=6f64d8b2cb741bb9938fedc0446f1d8be6724ae6 $ git describe --contains a0468da388126aece4c989eee5a6cd83945cf731 Ubuntu-5.15.0-47.50~244 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => 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/1969086 Title: Enable swiotlb to avoid untrusted devices errors on AMD platforms Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: It's been observed that plugging in a TBT3 NVME device to a port marked with ExternalFacingPort that some DMA transactions occur that are not a full page and so the DMA API attempts to use software bounce buffers instead of relying upon the IOMMU translation. This doesn't work and leads to messaging like: swiotlb buffer is full (sz: 4096 bytes), total 0 (slots), used 0 (slots) The bounce buffers were originally set up, but torn down during the boot process. * This happens because as part of IOMMU initialization `amd_iommu_init_dma_ops` gets called and resets the global swiotlb to 0. * When late_init gets called `pci_swiotlb_late_init` `swiotlb_exit` is called and the buffers are torn down. This can be observed in the logs: ``` [0.407286] AMD-Vi: Extended features (0x246577efa2254afa): PPR NX GT [5] IA GA PC GA_vAPIC [0.407291] AMD-Vi: Interrupt remapping enabled [0.407292] AMD-Vi: Virtual APIC enabled [0.407872] software IO TLB: tearing down default memory pool ``` This series fixes the behavior of AMD IOMMU to enable swiotlb so that non-page aligned DMA goes through a bounce buffer. It also adds a message to help with debugging similar problems in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
I can see this issue with B-5.4 lttng-modules-dkms 2.10.8-1ubuntu2~18.04.3 as well. /var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe- random.c:31:10: fatal error: trace/events/random.h: No such file or directory ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: lttng-modules (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix -- 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver
Yes 'linux' is the correct package but the kernel changelog is often deceiving with fixes coming from commits that don't sound related to what you want. ** Package changed: nvidia-graphics-drivers-515 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => 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/1987134 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver Status in linux package in Ubuntu: Fix Released Bug description: An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend to lead to a black screen. Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01 did not resolve the issue. There are several Nvidia sleep tickets that at first seem related, but mention dmesg entries that I am not seeing which makes me suspect I have a different issue: * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088 * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303 Workaround dhenry mentions in 1970088 of disabling the nvidia suspend and hibernate systemd services makes no difference for me. Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01, AMD Ryzen 7 5800X. Here are journalctl excerpts during the reboot process, with and without nvidia systemd suspend services. dmesg and /var/log/kern.log show no errors as are mentioned in the above tickets. With disabled nvidia suspend systemd services: Aug 19 12:42:37 uf-panacea ModemManager[2731]: [sleep-monitor] system is about to suspend Aug 19 12:42:37 uf-panacea NetworkManager[2617]: [1660938157.8491] manager: NetworkManager state> Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep. Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for GRUB... Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend... Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 'suspend'... Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for GRUB. With enabled nvidia suspend systemd services: Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend actions... Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: nvidia-suspend.service Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for GRUB. Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection... Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "40" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "43" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "44" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4 - USB Mouse OKLIC: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "45" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5 - USB Mouse OKLIC Mouse: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "46" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6 - USB Mouse OKLIC System Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "47" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7 - USB Mouse OKLIC Consumer Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - Valve Software Steam Controller: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9 - Logitech G305: device removed Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 processes of 1 users. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**)
[Kernel-packages] [Bug 1983291] Re: Update firmware for DCN316/GFX1037
Checked on correct system $ cat /proc/cpuinfo | grep "model\|family" | head -n 2 cpu family : 23 model : 160 $ dpkg -l | grep linux-firmware ii linux-firmware 20220329.git681281e4-0ubuntu3.5 all Firmware for Linux kernel drivers Ran a few cycles of s0i3, things look good. # cat /sys/kernel/debug/amd_pmc/smu_fw_info |grep "Last S0i3 Status" Last S0i3 Status: Success ** Tags added: verification-done-jammy -- 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/1983291 Title: Update firmware for DCN316/GFX1037 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Jammy already has firmware for upcoming product with GFX1037 and DCN316. However this firmware has some stability problems under stress and it should be updated to latest on linux-firmware.git to support systems that will take this firmware. [Fix] Upgrade following binaries: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122 [Test] Verify suspend/resume works. Verify that accelerated graphics works. Verify video playback works. [Where problems could occur] Firmware is only loaded to product with GFX1037/DCN316 This isn't yet on the market and regressions are not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Can you please see if it's working after suspend on previous kernel versions like 5.15.0-46? -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]: Operation 'sleep' finished. ``` I think the problem is: >
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
Can you please attach dmesg? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Status in Debian: New Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.0-34-generic N/A
[Kernel-packages] [Bug 1988466] Re: Getting "Operation not permitted" on "sudo apt upgrade"
/boot is full? Please run `df -h /boot`. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988473] Re: Version 5.15.0-47 Breaks Virtualbox Win10 VM
I can confirm, this is a bug in the kernel 47. I have an AMD Ryzen 7 5800. In my case the Windows 10 boots up in VM, but when I execute any Chromium based browser inside the VM it crashes without an error message. After trying several times to execute the browser the guest system also crashes without BSOD, and restarts. -- 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/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988479] Re: Jammy update: v5.15.58 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.58 upstream stable release + from git://git.kernel.org/ -v5.15.58 upstream stable release -from git://git.kernel.org/ + pinctrl: stm32: fix optional IRQ support to gpios + riscv: add as-options for modules with assembly compontents + mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication + lockdown: Fix kexec lockdown bypass with ima policy + drm/ttm: fix locking in vmap/vunmap TTM GEM helpers + bus: mhi: host: pci_generic: add Telit FN980 v1 hardware revision + bus: mhi: host: pci_generic: add Telit FN990 + Revert "selftest/vm: verify remap destination address in mremap_test" + Revert "selftest/vm: verify mmap addr in mremap_test" + PCI: hv: Fix multi-MSI to allow more than one MSI vector + PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI + PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() + PCI: hv: Fix interrupt mapping for multi-MSI + serial: mvebu-uart: correctly report configured baudrate value + batman-adv: Use netif_rx_any_context() any. + xfs: fix maxlevels comparisons in the btree staging code + xfs: fold perag loop iteration logic into helper function + xfs: rename the next_agno perag iteration variable + xfs: terminate perag iteration reliably on agcount + xfs: fix perag reference leak on iteration race with growfs + xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list() + r8152: fix a WOL issue + ip: Fix data-races around sysctl_ip_default_ttl. + xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() + power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe + RDMA/irdma: Do not advertise 1GB page size for x722 + RDMA/irdma: Fix sleep from invalid context BUG + pinctrl: ralink: rename MT7628(an) functions to MT76X8 + pinctrl: ralink: rename pinctrl-rt2880 to pinctrl-ralink + pinctrl: ralink: Check for null return of devm_kcalloc + perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() + ipv4/tcp: do not use per netns ctl sockets + net: tun: split run_ebpf_filter() and pskb_trim() into different "if statement" + mm/pagealloc: sysctl: change watermark_scale_factor max limit to 30% + sysctl: move some boundary constants from sysctl.c to sysctl_vals + tcp: Fix data-races around sysctl_tcp_ecn. + drm/amd/display: Add option to defer works of hpd_rx_irq + drm/amd/display: Fork thread to offload work of hpd_rx_irq + drm/amdgpu/display: add quirk handling for stutter mode + drm/amd/display: Ignore First MST Sideband Message Return Error + scsi: megaraid: Clear READ queue map's nr_queues + scsi: ufs: core: Drop loglevel of WriteBoost message + nvme: check for duplicate identifiers earlier + nvme: fix block device naming collision + igc: Reinstate IGC_REMOVED logic and implement it properly + ip: Fix data-races around sysctl_ip_no_pmtu_disc. + ip: Fix data-races around sysctl_ip_fwd_use_pmtu. + ip: Fix data-races around sysctl_ip_fwd_update_priority. + ip: Fix data-races around sysctl_ip_nonlocal_bind. + ip: Fix a data-race around sysctl_ip_autobind_reuse. + ip: Fix a data-race around sysctl_fwmark_reflect. + tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept. + tcp: sk->sk_bound_dev_if once in inet_request_bound_dev_if() + tcp: Fix data-races around sysctl_tcp_l3mdev_accept. + tcp: Fix data-races around sysctl_tcp_mtu_probing. + tcp: Fix data-races around sysctl_tcp_base_mss. + tcp: Fix data-races around sysctl_tcp_min_snd_mss. + tcp: Fix a data-race around sysctl_tcp_mtu_probe_floor. + tcp: Fix a data-race around sysctl_tcp_probe_threshold. + tcp: Fix a data-race around sysctl_tcp_probe_interval. + net: stmmac: fix pm runtime issue in stmmac_dvr_remove() + net: stmmac: fix unbalanced ptp clock issue in suspend/resume flow + mtd: rawnand: gpmi: validate controller clock rate + mtd: rawnand: gpmi: Set WAIT_FOR_READY timeout based on program/erase times + net: dsa: microchip: ksz_common: Fix refcount leak bug + net: skb: introduce kfree_skb_reason() + net: skb: use kfree_skb_reason() in tcp_v4_rcv() + net: skb: use kfree_skb_reason() in
[Kernel-packages] [Bug 1981783] Re: there is an ACPI error message every time it booting
** Bug watch added: Linux Kernel Bug Tracker #216390 https://bugzilla.kernel.org/show_bug.cgi?id=216390 -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
Created attachment 301572 alsa-info -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
Created attachment 301571 fwts -all -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
Created attachment 301570 pact -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
This is still an issue; running pop_os with 5.19.1-051901-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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783]
@mario, thanks for your answer. i opened an new issue: https://bugzilla.kernel.org/show_bug.cgi?id=216390 -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783]
Arthur your issues are different. Open your own issue and be sure to attach a full log and details of the regression: which BIOS or which kernel introduced it If it's not a regression you should report it to Lenovo. -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987870] Re: Demote to proposed LRM portions of intel-iotg
Dimitri, we should drop linux-intel-iotg from kinect from now. So far we don't need to provide this kernel for 22.10 GA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: Demote to proposed LRM portions of intel-iotg Status in linux-restricted-modules-intel-iotg package in Ubuntu: Triaged Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Triaged Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. Please demote to proposed linux-restricted-modules-intel-iotg linux- restricted-signatures-intel-iotg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+bug/1987870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783]
Lenovo Thinkpad P14s AMD Gen2 still errors here: [0.449031] ACPI BIOS Error (Bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.AC._PSR.AFN4], AE_NOT_FOUND (20220331/psargs-330) [0.449046] ACPI Error: Abotrting method \_SB.PCI0.LPC0.EC0.AC._PSR due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Kernel: Linux 5.19.2-arch1-1 -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
The previous Kernel I used was 5.4.0-81-generic on ubuntu 20.04. Grepping through /var/log there is no mention of cm32181 before the upgrade data (August 19th). After the upgrade to 5.15.0-47-generic and Ubuntu 22.04 the "cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121" appears. These errors continue with 5.15.0-48-generic If I run ```bash while true; do cat /sys/devices/pci:00/INT33C3:00/i2c-0/i2c-CPLM3218:00/iio:device0/in_illuminance_input; sleep 0.1; done ``` it returns 0, then if i shine a torch at the top left corner of the screen it registers different numbers, the max I saw was 500. If I suspend the laptop, the suspend will fail. After the failed suspend I can still run the above cat command and get a brightness readout. Is there any other debugging I can do to help figure out what is wrong? Perhaps I just need to tell the suspend system to ignore i2c? -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop
[Kernel-packages] [Bug 1988479] Re: Jammy update: v5.15.58 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1988479 Title: Jammy update: v5.15.58 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.58 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988479] [NEW] Jammy update: v5.15.58 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.58 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) 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/1988479 Title: Jammy update: v5.15.58 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.58 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
Launchpad has imported 8 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=81611. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-08-04T07:56:31+00:00 rockorequin wrote: Created attachment 145021 guvcview output, uvc trace output, lsusb output guvcview used to work fine with kernel 3.15 and earlier with my laptop webcam, but with kernel 3.16 (amd64) it just shows (and captures) a black screen and reports "Could not grab image (select timeout): Resource temporarily unavailable" or "ignoring empty buffer". With 3.15 it would complain that the resource was temporarily unavailable once or twice, but would then recover and display streaming video. I built the kernel using the same config as the ubuntu mainline builds for 3.16. 'motion' and 'skype' are both able to capture video with 3.16, so the underlying v4l driver looks like it is working. Is video (other) the right component to file this under? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/0 On 2014-08-07T14:25:06+00:00 chrylis wrote: I can confirm identical behavior on a Dell M6600 integrated webcam. The device has USB ID 1bcf:280b and is listed as "Sunplus Innovation Technology Inc.". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/1 On 2014-08-08T08:44:01+00:00 rockorequin wrote: I tested and it occurs with 3.16-rc2, so it regressed fairly early on. I couldn't test with 3.16-rc1 in the VM I set up because it failed to boot. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/2 On 2014-09-24T03:55:48+00:00 rockorequin wrote: The bug is still present in both 3.16.3 and 3.17-rc6. I started attempting to bisect, but 3.16-rc1 doesn't get past the very early boot stages on the laptop I first saw the problem on (I can't even get a tty prompt in recovery mode). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/19 On 2014-09-30T10:36:56+00:00 suse wrote: I was able to bisect and it looks like commit 61bd8fb37db948154ae01c8ed43a86633ae1d2be introduces the black screen. Using v3.16 and reverting 61bd8fb37db948154ae01c8ed43a86633ae1d2be works in virtualbox. I will try to test the fix on real hardware soon. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/21 On 2014-09-30T11:11:16+00:00 suse wrote: OK, laptop test successfully finished. with kernel v3.17-rc6 I need to revert two commits: 8a75ffb81b1c1b6949d191fbef3eaa03fd648852 [media] vb2: fix bytesused == 0 handling and again 61bd8fb37db948154ae01c8ed43a86633ae1d2be [media] vb2: if bytesused is 0, then fill with output buffer length Reverting both commits makes my two webcams working again. (integrated webcam 04f2:b1b4 and external 046d:09a4) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/22 On 2014-10-01T12:13:08+00:00 hverkuil wrote: I think you hit this guvcview bug: http://www.mail-archive.com/linux-media@vger.kernel.org/msg80144.html So it's not a driver bug, it's a bug in the application which was exposed by the driver change. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/24 On 2022-08-28T12:36:11+00:00 suse wrote: bug report should be closed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/comments/31 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Won't Fix Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports "Could not grab image" or "ignoring empty buffer". The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug
[Kernel-packages] [Bug 1983180] Re: ACPI Error _CPC not found
Launchpad has imported 73 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=213023. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-05-10T17:23:25+00:00 ionut_n2001 wrote: Hi Kernel Team, Observe this issue: [2.057284] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330) [2.057339] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [2.057443] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330) [2.057484] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [2.057569] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330) [2.057610] ACPI Error: Aborting method \_PR.CPU3._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz Stepping:9 CPU MHz: 2200.000 CPU max MHz: 3400. CPU min MHz: 400. BogoMIPS:4399.99 Virtualization: VT-x L1d cache: 64 KiB L1i cache: 64 KiB L2 cache:512 KiB L3 cache:4 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_t sc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibp b stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsav ec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d dmesg | grep -E "ACPI|BIOS" [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x00057fff] usable [0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved [0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x6cdbefff] usable [0.00] BIOS-e820: [mem 0x6cdbf000-0x6cdb] ACPI NVS [0.00] BIOS-e820: [mem 0x6cdc-0x6cdc0fff] reserved [0.00] BIOS-e820: [mem 0x6cdc1000-0x7a465fff] usable [0.00] BIOS-e820: [mem 0x7a466000-0x7a7a4fff] reserved [0.00] BIOS-e820: [mem 0x7a7a5000-0x7a7e2fff] ACPI data [0.00] BIOS-e820: [mem 0x7a7e3000-0x7afbafff] ACPI NVS [0.00] BIOS-e820: [mem 0x7afbb000-0x7b3fdfff] reserved [0.00] BIOS-e820: [mem 0x7b3fe000-0x7b3fefff] usable [
[Kernel-packages] [Bug 1988473] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: Confirmed Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988475] [NEW] 22.04 and vc4-fkms-v3d / vc4-kms-v3d overlays problem
Public bug reported: I have RPi4/8GB RAM. I had no problems with 20.04LTS. 'fkms' overlay was used by default, and I never changed it. I have serious problem after upgrade to 22.04. 1. vc4-fkms-v3d overlay (is used by default) causes very big lags in windows dragging by mouse. Also video player (any) freezes the video while mouse is moved across the screen. Sound goes OK though. 2. vc4-kms-v3d works softly, without any lags, when 'builtin-Xpresent' or 'picom:GLX' window manager is on. But both 'vc4-kms-v3d' and 'vc4-kms-v3d-pi4' cause random HDMI signal disappearance when video is running in any video player (both Celluloid and VLC were tested). Screen becomes black, then "No signal" message appears. Green "SD-card access" indicator is on at this time. This behavior was checked in both 20.04LTS and 22.04LTS. But 'fkms' overlay worked OK in 20.04, so it was the solution there. Now in 22.04 I have no solution, so I need to downgrade back to 20.04 unless this bug will be fixed. Also I tried to install KODI in 22.04. It runs with permanent (100%-reproduced) bug, as it was described above. Black screen appears instead of main KODI menu, then "No signal" message appears. Of course, it so happens only with 'kms' overlay. 'fkms' overlay works for KODI, though with big visual lags, as it was described above. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1988475 Title: 22.04 and vc4-fkms-v3d / vc4-kms-v3d overlays problem Status in linux-raspi package in Ubuntu: New Bug description: I have RPi4/8GB RAM. I had no problems with 20.04LTS. 'fkms' overlay was used by default, and I never changed it. I have serious problem after upgrade to 22.04. 1. vc4-fkms-v3d overlay (is used by default) causes very big lags in windows dragging by mouse. Also video player (any) freezes the video while mouse is moved across the screen. Sound goes OK though. 2. vc4-kms-v3d works softly, without any lags, when 'builtin-Xpresent' or 'picom:GLX' window manager is on. But both 'vc4-kms-v3d' and 'vc4-kms-v3d-pi4' cause random HDMI signal disappearance when video is running in any video player (both Celluloid and VLC were tested). Screen becomes black, then "No signal" message appears. Green "SD-card access" indicator is on at this time. This behavior was checked in both 20.04LTS and 22.04LTS. But 'fkms' overlay worked OK in 20.04, so it was the solution there. Now in 22.04 I have no solution, so I need to downgrade back to 20.04 unless this bug will be fixed. Also I tried to install KODI in 22.04. It runs with permanent (100%-reproduced) bug, as it was described above. Black screen appears instead of main KODI menu, then "No signal" message appears. Of course, it so happens only with 'kms' overlay. 'fkms' overlay works for KODI, though with big visual lags, as it was described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988473] [NEW] Version 5.15.0-47 Breaks Virtualbox Win10 VM
Public bug reported: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988473 Title: Version 5.15.0-47 Breaks Virtualbox Win10 VM Status in linux package in Ubuntu: New Bug description: The updated linux kernel would not allow my Win10 VM to boot. Rebooting Ubuntu into the 5.15.0-46 version restored the avility to boot. The 47 version also corrupted the VM, so I had to use a backup. I don't know if the problem was really with new Intel microcode that was installed with the new kernel. VB kernel modules were updated by dkms with the new version 47 install, so that should not be the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1980 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 14:54:58 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-12-04 (1366 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. OptiPlex 990 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ce42a622-1220-4d20-a2b5-97e15e83c527 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (127 days ago) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988465] Re: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-install
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988465 Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules- nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: I was trying to switch from the nouveau driver to the nvidia driver after a fresh install of Kinetic. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 1 10:28:11 2022 ErrorMessage: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988465] Re: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-install
** Tags added: cuqa-manual-testing need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988465 Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules- nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: I was trying to switch from the nouveau driver to the nvidia driver after a fresh install of Kinetic. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 1 10:28:11 2022 ErrorMessage: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988470] [NEW] System runs into emergency mode if SSD is missing
Public bug reported: I have M.2 SSD, attached to USB3 port. Everything worked fine in 20.04LTS. I could detach the drive, then boot the system, and it ran correctly in UI mode with desktop, etc. I have another behavior after upgrade to 22.04LTS with 5.15.0.1013 core. Now the system boots into emergency mode with command prompt, if SSD is detached. SSD linking is defined in the /etc/fstab. System works fine if SSD is attached to USB3 port before power is on. Also I can attach SDD when the system is in the command prompt mode (see above) then reboot from the command line, then system will boot the GUI. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1988470 Title: System runs into emergency mode if SSD is missing Status in linux-raspi package in Ubuntu: New Bug description: I have M.2 SSD, attached to USB3 port. Everything worked fine in 20.04LTS. I could detach the drive, then boot the system, and it ran correctly in UI mode with desktop, etc. I have another behavior after upgrade to 22.04LTS with 5.15.0.1013 core. Now the system boots into emergency mode with command prompt, if SSD is detached. SSD linking is defined in the /etc/fstab. System works fine if SSD is attached to USB3 port before power is on. Also I can attach SDD when the system is in the command prompt mode (see above) then reboot from the command line, then system will boot the GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988466] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613062/+files/WifiSyslog.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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03
[Kernel-packages] [Bug 1988466] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613061/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613060/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613063/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613058/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613057/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613059/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613056/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1988466] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613055/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613054/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613053/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613052/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613051/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613050/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613049/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613048/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1988466/+attachment/5613047/+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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbelanger 2394 F pulseaudio /dev/snd/controlC1: mbelanger 2394 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-15 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Precision 5550 NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal _MarkForUpload: True dmi.bios.date: 07/05/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1988466] Re: Getting "Operation not permitted" on "sudo apt upgrade"
apport information ** Tags added: apport-collected jammy ** Description changed: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mbelanger 2394 F pulseaudio + /dev/snd/controlC1: mbelanger 2394 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-15 (16 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: Dell Inc. Precision 5550 + NonfreeKernelModules: mfe_aac_100710227 nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f29f9a31-c3c3-4845-a04b-7055c6a5ed9e ro + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-46-generic N/A + linux-backports-modules-5.15.0-46-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.4 + Tags: jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo systemd-journal + _MarkForUpload: True + dmi.bios.date: 07/05/2022 + dmi.bios.release: 1.17 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.17.0 + dmi.board.name: 0V6K79 + dmi.board.vendor: Dell Inc. + dmi.board.version: A03 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd07/05/2022:br1.17:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr:sku097E: + dmi.product.family: Precision + dmi.product.name: Precision 5550 + dmi.product.sku: 097E + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt"
[Kernel-packages] [Bug 1988466] 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 1988466 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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle
** Summary changed: - IWLMEI may cause device failure at resuming from s2idle + IWLMEI may cause device down at resuming from s2idle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988465] Re: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-install
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988465 Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules- nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: I was trying to switch from the nouveau driver to the nvidia driver after a fresh install of Kinetic. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 1 10:28:11 2022 ErrorMessage: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988466] [NEW] Getting "Operation not permitted" on "sudo apt upgrade"
Public bug reported: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages: fdutils linux-doc | linux-source-5.15.0 linux-tools The following NEW packages will be installed: linux-image-5.15.0-47-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/11.4 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 287318 files and directories currently installed.) Preparing to unpack .../linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb ... Unpacking linux-image-5.15.0-47-generic (5.15.0-47.51) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb (--unpack): unable to open '/boot/vmlinuz-5.15.0-47-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.15.0-47-generic_5.15.0-47.51_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** 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/1988466 Title: Getting "Operation not permitted" on "sudo apt upgrade" Status in linux package in Ubuntu: New Bug description: I have Ubuntu 22.04.1. This is a fresh install from 2 weeks ago. I tried to do an apt update/upgrade this morning, but something failed. Suggested recovery (sudo apt --fix-broken install) is not working. $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-image-generic-hwe-22.04 : Depends: linux-image-5.15.0-47-generic but it is not installed linux-modules-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-extra-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-modules-nvidia-515-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed linux-signatures-nvidia-5.15.0-47-generic : Depends: linux-image-5.15.0-47-generic but it is not installed or linux-image-unsigned-5.15.0-47-generic but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-image-5.15.0-47-generic Suggested packages:
[Kernel-packages] [Bug 1988434] Re: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1988434 Title: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] This request for all the ARM images Kernel have config updated . There is performance issues due to these config setting and after troubleshooting MSFT team found below two settings to update . Recommended CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Test Case] Microsoft tested [Where things could go wrong] Performance could decrease for some workloads. [Other Info] SF: #00343662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1988434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988465] [NEW] package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-insta
Public bug reported: I was trying to switch from the nouveau driver to the nvidia driver after a fresh install of Kinetic. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 1 10:28:11 2022 ErrorMessage: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988465 Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules- nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: I was trying to switch from the nouveau driver to the nvidia driver after a fresh install of Kinetic. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 1 10:28:11 2022 ErrorMessage: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.2 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-470-5.15.0-27-generic 5.15.0-27.28 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
Kernel SRU request submitted for focal:
https://lists.ubuntu.com/archives/kernel-team/2022-September/thread.html#132957
changing status to 'In Progress'.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
--
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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing device attributes
during recovery
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification:
--
[Impact]
* If the mlx5 driver is reloading while the recovery flow is happening,
and if it receives new commands before the command interface is up
again, this can lead to null pointer that tries to access non-
initialized command structures.
* So it's required to avoid processing commands before the command
interface is up again.
* This is accomplished by a new cmdif state that helps to avoid
processing commands while cmdif is not ready.
[Fix]
* backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
"net/mlx5: Avoid processing commands before cmdif is ready"
[Test Plan]
* An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
is needed that has Mellanox cards (RoCE Express 2.1) assigned,
configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
* Now trigger a recovery (guess that can be done at the Support Element)
and reload the driver at the same time.
* Make sure the module/driver mlx5 is loaded and in use
(otherwise it can't be removed/unloaded).
* Now remove/unload the module with:
sudo modprobe -r mlx5
and (re-)load it again with:
sudo modprobe mlx5
* Due to the lack of RoCE Express 2.1 hardware,
IBM needs to do the verification.
[Where problems could occur]
* In case there is an issue with 'cmdif' it might not have the correct
interface state, which:
- either might lead to the fact that commands are not properly blocked
and the situation is similar like before
- or the commands may get always blocked,
which render the hardware useless
- or might block in wrong situation,
which will cause unexpected issues and broken behavior.
* Since the patch got upstream accepted with v5.7-rc7 it's
not new to the kernel, was already part of groovy (and above)
and is therefor already in use by newer Ubuntu releases.
[Other Info]
* Since the patch is upstream since v5.7-rc7,
it's already included in jammy and kinetic.
* Since the upstream patch incl. the line:
Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
Connect-IB adapters") it looks to me that it was forgotten
to mark the patch for upstream stable updates.
* Such SRUs for focal's 5.4 will automatically land in bionic's
hwe-5.4, too. But since this was especially requested for
bionic's hwe-5.4, I wanted to mention this here.
__
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I managed to find a reliable way to reproduce the issue that I believe isn't
tied to IBM Z at all.
The procedure to reproduce is as follows. I created a script to read
the sysfs attributes for the link's speed and duplex mode in a loop:
#!/usr/bin/env bash
if [ $# -lt 1 ]; then
echo "Usage: $0 "
exit 1
fi
while true; do
cat /sys/class/net/$1/duplex > /dev/null
cat /sys/class/net/$1/speed > /dev/null
done
Executed with:
# ./script.sh enP10p0s0
I ran this in one bash session and then in another one I triggered a PCI
reset with
the follwoing command where one needs to replace with the PCI address
of the NIC:
echo 1 > /sys/bus/pci/devices//reset
Then first I got a lot of the following messages:
mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings:
query port ptys failed: -5
And then as the mlx5 driver's recovery kicks in the oops as below:
[ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f
after 1 iterations
[ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called
[ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010
[ 659.104169] Unable to handle kernel pointer dereference in virtual kernel
address space
[ 659.104171] Failing address:
[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
** Changed in: linux Status: Unknown => 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: New Status in linux package in Ubuntu: New Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988364] Re: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
** Changed in: bluez Status: Unknown => Fix Released -- 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/1988364 Title: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: Triaged Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988461] 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 1988461 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/1988461 Title: intel_pmc_core not load on Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988461] [NEW] intel_pmc_core not load on Raptor Lake
Public bug reported: [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: oem-priority originate-from-1982567 originate-from-1982714 somerville ** Description changed: - TBD. + [Summary] + intel_pmc_core not load on Raptor Lake + + [Reproduce Steps] + 1. Boot into Ubuntu desktop + 2. Check if /sys/kernel/debug/pmc_core folder exist + + [Results] + Expected: folder /sys/kernel/debug/pmc_core folder been created + Actual: /sys/kernel/debug/pmc_core not exist ** Tags added: oem-priority originate-from-1982714 somerville ** Tags added: originate-from-1982567 -- 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/1988461 Title: intel_pmc_core not load on Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Still present in 5.15.0-48-lowlatency as well. Interestingly, the logs say the kernel is tainted in generic, but not in lowlatency, despite no other configuration changes when this is handled. 9/1/22 8:01 AM kernel 9/1/22 8:01 AM kernel UBSAN: array-index-out-of-bounds in /build/linux-lowlatency-FlX6Pk/linux-lowlatency-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 9/1/22 8:01 AM kernel index 8 is out of range for type 'aq_vec_s *[8]' 9/1/22 8:01 AM kernel CPU: 0 PID: 2103 Comm: daemon-init Not tainted 5.15.0-48-lowlatency #54-Ubuntu 9/1/22 8:01 AM kernel Hardware name: To Be Filled By O.E.M. X570 Creator/X570 Creator, BIOS P3.72 05/17/2022 9/1/22 8:01 AM kernel Call Trace: 9/1/22 8:01 AM kernel 9/1/22 8:01 AM kernel show_stack+0x52/0x5c 9/1/22 8:01 AM kernel dump_stack_lvl+0x4a/0x63 9/1/22 8:01 AM kernel dump_stack+0x10/0x16 9/1/22 8:01 AM kernel ubsan_epilogue+0x9/0x49 9/1/22 8:01 AM kernel __ubsan_handle_out_of_bounds.cold+0x44/0x49 9/1/22 8:01 AM kernel ? call_netdevice_notifiers+0x38/0x50 9/1/22 8:01 AM kernel ? aq_vec_stop+0x72/0x80 [atlantic] 9/1/22 8:01 AM kernel aq_nic_stop+0x1b6/0x1c0 [atlantic] 9/1/22 8:01 AM kernel aq_ndev_set_features+0x143/0x1a0 [atlantic] 9/1/22 8:01 AM kernel __netdev_update_features+0x184/0x820 9/1/22 8:01 AM kernel dev_disable_lro+0x34/0x150 9/1/22 8:01 AM kernel devinet_sysctl_forward+0x1fb/0x230 9/1/22 8:01 AM kernel proc_sys_call_handler+0x161/0x2d0 9/1/22 8:01 AM kernel proc_sys_write+0x13/0x20 9/1/22 8:01 AM kernel new_sync_write+0x117/0x1b0 9/1/22 8:01 AM kernel ? io_req_prep_async+0x2a0/0x2a0 9/1/22 8:01 AM kernel vfs_write+0x1fb/0x290 9/1/22 8:01 AM kernel ksys_write+0x67/0xf0 9/1/22 8:01 AM kernel __x64_sys_write+0x19/0x20 9/1/22 8:01 AM kernel do_syscall_64+0x5c/0xc0 9/1/22 8:01 AM kernel ? do_syscall_64+0x69/0xc0 9/1/22 8:01 AM kernel ? syscall_exit_to_user_mode+0x27/0x50 9/1/22 8:01 AM kernel ? irqentry_exit+0x3b/0x50 9/1/22 8:01 AM kernel ? exc_page_fault+0x89/0x190 9/1/22 8:01 AM kernel entry_SYSCALL_64_after_hwframe+0x61/0xcb 9/1/22 8:01 AM kernel RIP: 0033:0x7f79df4f1a6f 9/1/22 8:01 AM kernel Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 c0 f7 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 5c c0 f7 ff 48 9/1/22 8:01 AM kernel RSP: 002b:7f799f7fd810 EFLAGS: 0293 ORIG_RAX: 0001 9/1/22 8:01 AM kernel RAX: ffda RBX: 0002 RCX: 7f79df4f1a6f 9/1/22 8:01 AM kernel RDX: 0002 RSI: 7f79dfe7a5e5 RDI: 0013 9/1/22 8:01 AM kernel RBP: 7f79dfe7a5e5 R08: R09: 0001 9/1/22 8:01 AM kernel R10: R11: 0293 R12: 0013 9/1/22 8:01 AM kernel R13: 0013 R14: R15: 7f7994024a70 9/1/22 8:01 AM kernel 9/1/22 8:01 AM kernel -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
You can find the value of ambient light by reading "in_illuminance_input". $ find /sys 2>/dev/null | grep in_illuminance_input ...to find it's full path. -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop systemd-logind[1159]:
[Kernel-packages] [Bug 1949721] Re: [HUAWAI MateBook 14 2021] Sound not working
** Also affects: alsa-driver Importance: Undecided Status: New ** Summary changed: - [HUAWAI MateBook 14 2021] Sound not working + [HUAWAI MateBook 14 2021] Sound not working - Chip ES8336 -- 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/1949721 Title: [HUAWAI MateBook 14 2021] Sound not working - Chip ES8336 Status in ALSA driver: New Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: WIP here https://github.com/thesofproject/linux/wiki/ES8336-support TL;DR : You need patched 5.19 kernel , alsa , and topology and Patience Original Bug report I installed Ubuntu 20.04 and the sound is not working on the fresh install. The microphone either. I have 5 computers with same hardware. Same problem everywhere. I guess there is a missing driver. Here is lspci output: 00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) 00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) 00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) 00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) 00:15.2 Serial bus controller [0c80]: Intel Corporation Device a0ea (rev 20) 00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) 00:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) 00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809 Here is lspci -v output about audio: 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) Subsystem: QUANTA Computer Inc Device 1307 Flags: bus master, fast devsel, latency 32, IRQ 147 Memory at 600112 (64-bit, non-prefetchable) [size=16K] Memory at 600100 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci The pa-info output is in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1949721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
I reinstalled 20220329.git681281e4-0ubuntu3.4 (FPS: low), then installed 20220329.git681281e4-0ubuntu3.5 from the "proposed" repo. Test result: OK Tested: 20220329.git681281e4-0ubuntu3.5 FPS: high (100 FPS as expected, fixes the issue) Videos with VLC and Celluloid: OK Videos with Firefox and Youtube: OK dmesg: no error messages (the ACPI errors are normal) Thank you very much for kindly following through with the issue. :-) ** Attachment added: "dmesg with updated linux-firmware" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+attachment/5612991/+files/dmesg ** Tags added: verification-done-jammy -- 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/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all [Fix] Update amdgpu/dimgrey_cavefish_* firmware files to latest versions from kernel.org. [Test Case] See original description. [Where Problems Could Occur] Isolated to AMD GPUs that use dimgrey_cavefish firmware blobs. [Original Description] Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M.
[Kernel-packages] [Bug 1969086] Re: Enable swiotlb to avoid untrusted devices errors on AMD platforms
@vicamo, what about jammy/oem-5.17? ** 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/1969086 Title: Enable swiotlb to avoid untrusted devices errors on AMD platforms Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: It's been observed that plugging in a TBT3 NVME device to a port marked with ExternalFacingPort that some DMA transactions occur that are not a full page and so the DMA API attempts to use software bounce buffers instead of relying upon the IOMMU translation. This doesn't work and leads to messaging like: swiotlb buffer is full (sz: 4096 bytes), total 0 (slots), used 0 (slots) The bounce buffers were originally set up, but torn down during the boot process. * This happens because as part of IOMMU initialization `amd_iommu_init_dma_ops` gets called and resets the global swiotlb to 0. * When late_init gets called `pci_swiotlb_late_init` `swiotlb_exit` is called and the buffers are torn down. This can be observed in the logs: ``` [0.407286] AMD-Vi: Extended features (0x246577efa2254afa): PPR NX GT [5] IA GA PC GA_vAPIC [0.407291] AMD-Vi: Interrupt remapping enabled [0.407292] AMD-Vi: Virtual APIC enabled [0.407872] software IO TLB: tearing down default memory pool ``` This series fixes the behavior of AMD IOMMU to enable swiotlb so that non-page aligned DMA goes through a bounce buffer. It also adds a message to help with debugging similar problems in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969086] Re: Enable swiotlb to avoid untrusted devices errors on AMD platforms
Fixed in 5.19 and up ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Won't Fix -- 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/1969086 Title: Enable swiotlb to avoid untrusted devices errors on AMD platforms Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: It's been observed that plugging in a TBT3 NVME device to a port marked with ExternalFacingPort that some DMA transactions occur that are not a full page and so the DMA API attempts to use software bounce buffers instead of relying upon the IOMMU translation. This doesn't work and leads to messaging like: swiotlb buffer is full (sz: 4096 bytes), total 0 (slots), used 0 (slots) The bounce buffers were originally set up, but torn down during the boot process. * This happens because as part of IOMMU initialization `amd_iommu_init_dma_ops` gets called and resets the global swiotlb to 0. * When late_init gets called `pci_swiotlb_late_init` `swiotlb_exit` is called and the buffers are torn down. This can be observed in the logs: ``` [0.407286] AMD-Vi: Extended features (0x246577efa2254afa): PPR NX GT [5] IA GA PC GA_vAPIC [0.407291] AMD-Vi: Interrupt remapping enabled [0.407292] AMD-Vi: Virtual APIC enabled [0.407872] software IO TLB: tearing down default memory pool ``` This series fixes the behavior of AMD IOMMU to enable swiotlb so that non-page aligned DMA goes through a bounce buffer. It also adds a message to help with debugging similar problems in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988434] Re: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n
https://lists.ubuntu.com/archives/kernel-team/2022-September/132952.html ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Released -- 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/1988434 Title: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] This request for all the ARM images Kernel have config updated . There is performance issues due to these config setting and after troubleshooting MSFT team found below two settings to update . Recommended CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Test Case] Microsoft tested [Where things could go wrong] Performance could decrease for some workloads. [Other Info] SF: #00343662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1988434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
** Description changed:
SRU Justification:
--
[Impact]
- * If the mlx5 driver is reloading while the recovery flow is happening,
-and if it receives new commands before the command interface is up
-again, this can lead to null pointer that tries to access non-
-initialized command structures.
+ * If the mlx5 driver is reloading while the recovery flow is happening,
+ and if it receives new commands before the command interface is up
+ again, this can lead to null pointer that tries to access non-
+ initialized command structures.
- * So it's required to avoid processing commands before the command
-interface is up again.
+ * So it's required to avoid processing commands before the command
+ interface is up again.
- * This is accomplished by a new cmdif state that helps to avoid
-processing commands while cmdif is not ready.
+ * This is accomplished by a new cmdif state that helps to avoid
+ processing commands while cmdif is not ready.
[Fix]
- * backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
+ * backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
"net/mlx5: Avoid processing commands before cmdif is ready"
[Test Plan]
- * An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
-is needed that has Mellanox cards (RoCE Express 2.1) assigned,
-configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
+ * An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
+ is needed that has Mellanox cards (RoCE Express 2.1) assigned,
+ configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
- * Now trigger a recovery (guess that can be done at the Support Element)
-and reload the driver at the same time.
+ * Now trigger a recovery (guess that can be done at the Support Element)
+ and reload the driver at the same time.
- * Make sure the module/driver mlx5 is loaded and in use
-(otherwise it can't be removed/unloaded).
+ * Make sure the module/driver mlx5 is loaded and in use
+ (otherwise it can't be removed/unloaded).
- * Now remove/unload the module with:
-sudo modprobe -r mlx5
-and (re-)load it again with:
-sudo modprobe mlx5
+ * Now remove/unload the module with:
+ sudo modprobe -r mlx5
+ and (re-)load it again with:
+ sudo modprobe mlx5
- * Due to the lack of RoCE Express 2.1 hardware,
-IBM needs to do the verification.
+ * Due to the lack of RoCE Express 2.1 hardware,
+ IBM needs to do the verification.
[Where problems could occur]
- * In case there is an issue with 'cmdif' it might not have the correct
-interface state, which:
-- either might lead to the fact that commands are not properly blocked
- and the situation is similar like before
-- or the commands may get always blocked,
- which render the hardware useless
-- or might block in wrong situation,
- which will cause unexpected issues and broken behavior.
+ * In case there is an issue with 'cmdif' it might not have the correct
+ interface state, which:
+ - either might lead to the fact that commands are not properly blocked
+ and the situation is similar like before
+ - or the commands may get always blocked,
+ which render the hardware useless
+ - or might block in wrong situation,
+ which will cause unexpected issues and broken behavior.
- * Since the patch got upstream accepted with v5.7-rc7 it's
-not new to the kernel, was already part of groovy (and above)
-and is therefor already in use by newer Ubuntu releases.
+ * Since the patch got upstream accepted with v5.7-rc7 it's
+ not new to the kernel, was already part of groovy (and above)
+ and is therefor already in use by newer Ubuntu releases.
[Other Info]
-
- * Since the patch is upstream since v5.7-rc7,
-it's already included in jammy and kinetic.
- * Since the upstream patch incl. the line:
-Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
-Connect-IB adapters") it looks to me that it was forgotten
-to mark the patch for upstream stable updates.
+ * Since the patch is upstream since v5.7-rc7,
+ it's already included in jammy and kinetic.
+
+ * Since the upstream patch incl. the line:
+ Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
+ Connect-IB adapters") it looks to me that it was forgotten
+ to mark the patch for upstream stable updates.
+
+ * Such SRUs for focal's 5.4 will automatically land in bionic's
+hwe-5.4, too. But since this was especially requested for
+bionic's hwe-5.4, I wanted to mention this here.
__
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I
[Kernel-packages] [Bug 1988434] [NEW] azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n
Public bug reported: SRU Justification [Impact] This request for all the ARM images Kernel have config updated . There is performance issues due to these config setting and after troubleshooting MSFT team found below two settings to update . Recommended CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Test Case] Microsoft tested [Where things could go wrong] Performance could decrease for some workloads. [Other Info] SF: #00343662 ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Kinetic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1988434 Title: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Bug description: SRU Justification [Impact] This request for all the ARM images Kernel have config updated . There is performance issues due to these config setting and after troubleshooting MSFT team found below two settings to update . Recommended CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Test Case] Microsoft tested [Where things could go wrong] Performance could decrease for some workloads. [Other Info] SF: #00343662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1988434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969091] Re: Fixes for dma-iommu swiotlb bounce buffers
These are included in v5.15.33 and up ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** 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/1969091 Title: Fixes for dma-iommu swiotlb bounce buffers Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released 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: Won't Fix Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://lore.kernel.org/all/20210929023300.335969-1-steve...@google.com/ landed to v5.16 and is being requested to backport to v5.15.y in https://lore.kernel.org/stable/bl1pr12mb5157cd6b2c9d6b8525cfad0ee2...@bl1pr12mb5157.namprd12.prod.outlook.com/T/#u . Related commits are: 08ae5d4a1ae9 iommu/dma: Fix sync_sg with swiotlb (already in stable) 06e620345d54 iommu/dma: Fix arch_sync_dma for map (already in stable) ee9d4097cc14 iommu/dma: Skip extra sync during unmap w/swiotlb 9b49bbc2c4df iommu/dma: Fold _swiotlb helpers into callers 2e727bffbe93 iommu/dma: Check CONFIG_SWIOTLB more broadly e81e99bacc9f swiotlb: Support aligned swiotlb buffers 2cbc61a1b166 iommu/dma: Account for min_align_mask w/swiotlb To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969086] Re: Enable swiotlb to avoid untrusted devices errors on AMD platforms
** Changed in: linux (Ubuntu Impish) Status: Incomplete => Won't Fix -- 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/1969086 Title: Enable swiotlb to avoid untrusted devices errors on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: It's been observed that plugging in a TBT3 NVME device to a port marked with ExternalFacingPort that some DMA transactions occur that are not a full page and so the DMA API attempts to use software bounce buffers instead of relying upon the IOMMU translation. This doesn't work and leads to messaging like: swiotlb buffer is full (sz: 4096 bytes), total 0 (slots), used 0 (slots) The bounce buffers were originally set up, but torn down during the boot process. * This happens because as part of IOMMU initialization `amd_iommu_init_dma_ops` gets called and resets the global swiotlb to 0. * When late_init gets called `pci_swiotlb_late_init` `swiotlb_exit` is called and the buffers are torn down. This can be observed in the logs: ``` [0.407286] AMD-Vi: Extended features (0x246577efa2254afa): PPR NX GT [5] IA GA PC GA_vAPIC [0.407291] AMD-Vi: Interrupt remapping enabled [0.407292] AMD-Vi: Virtual APIC enabled [0.407872] software IO TLB: tearing down default memory pool ``` This series fixes the behavior of AMD IOMMU to enable swiotlb so that non-page aligned DMA goes through a bounce buffer. It also adds a message to help with debugging similar problems in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970482] Re: Xenial: kernel BUG/Oops/crash in fuse_readdir() due to CVE-2020-36322 backport
The fix has been released on Xenial ESM (kernel version 4.4.0-224.257).
$ git log --oneline -1 341e4f5e9e07
341e4f5e9e07 UBUNTU: SAUCE: fuse: fix bad !inode in fuse_direntplus_link()
$ git describe --contains 341e4f5e9e07
Ubuntu-4.4.0-224.257~6
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => 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/1970482
Title:
Xenial: kernel BUG/Oops/crash in fuse_readdir() due to CVE-2020-36322
backport
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
* Users might hit kernel BUG/Oops/crash with fuse filesystems
on Xenial kernel 4.4.0-222.255 and later (backport from 4.9),
including the derivative/optimized kernels (linux-aws below).
* Introduced by the backport from 4.9 for CVE-2020-36322 [1]
[1] https://ubuntu.com/security/CVE-2020-36322
* Offending commit 8deb786162e1 ("fuse: fix bad inode")
linux-xenial$ git log --oneline origin/master-prep -- fs/fuse/dir.c | head
-n1
8deb786162e1 fuse: fix bad inode
linux-xenial$ git describe --contains 8deb786162e1
Ubuntu-4.4.0-222.255~6
[Fix]
* Check for non-NULL inode pointer before fuse_is_bad(inode)
in fuse_direntplus_link().
* (This is the only modified function/patch hunk which seems
to have issues; all others dereference 'inode' w/out check
at some point, even before this patch).
[Test Case]
* Not available at the moment.
[Regression Potential]
* Probably none, as this changes the hunk/code behavior to
what it was before the offending patch/backport w/ issue
was applied (where fuse_is_bad() wasn't called at all if
inode is NULL), and makes sense with the patch applied;
also, this same form is used in another hunk, where NULL
was checked.
[Example Stacktrace]
kernel: BUG: unable to handle kernel NULL pointer dereference at
02c0
kernel: IP: [] fuse_readdir+0x376/0x700
kernel: PGD 1e3e02c067 PUD 1c8b2aa067 PMD 0
kernel: Oops: [#5] SMP
kernel: Modules linked in: <...>
kernel: CPU: 1 PID: 12133 Comm: php-fpm Tainted: G D
4.4.0-1138-aws #152-Ubuntu
kernel: Hardware name: Amazon EC2 m5a.8xlarge/, BIOS 1.0 10/16/2017
kernel: task: 881bcf164600 ti: 881bcffec000 task.ti:
881bcffec000
kernel: RIP: 0010:[] []
fuse_readdir+0x376/0x700
kernel: RSP: 0018:881bcffefe10 EFLAGS: 00010206
kernel: RAX: c9000524bd00 RBX: 01a0 RCX:
kernel: RDX: 0001 RSI: c9000524bd00 RDI:
881ed25bf3d8
kernel: RBP: 881bcffefea0 R08: R09:
0050
kernel: R10: 881b942a0c68 R11: 881ed25bf380 R12:
881b942a0bd0
kernel: R13: 880f8ced0d80 R14: 881f25cb1800 R15:
881ed25bf380
kernel: FS: 7f884d100740() GS:880fb8c4()
knlGS:
kernel: CS: 0010 DS: ES: CR0: 80050033
kernel: CR2: 02c0 CR3: 001cbc963000 CR4:
003406f0
kernel: Stack:
kernel: 881bcffefef0 00441d7f 880fb1c6a000
881b942a0bf8
kernel: 881f25cb1800 ea006e50a800
881b942a0ca0
kernel: ae046100 880fae046100 00361c41ec1e
881b942a0c68
kernel: Call Trace:
kernel: [] iterate_dir+0x98/0x120
kernel: [] ? __audit_syscall_entry+0xab/0xf0
kernel: [] SyS_getdents+0x99/0x110
kernel: [] ? iterate_dir+0x120/0x120
kernel: [] entry_SYSCALL_64_fastpath+0x22/0xd0
kernel: Code: 49 39 80 38 02 00 00 75 12 41 0f b7 00 41 33 44 24 64 f6
c4 f0 0f 84 72 02 00 00 4c 89 ff 4c 89 45 90 e8 ae 65 f0 ff 4c 8b 45 90 <49> 8b
80 c0 02 00 00 4c 89 ff a8 08 0f 85 67 02 00 00 e8 63 5c
kernel: RIP [] fuse_readdir+0x376/0x700
kernel: RSP
kernel: CR2: 02c0
kernel: ---[ end trace f89ac23b1e9bb24c ]---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970482/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988429] [NEW] support linux-oem-6.0
Public bug reported: [Impact] Building nvidia dkms against linux 6.0 fails. The compat code needs updates to support 6.0. [Test case] Check that it builds after fixes applied. [What could go wrong] The compat code changes affect only builds on 6.0, so there's no chance of it breaking build for other kernels. ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-510 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-515 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-515 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1988429 Title: support linux-oem-6.0 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New Status in nvidia-graphics-drivers-510 source package in Jammy: New Status in nvidia-graphics-drivers-515 source package in Jammy: New Bug description: [Impact] Building nvidia dkms against linux 6.0 fails. The compat code needs updates to support 6.0. [Test case] Check that it builds after fixes applied. [What could go wrong] The compat code changes affect only builds on 6.0, so there's no chance of it breaking build for other kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1988429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
Hello Da, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983291] Re: Update firmware for DCN316/GFX1037
Hello Mario, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1983291 Title: Update firmware for DCN316/GFX1037 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Jammy already has firmware for upcoming product with GFX1037 and DCN316. However this firmware has some stability problems under stress and it should be updated to latest on linux-firmware.git to support systems that will take this firmware. [Fix] Upgrade following binaries: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122 [Test] Verify suspend/resume works. Verify that accelerated graphics works. Verify video playback works. [Where problems could occur] Firmware is only loaded to product with GFX1037/DCN316 This isn't yet on the market and regressions are not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
Hello Ras, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all [Fix] Update amdgpu/dimgrey_cavefish_* firmware files to latest versions from kernel.org. [Test Case] See original description. [Where Problems Could Occur] Isolated to AMD GPUs that use dimgrey_cavefish firmware blobs. [Original Description] Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin
[Kernel-packages] [Bug 1987670] Re: Add support for AMD PMF
** Package changed: linux (Ubuntu) => linux-oem-6.0 (Ubuntu) ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress -- 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/1987670 Title: Add support for AMD PMF Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: Some upcoming platforms support for AMD-PMF. This will enable ACPI platform profiles and some automatic transitions. The first 11 patches are queued up for 6.1 and also available in an immutable branch. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf Can you please merge these to OEM-6.0? We will have 3-5 more patches targeted later as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1987670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988408] Re: bluetooth gaming controller
If this provides help of some sort, The BT game controller is defined as N1-9013 (similar to ipega) and works at 2.4 BT frequency. The BT dongle is an Asus USB-BT400. As for the laptop, the dongle used was the same but I can also post the BT integrated device of the laptop (laptop works fine with the controller on windows for both the usb dongle or the integrated BT device). If it serves any purpose, I can post the laptop data as well. -- 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/1988408 Title: bluetooth gaming controller Status in bluez package in Ubuntu: New Bug description: On 2 different ubuntu machines (laptop and desktop, with same ubuntu version and bluez) I can pair my generic BT game controller without any issues except for the fact that I can't send or receive any input. This controller with the same bluetooth dongle connects perfectly on windows 10 and 11 (had to dual boot to test it). The laptop itself, via dongle or via integrated BT receiver, can also connect perfectly and use it for steam on windows. There's something wrong going on with Bluez stack. Tried to use jstest-gtk and install xbox-drv to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 10:41:31 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.asset.tag: BC5FF494092A dmi.board.name: 960GM-VGS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd07/23/2015:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:A2:8B ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1035 acl:0 sco:0 events:60 errors:0 TX bytes:3694 acl:0 sco:0 commands:60 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
Chess and https://webcamtests.com/ not working for me /dev/video0 and /dev/video1 can found Kernel Version: 5.15.0-46-generic Device: Lenovo X1 Carbon gen 10 Packages: libcamhal-ipu6ep0=0~git202208100225.2a7c9c2~ubuntu22.04.1 ╰─ sudo dmesg|grep ipu6 [4.636891] intel-ipu6 intel-ipu: enabling device ( -> 0002) [4.637161] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x2) [4.637176] intel-ipu6 intel-ipu: physical base address 0x603c00 [4.637178] intel-ipu6 intel-ipu: mapped as: 0x42f5c0da [4.637245] intel-ipu6 intel-ipu: IPU in secure mode [4.653932] intel-ipu6 intel-ipu: IPC reset done [4.653937] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [4.655247] intel-ipu6 intel-ipu: FW version: 20211011 [4.776455] intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE [4.785568] intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE [4.853780] intel-ipu6 intel-ipu: CSE authenticate_run done [4.853811] intel-ipu6 intel-ipu: IPU driver version 1.0 [4.892138] intel-ipu6-isys intel-ipu6-isys0: no subdev found in graph [4.932719] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [4.932913] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 journalctl -k -b shows in attachment. ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5612903/+files/journal.log -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" -
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
Lenovo X1 Carbon gen 10 hasn't supported, here are the hardwares supported currently: https://wiki.ubuntu.com/Dell, "The Intel IPU6/IPU6EP is supported on some certified platforms, it contains the characteristic below" -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => 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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in HWE Next:
New
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux-oem-5.14 source package in Bionic:
Invalid
Status in linux-oem-5.17 source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux-oem-5.17 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Invalid
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
Chess and https://webcamtests.com/ not working for me /dev/video0 and /dev/video1 can found Kernel Version: 5.15.0-46-generic Device: Lenovo X1 Carbon gen 10 Packages: libcamhal-ipu6ep0=0~git202208100225.2a7c9c2~ubuntu22.04.1 ╰─ sudo dmesg|grep ipu6 [4.636891] intel-ipu6 intel-ipu: enabling device ( -> 0002) [4.637161] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x2) [4.637176] intel-ipu6 intel-ipu: physical base address 0x603c00 [4.637178] intel-ipu6 intel-ipu: mapped as: 0x42f5c0da [4.637245] intel-ipu6 intel-ipu: IPU in secure mode [4.653932] intel-ipu6 intel-ipu: IPC reset done [4.653937] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [4.655247] intel-ipu6 intel-ipu: FW version: 20211011 [4.776455] intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE [4.785568] intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE [4.853780] intel-ipu6 intel-ipu: CSE authenticate_run done [4.853811] intel-ipu6 intel-ipu: IPU driver version 1.0 [4.892138] intel-ipu6-isys intel-ipu6-isys0: no subdev found in graph [4.932719] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [4.932913] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: 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+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915
[Kernel-packages] [Bug 1988408] [NEW] bluetooth gaming controller
Public bug reported: On 2 different ubuntu machines (laptop and desktop, with same ubuntu version and bluez) I can pair my generic BT game controller without any issues except for the fact that I can't send or receive any input. This controller with the same bluetooth dongle connects perfectly on windows 10 and 11 (had to dual boot to test it). The laptop itself, via dongle or via integrated BT receiver, can also connect perfectly and use it for steam on windows. There's something wrong going on with Bluez stack. Tried to use jstest-gtk and install xbox-drv to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 10:41:31 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.asset.tag: BC5FF494092A dmi.board.name: 960GM-VGS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd07/23/2015:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:A8:A2:8B ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1035 acl:0 sco:0 events:60 errors:0 TX bytes:3694 acl:0 sco:0 commands:60 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988408 Title: bluetooth gaming controller Status in bluez package in Ubuntu: New Bug description: On 2 different ubuntu machines (laptop and desktop, with same ubuntu version and bluez) I can pair my generic BT game controller without any issues except for the fact that I can't send or receive any input. This controller with the same bluetooth dongle connects perfectly on windows 10 and 11 (had to dual boot to test it). The laptop itself, via dongle or via integrated BT receiver, can also connect perfectly and use it for steam on windows. There's something wrong going on with Bluez stack. Tried to use jstest-gtk and install xbox-drv to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 10:41:31 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.asset.tag: BC5FF494092A dmi.board.name: 960GM-VGS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1971597] Re: amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
Importance: Undecided => Critical
** 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/1971597
Title:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err
-517
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
Commit 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members
before initialization") attempted to fix a race condition that lead to
a NULL pointer, but in the process caused a regression for _AEI/_EVT
declared GPIOs.
This manifests in messages showing deferred probing while trying to
allocate IRQs like so:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x002C to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x003D to IRQ, err -517
[ .. more of the same .. ]
The code for walking _AEI doesn't handle deferred probing and so this
leads to non-functional GPIO interrupts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1971597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Triaged -- 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/1985901 Title: kernel hang when connecting monitor Status in OEM Priority Project: New 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: Triaged Status in linux source package in Jammy: Triaged Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: When I connected the ThinkVision 24i monitor on ThinkPad L14, we found below issue. Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ... kernel:[ 77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! [Xorg:1829] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 50s! [Xorg:1829] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core realtek wmi video 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg Tainted: G L5.14.0-1048-oem #55-Ubuntu 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 08 00 00 45 8b 6d 00 12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 c5 66 90 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 EFLAGS: 0282 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 9ab39d00 RCX: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX: RSI: 6741 RDI: 9ab39d00 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 9ab39d00 R09: 1140 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10: R11: 9ab389c9c400 R12: 6741 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13: R14: 0008 R15: 9ab389c9d400 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS: 7f9d97924a40() GS:9ab466e0() knlGS: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS: 0010 DS: ES: CR0: 80050033 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 00010c878000 CR4: 00750ef0 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_device_rreg+0x17/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_cgs_read_register+0x14/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dm_read_reg_func+0x3e/0xa0 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_srv_wait_for_idle+0x17/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3
[Kernel-packages] [Bug 1987394] Re: Enable kernel config for P2PDMA
** Package changed: linux-oem-5.17 (Ubuntu) => linux-oem-6.0 (Ubuntu) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987394 Title: Enable kernel config for P2PDMA Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Bug description: [Impact] We have a request to enable HSA_AMD_P2P for oem-6.0 [What could go wrong] this is a new config item, shouldn't affect the rest of the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1987394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949721] Re: [HUAWAI MateBook 14 2021] Sound not working
** Description changed: + WIP here https://github.com/thesofproject/linux/wiki/ES8336-support + + TL;DR : You need patched 5.19 kernel , alsa , and topology and Patience + + + Original Bug report + I installed Ubuntu 20.04 and the sound is not working on the fresh install. The microphone either. I have 5 computers with same hardware. Same problem everywhere. I guess there is a missing driver. Here is lspci output: 00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) 00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) 00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) 00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) 00:15.2 Serial bus controller [0c80]: Intel Corporation Device a0ea (rev 20) 00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) 00:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) 00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809 Here is lspci -v output about audio: 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) - Subsystem: QUANTA Computer Inc Device 1307 - Flags: bus master, fast devsel, latency 32, IRQ 147 - Memory at 600112 (64-bit, non-prefetchable) [size=16K] - Memory at 600100 (64-bit, non-prefetchable) [size=1M] - Capabilities: - Kernel driver in use: sof-audio-pci - Kernel modules: snd_hda_intel, snd_sof_pci - + Subsystem: QUANTA Computer Inc Device 1307 + Flags: bus master, fast devsel, latency 32, IRQ 147 + Memory at 600112 (64-bit, non-prefetchable) [size=16K] + Memory at 600100 (64-bit, non-prefetchable) [size=1M] + Capabilities: + Kernel driver in use: sof-audio-pci + Kernel modules: snd_hda_intel, snd_sof_pci The pa-info output is in attachment. -- 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/1949721 Title: [HUAWAI MateBook 14 2021] Sound not working Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: WIP here https://github.com/thesofproject/linux/wiki/ES8336-support TL;DR : You need patched 5.19 kernel , alsa , and topology and Patience Original Bug report I installed Ubuntu 20.04 and the sound is not working on the fresh install. The microphone either. I have 5 computers with same hardware. Same problem everywhere. I guess there is a missing driver. Here is lspci output: 00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) 00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) 00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) 00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) 00:15.2 Serial bus controller [0c80]: Intel Corporation Device a0ea (rev 20) 00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) 00:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) 00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809 Here is lspci -v output about audio: 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) Subsystem: QUANTA Computer Inc Device 1307 Flags: bus master, fast devsel, latency 32, IRQ 147 Memory at 600112 (64-bit, non-prefetchable) [size=16K] Memory at 600100 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci The pa-info output is in attachment. To manage notifications
[Kernel-packages] [Bug 1949721] Re: [HUAWAI MateBook 14 2021] Sound not working
Thanks! Yes I have ES8336. I will follow the progress of ES8336 support... -- 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/1949721 Title: [HUAWAI MateBook 14 2021] Sound not working Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 and the sound is not working on the fresh install. The microphone either. I have 5 computers with same hardware. Same problem everywhere. I guess there is a missing driver. Here is lspci output: 00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) 00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) 00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) 00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) 00:15.2 Serial bus controller [0c80]: Intel Corporation Device a0ea (rev 20) 00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) 00:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) 00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809 Here is lspci -v output about audio: 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) Subsystem: QUANTA Computer Inc Device 1307 Flags: bus master, fast devsel, latency 32, IRQ 147 Memory at 600112 (64-bit, non-prefetchable) [size=16K] Memory at 600100 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci The pa-info output is in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1949721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
** Changed in: maas Assignee: (unassigned) => Björn Tillenius (bjornt) -- 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/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: New Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
Updaet: We found that this bug was only triggering when you try to change the MTU to anything other than 1500. With MTU=1500 the VMs work fine even with the current 5.15 kernel. With MTU=1550 or MTU=9000 it fails even with the upstream 5.19 kernel and these patches. So seems we need to report and work with Intel on this to develop a new patch. Though probably we still need to backport these and maybe other ice patches to 5.15 -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
I did not know my laptop (Lenovo X1 Carbon Gen2) had an ambient light sensor until I upgraded to 22.04 so I cannot say it was working after suspend. I can say that with Ubuntu 20.04 suspend would proceed as normal and waking from suspend worked as normal. I can scan some log files and see if I can find any mentions cm32181 from before the upgrade. Is there an example script or C program I can run to verify the device is working and see its output? -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44
[Kernel-packages] [Bug 1976511] Re: [SRU]x86, sched: Treat Intel SNC topology as default, COD as exception
Below is full text from syslog ug 31 18:47:45 ubuntu kernel: [8.758773] x86: Booting SMP configuration: Aug 31 18:47:45 ubuntu kernel: [8.762673] node #0, CPUs:#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 Aug 31 18:47:45 ubuntu kernel: [8.850673] node #1, CPUs: #16 Aug 31 18:47:45 ubuntu kernel: [2.999509] [ cut here ] Aug 31 18:47:45 ubuntu kernel: [2.999509] sched: CPU #16's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Aug 31 18:47:45 ubuntu kernel: [2.999509] WARNING: CPU: 16 PID: 0 at arch/x86/kernel/smpboot.c:415 topology_sane.isra.0+0x70/0x80 Aug 31 18:47:45 ubuntu kernel: [2.999509] Modules linked in: Aug 31 18:47:45 ubuntu kernel: [2.999509] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-26-generic #30-Ubuntu Aug 31 18:47:45 ubuntu kernel: [2.999509] Hardware name: Quanta Cloud Technology Inc. QuantaEdge EGX66Y-2U/S6YQ-MB (LBG-T, RTT), BIOS 2A02 05/19/2022 Aug 31 18:47:45 ubuntu kernel: [2.999509] RIP: 0010:topology_sane.isra.0+0x70/0x80 Aug 31 18:47:45 ubuntu kernel: [2.999509] Code: 5d c3 80 3d dc a1 7a 01 00 75 ec 41 89 d9 45 89 e0 44 89 d9 44 89 d6 48 c7 c7 b0 06 75 94 c6 05 c0 a1 7a 01 01 e8 1b dc 03 00 <0f> 0b eb c9 66 66 2e 0f 1f 84 00 00 00 00 00 90 55 be 00 04 00 00 Aug 31 18:47:45 ubuntu kernel: [2.999509] RSP: :a96218c07ea8 EFLAGS: 00010086 Aug 31 18:47:45 ubuntu kernel: [2.999509] RAX: RBX: RCX: 0208 Aug 31 18:47:45 ubuntu kernel: [2.999509] RDX: 0001 RSI: 0086 RDI: 0046 Aug 31 18:47:45 ubuntu kernel: [2.999509] RBP: a96218c07eb8 R08: 0208 R09: 0010 Aug 31 18:47:45 ubuntu kernel: [2.999509] R10: 94f92228 R11: a96218c07d10 R12: 0001 Aug 31 18:47:45 ubuntu kernel: [2.999509] R13: R14: 9d2c3fc10260 R15: Aug 31 18:47:45 ubuntu kernel: [2.999509] FS: () GS:9d6c3f80() knlGS: Aug 31 18:47:45 ubuntu kernel: [2.999509] CS: 0010 DS: ES: CR0: 80050033 Aug 31 18:47:45 ubuntu kernel: [2.999509] CR2: CR3: 0052c160a001 CR4: 00760ee0 Aug 31 18:47:45 ubuntu kernel: [2.999509] DR0: DR1: DR2: Aug 31 18:47:45 ubuntu kernel: [2.999509] DR3: DR6: fffe0ff0 DR7: 0400 Aug 31 18:47:45 ubuntu kernel: [2.999509] PKRU: Aug 31 18:47:45 ubuntu kernel: [2.999509] Call Trace: Aug 31 18:47:45 ubuntu kernel: [2.999509] set_cpu_sibling_map+0x159/0x590 Aug 31 18:47:45 ubuntu kernel: [2.999509] start_secondary+0x6f/0x1c0 Aug 31 18:47:45 ubuntu kernel: [2.999509] secondary_startup_64+0xa4/0xb0 Aug 31 18:47:45 ubuntu kernel: [2.999509] ---[ end trace 4403443dce444e18 ]--- Aug 31 18:47:45 ubuntu kernel: [9.047785] #17 #18 #19 #20 #21 #22 #23 #24 #25 #26 #27 #28 #29 #30 #31 Aug 31 18:47:45 ubuntu kernel: [9.138674] node #2, CPUs: #32 Aug 31 18:47:45 ubuntu kernel: [2.999509] smpboot: CPU 32 Converting physical 0 to logical die 1 Aug 31 18:47:45 ubuntu kernel: [9.238774] #33 #34 #35 #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 Aug 31 18:47:45 ubuntu kernel: [9.326672] node #3, CPUs: #48 #49 #50 #51 #52 #53 #54 #55 #56 #57 #58 #59 #60 #61 #62 #63 Aug 31 18:47:45 ubuntu kernel: [9.420851] smp: Brought up 4 nodes, 64 CPUs Aug 31 18:47:45 ubuntu kernel: [9.426672] smpboot: Max logical packages: 2 Aug 31 18:47:45 ubuntu kernel: [9.430673] smpboot: Total of 64 processors activated (281650.20 BogoMIPS) -- 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/1976511 Title: [SRU]x86, sched: Treat Intel SNC topology as default, COD as exception Status in linux package in Ubuntu: Confirmed Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [
[Kernel-packages] [Bug 1988120] Re: Support Intel TDX guest attestation driver
** Description changed: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] - Tests have been performed by IBM, a test-case is included in the patch + Tests have been performed by Intel, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. -- 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/1988120 Title: Support Intel TDX guest attestation driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] Tests have been performed by Intel, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways
Investigating this issue with Frode, we saw that its is related to the Security Group applied to the HW Offload (switchdev) capable ports. If an "allow all traffic" security group is attached to the port, the issue is not seen. We see the issue when applying a security group with some explicit rules to allow specific traffic and an implicit DROP rule. -- 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/1987618 Title: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways Status in linux package in Ubuntu: Incomplete Bug description: Charmed OpenStack on Jammy. Hardware offloaded instances that reside on the hypervisor which is also the active OVN gateway for their network have degraded connectivity. $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/ Setting --output-document (outputdocument) to /dev/null DEBUG output created by Wget 1.21.2 on linux-gnu. Reading HSTS entries from /home/ubuntu/.wget-hsts URI encoding = ‘UTF-8’ --2022-08-25 07:16:54-- http://nova.clouds.archive.ubuntu.com/ubuntu/ Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 91.189.91.121, 185.125.190.38, 185.125.190.41, ... Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 2620:2d:4000:1::18 2001:67c:1562::26 Connecting to nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected. Created socket 4. Releasing 0x55ef05654490 (new refcount 1). ---request begin--- GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Date: Thu, 25 Aug 2022 07:16:54 GMT Server: Apache/2.4.29 (Ubuntu) Vary: Accept-Encoding Content-Length: 1779 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html;charset=UTF-8 ---response end--- 200 OK Registered socket 4 for persistent reuse. URI content encoding = ‘UTF-8’ Length: 1779 (1.7K) [text/html] Saving to: ‘/dev/null’ /dev/null 100%[>] 1.74K --.-KB/sin 0.07s 2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779] real 0m5.591s user 0m0.000s sys 0m0.005s $ sudo tcpdump -nevi ens3 not port 22 07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), length 60) 10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 ecr 0,nop,wscale 7], length 0 07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 60) 91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 932285789 ecr 4081686695,nop,wscale 7], length 0 07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), length 52) 10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 0 07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), length 204) 10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], length 152: HTTP, length: 152 GET /ubuntu/ HTTP/1.1 Host: nova.clouds.archive.ubuntu.com User-Agent: Wget/1.21.2 Accept: */* Accept-Encoding: identity Connection: Keep-Alive 07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0 07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6), length 52) 91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr
[Kernel-packages] [Bug 1988120] Re: Support Intel TDX guest attestation driver
** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => 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/1988120 Title: Support Intel TDX guest attestation driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] Tests have been performed by IBM, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
