June 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1200516] Machine locked full. Nouveau related
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200516 https://bugzilla.suse.com/show_bug.cgi?id=1200516#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos.e.r(a)opensuse.org, | |tiwai(a)suse.com Flags| |needinfo?(carlos.e.r@opensu | |se.org) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you check with Leap 15.4 kernel? The fix of nouveau for 15.3 kernel can't be expected (unless you can point out an exact upstream fix commit). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200539] booting only in nomodeset; 4K display but only gets 1280x1024; automatic screen rotation not working; does not come back from sleep mode-need to hard reboot;
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200539 https://bugzilla.suse.com/show_bug.cgi?id=1200539#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jphass(a)hotmail.com, | |tiwai(a)suse.com Flags| |needinfo?(jphass(a)hotmail.co | |m) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Please boot with nomodeset, and make the system running. Then run hwinfo and attach the output to Bugzilla (don't paste). And we need to check what's going on without nomodeset; please try to boot without nomodeset, but additionally with drm.debug=0x1e log_buf_len=16M options, and confirm that you get no proper screen. Reboot with ctrl-alt-del (you might need to press multiple times quickly) but with nomodeset again. Then get the previous boot log (e.g. the output of "journalctl -k -b-1"). Compress the kernel log and attach to Bugzilla. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200541] Tumbleweed Kernel 5.18.1 nvme SUBNQN not valid quirk is likely not enabled
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200541 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200519] missing internal.h header for x86 in kernel-devel package
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200519 https://bugzilla.suse.com/show_bug.cgi?id=1200519#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FEATURE --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Yes, it's intended. The files got removed in the upstream. If you're referring to those files due to the build failure of zfs KMP, it must be fixed in zfs package side now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200547] Hang on boot
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200547 https://bugzilla.suse.com/show_bug.cgi?id=1200547#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hr.denzler(a)bluewin.ch Flags| |needinfo?(hr.denzler@bluewi | |n.ch) --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Hm, does the bug never happen unless you enable the splash screen? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200600] [Build 20220614] openQA test fails in inotify12
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200600 https://bugzilla.suse.com/show_bug.cgi?id=1200600#c1 Jan Kara <jack(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|kernel-bugs(a)opensuse.org |jack(a)suse.com --- Comment #1 from Jan Kara <jack(a)suse.com> --- Indeed, we didn't backport a32e697cda27 ("inotify: show inotify mask flags in proc fdinfo") to our kernels yet. Tumbleweed will get it from upstream (it went to kernel 5.19-rc1) but we should be picking up this fix at least to all actively maintained branches... I'll do that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199901] New: [RPi4] Camera module not detected
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199901 Bug ID: 1199901 Summary: [RPi4] Camera module not detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, guillaume.gardet(a)opensuse.org, ivan.ivanov(a)suse.com, m.szczepaniak.000(a)gmail.com Found By: --- Blocker: --- Created attachment 859212 --> https://bugzilla.suse.com/attachment.cgi?id=859212&action=edit dmesg I'm using a raspberry Pi 4B and followed the steps at https://en.opensuse.org/HCL:Raspberry_Pi_Camera_Modules to get the camera module https://www.berrybase.de/raspberry-pi/raspberry-pi-computer/kameras/raspber… working. It is connected to the camera header, raspberrypi-firmware-extra-pi4 and raspberrypi-firmware-extra is installed. Updated /boot/efi/config.txt ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # Default gpu_mem value is 76 for 1GB (or greater) and 64 for less. Min 16 - Max 512 MB # See: https://www.raspberrypi.com/documentation/computers/config_txt.html#gpu_mem # We don't need that much memory reserved for it, because we drive most hardware # from Linux, not the VPU OS #gpu_mem=32 # start_x is used to enable the camera module (and must be set here - boo#1192047) # and requires to install raspberrypi-firmware-extra or raspberrypi-firmware-extra-pi4 # start_x=1 start_x=1 # gpu_mem needs to be increased when start_x is used, 128 is the minimum there # gpu_mem=128 gpu_mem=128 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I rebooted but I don't get a /dev/video* device -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1200380] New: [amdgpu] OpenCL workload can reliably crash GPU unrecoverably and also reliably cause reboot
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200380 Bug ID: 1200380 Summary: [amdgpu] OpenCL workload can reliably crash GPU unrecoverably and also reliably cause reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andreas_nordal_4(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- AMD Ryzen 5 3400G with Radeon Vega Graphics Linux 5.18.1-1-default amdocl 11.12-1.27 from https://download.opensuse.org/repositories/home:/patrikjakobsson:/aomp/open… * I have one (proprietary) OpenCL workload that reliably causes my computer to freeze and reboot. * In investigating this, I'm trying out various test programs that do a subset of it. A common theme is that after 2-3 runs, with kernel traces appearing in dmesg, the GPU disappears and never comes back (at least the OpenCL part): The desktop is responsive and fine afterwards, thankfully, but clinfo reports "Number of devices 0", and I have to manually reboot to fix it. The first run, with the trace in dmesg: [ 96.228040] [drm] Fence fallback timer expired on ring gfx [ 119.268047] [drm] Fence fallback timer expired on ring gfx [ 123.972050] [drm] Fence fallback timer expired on ring gfx [ 124.676047] [drm] Fence fallback timer expired on ring gfx [ 138.014780] ------------[ cut here ]------------ [ 138.014784] refcount_t: decrement hit 0; leaking memory. [ 138.014789] WARNING: CPU: 5 PID: 469 at lib/refcount.c:31 refcount_warn_saturate+0xe5/0xf0 [ 138.014795] Modules linked in: zram xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc overlay cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver fscache netfs af_packet iscsi_ibft iscsi_boot_sysfs dmi_sysfs joydev r8169 atlantic realtek mdio_devres libphy macsec hid_generic intel_rapl_msr intel_rapl_common usbhid snd_hda_codec_realtek snd_hda_codec_generic edac_mce_amd ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep eeepc_wmi asus_wmi snd_pcm kvm battery snd_timer sparse_keymap snd platform_profile irqbypass rfkill wmi_bmof pcspkr efi_pstore k10temp i2c_piix4 soundcore tiny_power_button gpio_amdpt gpio_generic button acpi_cpufreq nls_iso8859_1 nls_cp437 vfat fat fuse configfs ip_tables x_tables ext4 mbcache jbd2 amdgpu crct10dif_pclmul [ 138.014837] crc32_pclmul crc32c_intel ghash_clmulni_intel drm_ttm_helper ttm iommu_v2 gpu_sched i2c_algo_bit drm_dp_helper drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci crypto_simd xhci_pci_renesas cryptd drm xhci_hcd nvme sp5100_tco nvme_core cec ccp usbcore rc_core wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs [ 138.014855] CPU: 5 PID: 469 Comm: kworker/5:2 Not tainted 5.18.1-1-default #1 openSUSE Tumbleweed 76e6f98ac75e9529b1c9bcf308333727a2e8ebe3 [ 138.014858] Hardware name: Komplett Komplett PC/PRIME B450-PLUS, BIOS 2008 12/06/2019 [ 138.014859] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu] [ 138.015078] RIP: 0010:refcount_warn_saturate+0xe5/0xf0 [ 138.015081] Code: 48 c7 c7 98 ab 8b 94 c6 05 53 b6 9f 01 01 e8 f3 7e 52 00 0f 0b c3 cc 48 c7 c7 68 ab 8b 94 c6 05 3d b6 9f 01 01 e8 dc 7e 52 00 <0f> 0b c3 cc 0f 1f 80 00 00 00 00 8b 07 3d 00 00 00 c0 74 12 83 f8 [ 138.015082] RSP: 0018:ffff9d34807dfde8 EFLAGS: 00010282 [ 138.015084] RAX: 0000000000000000 RBX: ffff8f9929bec000 RCX: 0000000000000027 [ 138.015085] RDX: ffff8f9fc0b62528 RSI: 0000000000000001 RDI: ffff8f9fc0b62520 [ 138.015086] RBP: ffff8f9929bec000 R08: 0000000000000000 R09: ffff9d34807dfc18 [ 138.015087] R10: 0000000000000003 R11: ffff8f9fc07fffe8 R12: 0000000000000001 [ 138.015087] R13: ffff8f98c2fb4800 R14: ffff8f98c2fb4b90 R15: ffff8f98c807ec00 [ 138.015089] FS: 0000000000000000(0000) GS:ffff8f9fc0b40000(0000) knlGS:0000000000000000 [ 138.015090] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 138.015091] CR2: 00007f0e47700000 CR3: 0000000694010000 CR4: 00000000003506e0 [ 138.015092] Call Trace: [ 138.015094] <TASK> [ 138.015096] put_pasid_state_wait+0x9f/0xb0 [iommu_v2 6923f1fc45e94345ae677d5df84b0cda035fac36] [ 138.015100] ? mmu_notifier_unregister+0xa9/0xe0 [ 138.015103] amd_iommu_unbind_pasid+0xa5/0xc0 [iommu_v2 6923f1fc45e94345ae677d5df84b0cda035fac36] [ 138.015106] kfd_iommu_unbind_process+0x4b/0x60 [amdgpu 425139e59bdaa506cde69fb30b88f0810eed06e1] [ 138.015303] kfd_process_wq_release+0x1e5/0x350 [amdgpu 425139e59bdaa506cde69fb30b88f0810eed06e1] [ 138.015497] process_one_work+0x208/0x3c0 [ 138.015500] worker_thread+0x4a/0x3b0 [ 138.015502] ? process_one_work+0x3c0/0x3c0 [ 138.015503] kthread+0xda/0x100 [ 138.015505] ? kthread_complete_and_exit+0x20/0x20 [ 138.015507] ret_from_fork+0x22/0x30 [ 138.015510] </TASK> [ 138.015511] ---[ end trace 0000000000000000 ]--- The second run, when the GPU disappeared: [ 157.924040] [drm] Fence fallback timer expired on ring gfx [ 175.524041] [drm] Fence fallback timer expired on ring gfx [ 197.372016] amdgpu: qcm fence wait loop timeout expired [ 197.372021] amdgpu: The cp might be in an unrecoverable state due to an unsuccessful queues preemption [ 197.372062] amdgpu 0000:07:00.0: amdgpu: GPU reset begin! [ 197.372071] amdgpu: Failed to suspend process 0x800c As for the freeze and reboot, I don't have a trace of that (yet). I checked journalctl, but it seems that part didn't survive. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200547] Hang on boot
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200547 http://bugzilla.opensuse.org/show_bug.cgi?id=1200547#c5 --- Comment #5 from Hans-Rudi Denzler <hr.denzler(a)bluewin.ch> --- By deleting the 2 optional parameters from the kernel command line "splash = silent quiet" I get no hang on boot by avoiding the splash screen as I expected it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193652] New: Logitech mouse and keyboard stop working on the latest kernel.
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 Bug ID: 1193652 Summary: Logitech mouse and keyboard stop working on the latest kernel. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: benthomasgeorge7899(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854509 --> http://bugzilla.opensuse.org/attachment.cgi?id=854509&action=edit Logs of the said issue The mouse and keyboard stopped working randomly first while working. Later on reboot it works fine with bios and grub encryption password but within minutes the kernel is loaded it disconnects the keyboard and mouse. Possible reasons have been checked for- 1. Issue is not cause due to tlp 2. Issue not caused due to autosuspend of usb. Both the mouse and keyboard and mouse are working fine on the previous kernel 5.15.5-1. Rollback to the previous kernel has solved the issue. -- You are receiving this mail because: You are the assignee for the bug.

1 57