March 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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

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

25 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c12 --- Comment #12 from Neil Brown <nfbrown(a)suse.com> --- (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. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

25 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c11 --- Comment #11 from Yong Sun <yosun(a)suse.com> --- (In reply to Petr Vorel from comment #9) > (In reply to Yong Sun from comment #6) > > I could reproduce some failures in VM and limited RAM to 2GB. But not that > > many fails as in openqa. > > The fails are: CID5, CID3, CID4d, RENEW3, LKU10, LOCK24, CMT4, CLOSE9, CLOSE8 > > For a record, it's an upstream bug, fix [1] is hopefully going to be merged > soon. > > [1] > https://lore.kernel.org/linux-nfs/20230313112401.20488-6-jlayton@kernel.org/ I think the patch is already merged into upstream. And maybe we could close the current bug. For now, Tumbleweed only has CID* fails(https://openqa.opensuse.org/tests/4034155#step/CID5/2), and SP6 has only CID5 fails sporadically. Both issues could covered by https://bugzilla.opensuse.org/show_bug.cgi?id=1217488 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219195] /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_min increased from 6.6. to 6.7 way too much
by bugzilla_noreply＠suse.com 24 Mar '24

24 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219195 https://bugzilla.suse.com/show_bug.cgi?id=1219195#c5 --- Comment #5 from Benedict Broy <benedictbroy(a)gmx.de> --- If I understand correctly, this is - unfortunately - intended behaviour, so I'd suggest marking it as wontfix instead of resolved, if that's ok. Thanks! -- 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 24 Mar '24

24 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c42 --- Comment #42 from Paolo De Pasquale <paolo.depasquale(a)suse.com> --- Created attachment 873758 --> https://bugzilla.suse.com/attachment.cgi?id=873758&action=edit lenovo-tumbleweed-hwinfo -- 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 24 Mar '24

