December 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219522] New: Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 30 Dec '24

30 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 Bug ID: 1219522 Summary: Kernel panic with 6.7.x version 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: e.kleinmentink(a)zonnet.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872422 --> https://bugzilla.suse.com/attachment.cgi?id=872422&action=edit dmesg 6.6.11-1 kernel I get a kernel panic since the 6.7.x kernels. The capslock key is flickering and if i use the "recovery mode" i usually see: [T8] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf01fa3/0x940300/0x12e800/0x400000, board id: 3276, fw id: 2700068 [T8] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [T8] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2 I have no idea how to debug this. No error message. In the past i applied a kernel bisect (for debian i think) but i could not find a guide for Tumbleweed. Hardware: Lenovo T580 Grub menu contains: * 6.7.2-1 * 6.7.1-2 * 6.6.11-1 Included a "dmesg" output of a normal boot with the "6.6.11-1" kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 25

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 30 Dec '24

30 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 https://bugzilla.suse.com/show_bug.cgi?id=1220088#c42 --- Comment #42 from Paul Graff <pj.opensuse(a)gmx.com> --- (In reply to Takashi Iwai from comment #41) > Unfortunately there is no such state. We may close as WONTFIX but you can > reopen this at any time later, too. Thank you for letting me know. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 30 Dec '24

30 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 https://bugzilla.suse.com/show_bug.cgi?id=1220088#c41 --- Comment #41 from Takashi Iwai <tiwai(a)suse.com> --- Unfortunately there is no such state. We may close as WONTFIX but you can reopen this at any time later, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234860] New: Regression: Lenovo T14s Gen 2 AMD crashes on resume from suspend on kernel 6.12
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234860 Bug ID: 1234860 Summary: Regression: Lenovo T14s Gen 2 AMD crashes on resume from suspend on kernel 6.12 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The laptop comes up far enough from suspend to show the open applications on the desktop but the mouse doesn't react. The applications are NOT frozen - journalctl shows something (even though redirecting it into a file didn't show any content in that file after going into suspend. Then something really strange happens: - The display brightness goes through all the possible brightness steps - When reaching the full brightness it goes back to dark and starts over again - This process repeats faster and faster - Finally the screen goes completely dark -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1234782] Kernel 6.12.6 with amdgpu breaks brightness control after resume
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234782 https://bugzilla.suse.com/show_bug.cgi?id=1234782#c5 Frank Krüger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fkrueger@mailbox. | |org) | --- Comment #5 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Jiri Slaby from comment #4) > (In reply to Frank Krüger from comment #3) > > Added upstream bug report: > > https://gitlab.freedesktop.org/drm/amd/-/issues/3853 > > I took: > https://gitlab.freedesktop.org/drm/amd/-/issues/3853#note_2714815 > > into: > https://build.opensuse.org/project/monitor/home:jirislaby:bsc1234782 > > instead of the revert. Is it fixed there? I can confirm that the unofficial patch provided in https://gitlab.freedesktop.org/drm/amd/-/issues/3853#note_2714815 solves the issue. We are still waiting for Alex Deucher's (AMD) official response/patch anyway. Thank you! -- 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 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c15 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Flags|needinfo?(nfbrown(a)suse.com) | Status|NEW |RESOLVED --- Comment #15 from Petr Vorel <petr.vorel(a)suse.com> --- I'm closing this 2 years old bug. pynfs is now passing on Tumbleweed, it was fixed by using more up-to-date git repository [1] instead of the old one [2] Also, we increased RAM to 4 GB (via QEMURAM=4096) to avoid some failures due low RAM (not related to this, but to other failures). [1] https://git.linux-nfs.org/?p=cdmackay/pynfs.git;a=summary [2] https://git.linux-nfs.org/?p=bfields/pynfs.git;a=summary -- 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 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1222132 https://bugzilla.suse.com/show_bug.cgi?id=1222132#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |jslaby(a)suse.com Status|NEW |RESOLVED --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- 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 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c14 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(nfbrown(a)suse.com) --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Petr Vorel from comment #13) > (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=c75f65983498a3254e3970da86eb6954415cac01 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1220119] New: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:"
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220119 Bug ID: 1220119 Summary: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:" 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: jwiesner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Some tests running on o3 (openQA instance on https://openqa.opensuse.org/) triggers in dmesg. All tests run in VM via qemu. This is on x86_64 on my private openQA worker by ltp_net_tcp_cmds, triggered for 2 tests: arp and host (both tests did not fail): OpenQA::run_ltp.pm: Starting ipneigh01_arp [ 410.818828][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820365][ C0] clocksource: 'kvm-clock' wd_nsec: 506724586 wd_now: 610448443a wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821824][ C0] clocksource: 'tsc' cs_nsec: 49302930542 cs_now: 17c1364ba0a cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.823293][ C0] clocksource: Clocksource 'tsc' skewed 48796205956 ns (48796 ms) over watchdog 'kvm-clock' interval of 506724586 ns (506 ms) [ 410.824843][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.825707][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.109710][T28135] Initializing XFRM netlink socket OpenQA::run_ltp.pm: Starting ipneigh01_ip OpenQA::run_ltp.pm: Starting arping01 OpenQA::run_ltp.pm: Starting clockdiff01 OpenQA::run_ltp.pm: Starting ftp OpenQA::run_ltp.pm: Starting host [ 410.818845][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820687][ C0] clocksource: 'kvm-clock' wd_nsec: 506741379 wd_now: 61044885d3 wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821794][ C0] clocksource: 'tsc' cs_nsec: 804834172 cs_now: 154a546a082 cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.822919][ C0] clocksource: Clocksource 'tsc' skewed 298092793 ns (298 ms) over watchdog 'kvm-clock' interval of 506741379 ns (506 ms) [ 410.824088][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.824768][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.126759][T28138] Initializing XFRM netlink socket Also, originally I noted this on ltp_net_tcp_cmds running on ppc64le on o3 (kernel tests in https://openqa.opensuse.org/group_overview/32) where host test keeps failing (but arp test is working), I don't see it on ltp_net_tcp_cmds on x86_64 on o3. I was not able to trigger this on VM on my laptop (x86_64). Others found that systemd-networkd test on Tumbleweed on x86_64 (https://openqa.opensuse.org/group_overview/1) [ 570.754611][ C0] Showing busy workqueues and worker pools: [ 570.755654][ C0] workqueue events: flags=0x0 [ 570.756580][ C0] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 [ 570.756586][ C0] pending: drm_fb_helper_damage_work [ 570.759551][ C0] sysrq: Show Blocked State zDBFr-0- [ 311.682306][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 311.684482][ C0] clocksource: 'kvm-clock' wd_nsec: 621509306 wd_now: 49d9caac63 wd_last: 49b4bf31a9 mask: ffffffffffffffff [ 311.686513][ C0] clocksource: 'tsc' cs_nsec: 952336665 cs_now: a3a422af12 cs_last: a327415f8e mask: ffffffffffffffff [ 311.688559][ C0] clocksource: Clocksource 'tsc' skewed 330827359 ns (330 ms) over watchdog 'kvm-clock' interval of 621509306 ns (621 ms) [ 311.690452][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 311.691559][ C0] tsc: Marking TSC unstable due to clocksource watchdog Test runs also on aarch64, but error is not there. Is it a problem of openQA setup? There are other bugs. -- You are receiving this mail because: You are the assignee for the bug.

1 37

[Bug 1217748] Display corruption with spesific applications in Gnome-wayland session
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217748 https://bugzilla.suse.com/show_bug.cgi?id=1217748#c11 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #11 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0