March 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1221512] scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 29 Mar '24

29 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221512 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212696] Q965 with modesetting DIX GPU HANG
by bugzilla_noreply＠suse.com 29 Mar '24

29 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1212696 https://bugzilla.suse.com/show_bug.cgi?id=1212696#c23 --- Comment #23 from Felix Miata <mrmazda(a)earthlink.net> --- Comment added upstream (latest 15.5, 15.6 & Debian kernels continue to produce problem; TW 6.6.22-longterm does not): https://gitlab.freedesktop.org/xorg/xserver/-/issues/1593 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1213778] 15.5 upgrade: keyboard and mouse do not respond after resume from suspend to RAM
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213778 https://bugzilla.suse.com/show_bug.cgi?id=1213778#c16 Vadim Krevs <vkrevs(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #16 from Vadim Krevs <vkrevs(a)yahoo.com> --- Apologies for not posting an update for a long while. I had replaced my old AMD Radeon RX 580 with an NVIDIA Geforce RTX 4060Ti card, installed the latest proprietary NVIDIA driver, and the issue went away. Feel free to close this issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222132] New: kernel-firmware-20240322 breaks iwlwifi
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1222132 Bug ID: 1222132 Summary: kernel-firmware-20240322 breaks iwlwifi 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: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873903 --> https://bugzilla.suse.com/attachment.cgi?id=873903&action=edit Kernel logs for the described situation This is on TW snapshot 20240326; when I run "iwlist wlan0 scanning", the kernel issues a "Microcode SW error" resulting in a full Call Trace. See the attached file for all details. FWIW, this error happens with both kernels, ie. kernel-default and kernel-longterm! -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1222132] kernel-firmware-20240322 breaks iwlwifi
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1222132 https://bugzilla.suse.com/show_bug.cgi?id=1222132#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Then it's likely no regression, but it's triggered casually by some other reason. The error you've seen is basically a firmware error, and it happens occasionally via periodic scanning, AFAIK. If you have a proper way to reproduce the problem, at best, report it to the upstream (e.g. linux-wireless ML). There are quite a few similar report on the upstream bugzilla.kernel.org, and you can join there, too (although I doubt it would help). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222132] kernel-firmware-20240322 breaks iwlwifi
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1222132 https://bugzilla.suse.com/show_bug.cgi?id=1222132#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- I asked it because there was no change in iwlwifi-* firmware files in the previous update of kernel-firmware packages. If any, I suspect rather it's a kernel code change that broke. The same breakage may happen on slowroll just because the upstream stable tree can take the same backport. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222132] kernel-firmware-20240322 breaks iwlwifi
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1222132 https://bugzilla.suse.com/show_bug.cgi?id=1222132#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(manfred.h(a)gmx.net | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you confirm that downgrading the previous kernel-firmware(-iwlwifi) package fixes the problem again? The old package is found in TW history repo http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] New: tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 Bug ID: 1222098 Summary: tpm resource manager - tpm2_save-context failed with error 0x0901 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: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- dmesg shows: // [ 200.968893] tpm tpm0: tpm2_save_context: failed with a TPM error 0x0901 // [ 200.972263] tpm tpm0: A TPM error (459) occurred flushing context // [ 200.974210] tpm tpm0: tpm2_commit_space: error -14 This is discussed in the tpm2 tools project here: https://github.com/tpm2-software/tpm2-tools/issues/2279 The summary is that the in kernel resource managers context gap max is too low. This should be increased to prevent resource exhaustion. It is actually possible to trigger this even if you are correctly flushing session contexts after use. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211975] New: freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 26 Mar '24

26 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1211975 Bug ID: 1211975 Summary: freeze with flip_done time out when external monitor attached 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: mattm3a(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Only when external monitor is attached, display freezes for a Lenovo T14. External monitor is connected via HDMI. Mean time between freeze ~1 hour. Output from terminal (CTRL+ALT+F1) looks something like this (from image, not copied in text form): [374.123930][ T1729] i915 0000:00:02.0: [drm] *ERROR* flip_done timed out [374.123938][ T1729] i915 0000:00:02.0: [drm] *ERROR* [PLANE:82:plane 1B] commit wait timed out lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c) lsb-release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230531 Codename: n/a uname -srvp Linux 6.3.4-1-default #1 SMP PREEMPT_DYNAMIC Mon May 29 06:22:29 UTC 2023 (2c66b1f) x86_64 I think this issue first appeared for me in mid-May, but I'm unsure of exactly what Tumbleweed update that was. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 26 Mar '24

26 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c13 --- Comment #13 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to Neil Brown from comment #12) > (In reply to Radoslav Tzvetkov from comment #10) > > Ideally, we must get it with the Kernel next week, if not integrated already > > The problem is not in the kernel so no fix will be landing in the kernel. > > The problem is with the test code. NFS4ERR_DELAY should *always* be an > acceptable return code - it means the request should be retired after a > delay. There is a fix, which got merged in cdmackay git [1] we use for testing (the newest one). The original report without this fix (Dec 2022) reported in comment #6 9 errors, but now with this fix we have 6 errors (CID*), some of them were not in the original report. @Neil Do you think that testing code is still wrong and needs further fix? [1] https://git.linux-nfs.org/?p=cdmackay/pynfs.git;a=commit;h=c75f65983498a325… -- You are receiving this mail because: You are the assignee for the bug.

1 0