March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1208728] Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208728 https://bugzilla.suse.com/show_bug.cgi?id=1208728#c10 --- Comment #10 from Victor Fugazzotto <victorfuga(a)gmail.com> --- Wasn't sure where to take it next, I have opened https://bugzilla.kernel.org/show_bug.cgi?id=217262 now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209526] WOL not working with RTL8111/8168/8411 with 6.2.x kernel
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209526 https://bugzilla.suse.com/show_bug.cgi?id=1209526#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Juha Virtanen from comment #12) > (In reply to Takashi Iwai from comment #11) > > At best, could you join to the upstream bugzilla and comment there directly? > > So far I haven't had any facts to comment upstream. For example yesterday's > test: I had no knowledge, were I testing patch in > https://bugzilla.kernel.org/show_bug.cgi?id=217069#c33 or something else. I > just can't guess and comment based on guessing. You can write your test result directly there instead of answering here. In anyway, I'm building yet another test kernel from the patch of https://bugzilla.kernel.org/show_bug.cgi?id=217069#c40 in OBS home:tiwai:bsc1209526-4 repo. Please give it a try later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209296] Missing backlight control on Dell Vostro 3700
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209296 https://bugzilla.suse.com/show_bug.cgi?id=1209296#c19 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(eh(a)eggbird.eu) --- Comment #19 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Now I'm building a test kernel with the fix patch in OBS home:tiwai:bsc1209296 repo. Could you check it later? Once after confirmation, I'll merge the fix to TW kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209296] Missing backlight control on Dell Vostro 3700
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209296 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://gitlab.freedesktop. | |org/drm/nouveau/-/issues/20 | |2 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c14 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Group|novellonly | Flags|needinfo?(fvogt(a)suse.com) | --- Comment #14 from Fabian Vogt <fvogt(a)suse.com> --- FWICT this bug doesn't need to be restricted, I made it public now. (In reply to Petr Vorel from comment #13) > (In reply to WEI GAO from comment #12) > > kernel config has CONFIG_EXFAT_FS=m but you can not find exfat related > > modules installed so running system actually not support exfat, that's why > > LTP case failed on fsopen(exfat) > > @fvogt Are we OK that exfat works with just FUSE? Shouldn't be exfat kernel > driver also in kernel-default-base? IMO yes. I opened https://build.opensuse.org/request/show/1075034 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c13 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS CC| |fvogt(a)suse.com Flags| |needinfo?(fvogt(a)suse.com) --- Comment #13 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to WEI GAO from comment #12) > kernel config has CONFIG_EXFAT_FS=m but you can not find exfat related > modules installed so running system actually not support exfat, that's why > LTP case failed on fsopen(exfat) @fvogt Are we OK that exfat works with just FUSE? Shouldn't be exfat kernel driver also in kernel-default-base? > For LTP side, should we also need some fix? Since current LTP case still > think exfat is support on system but actually not. There are many LTP tests which use exfat, but mostly via FUSE (userspace driver). You're right, fsconfig is special, because it works with kernel driver, not with FUSE. fsconfig03.c:38: TBROK: fsopen() failed: ENODEV (19) First I thought there should be check for ENODEV and TCONF in that case, but in the end the problem is with FUSE. Patch sent. https://patchwork.ozlabs.org/project/ltp/patch/20230328144031.791212-1-pvor… -- 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 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c9 --- Comment #9 from Petr Vorel <petr.vorel(a)suse.com> --- (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/ -- 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 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206084 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1192211 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209296] Missing backlight control on Dell Vostro 3700
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209296 https://bugzilla.suse.com/show_bug.cgi?id=1209296#c18 --- Comment #18 from Egbert van der Haring <eh(a)eggbird.eu> --- At nouveau the bug is is reported here: https://gitlab.freedesktop.org/drm/nouveau/-/issues/202#note_1840116 And there is already a patch, here: https://lore.kernel.org/dri-devel/20230326205433.36485-1-hdegoede@redhat.co… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michael Hirmke from comment #14) > (In reply to Takashi Iwai from comment #13) > > (In reply to Michael Hirmke from comment #12) > > > (In reply to Stefan Dirsch from comment #10) > > > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > > > a bit complicated to figure out the right device. So I only wanted to > > > > mention keyboard here. > > > > > > Keyboard and mouse both have problems one the console, too. > > > The keyboard vanishes after a few seconds and returns, as soon as a key is > > > pressed, but the first keypress is not shown. The mouse never works on the > > > console - no events are shown. > > > > What do you mean "vanishes" here? It means that the /dev/input/event* device > > is gone? > > no, there is no mouse pointer and the keyboard light is off. > > > > > The point to check here is whether the device file persists and can > > read/write from a user-space (no matter whether it's processed or not). Or > > is the (USB?) audio device itself disappears and reappears automatically. > > Because the keyboard also has problems, this isn't easy to debug. > What exactly would you like me to test? If you have two USB keyboards, you can check it if a problem happens only a single one or on both. Also, if you can access remotely e.g. via ssh, it can be checked without interrupting the input device status, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0