[Kernel-packages] [Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Changed in: mutter Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-495 in Ubuntu. https://bugs.launchpad.net/bugs/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session Status in Mutter: Fix Released Status in OEM Priority Project: Fix Released Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-495 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Bug description: This is on my weird desktop setup, with one monitor plugged into an AMD card and one into an NVIDIA card. When using the Wayland session, by default Shell will come up on the monitor connected to the AMD card, and the second (NVIDIA) monitor will be blank. Attempting to enable the second monitor in Display Settings will immediately and reproducibly crash gnome-shell. This is trivial for me to reproduce, so if you need patches tested I can easily do so. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2 Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 09:37:51 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-11-02 (125 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961738] Re: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15
** Changed in: linux Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961738 Title: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15 Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This seems to happen at boot on all 11th gen Intel systems I've seen. But also on a 10th gen Intel system seen in other bug reports. [1.778960] [1.778964] UBSAN: shift-out-of-bounds in /build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/i915/display/intel_opregion.c:388:15 [1.778967] shift exponent 37 is too large for 32-bit type 'unsigned int' [1.778969] CPU: 5 PID: 374 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.778970] Hardware name: Microsoft Corporation Surface Laptop 4/Surface Laptop 4, BIOS 10.300.141 06/17/2021 [1.778971] Call Trace: [1.778972] [1.778973] show_stack+0x52/0x58 [1.778977] dump_stack_lvl+0x4a/0x5f [1.778979] dump_stack+0x10/0x12 [1.778980] ubsan_epilogue+0x9/0x45 [1.778981] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe9 [1.778983] ? icl_ddi_tc_is_clock_enabled+0x4d/0xc0 [i915] [1.779060] intel_opregion_notify_encoder.cold+0x2b/0x45 [i915] [1.779129] intel_sanitize_encoder+0x1e2/0x270 [i915] [1.779187] intel_modeset_setup_hw_state+0x322/0x680 [i915] [1.779236] ? drm_modeset_lock_all_ctx+0x151/0x1c0 [drm] [1.779253] ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm] [1.779265] intel_modeset_init_nogem+0x2a8/0x510 [i915] [1.779315] ? intel_irq_postinstall+0x38b/0x680 [i915] [1.779358] i915_driver_probe+0x1b7/0x470 [i915] [1.779395] ? mutex_lock+0x13/0x40 [1.779399] i915_pci_probe+0x58/0x140 [i915] [1.779435] local_pci_probe+0x48/0x90 [1.779438] pci_device_probe+0x115/0x1f0 [1.779439] really_probe+0x21b/0x420 [1.779442] __driver_probe_device+0x115/0x190 [1.779444] driver_probe_device+0x23/0xc0 [1.779445] __driver_attach+0xbd/0x1d0 [1.779447] ? __device_attach_driver+0x110/0x110 [1.779448] bus_for_each_dev+0x7c/0xc0 [1.779450] driver_attach+0x1e/0x20 [1.779452] bus_add_driver+0x135/0x200 [1.779453] driver_register+0x95/0xf0 [1.779454] __pci_register_driver+0x68/0x70 [1.779455] i915_register_pci_driver+0x23/0x30 [i915] [1.779488] i915_init+0x3b/0xfc [i915] [1.779534] ? 0xc1229000 [1.779535] do_one_initcall+0x46/0x1d0 [1.779539] ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.779543] do_init_module+0x62/0x280 [1.779545] load_module+0xac9/0xbb0 [1.779546] __do_sys_finit_module+0xbf/0x120 [1.779548] __x64_sys_finit_module+0x18/0x20 [1.779549] do_syscall_64+0x59/0xc0 [1.779551] ? do_syscall_64+0x69/0xc0 [1.779552] ? do_syscall_64+0x69/0xc0 [1.779553] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.779555] RIP: 0033:0x7f0a61a13a3d [1.779557] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 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 c3 53 0f 00 f7 d8 64 89 01 48 [1.779558] RSP: 002b:7ffcfe9e0748 EFLAGS: 0246 ORIG_RAX: 0139 [1.779560] RAX: ffda RBX: 5601776d2090 RCX: 7f0a61a13a3d [1.779561] RDX: RSI: 7f0a61ba8441 RDI: 0017 [1.779561] RBP: 0002 R08: R09: 0002 [1.779562] R10: 0017 R11: 0246 R12: 7f0a61ba8441 [1.779562] R13: 5601776cd450 R14: 5601777f7d60 R15: 5601777f8e30 [1.779564] [1.779564] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1364 F pipewire-media- dan1365 F pulseaudio /dev/snd/seq:dan1363 F pipewire CasperMD5CheckResult: pass CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Tue Feb 22 15:11:13 2022 InstallationDate: Installed on 2022-02-14 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220214) MachineType: Microsoft Corporation Surface Laptop 4 Pr
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: New Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/196
[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"
** Changed in: libinput Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975364] Re: Ubuntu 22.04 very long to resume from suspend to ram
Please notice the files above are captured after a normal-non-bug resume. Maybe you'll want I post new files when the bug rises again. Please let me know -- 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/1975364 Title: Ubuntu 22.04 very long to resume from suspend to ram Status in linux package in Ubuntu: New Bug description: When I want to resume my awaken laptop, then login screen comes up but it is stuck for roughly 1mn as soon as the password field pops up as I hit the Enter key to unlock. The mouse cursor won't move. Key strokes won't echo in the password field although they are buffered in memory: I can say this because if I type my password plus Enter then wait a long time I get my working screen OK. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-30-generic 5.15.0-30.31 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fab1721 F pulseaudio CasperMD5CheckResult: unknown Date: Sat May 21 10:20:33 2022 HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7 InstallationDate: Installed on 2013-07-05 (3241 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux 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-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago) dmi.bios.date: 08/28/2013 dmi.bios.release: 0.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.product.sku: XPS L322X dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975364] [NEW] Ubuntu 22.04 very long to resume from suspend to ram
Public bug reported: When I want to resume my awaken laptop, then login screen comes up but it is stuck for roughly 1mn as soon as the password field pops up as I hit the Enter key to unlock. The mouse cursor won't move. Key strokes won't echo in the password field although they are buffered in memory: I can say this because if I type my password plus Enter then wait a long time I get my working screen OK. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-30-generic 5.15.0-30.31 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fab1721 F pulseaudio CasperMD5CheckResult: unknown Date: Sat May 21 10:20:33 2022 HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7 InstallationDate: Installed on 2013-07-05 (3241 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux 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-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago) dmi.bios.date: 08/28/2013 dmi.bios.release: 0.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.product.sku: XPS L322X dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975364 Title: Ubuntu 22.04 very long to resume from suspend to ram Status in linux package in Ubuntu: New Bug description: When I want to resume my awaken laptop, then login screen comes up but it is stuck for roughly 1mn as soon as the password field pops up as I hit the Enter key to unlock. The mouse cursor won't move. Key strokes won't echo in the password field although they are buffered in memory: I can say this because if I type my password plus Enter then wait a long time I get my working screen OK. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-30-generic 5.15.0-30.31 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fab1721 F pulseaudio CasperMD5CheckResult: unknown Date: Sat May 21 10:20:33 2022 HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7 InstallationDate: Installed on 2013-07-05 (3241 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux 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-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago) dmi.bios.date: 08/28/2013 dmi.bios.release: 0.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvn
[Kernel-packages] [Bug 1975364] 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/1975364 Title: Ubuntu 22.04 very long to resume from suspend to ram Status in linux package in Ubuntu: Confirmed Bug description: When I want to resume my awaken laptop, then login screen comes up but it is stuck for roughly 1mn as soon as the password field pops up as I hit the Enter key to unlock. The mouse cursor won't move. Key strokes won't echo in the password field although they are buffered in memory: I can say this because if I type my password plus Enter then wait a long time I get my working screen OK. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-30-generic 5.15.0-30.31 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fab1721 F pulseaudio CasperMD5CheckResult: unknown Date: Sat May 21 10:20:33 2022 HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7 InstallationDate: Installed on 2013-07-05 (3241 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux 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-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago) dmi.bios.date: 08/28/2013 dmi.bios.release: 0.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.product.sku: XPS L322X dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975366] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.14 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit stat
Public bug reported: At automatic update, the system encountered an error and proposed to report it ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 21 11:46:41 2022 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-06 (135 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.14 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1975366 Title: package zfsutils-linux 0.8.3-1ubuntu12.14 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: At automatic update, the system encountered an error and proposed to report it ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 21 11:46:41 2022 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-06 (135 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.14 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1975366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970965] Re: Wifi randomly disconnects [AR9462]
** Description changed: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter - I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Kernel 5.13.0 without any problem. - When migrated to Ubuntu 22.04 which installs Kernel 5.15.5 then the problems started. + I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Ubuntu Kernel 5.13.0 without any problem. + When migrated to Ubuntu 22.04 which installs Ubuntu Kernel 5.15.0.x (which corresponds to Mainline Kernel 5.15.5) then the problems started. - I upgraded and tested unsuccessfully the following Kernels : 5.15.28, - 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 + I upgraded and tested unsuccessfully the following Mainline Kernels : + 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. - I downgraded and currently running without any problem using the Kernels - 5.13.19-051319-generic or 5.15.0 or 5.15.4 + I downgraded and currently running without any problem using the Ubuntu + Kernels 5.13.19-051319-generic or Mainline Kernels 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. - seems to be something between 5.15.4 and 5.15.5 that is also propagated - to 5.16.x and 5.17.x + seems to be something between Mainline Kernels 5.15.4 and 5.15.5 that is + also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True -- 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/1970965 Title: Wifi randomly disconnects [AR9462] Status in linux package in Ubuntu: Confirmed Bug description: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Ubuntu Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Ubuntu Kernel 5.15.0.x (which corresponds to Mainline Kernel 5.15.5) then the problems started. I upgraded and tested unsuccessfully the following Mainline Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Ubuntu Kernels 5.13.19-051319-generic or Mainline Kernels 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between Mainline Kernels 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bu
[Kernel-packages] [Bug 1970965] Re: Wifi randomly disconnects [AR9462]
** Description changed: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Ubuntu Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Ubuntu Kernel 5.15.0.x (which corresponds to Mainline Kernel 5.15.5) then the problems started. - I upgraded and tested unsuccessfully the following Mainline Kernels : - 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 + + The Mainline Kernel 5.15.4 corresponds to the Ubuntu Kernel 5.15.0-11.11 (date 2021-11-21 13:32:06) + The Mainline Kernel 5.15.5 corresponds to the Ubuntu Kernel 5.15.0-12.12 (date 2021-11-25 09:35:53) + + + I upgraded and tested unsuccessfully the following Mainline Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Ubuntu Kernels 5.13.19-051319-generic or Mainline Kernels 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between Mainline Kernels 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True -- 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/1970965 Title: Wifi randomly disconnects [AR9462] Status in linux package in Ubuntu: Confirmed Bug description: my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462 Wireless Network Adapter I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Ubuntu Kernel 5.13.0 without any problem. When migrated to Ubuntu 22.04 which installs Ubuntu Kernel 5.15.0.x (which corresponds to Mainline Kernel 5.15.5) then the problems started. The Mainline Kernel 5.15.4 corresponds to the Ubuntu Kernel 5.15.0-11.11 (date 2021-11-21 13:32:06) The Mainline Kernel 5.15.5 corresponds to the Ubuntu Kernel 5.15.0-12.12 (date 2021-11-25 09:35:53) I upgraded and tested unsuccessfully the following Mainline Kernels : 5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5 I disabled the power save as explained at https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471 without improvement in any of the Kernels tested. Also the "intel_iommu=off" mentioned at https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ Bug#994590 didn't help. I downgraded and currently running without any problem using the Ubuntu Kernels 5.13.19-051319-generic or Mainline Kernels 5.15.0 or 5.15.4 There is no problem in my airpoint (router) nor my internet access, I have other different computers and devices working correctly on wifi. In addition my N751JK works correctly when using the Ethernet adapter for the physical cable. seems to be something between Mainline Kernels 5.15.4 and 5.15.5 that is also propagated to 5.16.x and 5.17.x (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-21 (432 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: jammy Uname: Linux 5.15.5-051505-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage
[Kernel-packages] [Bug 1975367] [NEW] Weird colours after launching game
Public bug reported: After updating to the latest kernel and drivers today, I rebooted, launched Perfect Heist 2 from Steam and the colours for my entire desktop went quite weird. I exited the game and the colour issues remained the same. Whilst rebooting even the console mode graphics had odd artefacts in them. Relevant lines from dmesg: ``` May 21 10:46:39 polar kernel: [ 766.370050] NVRM: Xid (PCI::01:00): 31, pid=7680, Ch 0020, intr . MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_0 faulted @ 0x1_02805000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ May 21 10:46:50 polar kernel: [ 777.790920] NVRM: Xid (PCI::01:00): 31, pid=7680, Ch 0020, intr . MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_4 faulted @ 0x0_090d. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-510 510.73.05-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 21 11:10:19 2022 InstallationDate: Installed on 2017-05-24 (1823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to focal on 2020-06-28 (692 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1975367 Title: Weird colours after launching game Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: After updating to the latest kernel and drivers today, I rebooted, launched Perfect Heist 2 from Steam and the colours for my entire desktop went quite weird. I exited the game and the colour issues remained the same. Whilst rebooting even the console mode graphics had odd artefacts in them. Relevant lines from dmesg: ``` May 21 10:46:39 polar kernel: [ 766.370050] NVRM: Xid (PCI::01:00): 31, pid=7680, Ch 0020, intr . MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_0 faulted @ 0x1_02805000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ May 21 10:46:50 polar kernel: [ 777.790920] NVRM: Xid (PCI::01:00): 31, pid=7680, Ch 0020, intr . MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_4 faulted @ 0x0_090d. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-510 510.73.05-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 21 11:10:19 2022 InstallationDate: Installed on 2017-05-24 (1823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to focal on 2020-06-28 (692 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1975367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
adding "i915.enable_dc=0 intel_idle.max_cstate=2" doesn't help in my case (kernel 5.15, Intel UHD / i915 graphics) -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973709] Re: Thinkpad T460s won't turn off or resume after upgrade to 22.04
** Summary changed: - laptop won't turn off properly after upgrade to 22.04 + Thinkpad T460s won't turn off or resume after upgrade to 22.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973709 Title: Thinkpad T460s won't turn off or resume after upgrade to 22.04 Status in linux package in Ubuntu: Confirmed Bug description: If I click shutdown it will enter a "limbo" state, where some LEDs are on but it won't react to anything except holding power for a forced shutdown. It will drain the batteries this way. Quite annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue May 17 09:31:34 2022 InstallationDate: Installed on 2020-01-13 (855 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-05-13 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
This bug was fixed in the package mutter - 42.1-1ubuntu1
---
mutter (42.1-1ubuntu1) kinetic; urgency=medium
[ Jeremy Bicha ]
* Merge from Debian unstable. Remaining changes:
- Add triple-buffering patch
- Add x11-Add-support-for-fractional-scaling-using-Randr.patch:
+ X11: Add support for fractional scaling using Randr
- Add ubuntu/wayland-data-device-Allow-any-drag-timestamppatch
+ Allow any drag timestamp as drag start serial
- Add backends-native-kms-crtc-Don-t-compare-gamma-values-on-un.patch
+ Avoid memory errors when comparing gamma values
- Add monitor-manager-Ensure-monitors-settings-after-backend-ha.patch
+ Ensure privacy screen settings are applied on startup
- Add patches from GNOME !2364
+ Fix X11 selection related crash when Xwayland died
- debian/libmutter-10-0.symbols: Add symbols for triple buffering patch
* Refresh triple buffering patch with latest version
[ Marco Trevisan (Treviño) ]
* debian/patches: Adapt expected messages to new domains
mutter (42.1-1) unstable; urgency=medium
* New upstream release
(LP: #1972726, #1967274, #1965557, #1969574, #1948410, #1967219, #1971693)
* Drop patches applied in new release
* debian/libmutter-10-0.symbols: Add new symbol
* debian/libmutter-10-0.symbols: Drop a symbol that was only in experimental
* Add Breaks against old gtk3 & gtk4 versions.
See Ubuntu bug 1972721
* Release to unstable
mutter (42.0-5) experimental; urgency=medium
* Team upload
* d/patches: Update to upstream commit 42.0-74-g6c8e8fbba
- Bug fixes targeted for 42.1
- d/p/clutter-stage-Repick-when-pointer-actor-goes-unmapped.patch:
Replace with the version that was applied upstream
- d/p/core-Account-ClutterStage-grabs-on-Wayland-key-focus-sync.patch:
Mark as applied upstream
mutter (42.0-4) unstable; urgency=medium
* Team upload
* d/patches: Update to upstream commit 42.0-55-gbe9deeba0
- Update translations
- Update upstream status of cherry-picked patches
- Add various bug fixes including LP: #1959888, LP: #1964037
* d/p/core-Account-ClutterStage-grabs-on-Wayland-key-focus-sync.patch:
Add patch proposed upstream to fix grabs vs. system-modal prompts.
This is particularly annoying when using pkexec, or when using gcr as
a passphrase prompt for PGP, ssh and/or sudo.
(Closes: #1008998, LP: #1964442)
-- Jeremy Bicha Fri, 13 May 2022 09:14:41 -0400
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Committed
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpa
[Kernel-packages] [Bug 1975382] [NEW] ubuntu can't identify touchpad
Public bug reported: my touchpad is not working, but mouse is working, ubuntu cants identify touchpad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 21:51:15 2022 InstallationDate: Installed on 2022-01-01 (140 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1975382 Title: ubuntu can't identify touchpad Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: my touchpad is not working, but mouse is working, ubuntu cants identify touchpad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 21:51:15 2022 InstallationDate: Installed on 2022-01-01 (140 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1975382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel"
A fix for this is currently queued in linux-next: commit 1bbc21785b7336619fb6a67f1fff5afdaf229acc Author: Lorenzo Pieralisi Date: Thu Apr 7 11:51:20 2022 +0100 ACPI: sysfs: Fix BERT error region memory mapping My plan is to propose this for stable after it lands during the merge window. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973153 Title: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel" Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy 5.15.0-27-generic with ARM64 node helo-kernel only. It looks like this is hardware-specific. The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and test will timeout. Steps to reproduce this: git clone -b sru git://git.launchpad.net/~canonical-kernel-team/+git/ltp cd ltp make autotools ./configure make sudo make install echo "read_all_sys read_all -d /sys -q -r 3" > /tmp/fs sudo /opt/ltp/runltp -f /tmp/fs Test log: <<>> tag=read_all_sys stime=1652343855 cmdline="read_all -d /sys -q -r 3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s Test timeouted, sending SIGKILL! tst_test.c:1500: TINFO: Killed the leftover descendant processes tst_test.c:1506: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1508: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1800 termination_type=exited termination_id=2 corefile=no cutime=39 cstime=140 <<>> dmesg output: [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3) [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.641990] mpt3sas :8d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 1617.973894] WARNING! power/level is deprecated; use power/control instead [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. Use the stable_writes queue attribute instead. [ 1627.430319] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.438256] Mem abort info: [ 1627.441086] ESR = 0x9621 [ 1627.444133] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.449469] SET = 0, FnV = 0 [ 1627.452515] EA = 0, S1PTW = 0 [ 1627.455676] FSC = 0x21: alignment fault [ 1627.459701] Data abort info: [ 1627.462597] ISV = 0, ISS = 0x0021 [ 1627.466449] CM = 0, WnR = 0 [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000 [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f [ 1627.488712] Internal error: Oops: 9621 [#1] SMP [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm scsi_transport_sas xhci_pci ahci xhci_pci_renesas g
[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
The above is sadly false, a bit better, wifi lasts a bit longer but still fails after a while. -- 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/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Fix Released Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device is unable to scan for networks and error occurs when attempting
[Kernel-packages] [Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970865] Re: Kernel panic on sleep
I also have the same NVidia Hardware ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970865/+attachment/5591845/+files/prevboot.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/1970865 Title: Kernel panic on sleep Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Bug description: When I keep my laptop in sleep (super + L) or close its lid, the moment I open it i see a kernel panic which doesn't end. The only option I would have is to shutdown and lose all my unsaved work. What should I do? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 11:12:41 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:85f4] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:85f4] InstallationDate: Installed on 2022-04-22 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. 802.11ac WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G8 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=6c11dd1c-235a-4eec-87eb-f3b7fbe0add5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 15.53 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85F4 dmi.board.vendor: HP dmi.board.version: 40.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.34 dmi.modalias: dmi:bvnInsyde:bvrF.53:bd10/15/2021:br15.53:efr40.34:svnHP:pnHP250G8NotebookPC:pvrType1ProductConfigId:rvnHP:rn85F4:rvr40.34:cvnHP:ct10:cvrChassisVersion:sku3D3U1PA#ACJ: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G8 Notebook PC dmi.product.sku: 3D3U1PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1972281 Title: ext4: limit length to bitmap_maxbytes Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Abusing ext4_fallocate() (as a normal user) triggers a BUG()/kernel panic. [Fix] Apply this upstream fix: commit 2da376228a2427501feb9d15815a45dbdbdd753e Author: Tadeusz Struk Date: Thu Mar 31 13:05:15 2022 -0700 ext4: limit length to bitmap_maxbytes - blocksize in punch_hole [Test] The reporter has provided a working reproducer. [Where problems could occur] Upstream fix already slated for @stable inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975394] [NEW] iwlwifi sometimes failes to initialze on Z690
Public bug reported: Hello, Sometimes, about every 10 boot, the iwlwifi driver fails to initialize the hardware and WiFi connectivity is not available. dmesg from failed boot: [4.316757] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.400950] iwlwifi :00:14.3: CSR_RESET = 0x10 [4.400956] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [4.400987] iwlwifi :00:14.3: value [iter 0]: 0x3f1d0430 [4.400990] iwlwifi :00:14.3: value [iter 1]: 0x3f1d0030 [4.401011] iwlwifi :00:14.3: value [iter 2]: 0x3f1d0430 [4.401014] iwlwifi :00:14.3: value [iter 3]: 0x3f1d0430 [4.401036] iwlwifi :00:14.3: value [iter 4]: 0x3f1d0030 [4.401038] iwlwifi :00:14.3: value [iter 5]: 0x3f1d0430 [4.401061] iwlwifi :00:14.3: value [iter 6]: 0x3f1d0030 [4.401064] iwlwifi :00:14.3: value [iter 7]: 0x3f1d0030 [4.401086] iwlwifi :00:14.3: value [iter 8]: 0x3f1d0030 [4.401088] iwlwifi :00:14.3: value [iter 9]: 0x3f1d0030 [4.401110] iwlwifi :00:14.3: value [iter 10]: 0x3f1d0430 [4.401114] iwlwifi :00:14.3: value [iter 11]: 0x3f1d0030 [4.401137] iwlwifi :00:14.3: value [iter 12]: 0x3f1d0430 [4.401140] iwlwifi :00:14.3: value [iter 13]: 0x3f1d0430 [4.401161] iwlwifi :00:14.3: value [iter 14]: 0x3f1d0430 [4.401162] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [4.401165] iwlwifi :00:14.3: value [iter 0]: 0x040066c2 [4.401186] iwlwifi :00:14.3: value [iter 1]: 0x040066c2 [4.401189] iwlwifi :00:14.3: value [iter 2]: 0x040066c2 [4.401211] iwlwifi :00:14.3: value [iter 3]: 0x040066c2 [4.401214] iwlwifi :00:14.3: value [iter 4]: 0x040066c2 [4.401235] iwlwifi :00:14.3: value [iter 5]: 0x040066c2 [4.401238] iwlwifi :00:14.3: value [iter 6]: 0x040066c2 [4.401261] iwlwifi :00:14.3: value [iter 7]: 0x040066c2 [4.401263] iwlwifi :00:14.3: value [iter 8]: 0x040066c2 [4.401266] iwlwifi :00:14.3: value [iter 9]: 0x040066c2 [4.401287] iwlwifi :00:14.3: value [iter 10]: 0x040066c2 [4.401290] iwlwifi :00:14.3: value [iter 11]: 0x040066c2 [4.401312] iwlwifi :00:14.3: value [iter 12]: 0x040066c2 [4.401315] iwlwifi :00:14.3: value [iter 13]: 0x040066c2 [4.401336] iwlwifi :00:14.3: value [iter 14]: 0x040066c2 [4.401338] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [4.401341] iwlwifi :00:14.3: value [iter 0]: 0xe00c7c75 [4.401362] iwlwifi :00:14.3: value [iter 1]: 0xa00c7c75 [4.401365] iwlwifi :00:14.3: value [iter 2]: 0xa00c7c75 [4.401387] iwlwifi :00:14.3: value [iter 3]: 0xa00c7c75 [4.401390] iwlwifi :00:14.3: value [iter 4]: 0xa00c7c75 [4.401412] iwlwifi :00:14.3: value [iter 5]: 0xb00c7c75 [4.401414] iwlwifi :00:14.3: value [iter 6]: 0xb00c7c75 [4.401437] iwlwifi :00:14.3: value [iter 7]: 0xb00c7c75 [4.401439] iwlwifi :00:14.3: value [iter 8]: 0xb00c7c75 [4.401461] iwlwifi :00:14.3: value [iter 9]: 0xa00c7c75 [4.401463] iwlwifi :00:14.3: value [iter 10]: 0xb00c7c75 [4.401486] iwlwifi :00:14.3: value [iter 11]: 0xa00c7c75 [4.401489] iwlwifi :00:14.3: value [iter 12]: 0xa00c7c75 [4.401510] iwlwifi :00:14.3: value [iter 13]: 0xa00c7c75 [4.401513] iwlwifi :00:14.3: value [iter 14]: 0xa00c7c75 [4.401514] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [4.401535] iwlwifi :00:14.3: value [iter 0]: 0x99cec019 [4.401643] iwlwifi: probe of :00:14.3 failed with error -110 dmesg from good boot: [4.316245] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.328750] iwlwifi :00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-69.ucode failed with error -2 [4.329975] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [4.329995] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [4.330436] iwlwifi :00:14.3: loaded firmware version 68.01d30b0c.0 so-a0-gf-a0-68.ucode op_mode iwlmvm lspci output: 00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11) 00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11) 00:14.3 Network controller: Intel Corporation Device 7af0 (rev 11) 00:16.0 Communication controller: Intel Corporation Devi
[Kernel-packages] [Bug 1975394] Re: iwlwifi sometimes failes to initialze on Z690
** Attachment added: "failed_wifi_dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975394/+attachment/5591876/+files/failed_wifi_dmesg.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/1975394 Title: iwlwifi sometimes failes to initialze on Z690 Status in linux package in Ubuntu: New Bug description: Hello, Sometimes, about every 10 boot, the iwlwifi driver fails to initialize the hardware and WiFi connectivity is not available. dmesg from failed boot: [4.316757] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.400950] iwlwifi :00:14.3: CSR_RESET = 0x10 [4.400956] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [4.400987] iwlwifi :00:14.3: value [iter 0]: 0x3f1d0430 [4.400990] iwlwifi :00:14.3: value [iter 1]: 0x3f1d0030 [4.401011] iwlwifi :00:14.3: value [iter 2]: 0x3f1d0430 [4.401014] iwlwifi :00:14.3: value [iter 3]: 0x3f1d0430 [4.401036] iwlwifi :00:14.3: value [iter 4]: 0x3f1d0030 [4.401038] iwlwifi :00:14.3: value [iter 5]: 0x3f1d0430 [4.401061] iwlwifi :00:14.3: value [iter 6]: 0x3f1d0030 [4.401064] iwlwifi :00:14.3: value [iter 7]: 0x3f1d0030 [4.401086] iwlwifi :00:14.3: value [iter 8]: 0x3f1d0030 [4.401088] iwlwifi :00:14.3: value [iter 9]: 0x3f1d0030 [4.401110] iwlwifi :00:14.3: value [iter 10]: 0x3f1d0430 [4.401114] iwlwifi :00:14.3: value [iter 11]: 0x3f1d0030 [4.401137] iwlwifi :00:14.3: value [iter 12]: 0x3f1d0430 [4.401140] iwlwifi :00:14.3: value [iter 13]: 0x3f1d0430 [4.401161] iwlwifi :00:14.3: value [iter 14]: 0x3f1d0430 [4.401162] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [4.401165] iwlwifi :00:14.3: value [iter 0]: 0x040066c2 [4.401186] iwlwifi :00:14.3: value [iter 1]: 0x040066c2 [4.401189] iwlwifi :00:14.3: value [iter 2]: 0x040066c2 [4.401211] iwlwifi :00:14.3: value [iter 3]: 0x040066c2 [4.401214] iwlwifi :00:14.3: value [iter 4]: 0x040066c2 [4.401235] iwlwifi :00:14.3: value [iter 5]: 0x040066c2 [4.401238] iwlwifi :00:14.3: value [iter 6]: 0x040066c2 [4.401261] iwlwifi :00:14.3: value [iter 7]: 0x040066c2 [4.401263] iwlwifi :00:14.3: value [iter 8]: 0x040066c2 [4.401266] iwlwifi :00:14.3: value [iter 9]: 0x040066c2 [4.401287] iwlwifi :00:14.3: value [iter 10]: 0x040066c2 [4.401290] iwlwifi :00:14.3: value [iter 11]: 0x040066c2 [4.401312] iwlwifi :00:14.3: value [iter 12]: 0x040066c2 [4.401315] iwlwifi :00:14.3: value [iter 13]: 0x040066c2 [4.401336] iwlwifi :00:14.3: value [iter 14]: 0x040066c2 [4.401338] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [4.401341] iwlwifi :00:14.3: value [iter 0]: 0xe00c7c75 [4.401362] iwlwifi :00:14.3: value [iter 1]: 0xa00c7c75 [4.401365] iwlwifi :00:14.3: value [iter 2]: 0xa00c7c75 [4.401387] iwlwifi :00:14.3: value [iter 3]: 0xa00c7c75 [4.401390] iwlwifi :00:14.3: value [iter 4]: 0xa00c7c75 [4.401412] iwlwifi :00:14.3: value [iter 5]: 0xb00c7c75 [4.401414] iwlwifi :00:14.3: value [iter 6]: 0xb00c7c75 [4.401437] iwlwifi :00:14.3: value [iter 7]: 0xb00c7c75 [4.401439] iwlwifi :00:14.3: value [iter 8]: 0xb00c7c75 [4.401461] iwlwifi :00:14.3: value [iter 9]: 0xa00c7c75 [4.401463] iwlwifi :00:14.3: value [iter 10]: 0xb00c7c75 [4.401486] iwlwifi :00:14.3: value [iter 11]: 0xa00c7c75 [4.401489] iwlwifi :00:14.3: value [iter 12]: 0xa00c7c75 [4.401510] iwlwifi :00:14.3: value [iter 13]: 0xa00c7c75 [4.401513] iwlwifi :00:14.3: value [iter 14]: 0xa00c7c75 [4.401514] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [4.401535] iwlwifi :00:14.3: value [iter 0]: 0x99cec019 [4.401643] iwlwifi: probe of :00:14.3 failed with error -110 dmesg from good boot: [4.316245] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.328750] iwlwifi :00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-69.ucode failed with error -2 [4.329975] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [4.329995] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [4.330436] iwlwifi :00:14.3: loaded firmware version 68.01d30b0c.0 so-a0-gf-a0-68.ucode op_mode iwlmvm lspci output: 00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0
[Kernel-packages] [Bug 1975394] Re: iwlwifi sometimes failes to initialze on Z690
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975394/+attachment/5591878/+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/1975394 Title: iwlwifi sometimes failes to initialze on Z690 Status in linux package in Ubuntu: New Bug description: Hello, Sometimes, about every 10 boot, the iwlwifi driver fails to initialize the hardware and WiFi connectivity is not available. dmesg from failed boot: [4.316757] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.400950] iwlwifi :00:14.3: CSR_RESET = 0x10 [4.400956] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [4.400987] iwlwifi :00:14.3: value [iter 0]: 0x3f1d0430 [4.400990] iwlwifi :00:14.3: value [iter 1]: 0x3f1d0030 [4.401011] iwlwifi :00:14.3: value [iter 2]: 0x3f1d0430 [4.401014] iwlwifi :00:14.3: value [iter 3]: 0x3f1d0430 [4.401036] iwlwifi :00:14.3: value [iter 4]: 0x3f1d0030 [4.401038] iwlwifi :00:14.3: value [iter 5]: 0x3f1d0430 [4.401061] iwlwifi :00:14.3: value [iter 6]: 0x3f1d0030 [4.401064] iwlwifi :00:14.3: value [iter 7]: 0x3f1d0030 [4.401086] iwlwifi :00:14.3: value [iter 8]: 0x3f1d0030 [4.401088] iwlwifi :00:14.3: value [iter 9]: 0x3f1d0030 [4.401110] iwlwifi :00:14.3: value [iter 10]: 0x3f1d0430 [4.401114] iwlwifi :00:14.3: value [iter 11]: 0x3f1d0030 [4.401137] iwlwifi :00:14.3: value [iter 12]: 0x3f1d0430 [4.401140] iwlwifi :00:14.3: value [iter 13]: 0x3f1d0430 [4.401161] iwlwifi :00:14.3: value [iter 14]: 0x3f1d0430 [4.401162] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [4.401165] iwlwifi :00:14.3: value [iter 0]: 0x040066c2 [4.401186] iwlwifi :00:14.3: value [iter 1]: 0x040066c2 [4.401189] iwlwifi :00:14.3: value [iter 2]: 0x040066c2 [4.401211] iwlwifi :00:14.3: value [iter 3]: 0x040066c2 [4.401214] iwlwifi :00:14.3: value [iter 4]: 0x040066c2 [4.401235] iwlwifi :00:14.3: value [iter 5]: 0x040066c2 [4.401238] iwlwifi :00:14.3: value [iter 6]: 0x040066c2 [4.401261] iwlwifi :00:14.3: value [iter 7]: 0x040066c2 [4.401263] iwlwifi :00:14.3: value [iter 8]: 0x040066c2 [4.401266] iwlwifi :00:14.3: value [iter 9]: 0x040066c2 [4.401287] iwlwifi :00:14.3: value [iter 10]: 0x040066c2 [4.401290] iwlwifi :00:14.3: value [iter 11]: 0x040066c2 [4.401312] iwlwifi :00:14.3: value [iter 12]: 0x040066c2 [4.401315] iwlwifi :00:14.3: value [iter 13]: 0x040066c2 [4.401336] iwlwifi :00:14.3: value [iter 14]: 0x040066c2 [4.401338] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [4.401341] iwlwifi :00:14.3: value [iter 0]: 0xe00c7c75 [4.401362] iwlwifi :00:14.3: value [iter 1]: 0xa00c7c75 [4.401365] iwlwifi :00:14.3: value [iter 2]: 0xa00c7c75 [4.401387] iwlwifi :00:14.3: value [iter 3]: 0xa00c7c75 [4.401390] iwlwifi :00:14.3: value [iter 4]: 0xa00c7c75 [4.401412] iwlwifi :00:14.3: value [iter 5]: 0xb00c7c75 [4.401414] iwlwifi :00:14.3: value [iter 6]: 0xb00c7c75 [4.401437] iwlwifi :00:14.3: value [iter 7]: 0xb00c7c75 [4.401439] iwlwifi :00:14.3: value [iter 8]: 0xb00c7c75 [4.401461] iwlwifi :00:14.3: value [iter 9]: 0xa00c7c75 [4.401463] iwlwifi :00:14.3: value [iter 10]: 0xb00c7c75 [4.401486] iwlwifi :00:14.3: value [iter 11]: 0xa00c7c75 [4.401489] iwlwifi :00:14.3: value [iter 12]: 0xa00c7c75 [4.401510] iwlwifi :00:14.3: value [iter 13]: 0xa00c7c75 [4.401513] iwlwifi :00:14.3: value [iter 14]: 0xa00c7c75 [4.401514] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [4.401535] iwlwifi :00:14.3: value [iter 0]: 0x99cec019 [4.401643] iwlwifi: probe of :00:14.3 failed with error -110 dmesg from good boot: [4.316245] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.328750] iwlwifi :00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-69.ucode failed with error -2 [4.329975] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [4.329995] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [4.330436] iwlwifi :00:14.3: loaded firmware version 68.01d30b0c.0 so-a0-gf-a0-68.ucode op_mode iwlmvm lspci output: 00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) 00:06.0 PCI bridge:
[Kernel-packages] [Bug 1975394] Re: iwlwifi sometimes failes to initialze on Z690
** Attachment added: "worked_wifi_dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975394/+attachment/5591877/+files/worked_wifi_dmesg.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/1975394 Title: iwlwifi sometimes failes to initialze on Z690 Status in linux package in Ubuntu: New Bug description: Hello, Sometimes, about every 10 boot, the iwlwifi driver fails to initialize the hardware and WiFi connectivity is not available. dmesg from failed boot: [4.316757] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.400950] iwlwifi :00:14.3: CSR_RESET = 0x10 [4.400956] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [4.400987] iwlwifi :00:14.3: value [iter 0]: 0x3f1d0430 [4.400990] iwlwifi :00:14.3: value [iter 1]: 0x3f1d0030 [4.401011] iwlwifi :00:14.3: value [iter 2]: 0x3f1d0430 [4.401014] iwlwifi :00:14.3: value [iter 3]: 0x3f1d0430 [4.401036] iwlwifi :00:14.3: value [iter 4]: 0x3f1d0030 [4.401038] iwlwifi :00:14.3: value [iter 5]: 0x3f1d0430 [4.401061] iwlwifi :00:14.3: value [iter 6]: 0x3f1d0030 [4.401064] iwlwifi :00:14.3: value [iter 7]: 0x3f1d0030 [4.401086] iwlwifi :00:14.3: value [iter 8]: 0x3f1d0030 [4.401088] iwlwifi :00:14.3: value [iter 9]: 0x3f1d0030 [4.401110] iwlwifi :00:14.3: value [iter 10]: 0x3f1d0430 [4.401114] iwlwifi :00:14.3: value [iter 11]: 0x3f1d0030 [4.401137] iwlwifi :00:14.3: value [iter 12]: 0x3f1d0430 [4.401140] iwlwifi :00:14.3: value [iter 13]: 0x3f1d0430 [4.401161] iwlwifi :00:14.3: value [iter 14]: 0x3f1d0430 [4.401162] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [4.401165] iwlwifi :00:14.3: value [iter 0]: 0x040066c2 [4.401186] iwlwifi :00:14.3: value [iter 1]: 0x040066c2 [4.401189] iwlwifi :00:14.3: value [iter 2]: 0x040066c2 [4.401211] iwlwifi :00:14.3: value [iter 3]: 0x040066c2 [4.401214] iwlwifi :00:14.3: value [iter 4]: 0x040066c2 [4.401235] iwlwifi :00:14.3: value [iter 5]: 0x040066c2 [4.401238] iwlwifi :00:14.3: value [iter 6]: 0x040066c2 [4.401261] iwlwifi :00:14.3: value [iter 7]: 0x040066c2 [4.401263] iwlwifi :00:14.3: value [iter 8]: 0x040066c2 [4.401266] iwlwifi :00:14.3: value [iter 9]: 0x040066c2 [4.401287] iwlwifi :00:14.3: value [iter 10]: 0x040066c2 [4.401290] iwlwifi :00:14.3: value [iter 11]: 0x040066c2 [4.401312] iwlwifi :00:14.3: value [iter 12]: 0x040066c2 [4.401315] iwlwifi :00:14.3: value [iter 13]: 0x040066c2 [4.401336] iwlwifi :00:14.3: value [iter 14]: 0x040066c2 [4.401338] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [4.401341] iwlwifi :00:14.3: value [iter 0]: 0xe00c7c75 [4.401362] iwlwifi :00:14.3: value [iter 1]: 0xa00c7c75 [4.401365] iwlwifi :00:14.3: value [iter 2]: 0xa00c7c75 [4.401387] iwlwifi :00:14.3: value [iter 3]: 0xa00c7c75 [4.401390] iwlwifi :00:14.3: value [iter 4]: 0xa00c7c75 [4.401412] iwlwifi :00:14.3: value [iter 5]: 0xb00c7c75 [4.401414] iwlwifi :00:14.3: value [iter 6]: 0xb00c7c75 [4.401437] iwlwifi :00:14.3: value [iter 7]: 0xb00c7c75 [4.401439] iwlwifi :00:14.3: value [iter 8]: 0xb00c7c75 [4.401461] iwlwifi :00:14.3: value [iter 9]: 0xa00c7c75 [4.401463] iwlwifi :00:14.3: value [iter 10]: 0xb00c7c75 [4.401486] iwlwifi :00:14.3: value [iter 11]: 0xa00c7c75 [4.401489] iwlwifi :00:14.3: value [iter 12]: 0xa00c7c75 [4.401510] iwlwifi :00:14.3: value [iter 13]: 0xa00c7c75 [4.401513] iwlwifi :00:14.3: value [iter 14]: 0xa00c7c75 [4.401514] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [4.401535] iwlwifi :00:14.3: value [iter 0]: 0x99cec019 [4.401643] iwlwifi: probe of :00:14.3 failed with error -110 dmesg from good boot: [4.316245] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.328750] iwlwifi :00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-69.ucode failed with error -2 [4.329975] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [4.329995] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [4.330436] iwlwifi :00:14.3: loaded firmware version 68.01d30b0c.0 so-a0-gf-a0-68.ucode op_mode iwlmvm lspci output: 00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0
[Kernel-packages] [Bug 1975394] 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/1975394 Title: iwlwifi sometimes failes to initialze on Z690 Status in linux package in Ubuntu: Confirmed Bug description: Hello, Sometimes, about every 10 boot, the iwlwifi driver fails to initialize the hardware and WiFi connectivity is not available. dmesg from failed boot: [4.316757] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.400950] iwlwifi :00:14.3: CSR_RESET = 0x10 [4.400956] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x0 [4.400987] iwlwifi :00:14.3: value [iter 0]: 0x3f1d0430 [4.400990] iwlwifi :00:14.3: value [iter 1]: 0x3f1d0030 [4.401011] iwlwifi :00:14.3: value [iter 2]: 0x3f1d0430 [4.401014] iwlwifi :00:14.3: value [iter 3]: 0x3f1d0430 [4.401036] iwlwifi :00:14.3: value [iter 4]: 0x3f1d0030 [4.401038] iwlwifi :00:14.3: value [iter 5]: 0x3f1d0430 [4.401061] iwlwifi :00:14.3: value [iter 6]: 0x3f1d0030 [4.401064] iwlwifi :00:14.3: value [iter 7]: 0x3f1d0030 [4.401086] iwlwifi :00:14.3: value [iter 8]: 0x3f1d0030 [4.401088] iwlwifi :00:14.3: value [iter 9]: 0x3f1d0030 [4.401110] iwlwifi :00:14.3: value [iter 10]: 0x3f1d0430 [4.401114] iwlwifi :00:14.3: value [iter 11]: 0x3f1d0030 [4.401137] iwlwifi :00:14.3: value [iter 12]: 0x3f1d0430 [4.401140] iwlwifi :00:14.3: value [iter 13]: 0x3f1d0430 [4.401161] iwlwifi :00:14.3: value [iter 14]: 0x3f1d0430 [4.401162] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x1 [4.401165] iwlwifi :00:14.3: value [iter 0]: 0x040066c2 [4.401186] iwlwifi :00:14.3: value [iter 1]: 0x040066c2 [4.401189] iwlwifi :00:14.3: value [iter 2]: 0x040066c2 [4.401211] iwlwifi :00:14.3: value [iter 3]: 0x040066c2 [4.401214] iwlwifi :00:14.3: value [iter 4]: 0x040066c2 [4.401235] iwlwifi :00:14.3: value [iter 5]: 0x040066c2 [4.401238] iwlwifi :00:14.3: value [iter 6]: 0x040066c2 [4.401261] iwlwifi :00:14.3: value [iter 7]: 0x040066c2 [4.401263] iwlwifi :00:14.3: value [iter 8]: 0x040066c2 [4.401266] iwlwifi :00:14.3: value [iter 9]: 0x040066c2 [4.401287] iwlwifi :00:14.3: value [iter 10]: 0x040066c2 [4.401290] iwlwifi :00:14.3: value [iter 11]: 0x040066c2 [4.401312] iwlwifi :00:14.3: value [iter 12]: 0x040066c2 [4.401315] iwlwifi :00:14.3: value [iter 13]: 0x040066c2 [4.401336] iwlwifi :00:14.3: value [iter 14]: 0x040066c2 [4.401338] iwlwifi :00:14.3: Host monitor block 0x0 vector 0x6 [4.401341] iwlwifi :00:14.3: value [iter 0]: 0xe00c7c75 [4.401362] iwlwifi :00:14.3: value [iter 1]: 0xa00c7c75 [4.401365] iwlwifi :00:14.3: value [iter 2]: 0xa00c7c75 [4.401387] iwlwifi :00:14.3: value [iter 3]: 0xa00c7c75 [4.401390] iwlwifi :00:14.3: value [iter 4]: 0xa00c7c75 [4.401412] iwlwifi :00:14.3: value [iter 5]: 0xb00c7c75 [4.401414] iwlwifi :00:14.3: value [iter 6]: 0xb00c7c75 [4.401437] iwlwifi :00:14.3: value [iter 7]: 0xb00c7c75 [4.401439] iwlwifi :00:14.3: value [iter 8]: 0xb00c7c75 [4.401461] iwlwifi :00:14.3: value [iter 9]: 0xa00c7c75 [4.401463] iwlwifi :00:14.3: value [iter 10]: 0xb00c7c75 [4.401486] iwlwifi :00:14.3: value [iter 11]: 0xa00c7c75 [4.401489] iwlwifi :00:14.3: value [iter 12]: 0xa00c7c75 [4.401510] iwlwifi :00:14.3: value [iter 13]: 0xa00c7c75 [4.401513] iwlwifi :00:14.3: value [iter 14]: 0xa00c7c75 [4.401514] iwlwifi :00:14.3: Host monitor block 0x22 vector 0x0 [4.401535] iwlwifi :00:14.3: value [iter 0]: 0x99cec019 [4.401643] iwlwifi: probe of :00:14.3 failed with error -110 dmesg from good boot: [4.316245] iwlwifi :00:14.3: enabling device ( -> 0002) ... [4.328750] iwlwifi :00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-69.ucode failed with error -2 [4.329975] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [4.329995] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [4.330436] iwlwifi :00:14.3: loaded firmware version 68.01d30b0c.0 so-a0-gf-a0-68.ucode op_mode iwlmvm lspci output: 00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Pr
[Kernel-packages] [Bug 1975388] [NEW] upgrade from 18.04 to 20.04 while on rollbacked kernel 4.15-0-177 - package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed gr
You have been subscribed to a public bug: Dell XPS 15 9570. Dual boot with Windows 10. Linux was on 18.04 when attempting to upgrade to 20.04. Had previously installed kernel 4.15-0-177 which was rolled back to working kernel 4.15-0-175 due to issues already reported in Bug #1973482. Due to rollback, there was an unsigned image of kernel 4.15-0-177 in the machine, which caused the upgrade 20.04 to fail with following error. Ubuntu upgrade attempted while logged into kernel 4.15-0-175. package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 21 12:24:34 2022 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-09-23 (1336 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-21 (0 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- upgrade from 18.04 to 20.04 while on rollbacked kernel 4.15-0-177 - package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1975388 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 1975388] Re: upgrade from 18.04 to 20.04 while on rollbacked kernel 4.15-0-177 - package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub
You didn't remove all the 177 packages, the headers package or so pulls in a kernel and then apt switches to the unsigned one. I'm going to reassign this to Linux, as we should ensure that doesn't happen by not allowing unsigned to satisfy those dependencies. ** Package changed: grub2-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid => New ** Summary changed: - upgrade from 18.04 to 20.04 while on rollbacked kernel 4.15-0-177 - package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 + Removing signed kernel installs unsigned one due to dependencies -- 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/1975388 Title: Removing signed kernel installs unsigned one due to dependencies Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 15 9570. Dual boot with Windows 10. Linux was on 18.04 when attempting to upgrade to 20.04. Had previously installed kernel 4.15-0-177 which was rolled back to working kernel 4.15-0-175 due to issues already reported in Bug #1973482. Due to rollback, there was an unsigned image of kernel 4.15-0-177 in the machine, which caused the upgrade 20.04 to fail with following error. Ubuntu upgrade attempted while logged into kernel 4.15-0-175. package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 21 12:24:34 2022 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-09-23 (1336 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975388] 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/1975388 Title: Removing signed kernel installs unsigned one due to dependencies Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 15 9570. Dual boot with Windows 10. Linux was on 18.04 when attempting to upgrade to 20.04. Had previously installed kernel 4.15-0-177 which was rolled back to working kernel 4.15-0-175 due to issues already reported in Bug #1973482. Due to rollback, there was an unsigned image of kernel 4.15-0-177 in the machine, which caused the upgrade 20.04 to fail with following error. Ubuntu upgrade attempted while logged into kernel 4.15-0-175. package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 21 12:24:34 2022 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-09-23 (1336 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-05-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
Have the same problem on ThinkPad T480s and 18.04.6 -- 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/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.15.0-177-generic, my machine completely freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI mode. The mouse pointer is frozen, the keyboard does not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reaction. I cannot work with my machine at this point and have to hard reset it. Selecting advanced boot options in grub and selecting the previous linux kernel 4.15.0-176 makes it work again. So this bad bug was introduced with the 4.15.0-177 kernel release. I tried removing the nvidia-driver-510 package, presumably making Ubuntu use the "nouveau" driver, and with that, I could use the welcome screen and log in, but the machine still froze shortly afterwards. So maybe this is some sort of interference with my GeForce 1080 graphics card, but it is not specific to the driver used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2082 F pulseaudio /dev/snd/controlC0: robert 2082 F pulseaudio /dev/snd/controlC2: robert 2082 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 12 13:36:28 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-29 (2386 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Supermicro Super Server ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-176-generic N/A linux-backports-modules-4.15.0-176-generic N/A linux-firmware 1.173.21 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago) dmi.bios.date: 09/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961476] Re: The laptop turns off only through the button and won't wake up from sleep (black screen)
Hello At the moment, I managed to find a solution, after disabling the thunderbolt in the bios, the laptop itself turns off successfully. Perhaps this is not the best solution, but at the moment it is quite working. Regarding the problems with the sleep mode, if the laptop lid is not closed, then with the help of the touchpad, it wakes up without any problems. If the lid is closed, then after opening the touchpad, it does not come out of sleep, but after connecting the mouse and a short pause, it comes out of sleep mode. People have such problems very often on forums, I hope they can be solved in a more correct way. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961476 Title: The laptop turns off only through the button and won't wake up from sleep (black screen) Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: A complete shutdown of the laptop occurs only with the help of the shutdown button. If this is not done, then the keyboard backlight and fans work, and the screen itself is turned off. And also the sleep mode does not work (black screen and no reaction), you have to turn it off with a button to get out of it. The problem has been observed since ubuntu version 20.04 and the BIOS update. These problems are not observed in Windows OS. The video card is no longer displayed as nvidia in both operating systems, now it is displayed only asMesa Intel® UHD Graphics 630 (CFL GT2). I didn't reboot myself before, apparently the kernel was fixed. Thanks to the developers, that now he at least reboots himself. It remains to solve the issue with the shutdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 14:35:10 2022 InstallationDate: Installed on 2022-02-01 (17 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) Product Name: G7 7790 BIOS Information Vendor: Dell Inc. Version: 1.14.0 10/20/2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eve1634 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-01 (17 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. G7 7790 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=72a43957-07b7-4ade-9aa6-30aede661648 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0PJ0RG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 6564055862 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd10/20/2020:br1.14:svnDellInc.:pnG77790:pvr:rvnDellInc.:rn0PJ0RG:rvrA00:cvnDellInc.:ct10:cvr:sku08EC: dmi.product.family: GSeries dmi.product.name: G7 7790 dmi.product.sku: 08EC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Launchpad has imported 28 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=194825. 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 2017-03-09T11:15:45+00:00 fiedzia wrote: Created attachment 255151 kernel config I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried to: 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091] IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/3 On 2017-03-09T11:17:14+00:00 fiedzia wrote: Created attachment 255153 lspci_vv_nn Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/4 On 2017-03-09T11:17:58+00:00 fiedzia wrote: Created attachment 255155 dmidecode Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/5 On 2017-03-09T11:18:41+00:00 fiedzia wrote: Created attachment 255157 find_sys_bus_acpi Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/6 On 2017-03-09T11:19:23+00:00 fiedzia wrote: Created attachment 255159 content of /sys/bus/acpi/devices/AMDI0040 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/7 On 2017-03-10T09:25:21+00:00 fiedzia wrote: I've found a workaround (requires compiling own kernel, tested on 4.11 and r4.11rc1): When configuring kernel (I used make menuconfig) disable following things: Everything under device drivers/gpio support, especially: memory mapped files/amd promontory support (GPIO_AMDPT) and pci gpio expanders / amd 8111 gpio driver (GPIO_AMD8111) but I've turned of everything to make sure nothing is using gpio. device drivers / pin controllers / amd gpio pin control (PINCTRL_AMD) Perhaps only one of them could be really necessary, but I didn't tested that. System boots normally, no problems with journald and no weird messages from dmesg. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/13 On 2017-03-13T09:04:55+00:00 fiedzia wrote: >tested on 4.11 and r4.11rc1 Should be "tested on 4.10 and r4.11rc" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/28 On 2017-05-09T21:02:38+00:00 jonnyboysmithy wrote: Link to what appears to be the same bug over at the ubuntu launchpad site: https://bugs.launchpad.net/u
