April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c33 --- Comment #33 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- can you create a older kernel with the patch applied? Something like 6.8.1-1 (or older). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222249] New: Systemtap fails to run on v6.8 kernel
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222249 Bug ID: 1222249 Summary: Systemtap fails to run on v6.8 kernel 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: tonyj(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While testing fixes for bsc#1221706 I noticed that systemtap was not functioning correctly on v6.8 based kernels. # stap -e 'probe oneshot { println("hello world") }' In file included from /usr/share/systemtap/runtime/linux/access_process_vm.h:6, from /usr/share/systemtap/runtime/linux/runtime.h:315, from /usr/share/systemtap/runtime/runtime.h:26, from /tmp/stapQfrt4d/stap_12c74092879671ed4cd208bf7321d2eb_983_src.c:21: /usr/share/systemtap/runtime/linux/access_process_vm.h: In function ‘__access_process_vm_’: /usr/share/systemtap/runtime/linux/stap_mmap_lock.h:10:43: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 10 | #define mmap_read_lock(mm) down_read(&mm->mmap_sem) | ^~~~~~~~ /usr/share/systemtap/runtime/linux/access_process_vm.h:33:3: note: in expansion of macro ‘mmap_read_lock’ 33 | mmap_read_lock (mm); | ^~~~~~~~~~~~~~ /usr/share/systemtap/runtime/linux/access_process_vm.h:63:36: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] ... ... -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com, | |william.brown(a)suse.com Flags| |needinfo?(william.brown@sus | |e.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to William Brown from comment #0) > 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. The above looks like a pretty old issue (around 2020). That said, no changes done in kernel side? Or do you suggest something we need to change in config or such? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222014] Radeon video driver fails on the last 2 kernels after last night's update
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222014 https://bugzilla.suse.com/show_bug.cgi?id=1222014#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo?(rskunath(a)gmail.co | |m) | Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Let's close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c43 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opendreas(a)gmail.c | |om) --- Comment #43 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Andreas from comment #40) > The following message contains patches from the Intel developer. > https://patchwork.freedesktop.org/series/125157/ The patches aren't included in the upstream (yet?). I'm building a test kernel for SLE15-SP6 in OBS home:tiwai:bsc1193599-sp6 repo. The package will appear later at http://download.opensuse.org/repositories/home:/tiwai:/bsc1193599-sp6/pool/ Please give it a try later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219188] New: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219188 Bug ID: 1219188 Summary: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jack(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Starting from build 20240123, which brought kernel 6.7 splice fail: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded Jan, could you please have look whether it's a test bug or mainline kernel bug? I can reproduce the problem also on mainline 6.8.0-rc1 (testing with rapido). -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c30 --- Comment #30 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- installed kernel-default-6.8.2-2.1.gb88b81e.x86_64.rpm and restarted about 20 times. Can not trigger the kernel panic. Is it possible the issue is fixed recently? I assume we should look at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/driv…. This commit seems suspicious because it seems a timing issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/d… Not sure if that would even result in a kernel panic. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c28 --- Comment #28 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- I get a 404 for that link. fwiw: If i remember correctly i disabled the touchpad that years ago in the bios. -- You are receiving this mail because: You are the assignee for the bug.

1 0