[Kernel-packages] [Bug 2060655] [NEW] linux-signatures-nvidia-6.8.0-22-generic missing default nvidia 550 drivers
Public bug reported: The linux-signatures-nvidia-6.8.0-22-generic package only contains nvidia drivers as new as nvidia-driver-450 despite the current additional drivers in Software & Updates having nvidia-driver-550 as the tested topmost choice. ** Affects: linux-restricted-signatures (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-signatures in Ubuntu. https://bugs.launchpad.net/bugs/2060655 Title: linux-signatures-nvidia-6.8.0-22-generic missing default nvidia 550 drivers Status in linux-restricted-signatures package in Ubuntu: New Bug description: The linux-signatures-nvidia-6.8.0-22-generic package only contains nvidia drivers as new as nvidia-driver-450 despite the current additional drivers in Software & Updates having nvidia-driver-550 as the tested topmost choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-signatures/+bug/2060655/+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 2047208] Re: MaaS installed image unbootable on Ampere Altra
can you supply any more boot logs? ie: are you getting the same "You must load the kernel first" error as in https://bugs.launchpad.net/maas/+bug/2044169? I suspect this is a broken/malformed image ** Changed in: maas Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047208 Title: MaaS installed image unbootable on Ampere Altra Status in MAAS: Incomplete Status in linux package in Ubuntu: New Bug description: Over the past few days, I attempted to install a new ampere altra server with Ubuntu 22.04 via MaaS, the 22.04 arm image will not PXE boot/boot loops on the altra. 20.04 will PXE boot and install to the hard drive, but on subsequent boots, the image will not boot unless pxe booted first and then fall back to local GRUB on the disk - which seems to workaround the UEFI issue at boot. The system is running a supermicro build of the v2.10 altra SCP, and I think that's wherein the issue lays. There is a likely related patch here: https://lore.kernel.org/linux-arm- kernel/camj1kxety24d8syukkix7nr0pax2vzdvelnc64bz65ughup...@mail.gmail.com/T/ I am wondering if that or similar is incorporated/can be incorporated into the Ubuntu 22.04 LTS release image. Also, noted that the rescue image for MaaS fails with "bad magic number" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2047208/+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 2045951] Re: GpuWatchdog segfault in libcef.so
Yeah, i have this bug since forever, occurs randomly when opening steam. It will load the steam window but not all the content inside then freeze. Ubuntu 22.04 Kernel: 6.2.0-37-generic Amdgpu Mesa 23.3.0 - kisak-mesa PPA (LLVM 15.0.7) A crash from today Dec 8 15:31:33 H-Linux steam.desktop[20716]: RegisterForAppOverview 2: 325ms Dec 8 15:31:34 H-Linux ubuntu-appindicat...@ubuntu.com[2663]: unable to update icon for steam Dec 8 15:32:20 H-Linux kernel: [ 3518.714561] GpuWatchdog[20825]: segfault at 0 ip 7fb7cbd92bc6 sp 7fb7c09fd370 error 6 in libcef.so[7fb7c78ef000+777] likely on CPU 0 (core 0, socket 0) Dec 8 15:32:20 H-Linux kernel: [ 3518.714585] Code: 89 de e8 4d ee 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 2e 66 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 3a d1 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only bug reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/q/1490916/170177 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/q/658684/45386 https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux
[Kernel-packages] [Bug 2039991] Re: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt
** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610 oct 20 18:12:33 H-Linux kernel: read_pages+0x70/0x260 oct 20
[Kernel-packages] [Bug 2039991] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712652/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712648/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712651/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712650/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610
[Kernel-packages] [Bug 2039991] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712649/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712646/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712647/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712644/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712645/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712643/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610
[Kernel-packages] [Bug 2039991] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712642/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610
[Kernel-packages] [Bug 2039991] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712640/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610
[Kernel-packages] [Bug 2039991] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712639/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712641/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610
[Kernel-packages] [Bug 2039991] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712638/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610
[Kernel-packages] [Bug 2039991] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712637/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2039991] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2039991/+attachment/5712636/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610 oct
[Kernel-packages] [Bug 2039991] Re: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt
apport information ** Tags added: apport-collected ** Description changed: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610 oct 20 18:12:33 H-Linux kernel: read_pages+0x70/0x260 oct 20 18:12:33 H-Linux kernel: page_cache_ra_unbounded+0x157/0x1b0 oct 20 18:12:33 H-Linux kernel: page_cache_ra_order+0x264/0x330 oct 20 18:12:33 H-Linux kernel: ? xas_load+0x1f/0x100 oct 20 18:12:33 H-Linux kernel: do_sync_mmap_readahead+0x13d/0x270 oct 20 18:12:33 H-Linux kernel: filemap_fault+0x425/0x7f0 oct 20 18:12:33 H-Linux kernel: ?
[Kernel-packages] [Bug 2039991] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt
Public bug reported: Everything works fine, this error shows up in the boot log. Description:Ubuntu 22.04.3 LTS Release:22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel: xz_dec_run+0x38/0xe0 oct 20 18:12:33 H-Linux kernel: squashfs_xz_uncompress+0xd0/0x230 oct 20 18:12:33 H-Linux kernel: squashfs_decompress+0x5e/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_read_data+0x102/0x400 oct 20 18:12:33 H-Linux kernel: ? kmalloc_trace+0x2a/0xb0 oct 20 18:12:33 H-Linux kernel: squashfs_readahead+0x3ae/0x610 oct 20 18:12:33 H-Linux kernel: read_pages+0x70/0x260 oct 20 18:12:33 H-Linux kernel: page_cache_ra_unbounded+0x157/0x1b0 oct 20 18:12:33 H-Linux kernel: page_cache_ra_order+0x264/0x330 oct 20 18:12:33 H-Linux kernel: ? xas_load+0x1f/0x100 oct 20 18:12:33 H-Linux kernel: do_sync_mmap_readahead+0x13d/0x270 oct 20 18:12:33 H-Linux kernel: filemap_fault+0x425/0x7f0 oct 20 18:12:33 H-Linux kernel: ? filemap_map_pages+0x324/0x4b0 oct 20 18:12:33 H-Linux kernel: __do_fault+0x39/0x150 oct 20 18:12:33 H-Linux kernel: do_read_fault+0xef/0x170 oct 20 18:12:33 H-Linux kernel: do_fault+0xa0/0x2f0
[Kernel-packages] [Bug 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
The nvidia support is still messed up under 6.2.0-26 for those using secure boot. In previous iterations of the nvidia drivers and kernels, one could always count on the linux-signatures-nvidia-6.2.0-26-generic and linux-modules-nvidia-535-6.2.0-26-generic to use pre-signed kernel modules rather than dkms if the Software & Updates panel was used to select the tested nvidia driver. Now they are forcing the installation of dkms with nvidia-driver-535 instead. If you try to removed dkms, it removes nvidia-driver-535 of course which makes all of the nvidia packages marked as unused in 'sudo apt-get dist-upgrade'. Hopefully Ubuntu will fix this regression at some point as it is really annoying. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
After many false starts, the following similar RedHat bug report, gave
me a hint to a workaround that suppresses the CSR_RESET errors in
iwlwifi.
https://bugzilla.redhat.com/show_bug.cgi?id=2138790
Bug 2138790 - No WiFi on T16 Intel Gen 12th Alder Lake Wifi 6E AX 211
[NEEDINFO]
This bug report cites the following kernel commit as being the source of
the bug.
https://github.com/torvalds/linux/blob/4fe89d07dcc2804c8b562f6c7896a45643d34b2f/drivers/net/wireless/intel/iwlwifi/iwl-
io.c#L478-L483
Noticing this section in that file...
/*
* Wait for clock stabilization; once stabilized, access to
* device-internal resources is supported, e.g. iwl_write_prph()
* and accesses to uCode SRAM.
*/
err = iwl_poll_bit(trans, CSR_GP_CNTRL, poll_ready, poll_ready, 25000);
if (err < 0) {
IWL_DEBUG_INFO(trans, "Failed to wake NIC\n");
iwl_dump_host_monitor(trans);
}
... I decided to disable the BIOS setting for "Wake On LAN" in the Power
section of the Gigabyte X570 UD v1.1 F37d BIOS (which is on by default).
So far this change has fully suppressed the CSR_RESET bug. Disabling
"Wake On LAN" in BIOS is sufficient without resorting to...
options iwlwifi power_save=0
options iwlmvm power_scheme=1
options iwlwifi uapsd_disable=1
in /etc/modprobe.d/iwlwifi.conf.
** Bug watch added: Red Hat Bugzilla #2138790
https://bugzilla.redhat.com/show_bug.cgi?id=2138790
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1992194
Title:
random CSR_RESET errors in iwlwifi appear under kinetic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu
22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of
the time. When this occurs, the kern.log shows...
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0:
CSR_RESET = 0x10
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0:
Host monitor block 0x0 vector 0x0
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0:
value [iter 0]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0:
value [iter 1]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0:
value [iter 2]: 0x3f7d8430
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0:
value [iter 3]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0:
value [iter 4]: 0x3f7d8430
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0:
value [iter 5]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0:
value [iter 6]: 0x3f7d8430
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0:
value [iter 7]: 0x3f7d0830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0:
value [iter 8]: 0x3f7d0430
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0:
value [iter 9]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0:
value [iter 10]: 0x3f7d0430
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0:
value [iter 11]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0:
value [iter 12]: 0x3f7d0430
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0:
value [iter 13]: 0x3f7d8830
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0:
value [iter 14]: 0x3f7d0c30
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0:
Host monitor block 0x0 vector 0x1
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0:
value [iter 0]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0:
value [iter 1]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0:
value [iter 2]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0:
value [iter 3]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0:
value [iter 4]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0:
value [iter 5]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0:
value [iter 6]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0:
value [iter 7]: 0x040066c2
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0:
value [iter 8]:
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
Upgrading the BIOS to capture the USB 2.0 fixes significantly reduced the occurance of this bug but unfortunately doesn't totally eliminate it. I should note that the Ubuntu 22.04 LTS kernels initially suffered from this bug to a small degree but that by 22.04.1 LTS, the issue was extremely rare. It is unfortunate how fragile iwlwifi is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]:
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
It appears that this is fixable with a BIOS update on the Gigabyte X570 UD v1.1 motherboard. Upgrading from the F32 stable BIOS release to the F34 stable BIOS release captures the following change from the F33g beta BIOS release... 3. Fix USB 2.0 devices stability and compatibility which makes sense as the Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card is connected to a motherboard USB 2.0 connector. Since updating to F34, the boot issues with iwlwifi have disappeared. It would still be nice for upstream to make the iwlwifi drivers as robust to BIOS defects as the Windows drivers which always worked fine under F32. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
Unfortunately, this bug has gotten worse under 5.19.0-23.24 despite the options hack. On a cold boot, about half the time the iwlwifi driver shows the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
Apparently the options workaround doesn't completely eliminate the bug. It still occurs around five percent of the time when booting kinetic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :05:00.0:
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
Looking through the various bug reports against iwlwifi in bugzilla related to iwlwifi driver initialization failures and previous workarounds, I added... options iwlwifi power_save=0 options iwlmvm power_scheme=1 options iwlwifi uapsd_disable=1 to /etc/modprobe.d/iwlwifi.conf. Tentatively, this seems to have suppressed the "CSR_RESET = 0x10" failures in this driver. I would note that the occurance of these failures were reduced under the 5.19.0-21.21 kernel package but not entirely eliminated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938]
[Kernel-packages] [Bug 1992194] [NEW] random CSR_RESET errors in iwlwifi appear under kinetic
Public bug reported: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :05:00.0: value [iter 4]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582000] iwlwifi :05:00.0: value [iter 5]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582015] iwlwifi :05:00.0: value [iter 6]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582031] iwlwifi :05:00.0: value [iter 7]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582046] iwlwifi :05:00.0: value [iter 8]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.582061] iwlwifi :05:00.0: value [iter
[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby
I attempted the upgrade again today. Running 5.15.0-43 I have no issues. Battery or Power it seems to resume reliably. Running on a Thinkpad X260 Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+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 1981433] [NEW] Sound doesn't work at all
Public bug reported: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981433 Title: Sound doesn't work at all Status in linux package in Ubuntu: New Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby
Followed https://wiki.ubuntu.com/DebuggingKernelSuspend All of the modes are working except 'none'. dmesg has these hash matches lines: [ 11.920467] PM: Magic number: 1:0:0 [ 11.920512] memory memory48: hash matches Saw a few lines online that this might be bios related, updated from 1.21 1.21 (R02ET48W) 1.12 (R02HT30W)012016/06/20 to 1.49 1.49 (R02ET76W) 1.16 (R02HT34W)012022/03/04 but it did not fix the issue. I also tried echo s2idle > /sys/power/mem_sleep which "fixes" this issue except the power led is not pulsing and you cannot wake it up except for holding the power button for ~2 seconds. Hopefully that gives some more information on the issue. ** Attachment added: "pm_test_none.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+attachment/5583039/+files/pm_test_none.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/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+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 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Attachment added: "screenshot of the rendering artifact in cheese under 22.04" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577395/+files/Screenshot%20from%202022-04-05%2016-53-06.png -- 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/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
I also can confirm that the warnings... (cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. and associated rendering artifacts in the cheese display occur for both the nouveau and nvidia 510 drivers. -- 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/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string
[Kernel-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink' displays the webcam image fine. -- 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/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1967843] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577390/+files/Dependencies.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/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1967843] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577392/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1967843] lspci.txt
apport information ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577393/+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/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1967843] lsusb.txt
apport information ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577394/+files/lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1967843] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967843/+attachment/5577391/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
apport information ** Tags added: apport-collected ** Description changed: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-31 (4 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) + MachineType: Gigabyte Technology Co., Ltd. X570 UD + NonfreeKernelModules: nvidia_modeset nvidia + Package: cheese 41.1-1build1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 + RelatedPackageVersions: + cheese41.1-1build1 + cheese-common 41.1-1build1 + Tags: wayland-session third-party-packages jammy gstreamer-error + Uname: Linux 5.15.0-25-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: 01/18/2021 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F32 + dmi.board.asset.tag: Default string + dmi.board.name: X570 UD + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: + dmi.product.family: X570 MB + dmi.product.name: X570 UD + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "CheeseDebug.txt.gz" https://bugs.launchpad.net/bugs/1967843/+attachment/5577389/+files/CheeseDebug.txt.gz -- 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/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form...
[Kernel-packages] [Bug 1967843] [NEW] cheese display corrupted under Ubuntu 22.04
Public bug reported: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gstreamer-error jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in linux package in Ubuntu: New Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1917709] Re: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error
I'm having this issue when launching a game using steam proton. When launching the Stationeers game it wants to read from dvd-rw drive and once every 3-4 launches the game will also freeze the whole system. I'm guessing this is the reason for the freeze since this would be the last error in logs. Ubuntu 21.10, kernel 5.14.21-051421-generic, amdgpu and -force-opengl in launch options. dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 0, async page read dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 1, async page read dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 2, async page read dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 3, async page read -- 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/1917709 Title: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error Status in linux package in Ubuntu: Fix Released Bug description: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron:
[Kernel-packages] [Bug 1917709] Re: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917709 Title: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error Status in linux package in Ubuntu: Fix Released Bug description: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to:
[Kernel-packages] [Bug 1950205] Re: Some shaders can crash the amdgpu kernel module, tainting
Edit: Please close this bug -- it is a duplicate of an upstream issue in dxvk (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) and not the kernel per se (although that makes life worse by clearing out vram and hard-resetting the gpu once the crash occurs, which X and DMs have no way to recover from). ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 -- 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/1950205 Title: Some shaders can crash the amdgpu kernel module, tainting Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops cec crypto_simd rc_core cryptd drm r8169 ahci
[Kernel-packages] [Bug 1950205] Re: Some shaders can crash the amdgpu kernel module, tainting
Edit -- it transpires that, despite what I said, the magic <0 to <=0 change hasn't been made on the main branch of mesa's git repo yet. I've successfully compiled a local copy (with meson & ninja) and am running it in a separate root to avoid clobbering the system libraries using LD_LIBRARY_PATH and friends which can get glxgears working at least. Frankly I am in a little over my depth. I'd like to really be able to build the packages from source, apply a two character / one line diff as suggested upstream to see if it actually works, and then test further. Any advice very welcome ;-). -- 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/1950205 Title: Some shaders can crash the amdgpu kernel module, tainting Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul
[Kernel-packages] [Bug 1950205] [NEW] Some shaders can crash the amdgpu kernel module, tainting
Public bug reported: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops cec crypto_simd rc_core cryptd drm r8169 ahci i2c_piix4 xhci_pci libahci xhci_pci_renesas realtek wmi [ 1214.600336] CPU: 7 PID: 0 Comm: swapper/7 Tainted: P C OE 5.13.0-21-generic #21-Ubuntu [ 1214.600337] Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 1201 09/09/2019 [ 1214.600339] RIP: 0010:drm_vblank_put+0xef/0x100 [drm] [ 1214.600353] Code: 8b 7f 08 4c 8b 67 50 4d 85 e4 74 22 e8 ea 55 ef d7 48 c7 c1 d8 22 4e c0 4c 89 e2 48 c7 c7 75 d5 4d c0 48 89 c6 e8 c0 75 31 d8 <0f> 0b eb 8a 4c 8b 27 eb d9 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [ 1214.600354] RSP: 0018:a654803a8d78 EFLAGS: 00010086 [ 1214.600356] RAX: RBX: 94289d0a RCX: 0027 [ 1214.600357] RDX: 942f7ebd89c8 RSI: 0001 RDI: 942f7ebd89c0 [ 1214.600358] RBP:
[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS
The changes made to linux-firmware 1.201.1 on impish has destablized use of a Gigabyte GC-WB867D-I REV Bluetooth 4.0/Wireless AC/B/G/N Band Dual Frequency 2.4Ghz/5.8Ghz Expansion Card. Under the new linux-firmware 1.201.1, no wifi is available under Gnome in about 80-90% of the boots. Under the prior linux-firmware 1.201 release, the wifi always appears under Gnome. Below are the differences in syslog for the broken linux- firmware 1.201.1 release... Nov 3 04:27:07 home kernel: [ 13.045691] iwlwifi :4d:00.0: enabling device ( -> 0002) Nov 3 04:27:07 home kernel: [ 13.055795] iwlwifi :4d:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm Nov 3 04:27:07 home kernel: [ 13.112172] iwlwifi :4d:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 versus the stable linux-firmware 1.201 release... Nov 3 04:36:53 home kernel: [ 14.482126] iwlwifi :4d:00.0: enabling device ( -> 0002) Nov 3 04:36:53 home kernel: [ 14.492179] iwlwifi :4d:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm Nov 3 04:36:53 home kernel: [ 14.548114] iwlwifi :4d:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 Nov 3 04:36:53 home kernel: [ 14.606163] iwlwifi :4d:00.0: base HW address: 00:28:f8:f9:16:e0 Nov 3 04:36:53 home kernel: [ 14.722166] iwlwifi :4d:00.0 wlp77s0: renamed from wlan0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1947829 Title: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Sometimes MT7921 may not be probed due to an endless mcu reset: [ 5.789548] mt7921 mcu reset 0 [ 5.790625] mt7921 rx type 0x7 [ 5.790625] mt7921 eid 0x1 ext_eid 0x0 [ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0 [Fix] WiFi and Bluetooth firmware updates from mainline: * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * d34196f5 linux-firmware: update firmware for MT7921 WiFi device [Test Case] This should fix the mcu reset and wireless/bluetooh devices should be probed successfully. [Where problems could occur] While there is explicit FW API for kernel version compatibility checking, this might introduce some hidden glitches that we don't know yet. [Other Info] MT7921 is supported since Impish 5.13 kernel, and Impish already has the latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13 and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are required. == original bug report == [Reproduce Steps] 1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS. 2.During OOBE, Open the settings, there is no wireless settings in the panel,and the wifi cannot be used,issue occurred. [Results] Expected Result:The wireless settings should be exists and wifi can be used Actual Result:The wireless settings not exists and wifi can not be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1947829/+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 1934773] Re: Touchpad does not work
This looks like being a hardware issue (also does not work under Windows). ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934773 Title: Touchpad does not work Status in linux package in Ubuntu: Invalid Bug description: My touchpad does not work at all. For a while it worked adding i8042.kbdreset=1 i8042.nomux=1 i8042.reset to /etc/default/grub. It would periodically stop working and then I would be able to get it back with rmmod i2c_hid and modprobe i2c_hid, but now it does not work at all. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1388 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 6 12:09:55 2021 InstallationDate: Installed on 2021-07-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=dc6ba4f2-063a-427e-8a9b-bf760999f2e4 ro i8042.kbdreset=1 i8042.reset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-06 (0 days ago) dmi.bios.date: 09/30/2020 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: FBCN19WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ITL05 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrFBCN19WW:bd09/30/2020:br1.19:efr1.17:svnLENOVO:pn82A3:pvrYogaSlim714ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrYogaSlim714ITL05: dmi.product.family: Yoga Slim 7 14ITL05 dmi.product.name: 82A3 dmi.product.sku: LENOVO_MT_82A3_BU_idea_FM_Yoga Slim 7 14ITL05 dmi.product.version: Yoga Slim 7 14ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934773/+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 1934773] [NEW] Touchpad does not work
Public bug reported: My touchpad does not work at all. For a while it worked adding i8042.kbdreset=1 i8042.nomux=1 i8042.reset to /etc/default/grub. It would periodically stop working and then I would be able to get it back with rmmod i2c_hid and modprobe i2c_hid, but now it does not work at all. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1388 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 6 12:09:55 2021 InstallationDate: Installed on 2021-07-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=dc6ba4f2-063a-427e-8a9b-bf760999f2e4 ro i8042.kbdreset=1 i8042.reset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-06 (0 days ago) dmi.bios.date: 09/30/2020 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: FBCN19WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ITL05 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrFBCN19WW:bd09/30/2020:br1.19:efr1.17:svnLENOVO:pn82A3:pvrYogaSlim714ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrYogaSlim714ITL05: dmi.product.family: Yoga Slim 7 14ITL05 dmi.product.name: 82A3 dmi.product.sku: LENOVO_MT_82A3_BU_idea_FM_Yoga Slim 7 14ITL05 dmi.product.version: Yoga Slim 7 14ITL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934773 Title: Touchpad does not work Status in linux package in Ubuntu: New Bug description: My touchpad does not work at all. For a while it worked adding i8042.kbdreset=1 i8042.nomux=1 i8042.reset to /etc/default/grub. It would periodically stop working and then I would be able to get it back with rmmod i2c_hid and modprobe i2c_hid, but now it does not work at all. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1388 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 6 12:09:55 2021 InstallationDate: Installed on 2021-07-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=dc6ba4f2-063a-427e-8a9b-bf760999f2e4 ro i8042.kbdreset=1 i8042.reset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-06 (0 days ago) dmi.bios.date: 09/30/2020 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: FBCN19WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ITL05 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrFBCN19WW:bd09/30/2020:br1.19:efr1.17:svnLENOVO:pn82A3:pvrYogaSlim714ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrYogaSlim714ITL05: dmi.product.family: Yoga Slim 7 14ITL05 dmi.product.name: 82A3 dmi.product.sku: LENOVO_MT_82A3_BU_idea_FM_Yoga Slim 7 14ITL05 dmi.product.version: Yoga Slim 7 14ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubunt
[Kernel-packages] [Bug 1884058] Re: kernel warning in epyc2 nested virtualization
should be fixed by upcoming 5.4.120 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable- rc.git/commit/?h=linux-5.4.y=ec60172af2c6f7c4a59a22fc1ba68729ea3a2e4d -- 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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1919013] [NEW] Touchpad stopped working and only worked after switching kernel
Public bug reported: My touchpad (Lenovo Ideapad Slim 7, Intel version) was working fine until I woke the laptop one time and it stopped working. It did not appear in /proc/bus/input/devices. Restarting did not help. However, after restarting into 5.8.0-25 the touchpad worked again (devices file attached). Then restarting again into 5.8.0-44 everything was working. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 13 08:48:31 2021 InstallationDate: Installed on 2021-03-10 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=01a43871-5873-4879-ae9f-e7a807101182 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2020 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: FBCN19WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ITL05 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrFBCN19WW:bd09/30/2020:br1.19:efr1.17:svnLENOVO:pn82A3:pvrYogaSlim714ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrYogaSlim714ITL05: dmi.product.family: Yoga Slim 7 14ITL05 dmi.product.name: 82A3 dmi.product.sku: LENOVO_MT_82A3_BU_idea_FM_Yoga Slim 7 14ITL05 dmi.product.version: Yoga Slim 7 14ITL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy touchpad ** Attachment added: "touchpad-debug.txt" https://bugs.launchpad.net/bugs/1919013/+attachment/5476219/+files/touchpad-debug.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/1919013 Title: Touchpad stopped working and only worked after switching kernel Status in linux package in Ubuntu: Confirmed Bug description: My touchpad (Lenovo Ideapad Slim 7, Intel version) was working fine until I woke the laptop one time and it stopped working. It did not appear in /proc/bus/input/devices. Restarting did not help. However, after restarting into 5.8.0-25 the touchpad worked again (devices file attached). Then restarting again into 5.8.0-44 everything was working. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 13 08:48:31 2021 InstallationDate: Installed on 2021-03-10 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=01a43871-5873-4879-ae9f-e7a807101182 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2020 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: FBCN19WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ITL05 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrFBCN19WW:bd09/30/2020:br1.19:efr1.17:svnLENOVO:pn82A3:pvrYogaSlim714ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrYogaSlim714ITL05: dmi.product.family: Yoga Slim 7 14ITL05 dmi.product.name: 82A3 dmi.product.sku: LENOVO_MT_82A3_BU_idea_FM_Yoga Slim 7 14ITL05 dmi.product.version: Yoga Slim 7 14ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.laun
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted shell textures when switching users or resuming from suspend
I've seen the same issue with focal and System76 Stable PPA's 460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text was corrupted after waking from suspend but it has only occurred once so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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+git20200226-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/1876632/+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 1910806] Re: System hang - kernel 5.8.0-36
This problem report is related to 1910588. I am running kernel 5.8.0-36 now and found that the dd command I was using to test zfs raidz1 performance worked the last time I tried. dd now provides speed measurement skewed by arc though (2.0GB/s). I have run memtest86 on this machine recently. Four passes found no errors. The machine memory is non-ECC though. I'll try again after the next reboot. -- 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/1910806 Title: System hang - kernel 5.8.0-36 Status in linux package in Ubuntu: Confirmed Bug description: I reported what I believe to be the same problem yesterday with kernel -34 but running the rsync command to create a backup. I can cause the system to hang with the following commands: dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k cp Win10_20H2_v2_English_x64.iso /var/tmp The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB Seagate drives) These commands and the rsync work with kernel 5.8.0-33 The filename describes the contents. zpool scrub runs without errors... cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 Win10_20H2_v2_English_x64.iso jcw0624@cascade:~/Documents/Computing/Windows$ zpool status pool: data state: ONLINE scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan 8 11:48:13 2021 config: NAMESTATE READ WRITE CKSUM dataONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 errors: No known data errors jcw0624@cascade:~/Documents/Computing/Windows$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-36-generic 5.8.0-36.40 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245470 F pulseaudio /dev/snd/controlC1: jcw06245470 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 11:56:46 2021 InstallationDate: Installed on 2020-10-03 (97 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-09 (60 days ago) dmi.bios.date: 10/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910806/+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 1910806] [NEW] System hang - kernel 5.8.0-36
Public bug reported: I reported what I believe to be the same problem yesterday with kernel -34 but running the rsync command to create a backup. I can cause the system to hang with the following commands: dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k cp Win10_20H2_v2_English_x64.iso /var/tmp The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB Seagate drives) These commands and the rsync work with kernel 5.8.0-33 The filename describes the contents. zpool scrub runs without errors... cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 Win10_20H2_v2_English_x64.iso jcw0624@cascade:~/Documents/Computing/Windows$ zpool status pool: data state: ONLINE scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan 8 11:48:13 2021 config: NAMESTATE READ WRITE CKSUM dataONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 errors: No known data errors jcw0624@cascade:~/Documents/Computing/Windows$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-36-generic 5.8.0-36.40 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245470 F pulseaudio /dev/snd/controlC1: jcw06245470 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 11:56:46 2021 InstallationDate: Installed on 2020-10-03 (97 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-09 (60 days ago) dmi.bios.date: 10/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1910806 Title: System hang - kernel 5.8.0-36 Status in linux package in Ubuntu: New Bug description: I reported what I believe to be the same problem yesterday with kernel -34 but running the rsync command to create a backup. I can cause the system to hang with the following commands: dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k cp Win10_20H2_v2_English_x64.iso /var/tmp The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB Seagate drives) These commands and the rsync work with kernel 5.8.0-33 The filename describes the contents. zpool scrub runs without errors... cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 Win10_20H2_v2_English_x64.iso jcw0624@cascade:~/Documents/Computing/Windows$ zpool status pool: data state: ONLINE scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan 8 11:48:13 2021 config: NAMESTATE READ WRITE CKSUM dataONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda
[Kernel-packages] [Bug 1910588] [NEW] rsync backup hang
Public bug reported: I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs requiring machine reset; no response from mouse or keyboard. No response to ping from a windows machine. All drive activity stops. The hang occurs with the backup drive connected via sata and via usb3 (adapter) The source directories are ext4 (boot drive ssd) and zfs (raidz1 four x 4TB drives). The destination is a single 3TB drive formatted with zfs (drive is about 20% full). The hang occurred about 6 times before I decided to go back to kernel 5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel -33 (sata and usb3 connect). The install is 20.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245100 F pulseaudio /dev/snd/pcmC0D0p: jcw06245100 F...m pulseaudio /dev/snd/controlC1: jcw06245100 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 12:07:11 2021 InstallationDate: Installed on 2020-10-03 (96 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.0-34-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago) dmi.bios.date: 10/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- 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/1910588 Title: rsync backup hang Status in linux package in Ubuntu: Confirmed Bug description: I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs requiring machine reset; no response from mouse or keyboard. No response to ping from a windows machine. All drive activity stops. The hang occurs with the backup drive connected via sata and via usb3 (adapter) The source directories are ext4 (boot drive ssd) and zfs (raidz1 four x 4TB drives). The destination is a single 3TB drive formatted with zfs (drive is about 20% full). The hang occurred about 6 times before I decided to go back to kernel 5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel -33 (sata and usb3 connect). The install is 20.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245100 F pulseaudio /dev/snd/pcmC0D0p: jcw06245100 F...m pulseaudio /dev/snd/controlC1: jcw06245100 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 12:07:11 2021 InstallationDate: Installed on 2020-10-03 (96 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1873965] Re: booting into recovery mode hangs under 20.04
This offending package for bug is proving very difficult to pin down. I have tried to sequentially regress all the packages that the recovery kernel boot are likely to use back to their eoan versions on a 20.04 installation. In each case, I reinstalled the kernels afterwards to insure that the initrd.img files were full regenerated and reinstalled. The installed packages from the following have been regression tested... plymouth busybox udev kmod grub initramfs libklibc and none of these eliminate the breakage in nomodeset under 20.04 on a Mac ROMed GTX680. The only 'workaround' that I have found is to append 'nouveau.modeset=1' after 'nomodeset' in grub's recovery kernel entry. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] Re: booting into recovery mode hangs under 20.04
This issue extends to the daily desktop cd image for focal. When booted from a usb memory stick and the safe graphics (which uses nomodeset) is selected from grub, the screen remains black and never completes booting. This issue doesn't exist with the current 19.10 cd images which boot without issue on a GTX680. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] Re: booting into recovery mode hangs under 20.04
I have been able to eliminate the focal 5.4.0-26-generic kernel packages as the origin of this bug. Manually installing those onto an installation of Ubuntu 19.10, produced a fully functional boot. More importantly the recovery mode boot from grub worked fine. So the problem under 20.04 would appear to be something outside of the kernel itself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] Re: booting into recovery mode hangs under 20.04
This problem doesn't exist for current Ubuntu 19.10 under its 5.3.0-46-generic kernel. The recovery mode boots fine on the same hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] Re: booting into recovery mode hangs under 20.04
Oddly, so far I have not found a Ubuntu mainline kernel build that doesn't show the problem. 5.3.18-050318-generic 5.4.0-050400-generic 5.4.25-050425-generic 5.4.28-050428-generic 5.6.6-050606-generic all produce the hang at loading the ramdisk when booting the recovery kernel with the default use of nomodesetunder Ubuntu 18.04. The stock 5.3.0-46-generic kernel installed by bionics updates doesn't have this problem. So I am guessing this problem must be either a dropped patch in the kernels used by Ubuntu 20.04 or a change in configuration options in the kernels between 18.04 and 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] Re: booting into recovery mode hangs under 20.04
Interestingly, installing the mainline Ubuntu 5.4.25 generic kernel packages on Ubuntu 18.04 produces the same bug of nomodeset preventing the recovery dialog from appearing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] Re: booting into recovery mode hangs under 20.04
If I remove 'nomodeset' from the grub kernel options for the recovery kernel under 20.04, the hang in booting at loading the ramdisk is eliminated. The recovery dialog appears as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1873965] [NEW] booting into recovery mode hangs under 20.04
Public bug reported: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Required info on kernel used" https://bugs.launchpad.net/bugs/1873965/+attachment/5357409/+files/kernel_info.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873965 Title: booting into recovery mode hangs under 20.04 Status in linux-meta package in Ubuntu: New Bug description: On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10 installation dist-upgraded to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This bug is definitely triggered by the built kernel image loading the nvidia drivers. The autologin failures and associated hangs on restarts can be suppressed as follows... 1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT 2) Regenerate /boot/grub/grub.cfg with 'sudo update-grub' 3) Regenerate the initrd.img files by using 'sudo apt-get --reinstall install' to reinstall the currently installed kernel packages. After rebooting, the autologin feature in gdm3 can be reselected and on the next reboot, it will autologin as expected. No loading the nvidia module through initrd.img also eliminates the hangs on restarting while autologin is enabled. I suspect the folks who thought removing splash from grub.cfg didn't work had failed to rebuild the initrd.img files after regenerating grub.cfg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Couldn't the nvidia packages all be modified to prune 'splash' from /boot/grub/grub.cfg prior to rebuilding its kernel modules and thus regenerating the initrd.img files? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf under 20.04 has no impact on the autologin bug with nvidia-340. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro 3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is shown instead. While the login works fine at the point, restarting then causes the system to hang rather than completing the restart. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
With reference to post#50, it turns out my problems were caused by the 5.3 kernel not handling the nvidia gpu usb-c driver properly. I could fix using: sudo sh -c 'echo "blacklist ucsi_ccg # Fix suspend freeze bug" >> /etc/modprobe.d/blacklist.conf' See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850238 Sorry for the noise. -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1873313] [NEW] linux-image-5.4.0-24-generic 5.4.0.24.29 missing from repo
Public bug reported: The most recent kernel updates resulted in... ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-image-generic5.4.0.24.29 amd64Generic Linux kernel image where the 5.4.0.24.29 build of linux-image-5.4.0-24-generic didn't get moved into the repository. Likewise we have... ii linux-headers-5.4.0-24 5.4.0-24.28 all Header files related to Linux kernel version 5.4.0 ii linux-headers-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-libc-dev:amd64 5.4.0-24.28 amd64Linux Kernel Headers for development ii linux-modules-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-extra-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1873313 Title: linux-image-5.4.0-24-generic 5.4.0.24.29 missing from repo Status in linux-signed package in Ubuntu: New Bug description: The most recent kernel updates resulted in... ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-image-generic5.4.0.24.29 amd64Generic Linux kernel image where the 5.4.0.24.29 build of linux-image-5.4.0-24-generic didn't get moved into the repository. Likewise we have... ii linux-headers-5.4.0-24 5.4.0-24.28 all Header files related to Linux kernel version 5.4.0 ii linux-headers-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-libc-dev:amd64 5.4.0-24.28 amd64Linux Kernel Headers for development ii linux-modules-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-extra-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1873313/+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 1848771] Re: Reboot after resume from suspend (deep)
Today I upgraded from Linux Mint 19.2 to 19.3 (Tricia) and ran into the same issue. The PC suspends correctly, on resume I see the Mint logo, then after some seconds the machine reboots. There's nothing obvious in the logs between suspend and the reboot. I don't have an option in UEFI to disable TPM. Motherboard is an MSI MAG Z390 TOMAHAWK. Reverting to kernel 4.15.0-91 solves the issue. I'm happy to supply further details if helpful. -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865197 Title: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1867860 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Signoff phase-changed: Friday, 13. March 2020 17:28 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+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 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863274 Title: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 18. February 2020 07:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1863273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863274/+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 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863285 Title: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863297 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 18. February 2020 07:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1863284 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863285/+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 1863344] Re: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863344 Title: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 20. February 2020 23:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1863343 xenial/linux-azure/azure-kernel: bug 1863342 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863344/+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 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
I'm seeing this problem on linux 5.3.0-40-generic but with a different error log: [ 98.743076] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 98.743079] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 98.743080] iwlwifi :00:14.3: Found debug configuration: 0 [ 98.743277] iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm [ 98.789706] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x354 [ 98.796641] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 98.797136] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 99.804515] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 99.804588] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 99.804590] iwlwifi :00:14.3: Status: 0x, count: -1954858323 [ 99.804591] iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 [ 99.804592] iwlwifi :00:14.3: 0x26D769CE | ADVANCED_SYSASSERT [ 99.804593] iwlwifi :00:14.3: 0x1AD012CA | trm_hw_status0 [ 99.804594] iwlwifi :00:14.3: 0xFC94AD42 | trm_hw_status1 [ 99.804595] iwlwifi :00:14.3: 0x67BA92B1 | branchlink2 [ 99.804595] iwlwifi :00:14.3: 0x22CDF757 | interruptlink1 [ 99.804596] iwlwifi :00:14.3: 0x461C6C04 | interruptlink2 [ 99.804597] iwlwifi :00:14.3: 0xA7A9DF46 | data1 [ 99.804598] iwlwifi :00:14.3: 0x9842E652 | data2 [ 99.804598] iwlwifi :00:14.3: 0x8A8131D1 | data3 [ 99.804599] iwlwifi :00:14.3: 0x02ED2D8A | beacon time [ 99.804600] iwlwifi :00:14.3: 0x94023DEC | tsf low [ 99.804600] iwlwifi :00:14.3: 0xDA3FE4C7 | tsf hi [ 99.804601] iwlwifi :00:14.3: 0x734269F5 | time gp1 [ 99.804602] iwlwifi :00:14.3: 0xC611C271 | time gp2 [ 99.804603] iwlwifi :00:14.3: 0x615B3F67 | uCode revision type [ 99.804603] iwlwifi :00:14.3: 0x4404C0DF | uCode version major [ 99.804604] iwlwifi :00:14.3: 0x528219F3 | uCode version minor [ 99.804605] iwlwifi :00:14.3: 0x35C57CDC | hw version [ 99.804605] iwlwifi :00:14.3: 0x2AC20D01 | board version [ 99.804606] iwlwifi :00:14.3: 0xDD85CB00 | hcmd [ 99.804607] iwlwifi :00:14.3: 0x5E16FD9E | isr0 [ 99.804608] iwlwifi :00:14.3: 0x3F3FFEEF | isr1 [ 99.804608] iwlwifi :00:14.3: 0x954E1E05 | isr2 [ 99.804609] iwlwifi :00:14.3: 0x0D660BC0 | isr3 [ 99.804610] iwlwifi :00:14.3: 0x398FFD8C | isr4 [ 99.804610] iwlwifi :00:14.3: 0xF3A3EC53 | last cmd Id [ 99.804611] iwlwifi :00:14.3: 0x046CA3B9 | wait_event [ 99.804612] iwlwifi :00:14.3: 0x1D70E4DB | l2p_control [ 99.804612] iwlwifi :00:14.3: 0x09D518A7 | l2p_duration [ 99.804613] iwlwifi :00:14.3: 0xD586D9C8 | l2p_mhvalid [ 99.804614] iwlwifi :00:14.3: 0x20AA0718 | l2p_addr_match [ 99.804615] iwlwifi :00:14.3: 0xCEA91061 | lmpm_pmg_sel [ 99.804615] iwlwifi :00:14.3: 0x2B584FE3 | timestamp [ 99.804616] iwlwifi :00:14.3: 0xDCEFA7E5 | flow_handler [ 99.804648] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 99.804649] iwlwifi :00:14.3: Status: 0x, count: 7 [ 99.804649] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 99.804650] iwlwifi :00:14.3: 0x | umac branchlink1 [ 99.804651] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2 [ 99.804652] iwlwifi :00:14.3: 0x | umac interruptlink1 [ 99.804652] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 99.804653] iwlwifi :00:14.3: 0x0003 | umac data1 [ 99.804654] iwlwifi :00:14.3: 0x2302 | umac data2 [ 99.804654] iwlwifi :00:14.3: 0x01300202 | umac data3 [ 99.804655] iwlwifi :00:14.3: 0x0030 | umac major [ 99.804656] iwlwifi :00:14.3: 0x13675109 | umac minor [ 99.804657] iwlwifi :00:14.3: 0x5C8A | frame pointer [ 99.804657] iwlwifi :00:14.3: 0xC0887F58 | stack pointer [ 99.804658] iwlwifi :00:14.3: 0x | last host cmd [ 99.804659] iwlwifi :00:14.3: 0x | isr status reg [ 99.804672] iwlwifi :00:14.3: Fseq Registers: [ 99.804674] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE [ 99.804676] iwlwifi :00:14.3: 0x8026 | FSEQ_TOP_INIT_VERSION [ 99.804678] iwlwifi :00:14.3: 0x80020006 | FSEQ_CNVIO_INIT_VERSION [ 99.804681] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 99.804683] iwlwifi :00:14.3: 0xFD00C708 | FSEQ_TOP_CONTENT_VERSION [ 99.804685] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [ 99.804687] iwlwifi :00:14.3: 0x2302 | FSEQ_CNVI_ID [ 99.804690] iwlwifi :00:14.3: 0x01300202 | FSEQ_CNVR_ID [ 99.804692] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP [ 99.804696] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 99.804701] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 99.804735] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 99.804763]
[Kernel-packages] [Bug 1862818] Re: xenial/linux-azure: 4.15.0-1071.76 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1862818 Title: xenial/linux-azure: 4.15.0-1071.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862824 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Friday, 14. February 2020 03:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: trusty/linux-azure: bug 1862816 xenial/linux-azure/azure-kernel: bug 1862815 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862818/+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 1862398] Re: eoan/linux-azure: 5.3.0-1013.14 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1862398 Title: eoan/linux-azure: 5.3.0-1013.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 12. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-azure-5.3: bug 1862397 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862398/+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 1862405] Re: bionic/linux-azure: 5.0.0-1032.34 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1862405 Title: bionic/linux-azure: 5.0.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 11. February 2020 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1861182 trackers: bionic/linux-azure/azure-kernel: bug 1862404 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862405/+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 1862239] Re: bionic/linux-azure: 5.0.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1862239 Title: bionic/linux-azure: 5.0.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859724 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 07. February 2020 02:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff trackers: bionic/linux-azure/azure-kernel: bug 1862237 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862239/+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 1858533] Re: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1858533 Title: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858534 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Thursday, 30. January 2020 01:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- package in development blackout trackers: bionic/linux-azure/azure-kernel: bug 1858532 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858533/+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 1859798] Re: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker
Testing complete ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1859798 Title: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Wednesday, 29. January 2020 21:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- package in development blackout trackers: trusty/linux-azure: bug 1859797 xenial/linux-azure/azure-kernel: bug 1859796 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859798/+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 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker
Testing complete ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1859820 Title: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860119' packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Wednesday, 29. January 2020 21:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- package in development blackout trackers: bionic/linux-azure-5.3: bug 1859819 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859820/+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 1859797] Re: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker
Testing complete ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1859797 Title: trusty/linux-azure: 4.15.0-1067.72~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859798 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Wednesday, 29. January 2020 21:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- package in development blackout variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859797/+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 1543919] Re: Remove EISA support from main kernel image and make it M (modular)
Hi all, Noticed this in my Ubuntu 19.04 dmesg: [2.094782] platform eisa.0: Probing EISA bus 0 [2.094783] platform eisa.0: EISA: Cannot allocate resource for mainboard [2.094784] platform eisa.0: Cannot allocate resource for EISA slot 1 [2.094785] platform eisa.0: Cannot allocate resource for EISA slot 2 [2.094786] platform eisa.0: Cannot allocate resource for EISA slot 3 [2.094787] platform eisa.0: Cannot allocate resource for EISA slot 4 [2.094788] platform eisa.0: Cannot allocate resource for EISA slot 5 [2.094789] platform eisa.0: Cannot allocate resource for EISA slot 6 [2.094790] platform eisa.0: Cannot allocate resource for EISA slot 7 [2.094791] platform eisa.0: Cannot allocate resource for EISA slot 8 [2.094792] platform eisa.0: EISA: Detected 0 cards First time I've ever seen this on Ubuntu or any other distributions. My motherboard is an Asus Crosshair V Formula - not that new but not that old also, I think from 2011 or there abouts. -- 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/1543919 Title: Remove EISA support from main kernel image and make it M (modular) Status in linux package in Ubuntu: Triaged Bug description: (This is a sort of RfC. ) I have a PC that still has the good old PCI ports, but I am 100% sure that the active use of EISA dates back yet more 10 years. In other words, boards that _only_ support EISA date back 25 years now, while those that provide *one* EISA slot date back roughly 15 years (one of the Elitegroup K7 series comes to mind, from about 2001/02). So the EISA support *should* be provided, as we should even support ancient hardware (Linux principle :)) However, why the EISA support is *compiled in* is beyond me. For instance, it creates lots of totally unnecessary noise in dmesg: [0.08] EISA bus registered [1.598316] platform eisa.0: Probing EISA bus 0 [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1 (repeated 10 times, i=i+1) [1.598368] platform eisa.0: EISA: Detected 0 cards For a 1997 mainboard, this would make perfect sense. But it is very probable that said mainboard would require linux-image-extra nonetheless to support some days-of-yore chipset. So why not leave it as a *module*, while removing its support from main kernel image once and for all? Your turn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+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 1743908] Re: MODSIGN: Couldn't get UEFI db list
On my Disco Dingo see this also, though it doesn't seem to have any negative effect. kernel: 5.0.0-16-generic secureboot: Secure boot could not be determined (mode 0) [2.243394] Loaded X.509 cert 'Build time autogenerated kernel key: ...' [2.267416] Couldn't get size: 0x800e [2.267418] MODSIGN: Couldn't get UEFI db list [2.279452] Couldn't get size: 0x800e [2.279454] MODSIGN: Couldn't get UEFI MokListRT [2.291440] Couldn't get size: 0x800e [2.291443] MODSIGN: Couldn't get UEFI dbx list [2.291467] zswap: loaded using pool lzo/zbud motherboard : Asus Crosshair V formula - not capable of secure boot cpu : FX8320 This shows up also in openSUSE Tumbleweed with the 5 series kernel. Not present in Fedora. -- 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/1743908 Title: MODSIGN: Couldn't get UEFI db list Status in linux package in Ubuntu: Fix Released Bug description: Kernel is having problem loading or validating certificates. Looking over the internet looks like this is a kernel issue. Patchs from other distro: https://bugzilla.redhat.com/show_bug.cgi?id=1497559 - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734' [1.203352] Couldn't get size: 0x800e [1.203354] MODSIGN: Couldn't get UEFI db list [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys keyring [1.205102] Couldn't get size: 0x800e [1.205103] MODSIGN: Couldn't get UEFI dbx list ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wellington 1429 F pulseaudio /dev/snd/pcmC1D3p: wellington 1429 F...m pulseaudio /dev/snd/controlC1: wellington 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 22:37:13 2018 HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e InstallationDate: Installed on 2018-01-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 R5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743908/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
For me ant_sel=0 "zero!" was the magic key. Took me a week of messing around until I realized one cannot only select 1 or 2 but also 0. Try out with these: sudo modprobe -r rtl8723be sudo modprobe rtl8723be ant_sel=0 iwlist scan | egrep -i 'ssid|quality' sudo modprobe -r rtl8723be sudo modprobe rtl8723be ant_sel=1 iwlist scan | egrep -i 'ssid|quality' sudo modprobe -r rtl8723be sudo modprobe rtl8723be ant_sel=2 iwlist scan | egrep -i 'ssid|quality' http://forums.debian.net/viewtopic.php?f=5=140368=691244#p691244 -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
This problem still exists for me on debian testing with 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 Only if I put my laptop directly next to a device emitting a wifi network I am able to connect. Few meters away it already becomes unusable. ant_sel=1 makes it worse. ant_sel=2 not better. Detailed information here: http://forums.debian.net/viewtopic.php?f=5=140368=691244#p691244 -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1521173] Re: AER: Corrected error received: id=00e0
I'm also experiencing this bug with the latest debian testing release: Linux lemon 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1173759] Re: Ubuntu 13.04 can detect wi-fi but can't connect
In reality, it is a typical issue with Broadcom arrange connectors in Ubuntu. An alleviation is that Ubuntu gives extra drivers explicitly to Broadcom connectors. Be that as it may, the issue is that to introduce extra drivers in Ubuntu you will require a system association. On the off chance that you have a wired association, it will be anything but difficult to introduce the extra drivers. Yet, in the event that you are limited to the remote system just, you'll need to search for exchange techniques. https://technicalhelplineaustralia.com/apple-repair-centre.php -- 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/1173759 Title: Ubuntu 13.04 can detect wi-fi but can't connect Status in linux package in Ubuntu: Expired Bug description: HP Pavilion laptop with Ralink RT5390 wireless interface 1. Can detect home wi-fi signal but can't connect. Keeps asking for password then "disconnects" over and over again. 2. All other computers, tablets, and smartphones at home can connect to the wi-fi without any trouble at all. 3. HP Pavilion laptop can connect to the internet if tethered to my smartphone (used as a portable wi-fi hotspot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173759/+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 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
FWIW mine appears to have hung during a hidden (invisible to me) step where it was attempting to set a MOK. I had to first kill the existing dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh to #!/bin/bash (I was getting a local variable error), then manually run /usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update- secureboot-policy --enroll-key, then reboot, install the key, finish booting, and dpkg --configure -a. I have no idea if the terminal-gui app that is attempting to ask for a password for the MOK can be surfaced into the apt/dpkg configurating process, but that seems to be the missing link for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1776076 Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) Status in dkms package in Ubuntu: Confirmed Bug description: virtualbox installation getting stuck ProblemType: Package DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.10-dfsg-6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:11:06 2018 ErrorMessage: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) InstallationDate: Installed on 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: virtualbox Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1776076/+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 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
Hey folks, just piping in that I am also having this problem. I am on an encrypted disk, and the build of the kernel modules just hangs. Please let me know if there is anything I can provide to assist in debugging. Note that there appear to be two other related / duplicate bugs: 1769327 and 1775672. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1776076 Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) Status in dkms package in Ubuntu: Confirmed Bug description: virtualbox installation getting stuck ProblemType: Package DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.10-dfsg-6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 10 19:11:06 2018 ErrorMessage: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) InstallationDate: Installed on 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: virtualbox Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1776076/+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 1777337] [NEW] sound says dummy output, but it doesnt appear to be detecting any hardware
Public bug reported: sound says dummy output, but it doesn’t appear to be detecting any hardware ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-151-generic 3.13.0-151.201 ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39 Uname: Linux 3.13.0-151-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Jun 17 18:00:47 2018 HibernationDevice: RESUME=UUID=5b3d6d5c-298e-41a4-a14f-98a99134bc94 InstallationDate: Installed on 2018-06-16 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-151-generic.efi.signed root=UUID=8946eaec-a7d9-4d63-9527-aa6575a235c2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-151-generic N/A linux-backports-modules-3.13.0-151-generic N/A linux-firmware 1.127.24 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ABE dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP350V5C-A0NUK dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ABE:bd11/08/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04ABE.007.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-A0NUK:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX dmi.product.version: P04ABE.007.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1777337 Title: sound says dummy output, but it doesnt appear to be detecting any hardware Status in linux package in Ubuntu: New Bug description: sound says dummy output, but it doesn’t appear to be detecting any hardware ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-151-generic 3.13.0-151.201 ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39 Uname: Linux 3.13.0-151-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Jun 17 18:00:47 2018 HibernationDevice: RESUME=UUID=5b3d6d5c-298e-41a4-a14f-98a99134bc94 InstallationDate: Installed on 2018-06-16 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-151-generic.efi.signed root=UUID=8946eaec-a7d9-4d63-9527-aa6575a235c2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-151-generic N/A linux-backports-modules-3.13.0-151-generic N/A linux-firmware 1.127.24 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ABE dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP350V5C-A0NUK dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ABE:bd11/08/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04ABE.007.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-A0NUK:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX dmi.product.version: P04ABE.007.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
I'm happy to create a new bug report for this, however before I do I wanted to follow up here first. I've been working on a bionic VM template this week and the issue has resurfaced. Client (18.04) reboots daily at 3:00 a.m., and somewhere between 30 minutes and 2 hours later, the CIFS mount point stops responding. Meanwhile other clients (16.04, and Windows) continue chugging along merrily. A reboot sometimes fixes the problem, and sometimes the problem has fixed itself by 8am when I arrive. Here's some syslog debug output after the machine finishes booting. Yesterday it cleared up on its own. Today the server is still down 10 hours later. I would blame Java, except that the whole mount point becomes non- responsive when this happens, not just for that one process. Jun 6 03:00:37 localhost systemd[1]: Reached target Multi-User System. Jun 6 03:00:37 localhost systemd[1]: Starting Execute cloud user/final scripts... Jun 6 03:00:37 localhost systemd[1]: Reached target Graphical Interface. Jun 6 03:00:37 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 6 03:00:38 localhost systemd[1]: Started Update UTMP about System Runlevel Changes. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 running 'modules:final' at Wed, 06 Jun 2018 03:00:38 +. Up 23.72 seconds. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 finished at Wed, 06 Jun 2018 03:00:38 +. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 23.84 seconds Jun 6 03:00:38 localhost systemd[1]: Started Execute cloud user/final scripts. Jun 6 03:00:38 localhost systemd[1]: Reached target Cloud-init target. Jun 6 03:00:38 localhost systemd[1]: Startup finished in 2.806s (kernel) + 21.078s (userspace) = 23.885s. Jun 6 03:00:39 localhost kernel: [ 24.927412] TCP: ens160: Driver has suspect GRO implementation, TCP performance may be compromised. Jun 6 03:00:51 localhost systemd-timesyncd[574]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). Jun 6 03:14:28 localhost systemd[1]: Starting Message of the Day... Jun 6 03:14:30 localhost 50-motd-news[1699]: * Meltdown, Spectre and Ubuntu: What are the attack vectors, Jun 6 03:14:30 localhost 50-motd-news[1699]:how the fixes work, and everything else you need to know Jun 6 03:14:30 localhost 50-motd-news[1699]:- https://ubu.one/u2Know Jun 6 03:14:30 localhost systemd[1]: Started Message of the Day. Jun 6 03:15:48 localhost systemd[1]: Starting Cleanup of Temporary Directories... Jun 6 03:15:48 localhost systemd[1]: Started Cleanup of Temporary Directories. Jun 6 03:17:01 localhost CRON[1770]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:00:01 localhost CRON[1878]: (root) CMD (/mnt/www/config/backup_config.sh) Jun 6 04:17:01 localhost CRON[1916]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] failed to bind to LDAP server ldap://dc01.example.com: Can't contact LDAP server Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] connected to LDAP server ldap://dc02.example.com Jun 6 04:30:01 localhost CRON[1938]: (root) CMD (/usr/sbin/ntpdate time-a.nist.gov time-b.nist.gov 0.pool.ntp.org 1.pool.ntp.org) Jun 6 04:30:01 localhost CRON[1937]: (CRON) info (No MTA installed, discarding output) Jun 6 05:12:02 localhost kernel: [ 7906.798052] CIFS VFS: Server cifshost.example.com has not responded in 120 seconds. Reconnecting... Jun 6 05:12:02 localhost kernel: [ 7906.800726] CIFS VFS: Free previous auth_key.response = 3e802799 Jun 6 05:13:10 localhost kernel: [ 7975.657719] INFO: task java:1672 blocked for more than 120 seconds. Jun 6 05:13:10 localhost kernel: [ 7975.657741] Not tainted 4.15.0-22-generic #24-Ubuntu Jun 6 05:13:10 localhost kernel: [ 7975.657757] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 6 05:13:10 localhost kernel: [ 7975.657779] javaD0 1672 1 0x8000 Jun 6 05:13:10 localhost kernel: [ 7975.657781] Call Trace: Jun 6 05:13:10 localhost kernel: [ 7975.657788] __schedule+0x297/0x8b0 Jun 6 05:13:10 localhost kernel: [ 7975.657791] ? __wake_up+0x13/0x20 Jun 6 05:13:10 localhost kernel: [ 7975.657792] schedule+0x2c/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657795] io_schedule+0x16/0x40 Jun 6 05:13:10 localhost kernel: [ 7975.657798] wait_on_page_bit_common+0xd8/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657800] ? page_cache_tree_insert+0xe0/0xe0 Jun 6 05:13:10 localhost kernel: [ 7975.657801] __filemap_fdatawait_range+0xfa/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657803] filemap_write_and_wait+0x4d/0x90 Jun 6 05:13:10 localhost kernel: [ 7975.657826] cifs_flush+0x43/0x90 [cifs] Jun 6 05:13:10 localhost kernel: [ 7975.657830] filp_close+0x2f/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657832] __close_fd+0x85/0xa0 Jun 6 05:13:10 localhost
[Kernel-packages] [Bug 1727320] Re: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]
this bug seems fixed for me since updating E7470 BIOS to v1.18.5, which was released 12/22/17 here: http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=ND42N=rt as this leaves us with 0 affected users, I think this bug can be closed. -- 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/1727320 Title: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470] Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Gnome-shell crash and restart after the login and the screen flicker 1 time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470 laptop. If I go in display settings I notice a second monitor Synaptics Inc 24'' which doesn't exist in reality. In Wayland after the screen stop flickering I don't have any other problem and that monitor is not present there. xrandr | grep -i ' connected' eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 174mm DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have anything connected to this port With Fedora 26 I don't have this problem but I'm not yet able to find what package is the culprit. I believe this problem is related to Displayport 1.2, I don't have any dock nor I need to connect more than 1 monitor and would be satisfied just having one interface. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Oct 25 11:46:16 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727320/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Why didn't this land in mainline yet? -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: SRU Justification: [Impact] Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work. [Test Case] Touchpad doesn't work on the system. With the patch, touchpad works. [Regression Potential] Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to one device. --- Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
That did it for me on Xenial. root@client:~# uname -a Linux client 4.4.0-98-generic #121~lp1729337 SMP Thu Nov 2 20:53:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@client:~# mount | grep share //server/share on /mnt/share type cifs (rw,nosuid,nodev,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=1.2.3.4,file_mode=0770,dir_mode=0770,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user) Interestingly, as FedeX pointed out, the option (unspecified in my fstab) of sec=ntlmssp has appeared as a new explicit parameter. Makes no difference to me, and it works, just FYI. -- 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/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: We have a cluster of servers that applied a security update overnight and were unable to mount CIFS shares after upgrading to 4.4.0-98. The same machines on 4.4.0-97 were fine the night before, and are fine after downgrading. The only error message CIFS would report, even on verbose, was: [ 257.089876] CIFS VFS: validate protocol negotiate failed: -11 [ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5 Rebooting did not help. Nor did attempting to mount the share manually using mount -t cifs. Here's the offending line from our /etc/fstab (with hostnames sanitized): //server/share /mnt/share cifs rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770 ,exec,soft,noserverino,vers=3.0 0 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 1 07:56 seq crw-rw 1 root audio 116, 33 Nov 1 07:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 1 08:49:47 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1 InstallationDate: Installed on 2016-12-16 (319 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--template--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+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 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
FWIW I can confirm that adding sec=ntlmsspi fixed our issue with 4.4.0-98. root@client:~# mount | grep share //server/share on /mnt/share type cifs (rw,nosuid,nodev,relatime,vers=3.0,sec=ntlmsspi,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=10.4.0.30,file_mode=0770,dir_mode=0770,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user) root@client:~# uname -a Linux client 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: We have a cluster of servers that applied a security update overnight and were unable to mount CIFS shares after upgrading to 4.4.0-98. The same machines on 4.4.0-97 were fine the night before, and are fine after downgrading. The only error message CIFS would report, even on verbose, was: [ 257.089876] CIFS VFS: validate protocol negotiate failed: -11 [ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5 Rebooting did not help. Nor did attempting to mount the share manually using mount -t cifs. Here's the offending line from our /etc/fstab (with hostnames sanitized): //server/share /mnt/share cifs rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770 ,exec,soft,noserverino,vers=3.0 0 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 1 07:56 seq crw-rw 1 root audio 116, 33 Nov 1 07:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 1 08:49:47 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1 InstallationDate: Installed on 2016-12-16 (319 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--template--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+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
