December 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1229042] New: Enable kernel-default-livepatch-devel for TW since it's already enabled on Leap
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229042 Bug ID: 1229042 Summary: Enable kernel-default-livepatch-devel for TW since it's already enabled on Leap 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: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Remove the condition that currently only applies to openSUSE Tumbleweed. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1234330] New: AMDGPU makes CPU stuck
by bugzilla_noreply＠suse.com 07 Jan '25

07 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234330 Bug ID: 1234330 Summary: AMDGPU makes CPU stuck 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: axel(a)hiq2.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently, my system regularly freezes completely. Sometimes, mouse movement becomes slow before, sometimes it freezes suddenly. After a reboot, I find the attached messages in the journal. Kernel version is 6.11.8-1-default. Hint: these logs have been collected during some days, updates regarding affected modules were installed in between. Carsh3.log is recent. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1234619] New: CPU reporting and using incorrect max freq
by bugzilla_noreply＠suse.com 05 Jan '25

05 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234619 Bug ID: 1234619 Summary: CPU reporting and using incorrect max freq Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ez2blost(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On an Intel i9-13900HX, /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq reports the same frequency as base_frequency. E.g., cat /sys/devices/system/cpu/cpu0/cpufreq/{base_frequency,cpuinfo_max_freq} 2200000 2200000 By default the maximum scaling frequency for performance is set to the cpuinfo_max_freq cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq 2200000 However the maximum frequency for cpu1 is 5400000 as can be seen if a higher valuer is written to scaling_max_freq: echo 10000000 >| /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq ; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 5400000 By default the cpu frequency never exceeds 2.2Ghz resulting in poor performance. A workaround is to set the maximum scaling frequency in the TLP configuration file (if tlp is used), e.g. Echo "CPU_SCALING_MAX_FREQ_ON_AC=5400000" >> /etc/tlp.d/50.local.conf This is partial fix because other software, such as NVIDIA power management features, can reset the scaling_max_frequency to cpuinfo_max_frequency, and cannot be enabled easily without a performance hit. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1234782] New: Kernel 6.12.6 with amdgpu breaks brightness control after resume
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234782 Bug ID: 1234782 Summary: Kernel 6.12.6 with amdgpu breaks brightness control after resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Given TW20241220 with kernel 6.12.6 and resuming after suspend, the display brightness starts to increase until reaching its maximum value, and then switches off (Thinkpad T14 with AMD Ryzen 7 PRO 4750U). Since kernel version 6.12.4 works fine, I suspect that this was introduced with 6.12.5 and is due to commit 99a02eab82515343d536796aa917dee50aec1551 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Mon Nov 25 13:59:09 2024 -0500 drm/amdgpu: rework resume handling for display (v2) commit 73dae652dcac776296890da215ee7dec357a1032 upstream. Split resume into a 3rd step to handle displays when DCC is enabled on DCN 4.0.1. Move display after the buffer funcs have been re-enabled so that the GPU will do the move and properly set the DCC metadata for DCN. v2: fix fence irq resume ordering -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1227749] New: Orange PI 5 Plus limited functionality
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227749 Bug ID: 1227749 Summary: Orange PI 5 Plus limited functionality Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876046 --> https://bugzilla.suse.com/attachment.cgi?id=876046&action=edit idbloader for Orange PI 5 Plus I managed to get U-Boot running on the Orange PI 5 Plus with a couple of key SUSE patches to the point where it is booting into OpenSUSE AARCH64 Rockchip version. Currently only the following are working: - PCIe - NVME - eMMC/SD - Serial port The following are not working: - USB - Realtek RTL8125 2.5G Ethernet drivers (seen on PCIe bus) - Realtek RTL8852BE (seen on PCIe bus, not driver seems to be available) Note that in U-Boot that USB also does not work and the network cards are not supported (as of 7/15). I am attaching my U-Boot and idbloader for this board which should allow it to boot, use the usual offset 64 for the idbloader and offset 16384 for U-Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Bug ID: 1222902 Summary: Monitor detection fails after hard reset 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: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a hard reset (laptop locked up when I tried to suspend it), my external monitors are no longer detected. I've seen this happen 3 times in as many weeks (on several recent versions of TW), and the only solution I've found is reinstalling TW. > sudo hwinfo --monitor 45: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.iVNqLoWlvi7 Parent ID: _Znp.TcrQYGYoBS2 Hardware Class: monitor Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0a7d Serial ID: "0" Resolution: 1920x1200@60Hz Size: 345x215 mm Year of Manufacture: 2021 Week of Manufacture: 27 Detailed Timings #0: Resolution: 1920x1200 Horizontal: 1920 1968 2000 2140 (+48 +80 +220) -hsync Vertical: 1200 1203 1209 1260 (+3 +9 +60) +vsync Frequencies: 161.79 MHz, 75.60 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1200 Vert. Sync Range: 40-60 Hz Hor. Sync Range: 76-76 kHz Bandwidth: 161 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (VGA compatible controller) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[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 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