[Kernel-packages] [Bug 1992216] 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/1992216 Title: package linux-modules-extra-5.15.0-48-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules- extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig Status in linux package in Ubuntu: Confirmed Bug description: problem during the installation ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-5.15.0-48-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andi 3432 F pulseaudio /dev/snd/controlC1: andi 3432 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Oct 8 06:49:09 2022 ErrorMessage: Neue Datei »/var/lib/dpkg/info/linux-modules-extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig HookError_cloud_archive: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/cloud_archive.py' HookError_powerpc: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/powerpc.py' HookError_ubuntu_gnome: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/ubuntu-gnome.py' InstallationDate: Installed on 2020-01-25 (986 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=76342c9b-c354-4fb4-9195-fe5920a05ddc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-modules-extra-5.15.0-48-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules-extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to jammy on 2022-09-17 (20 days ago) dmi.bios.date: 06/04/2013 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:br1.0:efr1.0:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992216] [NEW] package linux-modules-extra-5.15.0-48-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules-extra-5.15.0-48-generic.list
Public bug reported: problem during the installation ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-5.15.0-48-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andi 3432 F pulseaudio /dev/snd/controlC1: andi 3432 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Oct 8 06:49:09 2022 ErrorMessage: Neue Datei »/var/lib/dpkg/info/linux-modules-extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig HookError_cloud_archive: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/cloud_archive.py' HookError_powerpc: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/powerpc.py' HookError_ubuntu_gnome: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/ubuntu-gnome.py' InstallationDate: Installed on 2020-01-25 (986 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=76342c9b-c354-4fb4-9195-fe5920a05ddc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-modules-extra-5.15.0-48-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules-extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to jammy on 2022-09-17 (20 days ago) dmi.bios.date: 06/04/2013 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:br1.0:efr1.0:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-hook-error apport-package 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/1992216 Title: package linux-modules-extra-5.15.0-48-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules- extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig Status in linux package in Ubuntu: Confirmed Bug description: problem during the installation ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-5.15.0-48-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andi 3432 F pulseaudio /dev/snd/controlC1: andi 3432 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Oct 8 06:49:09 2022 ErrorMessage: Neue Datei »/var/lib/dpkg/info/linux-modules-extra-5.15.0-48-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig HookError_cloud_archive: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/cloud_archive.py' HookError_powerpc: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/powerpc.py' HookError_ubuntu_gnome: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 225, in _run_hook PermissionError: [Errno 1] Vorgang nicht zulässig: '/usr/share/apport/general-hooks/ubuntu-gnome.py' InstallationDate: Installed on 2020-01-25 (986
[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic
I suspect that my installation has the same issue (Ubuntu 22.04 upgraded to 22.10 on Framework i5-1240p). I am using Gnome. Linux 5.19.0-18-generic fails to boot. It just stops during the boot process and does not show the login screen. It does boot with the kernel parameter "nomodeset" but then my two external screens do not work. Linux 5.19.0-15-generic does boot but has lots of error messages in dmesg (see below). My usb network adapter (ASIX Electronics Corp. AX88179 Gigabit Ethernet) also loses intermittently the connection which can be recovered by "sudo nmcli networking off" and then "sudo nmcli networking on". I am not sure if this is a separate bug but this was working fine on 22.04. [ 10.953711] usb 3-9: reset full-speed USB device number 3 using xhci_hcd [ 16.024913] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr (expected yes, found no) [ 16.024925] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr2 (expected yes, found no) [ 16.024928] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in enable_psr2_sel_fetch (expected yes, found no) [ 16.024933] [ cut here ] [ 16.024934] pipe state doesn't match! [ 16.024975] WARNING: CPU: 6 PID: 1343 at drivers/gpu/drm/i915/display/intel_display.c:6682 verify_crtc_state+0x47d/0x540 [i915] [ 16.025177] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) snd_seq_dummy rfcomm snd_hrtimer cmac snd_hda_codec_hdmi algif_hash algif_skcipher af_alg snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel nf_tables soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci libcrc32c snd_sof_xtensa_dsp nfnetlink snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match bridge snd_soc_acpi soundwire_bus stp iwlmvm snd_soc_core llc snd_compress intel_tcc_cooling mac80211 ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg x86_pkg_temp_thermal intel_powerclamp snd_intel_sdw_acpi bnep i915 snd_usb_audio snd_hda_codec libarc4 uvcvideo snd_hda_core coretemp snd_usbmidi_lib snd_hwdep videobuf2_vmalloc crct10dif_pclmul [ 16.025241] snd_seq_midi drm_buddy btusb ghash_clmulni_intel videobuf2_memops snd_seq_midi_event ttm btrtl hid_sensor_als videobuf2_v4l2 aesni_intel btbcm hid_sensor_trigger iwlwifi drm_display_helper btintel pmt_telemetry industrialio_triggered_buffer mei_pxp mei_hdcp kvm_intel snd_rawmidi snd_seq pmt_class intel_rapl_msr btmtk videobuf2_common crypto_simd cmdlinepart kfifo_buf cec iwlmei cryptd bluetooth snd_pcm videodev snd_seq_device spi_nor hid_sensor_iio_common cros_usbpd_charger rc_core int3403_thermal cfg80211 ecdh_generic rapl kvm input_leds snd_timer mc intel_cstate industrialio ecc wmi_bmof cros_usbpd_notify serio_raw drm_kms_helper snd joydev mei_me cros_ec_debugfs cros_usbpd_logger cros_ec_sysfs cros_ec_chardev hid_multitouch ee1004 mtd processor_thermal_device_pci i2c_algo_bit soundcore nls_iso8859_1 processor_thermal_device mei fb_sys_fops processor_thermal_rfim syscopyarea sysfillrect processor_thermal_mbox ucsi_acpi processor_thermal_rapl intel_rapl_common sysimg blt [ 16.025317] typec_ucsi intel_vsec int340x_thermal_zone mac_hid typec igen6_edac int3400_thermal acpi_thermal_rel acpi_pad msr parport_pc ppdev lp ramoops pstore_blk parport reed_solomon pstore_zone drm efi_pstore ip_tables x_tables autofs4 usbhid uas usb_storage ax88179_178a usbnet mii hid_sensor_hub hid_generic cros_ec_dev cros_ec_lpcs intel_lpss_pci cros_ec nvme i2c_hid_acpi spi_intel_pci intel_lpss crc32_pclmul i2c_i801 i2c_hid xhci_pci thunderbolt spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pinctrl_tigerlake [ 16.025369] CPU: 6 PID: 1343 Comm: gnome-shell Tainted: G OE 5.19.0-15-generic #15-Ubuntu [ 16.025374] Hardware name: Framework Laptop (12th Gen Intel Core)/FRANGACP04, BIOS 03.04 07/15/2022 [ 16.025377] RIP: 0010:verify_crtc_state+0x47d/0x540 [i915] [ 16.025521] Code: d8 da 15 c1 83 e6 01 e8 91 3d 48 ff e9 ed fc ff ff e8 d1 66 d1 ca 0f 0b 4c 8b 4d c0 4c 8b 45 b8 e9 c6 fd ff ff e8 bd 66 d1 ca <0f> 0b e9 a5 fe ff ff 80 f9 01 0f 87 cf fb 0c 00 8b 73 18 83 e1 01 [ 16.025525] RSP: 0018:b75801b4ba70 EFLAGS: 00010282 [ 16.025529] RAX: RBX: 0001 RCX: 0027 [ 16.025531] RDX: 8f418f9a0568 RSI: 0001 RDI: 8f418f9a0560 [ 16.025533] RBP: b75801b4bac0 R08: R09: b75801b4ba08 [ 16.025534] R10: R11: 04d6 R12: 8f3a1458e000 [ 16.025536] R13: 8f3a1458a000 R14: 8f3a0cc68000 R15: 0001 [ 16.025538] FS: 7f2fa60505c0() GS:8f418f98() knlGS: [ 16.025541]
[Kernel-packages] [Bug 1983756] Re: Please backport kernel patches to support thermal policy handling in OMEN laptops
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1983756 Title: Please backport kernel patches to support thermal policy handling in OMEN laptops Status in linux package in Ubuntu: Expired Bug description: As described in https://www.phoronix.com/news/HP-OMEN-Linux-5.16 and https://www.phoronix.com/news/Linux-5.18-HP-Omen-Thermal, thermal policy handling for OMEN laptops was added in kernel 5.16 and updated in 5.18: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=4c51ba9af42dff0ef6a2ca3edcefa76f3466959e https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=286e937efbc7177c114e80aae9b402131e3886c1 Please backport these kernel patches so that we can check and control fan speed, performance profiles and some device temps. $ cat /proc/version_signature Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 $ lsb_release -rd Description:KDE neon User - 5.25 Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992154] Re: hibernation is restricted with secure boot
You may wish to try suspend to ram, instead of hibernation; please save any open work before testing, some systems don't handle suspend to ram well. sudo systemctl suspend Hopefully this just works and suffices for your needs. It's not the same as hibernation, but might reduce power use enough to use it. Thanks ** 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/1992154 Title: hibernation is restricted with secure boot Status in linux package in Ubuntu: Confirmed Bug description: My PC will not hibernate with 22.04 and secure boot enabled. Only workaround seems to be to disable secure boot, og do not hibernate. Unfortunately my PC is locked on secure boot from the IT department. As disabling secure boot is the most useful workaround, I mark this as a security issue. I get these messages from the kernel sudo dmesg | grep lockdown [sudo] password for kfa: [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.838074] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 [1.902562] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [4.290619] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 I found a number of reports regarding this stating that it is not possible to sign the memory when swapping it to disk. Possibly it is solved in a later 5.19 kernel version, but 22.04 is on 5.15. I found a 5.17 kernel, but that did not solve the problem. It is not possible for me to try the latest 5.19 kernel, as it has to be signed to test this. An alternative could be a patch to the Ubuntu kernel, disabling this until a real solution is found. Here are some references to other sites mentioning the problem https://askubuntu.com/questions/1106105/hibernate-with-uefi-and-secure-boot-enabled https://unix.stackexchange.com/questions/591488/why-does-the-kernel-lockdown-prevent-hibernation/591493#591493 https://askubuntu.com/questions/1259538/lockdown-systemd-logind-hibernation-is-restricted-see-man-kernel-lockdown-7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992212] 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 1992212 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/1992212 Title: nouveau pmu: firmware unavailable gp107 Status in linux package in Ubuntu: Incomplete Bug description: /lib/firmware/nvidia/gp107 /lib/firmware/nvidia/gp107/acr /lib/firmware/nvidia/gp107/gr /lib/firmware/nvidia/gp107/gr/fecs_bl.bin /lib/firmware/nvidia/gp107/gr/fecs_data.bin /lib/firmware/nvidia/gp107/gr/fecs_inst.bin /lib/firmware/nvidia/gp107/gr/fecs_sig.bin /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin /lib/firmware/nvidia/gp107/gr/gpccs_data.bin /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin /lib/firmware/nvidia/gp107/gr/sw_ctx.bin /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin /lib/firmware/nvidia/gp107/nvdec /lib/firmware/nvidia/gp107/sec2 /lib/firmware/nvidia/gp107/acr/bl.bin /lib/firmware/nvidia/gp107/acr/ucode_load.bin /lib/firmware/nvidia/gp107/acr/ucode_unload.bin /lib/firmware/nvidia/gp107/acr/unload_bl.bin /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin /lib/firmware/nvidia/gp107/gr/sw_method_init.bin /lib/firmware/nvidia/gp107/nvdec/scrubber.bin /lib/firmware/nvidia/gp107/sec2/desc-1.bin /lib/firmware/nvidia/gp107/sec2/desc.bin /lib/firmware/nvidia/gp107/sec2/image-1.bin /lib/firmware/nvidia/gp107/sec2/image.bin /lib/firmware/nvidia/gp107/sec2/sig-1.bin /lib/firmware/nvidia/gp107/sec2/sig.bin Package: linux-firmware Status: install ok installed Priority: optional Section: misc Installed-Size: 846721 Maintainer: Ubuntu Kernel Team Architecture: all Multi-Arch: foreign Version: 20220329.git681281e4-0ubuntu3.5 Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-res tricted-common Provides: atmel-firmware Recommends: firmware-sof-signed Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdrago n (<= 1.2-0ubuntu1) Conflicts: atmel-firmware Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. Oct 8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS Oct 8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210730/ns arguments-61) Oct 8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: \_SB.PCI0.PEG0.PEGP._ DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (202107 30/nsarguments-61) Oct 8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus capabilit ies: enabled, status dynamic power, hda bios codec supported Oct 8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus DS M method \_SB_.PCI0.PEG0.PEGP handle Oct 8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling devi ce (0006 -> 0007) Oct 8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 7e9000) vs hw (a300 100) Oct 8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 7e9000) vs hw (9000 1000) Oct 8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 7e9000) vs hw (a000 200) Oct 8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA GP107 (137000a1) Oct 8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 7e9000) vs hw (a200 100) Oct 8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 7e9000) vs hw (8000 1000) Oct 8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: version 86.07.50.00.59 Oct 8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: firmware unavailable Oct 8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] [ENCODER:1 02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it Oct 8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 MiB GDDR5 Oct 8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 202011 03 for :00:02.0 on minor 0 Oct 8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] (m ulti-head: yes rom: no post: no) Oct 8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM:
[Kernel-packages] [Bug 1992212] [NEW] nouveau pmu: firmware unavailable gp107
Public bug reported: /lib/firmware/nvidia/gp107 /lib/firmware/nvidia/gp107/acr /lib/firmware/nvidia/gp107/gr /lib/firmware/nvidia/gp107/gr/fecs_bl.bin /lib/firmware/nvidia/gp107/gr/fecs_data.bin /lib/firmware/nvidia/gp107/gr/fecs_inst.bin /lib/firmware/nvidia/gp107/gr/fecs_sig.bin /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin /lib/firmware/nvidia/gp107/gr/gpccs_data.bin /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin /lib/firmware/nvidia/gp107/gr/sw_ctx.bin /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin /lib/firmware/nvidia/gp107/nvdec /lib/firmware/nvidia/gp107/sec2 /lib/firmware/nvidia/gp107/acr/bl.bin /lib/firmware/nvidia/gp107/acr/ucode_load.bin /lib/firmware/nvidia/gp107/acr/ucode_unload.bin /lib/firmware/nvidia/gp107/acr/unload_bl.bin /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin /lib/firmware/nvidia/gp107/gr/sw_method_init.bin /lib/firmware/nvidia/gp107/nvdec/scrubber.bin /lib/firmware/nvidia/gp107/sec2/desc-1.bin /lib/firmware/nvidia/gp107/sec2/desc.bin /lib/firmware/nvidia/gp107/sec2/image-1.bin /lib/firmware/nvidia/gp107/sec2/image.bin /lib/firmware/nvidia/gp107/sec2/sig-1.bin /lib/firmware/nvidia/gp107/sec2/sig.bin Package: linux-firmware Status: install ok installed Priority: optional Section: misc Installed-Size: 846721 Maintainer: Ubuntu Kernel Team Architecture: all Multi-Arch: foreign Version: 20220329.git681281e4-0ubuntu3.5 Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-res tricted-common Provides: atmel-firmware Recommends: firmware-sof-signed Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdrago n (<= 1.2-0ubuntu1) Conflicts: atmel-firmware Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. Oct 8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS Oct 8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210730/ns arguments-61) Oct 8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: \_SB.PCI0.PEG0.PEGP._ DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (202107 30/nsarguments-61) Oct 8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus capabilit ies: enabled, status dynamic power, hda bios codec supported Oct 8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus DS M method \_SB_.PCI0.PEG0.PEGP handle Oct 8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling devi ce (0006 -> 0007) Oct 8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 7e9000) vs hw (a300 100) Oct 8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 7e9000) vs hw (9000 1000) Oct 8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 7e9000) vs hw (a000 200) Oct 8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA GP107 (137000a1) Oct 8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 7e9000) vs hw (a200 100) Oct 8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 7e9000) vs hw (8000 1000) Oct 8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: version 86.07.50.00.59 Oct 8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: firmware unavailable Oct 8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] [ENCODER:1 02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it Oct 8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 MiB GDDR5 Oct 8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 202011 03 for :00:02.0 on minor 0 Oct 8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] (m ulti-head: yes rom: no post: no) Oct 8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 40 96 MiB Oct 8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 53 6870912 MiB Oct 8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT tabl e 'A' not found Oct 8 08:49:44 fx504 kernel: [3.139768] nouveau :01:00.0: DRM: BIT tabl e 'L' not found Oct 8 08:49:44 fx504 kernel: [3.139770] nouveau :01:00.0: DRM: Pointer to TMDS table not found Oct 8 08:49:44 fx504 kernel: [3.139773] nouveau :01:00.0: DRM: DCB vers ion 4.1 Oct 8 08:49:44 fx504 kernel: [3.140071] nouveau :01:00.0: DRM: MM: usin Oct 8 08:49:44 fx504 kernel: [3.140137] input: Video Bus as /devices/LNXSYS TM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8 Oct 8 08:49:44 fx504 kernel: [3.140265] ACPI: video: Video Device [PEGP] (m ulti-head: no rom: yes post: no) Oct 8 08:49:44 fx504 kernel: [3.140294] input: Video Bus as /devices/LNXSYS TM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input9 Oct 8 08:49:44 fx504 kernel: [3.140322] [drm] Initialized nouveau 1.3.1 201
[Kernel-packages] [Bug 1992211] [NEW] Focal update: v5.4.213 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.4.213 upstream stable release from git://git.kernel.org/ efi: capsule-loader: Fix use-after-free in efi_capsule_write wifi: iwlegacy: 4965: corrected fix for potential off-by-one overflow in il4965_rs_fill_link_cmd() fs: only do a memory barrier for the first set_buffer_uptodate() Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()" net: dp83822: disable false carrier interrupt drm/msm/dsi: fix the inconsistent indenting drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask iio: adc: mcp3911: make use of the sign bit ieee802154/adf7242: defer destroy_workqueue call wifi: cfg80211: debugfs: fix return type in ht40allow_map_read() Revert "xhci: turn off port power in shutdown" net: sched: tbf: don't call qdisc_put() while holding tree lock ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler kcm: fix strp_init() order and cleanup sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb tcp: annotate data-race around challenge_timestamp Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb" net/smc: Remove redundant refcount increase serial: fsl_lpuart: RS485 RTS polariy is inverse staging: rtl8712: fix use after free bugs powerpc: align syscall table for ppc32 vt: Clear selection before changing the font tty: serial: lpuart: disable flow control while waiting for the transmit engine to complete Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag iio: adc: mcp3911: use correct formula for AD conversion misc: fastrpc: fix memory corruption on probe misc: fastrpc: fix memory corruption on open USB: serial: ftdi_sio: add Omron CS1W-CIF31 device id binder: fix UAF of ref->proc caused by race condition usb: dwc3: qcom: fix use-after-free on runtime-PM wakeup drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported" clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops Revert "clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops" clk: core: Fix runtime PM sequence in clk_core_unprepare() Input: rk805-pwrkey - fix module autoloading clk: bcm: rpi: Fix error handling of raspberrypi_fw_get_rate hwmon: (gpio-fan) Fix array out of bounds access gpio: pca953x: Add mutex_lock for regcache sync in PM thunderbolt: Use the actual buffer in tb_async_error() xhci: Add grace period after xHC start to prevent premature runtime suspend. USB: serial: cp210x: add Decagon UCA device id USB: serial: option: add support for OPPO R11 diag port USB: serial: option: add Quectel EM060K modem USB: serial: option: add support for Cinterion MV32-WA/WB RmNet mode usb: typec: altmodes/displayport: correct pin assignment for UFP receptacles usb: dwc2: fix wrong order of phy_power_on and phy_init USB: cdc-acm: Add Icom PMR F3400 support (0c26:0020) usb-storage: Add ignore-residue quirk for NXP PN7462AU s390/hugetlb: fix prepare_hugepage_range() check for 2 GB hugepages s390: fix nospec table alignments USB: core: Prevent nested device-reset calls usb: gadget: mass_storage: Fix cdrom data transfers on MAC-OS driver core: Don't probe devices after bus_type.match() probe deferral wifi: mac80211: Don't finalize CSA in IBSS mode if state is disconnected net: mac802154: Fix a condition in the receive path ALSA: seq: oss: Fix data-race for max_midi_devs access ALSA: seq: Fix data-race at module auto-loading drm/i915/glk: ECS Liva Q2 needs GLK HDMI port timing quirk btrfs: harden identification of a stale device usb: dwc3: fix PHY disable sequence usb: dwc3: disable USB core PHY management USB: serial: ch341: fix lost character on LCR updates USB: serial: ch341: fix disabled rx timer on older devices scsi: megaraid_sas: Fix double kfree() drm/gem: Fix GEM handle release errors drm/amdgpu: Check num_gfx_rings for gfx v9_0 rb setup. drm/radeon: add a force flush to delay work when radeon parisc: ccio-dma: Handle kmalloc failure in ccio_init_resources() parisc: Add runtime check to prevent PA2.0 kernels on PA1.x machines arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level fbdev: chipsfb: Add missing pci_disable_device() in chipsfb_pci_init() drm/amdgpu: mmVM_L2_CNTL3 register not initialized correctly ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() ALSA: aloop: Fix random zeros in capture data when using jiffies timer ALSA: usb-audio: Fix an out-of-bounds bug in __snd_usb_parse_audio_interface() kprobes: Prohibit probes in gate area debugfs: add debugfs_lookup_and_remove() nvmet:
[Kernel-packages] [Bug 1741959] Re: Double message from BTRFS: "disk space caching is enabled"
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=198401. 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 2018-01-08T19:07:47+00:00 caravena wrote: Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1741959 "dmesg: $ dmesg | grep BTRFS [...] [ 3.687164] BTRFS info (device sdb1): disk space caching is enabled [...] [ 4.160166] BTRFS info (device sdb1): disk space caching is enabled" Regards, -- Cristian Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741959/comments/2 On 2022-10-06T21:23:22+00:00 dsterba wrote: This is a semi-automated bugzilla cleanup, report is against an old kernel version. If the problem still happens, please open a new bug. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741959/comments/3 ** Changed in: linux Status: Unknown => Expired ** 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/1741959 Title: Double message from BTRFS: "disk space caching is enabled" Status in Linux: Expired Status in linux package in Ubuntu: Triaged Bug description: Hello, dmesg: $ dmesg | grep BTRFS [...] [3.687164] BTRFS info (device sdb1): disk space caching is enabled [...] [4.160166] BTRFS info (device sdb1): disk space caching is enabled Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.14.0-15-generic 4.14.0-15.18 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 1793 F...m pulseaudio /dev/snd/controlC0: caravena 1793 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 16:02:18 2018 InstallationDate: Installed on 2017-10-13 (87 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-15-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.14.0-15-generic N/A linux-backports-modules-4.14.0-15-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1741959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992194] 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/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :05:00.0: value [iter 4]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582000] iwlwifi
[Kernel-packages] [Bug 1992194] [NEW] random CSR_RESET errors in iwlwifi appear under kinetic
Public bug reported: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :05:00.0: value [iter 4]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582000] iwlwifi :05:00.0: value [iter 5]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582015] iwlwifi :05:00.0: value [iter 6]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582031] iwlwifi :05:00.0: value [iter 7]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582046] iwlwifi :05:00.0: value [iter 8]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582061] iwlwifi :05:00.0: value [iter
[Kernel-packages] [Bug 1991782] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622104/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622098/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622102/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622106/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622101/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622103/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622097/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622105/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622099/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622095/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622094/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622096/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622100/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622092/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622093/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622090/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991782] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1991782/+attachment/5622091/+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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IL:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 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-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991782] Re: mktme error on boot
apport information ** Tags added: apport-collected jammy ** Description changed: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: amyekut1134 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-06-15 (479 days ago) + InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: Dell Inc. XPS 13 9310 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash + ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-48-generic N/A + linux-backports-modules-5.15.0-48-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 + Tags: jammy + Uname: Linux 5.15.0-48-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + acpidump: + Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized + + This incident has been reported. + dmi.bios.date: 08/09/2022 + dmi.bios.release: 3.10 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 3.10.0 + dmi.board.name: 0DXP1F + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: + dmi.product.family: XPS + dmi.product.name: XPS 13 9310 + dmi.product.sku: 0991 + dmi.sys.vendor: Dell Inc. ** Description changed: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amyekut1134 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-15 (479 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/09/2022 dmi.bios.release: 3.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.10.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS
[Kernel-packages] [Bug 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support
The attached patch can be used to disable PCIe in the device-tree: [PATCH] riscv: dts: microchip: disable the icicle's pcie controller PCIe on the icicle kit is unfortunately non-functional in the v2022.10 design as things stand. Disable it in the devicetree so that there will be no issues if the driver happens to be enabled. Signed-off-by: Conor Dooley ** Patch added: "0001-riscv-dts-microchip-disable-the-icicle-s-pcie-contro.patch" https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+attachment/5622081/+files/0001-riscv-dts-microchip-disable-the-icicle-s-pcie-contro.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1989566 Title: [FFe] PolarFire Icicle Kit: enable PCIe support Status in linux-riscv package in Ubuntu: Triaged Bug description: The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it is not usable. Please, add the following patches: # https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/ riscv: dts: microchip: add pci dma ranges for the icicle # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: move the mpfs' pci node to # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: update pci address # https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: re-jig fabric peripheral # https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/ riscv: dts: microchip: add fabric address translation # https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/ PCI: microchip: add fabric address translation properties All patches are strictly restricted to the PolarFire Icicle Kit and have no impact on any other RISC-V boards that we support. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
Here's the full trace, #7 cuts off the start of the BUG: [2.390194] kernel: i915 :00:02.0: vgaarb: deactivate vga console [2.390270] kernel: BUG: kernel NULL pointer dereference, address: 002e [2.390272] kernel: #PF: supervisor write access in kernel mode [2.390273] kernel: #PF: error_code(0x0002) - not-present page [2.390273] kernel: PGD 0 P4D 0 [2.390275] kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI [2.390277] kernel: CPU: 10 PID: 516 Comm: systemd-udevd Not tainted 5.19.0-18-generic #18-Ubuntu [2.390278] kernel: Hardware name: Dell Inc. OptiPlex 7000/0R8DWV, BIOS 1.3.62 06/13/2022 [2.390279] kernel: RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915] [2.390352] kernel: Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff 46 2e 00 66 41 89 85 e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08 [2.390354] kernel: RSP: :ae11c088f770 EFLAGS: 00010206 [2.390355] kernel: RAX: 0301 RBX: 0003 RCX: 0001 [2.390356] kernel: RDX: RSI: RDI: 0001 [2.390356] kernel: RBP: ae11c088f860 R08: R09: [2.390357] kernel: R10: 0002 R11: 0001 R12: 0100 [2.390358] kernel: R13: a0aa063b00f0 R14: 0005 R15: a0aa063b [2.390359] kernel: FS: 7f42f4c368c0() GS:a0b16f88() knlGS: [2.390359] kernel: CS: 0010 DS: ES: CR0: 80050033 [2.390360] kernel: CR2: 002e CR3: 0001042a4005 CR4: 00770ee0 [2.390361] kernel: PKRU: 5554 [2.390362] kernel: Call Trace: [2.390363] kernel: [2.390364] kernel: ? __intel_wait_for_register_fw+0xf5/0x200 [i915] [2.390412] kernel: intel_bw_init_hw+0xe5/0x140 [i915] [2.390461] kernel: i915_driver_hw_probe+0x2cc/0x370 [i915] [2.390502] kernel: i915_driver_probe+0x19b/0x490 [i915] [2.390538] kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm] [2.390558] kernel: ? acpi_dev_found+0x64/0x80 [2.390562] kernel: i915_pci_probe+0x56/0x150 [i915] [2.390599] kernel: local_pci_probe+0x44/0x90 [2.390602] kernel: pci_call_probe+0x55/0x190 [2.390603] kernel: pci_device_probe+0x84/0x120 [2.390605] kernel: really_probe+0x1dc/0x3b0 [2.390607] kernel: __driver_probe_device+0x12c/0x1b0 [2.390608] kernel: driver_probe_device+0x24/0xd0 [2.390609] kernel: __driver_attach+0xe0/0x210 [2.390611] kernel: ? __device_attach_driver+0x130/0x130 [2.390612] kernel: bus_for_each_dev+0x8d/0xe0 [2.390614] kernel: driver_attach+0x1e/0x30 [2.390615] kernel: bus_add_driver+0x187/0x230 [2.390616] kernel: driver_register+0x8f/0x100 [2.390617] kernel: __pci_register_driver+0x62/0x70 [2.390618] kernel: i915_pci_register_driver+0x23/0x30 [i915] [2.390651] kernel: i915_init+0x3b/0xf2 [i915] [2.390695] kernel: ? 0xc27bb000 [2.390697] kernel: do_one_initcall+0x5b/0x240 [2.390700] kernel: do_init_module+0x50/0x210 [2.390702] kernel: load_module+0xb7d/0xcd0 [2.390703] kernel: __do_sys_finit_module+0xc4/0x140 [2.390704] kernel: ? __do_sys_finit_module+0xc4/0x140 [2.390706] kernel: __x64_sys_finit_module+0x18/0x30 [2.390707] kernel: do_syscall_64+0x58/0x90 [2.390710] kernel: ? exit_to_user_mode_prepare+0x30/0xb0 [2.390712] kernel: ? syscall_exit_to_user_mode+0x26/0x50 [2.390714] kernel: ? __x64_sys_newfstatat+0x1c/0x30 [2.390715] kernel: ? do_syscall_64+0x67/0x90 [2.390717] kernel: ? exit_to_user_mode_prepare+0x9b/0xb0 [2.390718] kernel: ? syscall_exit_to_user_mode+0x26/0x50 [2.390720] kernel: ? __x64_sys_read+0x19/0x30 [2.390721] kernel: ? do_syscall_64+0x67/0x90 [2.390723] kernel: ? do_syscall_64+0x67/0x90 [2.390724] kernel: ? sysvec_call_function+0x4b/0xd0 [2.390725] kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd [2.390727] kernel: RIP: 0033:0x7f42f4b16a1d [2.390728] kernel: Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 f3 0d 00 f7 d8 64 89 01 48 [2.390729] kernel: RSP: 002b:7ffc506fbdc8 EFLAGS: 0246 ORIG_RAX: 0139 [2.390730] kernel: RAX: ffda RBX: 55622782d830 RCX: 7f42f4b16a1d [2.390731] kernel: RDX: RSI: 7f42f4e43458 RDI: 0018 [2.390732] kernel: RBP: 7f42f4e43458 R08: R09: 7ffc506fbef0 [2.390733] kernel: R10: 0018 R11: 0246 R12: 0002 [2.390733] kernel: R13: 5562277ae470 R14: R15: 55622775f110 [2.390734] kernel: [2.390735] kernel: Modules linked in: i915(+) snd_hwdep
[Kernel-packages] [Bug 1991782] Re: mktme error on boot
a video of the boot process: https://drive.google.com/file/d/1tbCe35ueDi5lmo_UHacL5hhG_ZlM-AOQ/view?usp=sharing the error message screenshot https://drive.google.com/file/d/1tXqgyFG4CheKtf7vKw5cSUutd2SsYs0Z/view?usp=sharing -- 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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
On my Alder Lake system this appears to be a failure to load the Intel driver in some way. I get the following error in XOrg.0.log on 5.19.0-18: [ 3.817] (EE) open /dev/dri/card0: No such file or directory On 5.19.0-15, it loads the card correctly, and that device does exist. -- 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/1991704 Title: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Confirmed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991782] 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 1991782 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/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991782] Re: mktme error on boot
This is my best guess at "package" ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991782 Title: mktme error on boot Status in linux package in Ubuntu: Incomplete Bug description: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991782] [NEW] mktme error on boot
You have been subscribed to a public bug: While booting the system I get this error message twice: kernel: x86/mktme: No known encryption algorithm is supported: 0x0 pci :00:07.0: DPC: RP PIO log size 0 is invalid pci :00:07.2: DPC: RP PIO log size 0 is invalid This seems to be new, after recent upgrade to KUBUNTU 22.04. My system: Dell XPS 13 9310 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- mktme error on boot https://bugs.launchpad.net/bugs/1991782 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 1991975] Re: dev file system is mounted without nosuid or noexec
Here is a workaround for this issue in case anyone finds this in the future. Copy remount_dev.service to /etc/systemd/system sudo chown root:root /etc/systemd/system/remount_dev.service sudo systemctl daemon-reload sudo systemctl enable remount_dev.service Still I think the kernel patch should be applied, but at least there's a workaround for now. ** Attachment added: "Systemd unit file as workaround" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+attachment/5622080/+files/remount_dev.service -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to:
[Kernel-packages] [Bug 1990916] Re: Add AMDI0009 support to amd-pmc
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990916 Title: Add AMDI0009 support to amd-pmc Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: New Bug description: For AMD Pink Sardine a change is being made in newer BIOSes that will use a different _HID than is currently supported in amd-pmc as of kernel 6.0. This new ID changes a interface to the BIOS and is not just adding the ID. To support s0i3 in OEM 6.0 kernel we will need to support this new ID/interface. AMD will submit the code to target to kernel 6.1, but it will be needed in OEM-6.0 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
** Information type changed from Private Security to Public Security ** Summary changed: - dev file system is mounted without nosuid + dev file system is mounted without nosuid or noexec -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
** Changed in: hwe-next Importance: Undecided => Critical ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid -- 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/1990920 Title: Fix resume on AMD platforms when TBT monitor is plugged Status in HWE Next: New 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: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] When TBT monitor is connected to AMD platform, system resume will hit stack corruption or BUG_ON() macro. [Fix] Revert the offending commit and handle MST properly. [Test] The system can resume normally and no more kernel splat. [Where problems could occur] The new logic is restriced to MST hub, so normal DP/HDMI usage should be unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
** Tags removed: foundations-todo -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: In Progress Status in strace package in Ubuntu: Triaged Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986477] Re: Failure to Suspend With Laptop Lid Closure After Upgrade to 22.04
Is my only option to fall back to 20.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/1986477 Title: Failure to Suspend With Laptop Lid Closure After Upgrade to 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS-15 9550 Laptop lid closure does not result in transition to Suspend mode following upgrade from 20.04 to 22.04. Screen remains on and hard disk does not spin down. If Suspend is enforced from the Power Off/Log Out option, disk remains on. Attempted the following: 1. Edit the file /etc/systemd/logind.conf to uncomment the lines HandleLidSwitch=suspend, HandleLidSwithExternalPower=suspend, and HandleLidSwitchDocked=ignore. Did not result in Suspend mode when lid was closed. 2. Activated Standby Timeout Settings and set time to 5 minutes for the hard disk. The disk remained on. Both gnome-power-manager and pm-utils are installed. Using X.Org X server ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 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 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Aug 14 12:03:55 2022 InstallationDate: Installed on 2018-06-01 (1535 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-12 (2 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989566] Re: [FFe] PolarFire Icicle Kit: enable PCIe support
Microchip informed us that a matching and tested set of upstream Linux PCIe patches matching the updcoming HSS v2022.10 is not available. We should postpone adding patches for PCIe to after the 2022.10 Ubuntu release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1989566 Title: [FFe] PolarFire Icicle Kit: enable PCIe support Status in linux-riscv package in Ubuntu: Triaged Bug description: The PolarFire Icicle Kit provides a PCIe slot. With our 5.19 kernel it is not usable. Please, add the following patches: # https://lore.kernel.org/linux-riscv/20220901133403.3392291-5-conor.doo...@microchip.com/ riscv: dts: microchip: add pci dma ranges for the icicle # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: move the mpfs' pci node to # https://lore.kernel.org/linux-riscv/20220901133403.3392291-6-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: update pci address # https://lore.kernel.org/linux-riscv/20220901133403.3392291-8-conor.doo...@microchip.com/ riscv: dts: microchip: icicle: re-jig fabric peripheral # https://lore.kernel.org/linux-riscv/20220902142202.2437658-3-daire.mcnam...@microchip.com/ riscv: dts: microchip: add fabric address translation # https://lore.kernel.org/linux-riscv/20220902142202.2437658-4-daire.mcnam...@microchip.com/ PCI: microchip: add fabric address translation properties All patches are strictly restricted to the PolarFire Icicle Kit and have no impact on any other RISC-V boards that we support. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1989566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
Hi Michael, Regression risk of this patch set is very less. It just includes minor bug fixes. We have tested these patches and didn't find any issues. Thanks, Sreekanth -- 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface [Fix] Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. [Test Plan] 1. All drives attached to the controller are Enumerated in OS 2. IO stress for 5Hrs 3. Created a filesystem and done some IO transitions 4. Controller reset and TMs and while IOs are running 5. driver load and unload 6. Reboot loop 7. Verified that the diag trigger settings are persistent across the reboots. [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface [Fix] Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. [Test Plan] 1. All drives attached to the controller are Enumerated in OS 2. IO stress for 5Hrs 3. Created a filesystem and done some IO transitions 4. Controller reset and TMs and while IOs are running 5. driver load and unload 6. Reboot loop 7. Verified that the diag trigger settings are persistent across the reboots. [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991142] Re: UAF bug caused by rose_t0timer_expiry
** Changed in: linux (Ubuntu Kinetic) Importance: High => Low ** Changed in: linux (Ubuntu Jammy) Importance: High => Low ** Changed in: linux (Ubuntu Focal) Importance: High => Low ** Changed in: linux (Ubuntu Bionic) Importance: High => Low ** Changed in: linux (Ubuntu Xenial) Importance: High => Low -- 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/1991142 Title: UAF bug caused by rose_t0timer_expiry Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: There are UAF bugs in rose_heartbeat_expiry(), rose_timer_expiry() and rose_idletimer_expiry(). The root cause is that del_timer() could not stop the timer handler that is running and the refcount of sock is not managed properly. One of the UAF bugs is shown below: (thread 1) |(thread 2) | rose_bind | rose_connect |rose_start_heartbeat rose_release|(wait a time) case ROSE_STATE_0 | rose_destroy_socket | rose_heartbeat_expiry rose_stop_heartbeat | sock_put(sk)|... sock_put(sk) // FREE | |bh_lock_sock(sk) // USE The sock is deallocated by sock_put() in rose_release() and then used by bh_lock_sock() in rose_heartbeat_expiry(). Although rose_destroy_socket() calls rose_stop_heartbeat(), it could not stop the timer that is running. The KASAN report triggered by POC is shown below: BUG: KASAN: use-after-free in _raw_spin_lock+0x5a/0x110 Write of size 4 at addr 88800ae59098 by task swapper/3/0 ... Call Trace: dump_stack_lvl+0xbf/0xee print_address_description+0x7b/0x440 print_report+0x101/0x230 ? irq_work_single+0xbb/0x140 ? _raw_spin_lock+0x5a/0x110 kasan_report+0xed/0x120 ? _raw_spin_lock+0x5a/0x110 kasan_check_range+0x2bd/0x2e0 _raw_spin_lock+0x5a/0x110 rose_heartbeat_expiry+0x39/0x370 ? rose_start_heartbeat+0xb0/0xb0 call_timer_fn+0x2d/0x1c0 ? rose_start_heartbeat+0xb0/0xb0 expire_timers+0x1f3/0x320 __run_timers+0x3ff/0x4d0 run_timer_softirq+0x41/0x80 __do_softirq+0x233/0x544 irq_exit_rcu+0x41/0xa0 sysvec_apic_timer_interrupt+0x8c/0xb0 asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:default_idle+0xb/0x10 RSP: 0018:c912fea0 EFLAGS: 0202 RAX: bcae RBX: 888006660f00 RCX: bcae RDX: 0001 RSI: 843a11c0 RDI: 843a1180 RBP: dc00 R08: dc00 R09: ed100da36d46 R10: dfffe9100da36d47 R11: 83cf0950 R12: R13: 111000ccc1e0 R14: 8542af28 R15: dc00 ... Allocated by task 146: __kasan_kmalloc+0xc4/0xf0 sk_prot_alloc+0xdd/0x1a0 sk_alloc+0x2d/0x4e0 rose_create+0x7b/0x330 __sock_create+0x2dd/0x640 __sys_socket+0xc7/0x270 __x64_sys_socket+0x71/0x80 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Freed by task 152: kasan_set_track+0x4c/0x70 kasan_set_free_info+0x1f/0x40 kasan_slab_free+0x124/0x190 kfree+0xd3/0x270 __sk_destruct+0x314/0x460 rose_release+0x2fa/0x3b0 sock_close+0xcb/0x230 __fput+0x2d9/0x650 task_work_run+0xd6/0x160 exit_to_user_mode_loop+0xc7/0xd0 exit_to_user_mode_prepare+0x4e/0x80 syscall_exit_to_user_mode+0x20/0x40 do_syscall_64+0x4f/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992118] Re: AX210 WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel
** Summary changed: - AX210 WLAN failed after upgrade to 5.15 intel IoTG kernel + AX210 WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel ** Summary changed: - AX210 WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel + AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel ** Description changed: [Summary] - AX210 (8086:e024) WLAN down after update to 5.15 Intel IoTG kernel. + AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 Intel IoTG kernel. [Steps to reproduce] $ sudo apt update $ sudo apt upgrade $ reboot [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% - [Other Info] + [Other Info] [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002) [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported by driver [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode - [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL + [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1 [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2 [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1 [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2 [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1 [4.812520] iwlwifi :02:00.0: 0x0010 | data2 [4.812523] iwlwifi :02:00.0: 0x | data3 [4.812527] iwlwifi :02:00.0: 0x | beacon time [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low [4.812533] iwlwifi :02:00.0: 0x | tsf hi [4.812536] iwlwifi :02:00.0: 0x | time gp1 [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2 [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor [4.812553] iwlwifi :02:00.0: 0x0420 | hw version [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd [4.812563] iwlwifi :02:00.0: 0x0002 | isr0 [4.812566] iwlwifi :02:00.0: 0x6000 | isr1 [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2 [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3 [4.812575] iwlwifi :02:00.0: 0x | isr4 [4.812578] iwlwifi :02:00.0: 0x | last cmd Id [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event [4.812584] iwlwifi :02:00.0: 0x | l2p_control [4.812588] iwlwifi :02:00.0: 0x | l2p_duration [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel [4.812600] iwlwifi :02:00.0: 0x | timestamp [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7 [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1 [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2 [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1 [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2 [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1 [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2 [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3 [4.812673] iwlwifi :02:00.0: 0x0042 | umac major [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd [4.812689] iwlwifi :02:00.0: 0x | isr status reg [4.812702] iwlwifi :02:00.0: IML/ROM dump: [
[Kernel-packages] [Bug 1990275] Re: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04
Okay, that's good - thanks for that. Closing this ticket as invalid. ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: ubuntu-z-systems Status: Incomplete => Opinion ** Changed in: ubuntu-z-systems Status: Opinion => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990275 Title: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: == Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42 == ---Problem Description--- On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports connected to the a pair of TOR switches , act as entry point to cluster of compute nodes to access public network ( edge node) with following level of mlx firmware : ethtool -i p0 driver: mlx5e_rep version: 5.4.0-104.118- firmware-version: 16.27.1016 (MT_13) expansion-rom-version: bus-info: 0100:00:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to routing events and sets the LAG affinity accordingly , whereas in one of custom services has Fabcon service listens to the routing events and sets the LAG affinity in the mellanox driver accordingly. The edge node routes defined in compute nodes use both the two interfaces (port1 -P0 and port2- P1) for the LAG affinity. For instance 10.66.0.170 proto bgp src 10.66.11.43 metric 20 nexthop via 172.31.22.42 dev p0 weight 1 nexthop via 172.31.22.170 dev p1 weight 1 As an example post an edge node bootup , LAG mapping gets converged to use both port1(P0) and port2 (P1) by default root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 (<-- Both ports are equally mapped) The issue comes, when the mlx5_core driver cannot derive the LAG configuration from specific routes. For instance,an operation of disabling an interface from edge node above (10.66.0.170) or addition/removal of the interface, causes mlx5_core driver to listen on the routing change and change the LAG affinity to use a single network interface only. In the following example ,a new static route entry to a single destination (10.66.47.34) is added as below ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via 172.31.22.42 dev p0 Caused the LAG mapping change to port1(p0) as detected as following root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 [ 757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1
[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760106 Title: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs
Since this is no longer an FFe thing, I am removing so from the title. This should help fix our searches better. The ideal way would be to unsubscribe ubuntu-release, though. ** Summary changed: - FFe: Enable configuring resume offset via sysfs + Enable configuring resume offset via sysfs -- 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/1760106 Title: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992154] 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 1992154 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/1992154 Title: hibernation is restricted with secure boot Status in linux package in Ubuntu: Incomplete Bug description: My PC will not hibernate with 22.04 and secure boot enabled. Only workaround seems to be to disable secure boot, og do not hibernate. Unfortunately my PC is locked on secure boot from the IT department. As disabling secure boot is the most useful workaround, I mark this as a security issue. I get these messages from the kernel sudo dmesg | grep lockdown [sudo] password for kfa: [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.838074] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 [1.902562] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [4.290619] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 I found a number of reports regarding this stating that it is not possible to sign the memory when swapping it to disk. Possibly it is solved in a later 5.19 kernel version, but 22.04 is on 5.15. I found a 5.17 kernel, but that did not solve the problem. It is not possible for me to try the latest 5.19 kernel, as it has to be signed to test this. An alternative could be a patch to the Ubuntu kernel, disabling this until a real solution is found. Here are some references to other sites mentioning the problem https://askubuntu.com/questions/1106105/hibernate-with-uefi-and-secure-boot-enabled https://unix.stackexchange.com/questions/591488/why-does-the-kernel-lockdown-prevent-hibernation/591493#591493 https://askubuntu.com/questions/1259538/lockdown-systemd-logind-hibernation-is-restricted-see-man-kernel-lockdown-7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990275] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-10-07 05:40 EDT--- @fheimes: Hello Frank, Kishore stated that they have decided to upgrade to a new level of Ubuntu kernel that has a stable LAG code base 5.15.39 that includes the fixes. Therefore, a backport / SRU to focal is no longer required. With that, I think we can close this bugzilla and the corresponding LP item. Thanks again for your help! -- 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/1990275 Title: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: == Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42 == ---Problem Description--- On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports connected to the a pair of TOR switches , act as entry point to cluster of compute nodes to access public network ( edge node) with following level of mlx firmware : ethtool -i p0 driver: mlx5e_rep version: 5.4.0-104.118- firmware-version: 16.27.1016 (MT_13) expansion-rom-version: bus-info: 0100:00:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to routing events and sets the LAG affinity accordingly , whereas in one of custom services has Fabcon service listens to the routing events and sets the LAG affinity in the mellanox driver accordingly. The edge node routes defined in compute nodes use both the two interfaces (port1 -P0 and port2- P1) for the LAG affinity. For instance 10.66.0.170 proto bgp src 10.66.11.43 metric 20 nexthop via 172.31.22.42 dev p0 weight 1 nexthop via 172.31.22.170 dev p1 weight 1 As an example post an edge node bootup , LAG mapping gets converged to use both port1(P0) and port2 (P1) by default root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 (<-- Both ports are equally mapped) The issue comes, when the mlx5_core driver cannot derive the LAG configuration from specific routes. For instance,an operation of disabling an interface from edge node above (10.66.0.170) or addition/removal of the interface, causes mlx5_core driver to listen on the routing change and change the LAG affinity to use a single network interface only. In the following example ,a new static route entry to a single destination (10.66.47.34) is added as below ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via 172.31.22.42 dev p0 Caused the LAG mapping change to port1(p0) as detected as following root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 [ 757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1
[Kernel-packages] [Bug 1992118] Re: AX210 WLAN failed after upgrade to 5.15 intel IoTG kernel
** Description changed: [Summary] AX210 (8086:e024) WLAN down after update to 5.15 Intel IoTG kernel. [Steps to reproduce] $ sudo apt update $ sudo apt upgrade $ reboot [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% + + [Other Info] + [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002) + [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported by driver + [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 + [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm + [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 + [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 + [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. + [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump: + [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 + [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode + [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL + [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 + [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1 + [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2 + [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1 + [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2 + [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1 + [4.812520] iwlwifi :02:00.0: 0x0010 | data2 + [4.812523] iwlwifi :02:00.0: 0x | data3 + [4.812527] iwlwifi :02:00.0: 0x | beacon time + [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low + [4.812533] iwlwifi :02:00.0: 0x | tsf hi + [4.812536] iwlwifi :02:00.0: 0x | time gp1 + [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2 + [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type + [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major + [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor + [4.812553] iwlwifi :02:00.0: 0x0420 | hw version + [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version + [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd + [4.812563] iwlwifi :02:00.0: 0x0002 | isr0 + [4.812566] iwlwifi :02:00.0: 0x6000 | isr1 + [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2 + [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3 + [4.812575] iwlwifi :02:00.0: 0x | isr4 + [4.812578] iwlwifi :02:00.0: 0x | last cmd Id + [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event + [4.812584] iwlwifi :02:00.0: 0x | l2p_control + [4.812588] iwlwifi :02:00.0: 0x | l2p_duration + [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid + [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match + [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel + [4.812600] iwlwifi :02:00.0: 0x | timestamp + [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler + [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump: + [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7 + [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT + [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1 + [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2 + [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1 + [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2 + [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1 + [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2 + [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3 + [4.812673] iwlwifi :02:00.0: 0x0042 | umac major + [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor + [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer + [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer + [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd + [4.812689] iwlwifi :02:00.0: 0x | isr status reg + [4.812702] iwlwifi :02:00.0: IML/ROM dump: + [4.812705] iwlwifi :02:00.0: 0x0B03 | IML/ROM error/state + [4.812717] iwlwifi :02:00.0: 0x6FBE | IML/ROM data1 + [4.812730] iwlwifi :02:00.0: 0x0080 | IML/ROM WFPM_AUTH_KEY_0 + [4.812739] iwlwifi :02:00.0: Fseq Registers: + [4.812765] iwlwifi :02:00.0: 0x6100 | FSEQ_ERROR_CODE + [4.812775] iwlwifi :02:00.0: 0x00440005 | FSEQ_TOP_INIT_VERSION + [4.812781] iwlwifi :02:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION + [4.812787] iwlwifi :02:00.0: 0xA652 |
[Kernel-packages] [Bug 1992154] [NEW] hibernation is restricted with secure boot
Public bug reported: My PC will not hibernate with 22.04 and secure boot enabled. Only workaround seems to be to disable secure boot, og do not hibernate. Unfortunately my PC is locked on secure boot from the IT department. As disabling secure boot is the most useful workaround, I mark this as a security issue. I get these messages from the kernel sudo dmesg | grep lockdown [sudo] password for kfa: [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.838074] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 [1.902562] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [4.290619] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 I found a number of reports regarding this stating that it is not possible to sign the memory when swapping it to disk. Possibly it is solved in a later 5.19 kernel version, but 22.04 is on 5.15. I found a 5.17 kernel, but that did not solve the problem. It is not possible for me to try the latest 5.19 kernel, as it has to be signed to test this. An alternative could be a patch to the Ubuntu kernel, disabling this until a real solution is found. Here are some references to other sites mentioning the problem https://askubuntu.com/questions/1106105/hibernate-with-uefi-and-secure-boot-enabled https://unix.stackexchange.com/questions/591488/why-does-the-kernel-lockdown-prevent-hibernation/591493#591493 https://askubuntu.com/questions/1259538/lockdown-systemd-logind-hibernation-is-restricted-see-man-kernel-lockdown-7 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: hibernation secure-boot ** Information type changed from Private Security to Public -- 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/1992154 Title: hibernation is restricted with secure boot Status in linux package in Ubuntu: New Bug description: My PC will not hibernate with 22.04 and secure boot enabled. Only workaround seems to be to disable secure boot, og do not hibernate. Unfortunately my PC is locked on secure boot from the IT department. As disabling secure boot is the most useful workaround, I mark this as a security issue. I get these messages from the kernel sudo dmesg | grep lockdown [sudo] password for kfa: [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.838074] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 [1.902562] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [4.290619] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 I found a number of reports regarding this stating that it is not possible to sign the memory when swapping it to disk. Possibly it is solved in a later 5.19 kernel version, but 22.04 is on 5.15. I found a 5.17 kernel, but that did not solve the problem. It is not possible for me to try the latest 5.19 kernel, as it has to be signed to test this. An alternative could be a patch to the Ubuntu kernel, disabling this until a real solution is found. Here are some references to other sites mentioning the problem https://askubuntu.com/questions/1106105/hibernate-with-uefi-and-secure-boot-enabled https://unix.stackexchange.com/questions/591488/why-does-the-kernel-lockdown-prevent-hibernation/591493#591493 https://askubuntu.com/questions/1259538/lockdown-systemd-logind-hibernation-is-restricted-see-man-kernel-lockdown-7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748105] Re: port80 test in ubuntu_kvm_unit_tests failed with timeout
Test has long gone, let's close this. ** Changed in: ubuntu-kernel-tests Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-azure-edge (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oracle-5.0 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1748105 Title: port80 test in ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-oracle-5.0 package in Ubuntu: Invalid Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test port80 test will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the port80 test as root: # TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/port80.flat -smp 1 # -initrd /tmp/tmp.3p9PWc2SRi enabling apic begining port 0x80 write test qemu-system-x86_64: terminating on signal 15 from pid 7790 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:13:18 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
Hello Dimitri, or anyone else affected, Accepted dkms into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.8.7-2ubuntu2.1 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: dkms (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: In Progress Status in zfs-linux package in Ubuntu: In Progress Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Committed Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. * Some DKMS modules need further fixes to preserve and not loose the compiler setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992149] 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/1992149 Title: framework laptop touchpad doesn't work about 50% of the time upon resume from deep sleep Status in linux package in Ubuntu: Confirmed Bug description: The `hid_multitouch` module may be at fault, but `sudo modprobe -r hid_multitouch` and then reinserting it doesn't address the issue. The only workaround is to close the framework laptop lid to trigger sleep, and then upon resume from sleep a second time it works 100% of the times so far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 8442 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 7 09:27:38 2022 InstallationDate: Installed on 2022-03-11 (209 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (161 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992149] [NEW] framework laptop touchpad doesn't work about 50% of the time upon resume from deep sleep
Public bug reported: The `hid_multitouch` module may be at fault, but `sudo modprobe -r hid_multitouch` and then reinserting it doesn't address the issue. The only workaround is to close the framework laptop lid to trigger sleep, and then upon resume from sleep a second time it works 100% of the times so far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 8442 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 7 09:27:38 2022 InstallationDate: Installed on 2022-03-11 (209 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (161 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1992149 Title: framework laptop touchpad doesn't work about 50% of the time upon resume from deep sleep Status in linux package in Ubuntu: New Bug description: The `hid_multitouch` module may be at fault, but `sudo modprobe -r hid_multitouch` and then reinserting it doesn't address the issue. The only workaround is to close the framework laptop lid to trigger sleep, and then upon resume from sleep a second time it works 100% of the times so far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 8442 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 7 09:27:38 2022 InstallationDate: Installed on 2022-03-11 (209 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (161 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family:
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Yes, with kernel number 4, if I unload the kernel module it suspends and resumes fine. I attach the DMESG log of the successful suspend/resume without cm32181. ** Attachment added: "kernel_lp1988346-4_dmesg_unload_successful_suspend" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988346/+attachment/5621970/+files/kernel_lp1988346-4_dmesg_unload_successful_suspend -- 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
[Kernel-packages] [Bug 1991934] Re: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic
Tracking in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995357 ** Bug watch added: Debian Bug tracker #995357 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995357 ** Package changed: linux (Ubuntu) => pipewire (Ubuntu) ** Changed in: pipewire (Ubuntu) Status: Incomplete => Confirmed ** Also affects: pipewire (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995357 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991934 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic Status in pipewire package in Ubuntu: Confirmed Status in pipewire package in Debian: Unknown Bug description: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1991934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Unassign myself as it's unlikely to get fixed in X-4.4, which is an ESM
kernel now.
Issue still exist with kvm-unit-test repo updated to d8a4f9e5 (ci:
Update the list of tests that we run in the Fedora Cirrus-CI)
** Changed in: ubuntu-kernel-tests
Status: In Progress => Confirmed
** Changed in: ubuntu-kernel-tests
Assignee: Po-Hsu Lin (cypressyew) => (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/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
I didn't see any other patch that claims to be a fix of this one in
the upstream tree. The problem I think of for the moment is that we
[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
More data points since bug 1992126 was reported: PASS 5.19.0-15-generic PASS 5.19.0-16-generic 5.19.0-17-generic FAIL 5.19.0-18-generic FAIL 5.19.0-19-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/1991704 Title: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Confirmed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: intel_pmc_core not load on Raptor Lake
Verified linux-oem-6.0/jammy-proposed version 6.0.0-1005.5 on Intel RPL-S RVP. ** Tags added: verification-done-jammy -- 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/1988461 Title: intel_pmc_core not load on Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid 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 1988346] Re: cm32181 module error blocking suspend
This is very weird. The suspend function of cm32181 shouldn't be called on your laptop. Does removing cm32181 before suspend help? -- 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.
[Kernel-packages] [Bug 1991934] Re: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic
Is this causing any actual problems like non-working audio? (bug 1992101) ** Tags added: kinetic -- 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/1991934 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic Status in linux package in Ubuntu: Incomplete Bug description: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992126] Re: Kernel Oops: kernel NULL pointer dereference; RIP is at 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915]
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 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 1991704, 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. ** This bug has been marked a duplicate of bug 1991704 New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen -- 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/1992126 Title: Kernel Oops: kernel NULL pointer dereference; RIP is at 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915] Status in linux package in Ubuntu: Confirmed Bug description: `linux-image-5.19.0-16-generic` looks fine; === [1.699774] i915 :00:02.0: [drm] VT-d active for gfx access [1.699828] Console: switching to colour dummy device 80x25 [1.699851] i915 :00:02.0: vgaarb: deactivate vga console [1.699884] i915 :00:02.0: [drm] Transparent Hugepage mode 'huge=within_size' [1.699966] BUG: kernel NULL pointer dereference, address: 002e [1.699969] #PF: supervisor write access in kernel mode [1.699971] #PF: error_code(0x0002) - not-present page [1.699972] PGD 0 P4D 0 [1.699974] Oops: 0002 [#1] PREEMPT SMP NOPTI [1.699976] CPU: 0 PID: 324 Comm: systemd-udevd Not tainted 5.19.0-19-generic #19-Ubuntu [1.699978] Hardware name: LENOVO 82TF/LNVNB161216, BIOS JYCN39WW 06/16/2022 [1.699980] RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915] [1.700052] Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff 46 2e 00 66 41 89 85 e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08 [1.700054] RSP: 0018:b92181fe7860 EFLAGS: 00010202 [1.700056] RAX: 0304 RBX: 0003 RCX: 0004 [1.700057] RDX: RSI: RDI: 0001 [1.700058] RBP: b92181fe7950 R08: R09: [1.700059] R10: 0004 R11: 0004 R12: 0080 [1.700061] R13: 9d3a9d8f80f0 R14: 0005 R15: 9d3a9d8f8000 [1.700062] FS: 7f4c6b69e8c0() GS:9d3dff60() knlGS: [1.700064] CS: 0010 DS: ES: CR0: 80050033 [1.700065] CR2: 002e CR3: 000119dce001 CR4: 00770ef0 [1.700066] PKRU: 5554 [1.700067] Call Trace: [1.700068] [1.700070] ? __intel_wait_for_register_fw+0xf5/0x200 [i915] [1.700123] intel_bw_init_hw+0xf3/0x140 [i915] [1.700184] i915_driver_hw_probe+0x2cc/0x370 [i915] [1.700229] i915_driver_probe+0x19b/0x490 [i915] [1.700267] ? drm_privacy_screen_get+0x16d/0x190 [drm] [1.700294] ? acpi_dev_found+0x64/0x80 [1.700299] i915_pci_probe+0x56/0x150 [i915] [1.700339] local_pci_probe+0x44/0x90 [1.700342] pci_call_probe+0x55/0x190 [1.700343] pci_device_probe+0x84/0x120 [1.700345] really_probe+0x1dc/0x3b0 [1.700348] __driver_probe_device+0x12c/0x1b0 [1.700349] driver_probe_device+0x24/0xd0 [1.700351] __driver_attach+0xe0/0x210 [1.700353] ? __device_attach_driver+0x130/0x130 [1.700355] bus_for_each_dev+0x8d/0xe0 [1.700356] driver_attach+0x1e/0x30 [1.700358] bus_add_driver+0x187/0x230 [1.700360] driver_register+0x8f/0x100 [1.700361] __pci_register_driver+0x62/0x70 [1.700363] i915_pci_register_driver+0x23/0x30 [i915] [1.700400] i915_init+0x3b/0xf2 [i915] [1.700449] ? 0xc0877000 [1.700451] do_one_initcall+0x5b/0x240 [1.700454] do_init_module+0x50/0x210 [1.700456] load_module+0xb7d/0xcd0 [1.700459] __do_sys_finit_module+0xc4/0x140 [1.700460] ? __do_sys_finit_module+0xc4/0x140 [1.700462] __x64_sys_finit_module+0x18/0x30 [1.700464] do_syscall_64+0x58/0x90 [1.700466] entry_SYSCALL_64_after_hwframe+0x63/0xcd [1.700469] RIP: 0033:0x7f4c6bd7ea1d [1.700470] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 f3 0d 00 f7 d8 64 89 01 48 [1.700473] RSP: 002b:7fff8a8b9a88 EFLAGS: 0246 ORIG_RAX: 0139 [1.700475] RAX: ffda RBX: 55649dea3290 RCX: 7f4c6bd7ea1d [1.700476] RDX: RSI: 7f4c6bf00458 RDI:
[Kernel-packages] [Bug 1991779] Re: [HP ProBook 450 G3] Touchpad not being detected
** Summary changed: - Touchpad not being detected + [HP ProBook 450 G3] Touchpad not being detected -- 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/1991779 Title: [HP ProBook 450 G3] Touchpad not being detected Status in linux package in Ubuntu: Confirmed Bug description: Details as mentioned here - https://wiki.ubuntu.com/DebuggingTouchpadDetection Laptop model - HP ProBook 450 G3 Touchpad manufacturer - Synaptics Seeing issue since - Not sure, a few months My touchpad started malfunctioning (pointer moving by itself). To be able to finish my work, I had disabled my touchpad temporarily using "xinput disable https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991902] Re: video runs at few frames per second
** Package changed: linux (Ubuntu) => cheese (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991902 Title: video runs at few frames per second Status in cheese package in Ubuntu: Confirmed Bug description: I have problems with cheese, so i enter command 'ubuntu-bug cheese' cheese start but ubuntu-bug creates a bug for 'linux' package ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Oct 6 09:53:32 2022 InstallationDate: Installed on 2022-04-22 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. H87M-D3H RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH87M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1763 F pulseaudio /dev/snd/controlC2: corrado1763 F pulseaudio /dev/snd/controlC1: corrado1763 F pulseaudio CRDA: N/A CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-22 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. H87M-D3H Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=85954416-b528-4791-b519-18e9a1b7b145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie _MarkForUpload: True dmi.bios.date: 04/24/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH87M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
By default, we expect (many of us using Linux laptops/desktops) that we get a GUI. Now it fails to initialize graphics properly. For now the system is only usable through ssh as I don't even get text console locally. The 'nosplash' ultimately will change nothing or very little. -- 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/1991704 Title: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Confirmed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
It was reported internally that following patch series fixed this issue:
87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump
collection
140424d90165 net: wwan: t7xx: PCIe reset rescan
007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
d20ef656f994 net: wwan: t7xx: Add AP CLDMA
However, they were then reverted in netdev-next in commit bf294c3feafe
("Revert "Merge branch 'wwan-t7xx-fw-flashing-and-coredump-support'""),
so we're still waiting for the updates from chip vendor.
--
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/1990700
Title:
Fibocom WWAN FM350-GL suspend error (notebook not suspend)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hi,
I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module
mtk_t7xx . Power management for this modem is bad. When the notebook goes to
sleep/suspend, kernel module mtk_t7xx return an error:
mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20
[mtk_t7xx] returns -110
mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0
returns -110
mtk_t7xx :58:00.0: PM: failed to suspend async: error -110
So power management failed to suspend:
PM: Some devices failed to suspend, or early wake event detected
And the notebook not suspend and wake up again.
It must be this module, because if I remove the module first (modprobe -r),
the laptop goes to sleep and wakes up normally.
However, after reinserting the module, the modem no longer appears in the
system.
Expected state: sleep occurs when the device is put to sleep -
including the modem. When you wake up, you will wake up, including
activating the modem and logging into the operator's network.
Description:Ubuntu 20.04.5 LTS
Release:20.04
lspci -v:
58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
Subsystem: Device 1cf8:3500
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at 601e80 (64-bit, prefetchable) [size=32K]
Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
Memory at 601e00 (64-bit, prefetchable) [size=8M]
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1
Len=008
Capabilities: [108] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [200] Advanced Error Reporting
Capabilities: [300] Secondary PCI Express
Kernel driver in use: mtk_t7xx
Kernel modules: mtk_t7xx
lshw:
*-generic
description: Wireless controller
product: MEDIATEK Corp.
vendor: MEDIATEK Corp.
physical id: 0
bus info: pci@:58:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pciexpress msix msi pm bus_master cap_list
configuration: driver=mtk_t7xx latency=0
resources: iomemory:600-5ff iomemory:600-5ff irq:17
memory:601e80-601e807fff memory:5e80-5eff
memory:601e00-601e7f
modinfo:
modinfo mtk_t7xx
filename:
/lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko
license:GPL
description:MediaTek PCIe 5G WWAN modem T7xx driver
author: MediaTek Inc
srcversion: 5FA53465EA0167231B632D4
alias: pci:v14C3d4D75sv*sd*bc*sc*i*
depends:
retpoline: Y
intree: Y
name: mtk_t7xx
vermagic: 5.19.10-051910-generic SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key:7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45
sig_hashalgo: sha512
signature: 78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F:
36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40:
45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D:
77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D:
9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09:
4D:04:98:59:35:2A:95:D1:9A:B3:53:77:BE:E5:3E:50:51:18:D0:CE:
9A:DB:3B:0E:DA:4D:05:5D:D1:5F:4F:6B:DB:98:47:F3:32:25:D8:AD:
4E:CE:5F:3E:46:76:D9:F4:FA:28:F2:49:B3:3D:D1:5F:74:CF:69:39:
D2:B0:64:3D:41:FB:55:1F:AB:D3:76:65:54:C6:06:6E:F7:01:F2:F7:
[Kernel-packages] [Bug 1992126] 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/1992126 Title: Kernel Oops: kernel NULL pointer dereference; RIP is at 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915] Status in linux package in Ubuntu: Confirmed Bug description: `linux-image-5.19.0-16-generic` looks fine; === [1.699774] i915 :00:02.0: [drm] VT-d active for gfx access [1.699828] Console: switching to colour dummy device 80x25 [1.699851] i915 :00:02.0: vgaarb: deactivate vga console [1.699884] i915 :00:02.0: [drm] Transparent Hugepage mode 'huge=within_size' [1.699966] BUG: kernel NULL pointer dereference, address: 002e [1.699969] #PF: supervisor write access in kernel mode [1.699971] #PF: error_code(0x0002) - not-present page [1.699972] PGD 0 P4D 0 [1.699974] Oops: 0002 [#1] PREEMPT SMP NOPTI [1.699976] CPU: 0 PID: 324 Comm: systemd-udevd Not tainted 5.19.0-19-generic #19-Ubuntu [1.699978] Hardware name: LENOVO 82TF/LNVNB161216, BIOS JYCN39WW 06/16/2022 [1.699980] RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915] [1.700052] Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff 46 2e 00 66 41 89 85 e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08 [1.700054] RSP: 0018:b92181fe7860 EFLAGS: 00010202 [1.700056] RAX: 0304 RBX: 0003 RCX: 0004 [1.700057] RDX: RSI: RDI: 0001 [1.700058] RBP: b92181fe7950 R08: R09: [1.700059] R10: 0004 R11: 0004 R12: 0080 [1.700061] R13: 9d3a9d8f80f0 R14: 0005 R15: 9d3a9d8f8000 [1.700062] FS: 7f4c6b69e8c0() GS:9d3dff60() knlGS: [1.700064] CS: 0010 DS: ES: CR0: 80050033 [1.700065] CR2: 002e CR3: 000119dce001 CR4: 00770ef0 [1.700066] PKRU: 5554 [1.700067] Call Trace: [1.700068] [1.700070] ? __intel_wait_for_register_fw+0xf5/0x200 [i915] [1.700123] intel_bw_init_hw+0xf3/0x140 [i915] [1.700184] i915_driver_hw_probe+0x2cc/0x370 [i915] [1.700229] i915_driver_probe+0x19b/0x490 [i915] [1.700267] ? drm_privacy_screen_get+0x16d/0x190 [drm] [1.700294] ? acpi_dev_found+0x64/0x80 [1.700299] i915_pci_probe+0x56/0x150 [i915] [1.700339] local_pci_probe+0x44/0x90 [1.700342] pci_call_probe+0x55/0x190 [1.700343] pci_device_probe+0x84/0x120 [1.700345] really_probe+0x1dc/0x3b0 [1.700348] __driver_probe_device+0x12c/0x1b0 [1.700349] driver_probe_device+0x24/0xd0 [1.700351] __driver_attach+0xe0/0x210 [1.700353] ? __device_attach_driver+0x130/0x130 [1.700355] bus_for_each_dev+0x8d/0xe0 [1.700356] driver_attach+0x1e/0x30 [1.700358] bus_add_driver+0x187/0x230 [1.700360] driver_register+0x8f/0x100 [1.700361] __pci_register_driver+0x62/0x70 [1.700363] i915_pci_register_driver+0x23/0x30 [i915] [1.700400] i915_init+0x3b/0xf2 [i915] [1.700449] ? 0xc0877000 [1.700451] do_one_initcall+0x5b/0x240 [1.700454] do_init_module+0x50/0x210 [1.700456] load_module+0xb7d/0xcd0 [1.700459] __do_sys_finit_module+0xc4/0x140 [1.700460] ? __do_sys_finit_module+0xc4/0x140 [1.700462] __x64_sys_finit_module+0x18/0x30 [1.700464] do_syscall_64+0x58/0x90 [1.700466] entry_SYSCALL_64_after_hwframe+0x63/0xcd [1.700469] RIP: 0033:0x7f4c6bd7ea1d [1.700470] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 f3 0d 00 f7 d8 64 89 01 48 [1.700473] RSP: 002b:7fff8a8b9a88 EFLAGS: 0246 ORIG_RAX: 0139 [1.700475] RAX: ffda RBX: 55649dea3290 RCX: 7f4c6bd7ea1d [1.700476] RDX: RSI: 7f4c6bf00458 RDI: 0016 [1.700477] RBP: 7f4c6bf00458 R08: R09: 7fff8a8b9bb0 [1.700478] R10: 0016 R11: 0246 R12: 0002 [1.700479] R13: 55649de9b8f0 R14: R15: 55649deabad0 [1.700481] [1.700482] Modules linked in: fjes(-) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops aesni_intel nvme drm crypto_simd xhci_pci cryptd thunderbolt nvme_core xhci_pci_renesas mac_hid wmi video pinctrl_tigerlake [1.700492] CR2: 002e [