24 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c41 Paolo De Pasquale <paolo.depasquale(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paolo.depasquale(a)suse.com --- Comment #41 from Paolo De Pasquale <paolo.depasquale(a)suse.com> --- Created attachment 873757 --> https://bugzilla.suse.com/attachment.cgi?id=873757&action=edit lenovo-tumbleweed-dmesg Same issue seen on my Lenovo after updating Tumbleweed to version 20240321 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221884] Kernel panics kworker/3:2
by bugzilla_noreply＠suse.com 23 Mar '24

23 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221884 https://bugzilla.suse.com/show_bug.cgi?id=1221884#c1 Anthony Iliopoulos <ailiopoulos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ailiopoulos(a)suse.com --- Comment #1 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- looks like another instance of bsc#1220814 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221884] New: Kernel panics kworker/3:2
by bugzilla_noreply＠suse.com 23 Mar '24

23 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221884 Bug ID: 1221884 Summary: Kernel panics kworker/3:2 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: luna.dragon(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Over the past few weeks I've been suffering from kernel panics so I setup `kdump`. Today I had another kernel panic and using crash I have gotten a backtrace ``` PID: 4288 TASK: ffff8e18c865af40 CPU: 3 COMMAND: "kworker/3:2" #0 [ffffabe5a583fb48] machine_kexec at ffffffffa108fe0f #1 [ffffabe5a583fba0] __crash_kexec at ffffffffa11c7e0e #2 [ffffabe5a583fc60] crash_kexec at ffffffffa11c92a4 #3 [ffffabe5a583fc68] oops_end at ffffffffa10457c4 #4 [ffffabe5a583fc88] page_fault_oops at ffffffffa10a53f1 #5 [ffffabe5a583fd08] exc_page_fault at ffffffffa1ccfc21 #6 [ffffabe5a583fd30] asm_exc_page_fault at ffffffffa1e012a6 [exception RIP: rb_first+15] RIP: ffffffffa1cb7a8f RSP: ffffabe5a583fde0 RFLAGS: 00010206 RAX: 0000000000003593 RBX: ffff8e18842b7780 RCX: ffffcd4cdc678a90 RDX: 0000000000003593 RSI: 0000000000000000 RDI: ffff8e1886681498 RBP: ffff8e22b4bd9d80 R8: 0000000000000246 R9: 00000000010000ff R10: 00000000010000ff R11: fefefefefefefeff R12: 0000000000000000 R13: ffff8e1886681498 R14: ffff8e19216b3000 R15: ffff8e18817e8ab0 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000 #7 [ffffabe5a583fde0] simple_xattrs_free at ffffffffa1453ba9 #8 [ffffabe5a583fe08] kernfs_put at ffffffffa14dd160 #9 [ffffabe5a583fe30] css_free_rwork_fn at ffffffffa11d59d5 #10 [ffffabe5a583fe68] process_one_work at ffffffffa10e8635 #11 [ffffabe5a583fea8] worker_thread at ffffffffa10e97e5 #12 [ffffabe5a583fef8] kthread at ffffffffa10f38c5 #13 [ffffabe5a583ff30] ret_from_fork at ffffffffa1050f41 #14 [ffffabe5a583ff50] ret_from_fork_asm at ffffffffa100383b ``` Please inform me if more information/data is required I will do my best to provide it -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219653] New: Enable CONFIG_GDB_SCRIPTS
by bugzilla_noreply＠suse.com 22 Mar '24

22 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219653 Bug ID: 1219653 Summary: Enable CONFIG_GDB_SCRIPTS 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CONFIG_GDB_SCRIPTS installs useful gdb macros. See: https://www.kernel.org/doc/html/latest/dev-tools/gdb-kernel-debugging.html -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1221867] New: Can read /proc/pid/exe but test -r /proc/pid/exe fails
by bugzilla_noreply＠suse.com 22 Mar '24

22 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221867 Bug ID: 1221867 Summary: Can read /proc/pid/exe but test -r /proc/pid/exe fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Consider the following script: ... $ cat try.sh #!/bin/sh kill -9 $(pidof mysleep) 2> /dev/null cp /usr/bin/sleep mysleep md5sum mysleep ./mysleep 10000 & ( sleep 1 pid=$(pidof mysleep) echo "PID: $pid" test -r /proc/$pid/exe echo $? md5sum /proc/$pid/exe kill -9 $(pidof mysleep) 2> /dev/null ) ... If we run it, we get: ... $ ./try.sh 6a85b2e53dce34ce2c35129b5b20c50b mysleep PID: 4462 0 6a85b2e53dce34ce2c35129b5b20c50b /proc/4462/exe ... So: - we copy sleep, calculate its md5sum, run it, and get the pid - we check if we can read /proc/$pid/exe - we calculate the md5sum of /proc/$pid/exe and we find that: - we can read /proc/$pid/exe, and - we are able to calculate the same md5sum for /proc/$pid/exe. Now consider: ... $ cat ./try2.sh #!/bin/sh sudo \ -E \ capsh \ --caps="cap_setpcap,cap_setuid,cap_setgid+ep cap_sys_ptrace+eip" \ --keep=1 \ --user=$USER \ --addamb="cap_sys_ptrace" \ --shell=./try.sh -- ... This time, we get: ... $ ./try2.sh [sudo] password for root: 6a85b2e53dce34ce2c35129b5b20c50b mysleep PID: 4536 1 6a85b2e53dce34ce2c35129b5b20c50b /proc/4536/exe ... So, this seems contradictory: - according to test -r, we cannot read /proc/$pid/exe - but according to md5sum, we can read /proc/$pid/exe This hit in gdb ( https://sourceware.org/bugzilla/show_bug.cgi?id=31528 ), where we decide not to try to open /proc/$pid/exe to get the symbols of an exec we've attached to, because first access(..., R_OK) is called to determine whether gdb can open it, which replies no. If we skip the access check, we're able to read the symbols and the test-case passes. However, there's the possibility that this is a kernel bug: - if access is supposed to be unavailable, but in fact it is, it looks like a bug to me - if access is supposed to be available, but we don't advertise that through access, it might be a bug, or it might be an inconvenience that ideally would be documented. I came across https://bugzilla.kernel.org/show_bug.cgi?id=211593 , which I think comes from https://bugzilla.suse.com/show_bug.cgi?id=1216352 , which are probably related. From what I understand from reading those two PRs, I probably need to fix gdb to avoid using readlink for /proc/$pid/exe. Regardless, I would like to understand if I stumbled upon a kernel bug and whether it needs filing/fixing upstream in some form or another. This is with opensuse leap 15.4, with a recent kernel: ... $ uname -a Linux xerxes 6.8.1-lp155.4.gd922afa-default #1 SMP PREEMPT_DYNAMIC Tue Mar 19 07:32:20 UTC 2024 (d922afa) x86_64 x86_64 x86_64 GNU/Linux ... -- You are receiving this mail because: You are the assignee for the bug.

1 0