December 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1212877] [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 https://bugzilla.suse.com/show_bug.cgi?id=1212877#c27 --- Comment #27 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- > > > But it would make more sense to report and handle this upstream. > > Given it's a longstanding problem, it is an upstream issue, so this would be > better addressed upstream. You will likely get more help and progress there > than here. Having the bug open here won't help you much as was already > demonstrated, sorry. Yes. I think Stefan Wahren has been working on this. Unfortunately I can not find reference to the patches at the moment. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c27 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #27 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #26) > > origin/master:config/arm64/default:CONFIG_HZ_300=y > > origin/master:config/armv6hl/default:CONFIG_HZ_300=y > > origin/master:config/armv7hl/default:CONFIG_HZ_300=y > > origin/master:config/i386/pae:CONFIG_HZ_300=y > > origin/master:config/ppc64le/default:CONFIG_HZ_300=y > > origin/master:config/riscv64/default:CONFIG_HZ_300=y > > origin/master:config/s390x/default:CONFIG_HZ_300=y > > origin/master:config/s390x/zfcpdump:CONFIG_HZ_300=y > > origin/master:config/x86_64/default:CONFIG_HZ_300=y > > > > We seem we have switched master after all? > > I am going to unify master+stable to SUSE-2025 now. master done, stable will inherit later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189283] kernel-obs-build needs af_alg
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1189283 https://bugzilla.suse.com/show_bug.cgi?id=1189283#c12 --- Comment #12 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Jiri Slaby from comment #11) > I don't remember, really. > > Is this bug still a bug? If so, feel free to reopen. Not sure. Meanwhile kernel-obs-build includes algif_hash and thus af_alg, but that wasn't enough to make libkcapi happy. There might still be some hack in libkcapi/gnutls builds? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c26 --- Comment #26 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #25) > (In reply to Cyril Hrubis from comment #24) > > Just for the record, this has been thoroughly discussed and in the end we > > decided to go with upstream per architecture defaults for CONFIG_HZ. The > > conclusion was that the upstream defaults perform well enough in benchmarks > > and on the top of that we are using the most tested and stable variants. > > origin/SUSE-2025:config/arm64/default:CONFIG_HZ_250=y > origin/SUSE-2025:config/ppc64le/default:CONFIG_HZ_100=y > origin/SUSE-2025:config/s390x/default:CONFIG_HZ_100=y > origin/SUSE-2025:config/s390x/zfcpdump:CONFIG_HZ_100=y > origin/SUSE-2025:config/x86_64/default:CONFIG_HZ_1000=y > > 1000, really? Yes, see the referenced jsc: commit 80f3e036d1d467a1db3db32c44e335da38072857 Author: Yousaf Kaukab <ykaukab(a)suse.de> Date: Wed Nov 27 14:32:00 2024 +0100 config: x86_64: change HZ to upstream default References: jsc#PED-11606 > origin/master:config/arm64/default:CONFIG_HZ_300=y > origin/master:config/armv6hl/default:CONFIG_HZ_300=y > origin/master:config/armv7hl/default:CONFIG_HZ_300=y > origin/master:config/i386/pae:CONFIG_HZ_300=y > origin/master:config/ppc64le/default:CONFIG_HZ_300=y > origin/master:config/riscv64/default:CONFIG_HZ_300=y > origin/master:config/s390x/default:CONFIG_HZ_300=y > origin/master:config/s390x/zfcpdump:CONFIG_HZ_300=y > origin/master:config/x86_64/default:CONFIG_HZ_300=y > > We seem we have switched master after all? I am going to unify master+stable to SUSE-2025 now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c25 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |--- Status|RESOLVED |REOPENED --- Comment #25 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Cyril Hrubis from comment #24) > Just for the record, this has been thoroughly discussed and in the end we > decided to go with upstream per architecture defaults for CONFIG_HZ. The > conclusion was that the upstream defaults perform well enough in benchmarks > and on the top of that we are using the most tested and stable variants. origin/SUSE-2025:config/arm64/default:CONFIG_HZ_250=y origin/SUSE-2025:config/ppc64le/default:CONFIG_HZ_100=y origin/SUSE-2025:config/s390x/default:CONFIG_HZ_100=y origin/SUSE-2025:config/s390x/zfcpdump:CONFIG_HZ_100=y origin/SUSE-2025:config/x86_64/default:CONFIG_HZ_1000=y 1000, really? origin/SUSE-2024:config/arm64/default:CONFIG_HZ_250=y origin/SUSE-2024:config/ppc64le/default:CONFIG_HZ_100=y origin/SUSE-2024:config/s390x/default:CONFIG_HZ_100=y origin/SUSE-2024:config/s390x/zfcpdump:CONFIG_HZ_100=y origin/SUSE-2024:config/x86_64/default:CONFIG_HZ_250=y This looks sane. origin/master:config/arm64/default:CONFIG_HZ_300=y origin/master:config/armv6hl/default:CONFIG_HZ_300=y origin/master:config/armv7hl/default:CONFIG_HZ_300=y origin/master:config/i386/pae:CONFIG_HZ_300=y origin/master:config/ppc64le/default:CONFIG_HZ_300=y origin/master:config/riscv64/default:CONFIG_HZ_300=y origin/master:config/s390x/default:CONFIG_HZ_300=y origin/master:config/s390x/zfcpdump:CONFIG_HZ_300=y origin/master:config/x86_64/default:CONFIG_HZ_300=y We seem we have switched master after all? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212877] [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 https://bugzilla.suse.com/show_bug.cgi?id=1212877#c26 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|REOPENED |RESOLVED --- Comment #26 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Zaoliang Luo from comment #25) > This issue persistent on Tumbleweed running on RPi4. > > What have you ever tried to find out why? Sorry, I don't have the device, nor I have enough knowledge about power management. > After a long time just close it now as resolved, I don't think this is not > acceptable. > Again, this is so easy to reproduce. You can just try with 'systemctl > suspend', at moment it behaves like a shutdown. Nice, but: > But it would make more sense to report and handle this upstream. Given it's a longstanding problem, it is an upstream issue, so this would be better addressed upstream. You will likely get more help and progress there than here. Having the bug open here won't help you much as was already demonstrated, sorry. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212877] [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 https://bugzilla.suse.com/show_bug.cgi?id=1212877#c25 Zaoliang Luo <zluo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #25 from Zaoliang Luo <zluo(a)suse.com> --- This issue persistent on Tumbleweed running on RPi4. What have you ever tried to find out why? After a long time just close it now as resolved, I don't think this is not acceptable. Again, this is so easy to reproduce. You can just try with 'systemctl suspend', at moment it behaves like a shutdown. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234055] Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Could you boot again the non-working kernel with the same debug boot options, and get the kernel messages that have been output during you try (and fail) xrandr manually? The log was huge, so I couldn't spot easily what was tested and failed... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215927] New: kernel-default-6.5.4 reboots instead of resuming from suspend
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215927 Bug ID: 1215927 Summary: kernel-default-6.5.4 reboots instead of resuming from suspend 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: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: mrmazda(a)earthlink.net Target Milestone: --- Found By: --- Blocker: --- I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. I always suspend my computer at night (with systemctl suspend) and wake it the next morning. With the new kernel, the computer always restarts instead of resuming from suspend. The problem does not occur with the old kernel. Interestingly, the problem is reproducible only when I leave the computer suspended overnight. Simply suspending the computer and then waking it a few seconds later does not trigger the bug. hwinfo output (with the old kernel) is available in Attachment 869836 of Bug 1215826. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1196438] Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1196438 https://bugzilla.suse.com/show_bug.cgi?id=1196438#c24 --- Comment #24 from Cyril Hrubis <chrubis(a)suse.com> --- Just for the record, this has been thoroughly discussed and in the end we decided to go with upstream per architecture defaults for CONFIG_HZ. The conclusion was that the upstream defaults perform well enough in benchmarks and on the top of that we are using the most tested and stable variants. -- You are receiving this mail because: You are the assignee for the bug.

1 0