February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1182762] uvcvideo: webcam stops working after 3 seconds
by bugzilla_noreply＠suse.com 25 Feb '22

25 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1182762 https://bugzilla.suse.com/show_bug.cgi?id=1182762#c6 --- Comment #6 from Miroslav Bene�� <mbenes(a)suse.com> --- Ok. And could you try using Takashi's repositories, please? It would be really great to know if v5.11 worked for you and this is a regression again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196481] synaptics touchpad doesn't work in wayland session
by bugzilla_noreply＠suse.com 25 Feb '22

25 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196481 https://bugzilla.suse.com/show_bug.cgi?id=1196481#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Please give hwinfo output and the full dmesg output. And, install evtest package, run it, and check whether the corresponding (raw) kernel input device generates proper events. I guess this should work, as you mentioned the device is working on X11. If so, the problem is rather libinput and/or KDE/Wayland. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196481] synaptics touchpad doesn't work in wayland session
by bugzilla_noreply＠suse.com 25 Feb '22

25 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196481 https://bugzilla.suse.com/show_bug.cgi?id=1196481#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Workspace (Plasma) |Kernel Assignee|opensuse-kde-bugs@opensuse. |kernel-bugs(a)opensuse.org |org | --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- Ok, so most likely a driver issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 25 Feb '22

25 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196104 https://bugzilla.suse.com/show_bug.cgi?id=1196104#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- If the kdump succeeded, it should have been saved under /var/crash. Take a look at there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193889] [Build 20211215] openQA test fails in reconnect_mgmt_console because yast.ssh can not restart the operating system
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193889 http://bugzilla.opensuse.org/show_bug.cgi?id=1193889#c55 --- Comment #55 from Mark Post <mpost(a)suse.com> --- Hmm. I don't know if this means anything, but I installed s390-tools-2.19.0-3.1 from openSUSE:Factory:zSystems, and read_values now works as expected. I would pursue this further, but first I would need to know how to get my hands on all the various debuginfo and debugsource RPMs for things like s390-tools, qclib, glibc, etc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193889] [Build 20211215] openQA test fails in reconnect_mgmt_console because yast.ssh can not restart the operating system
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1193889 https://bugzilla.suse.com/show_bug.cgi?id=1193889#c54 --- Comment #54 from Mark Post <mpost(a)suse.com> --- I think I've figured out what the problem is, although not its cause. It appears that the guest is not bringing up the enc800 interface. It seems that NetworkManager is having issues. This may because NetworkManager is trying to use dhclient to get an IP address for the interface, instead of setting a static IP and route. I have no idea why this might be happening, but perhaps someone else will. So, over to the NetworkManager people to figure this out. In the meantime, the problem with read_values is puzzling, but not contributing to this problem. I will keep looking at it, however, since rebuilding it from source on the system under test results in a working binary. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c7 --- Comment #7 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- I did a normal reboot with kdump in yast disabled. After that, I triggered the dump with this command. After a while the system reboots. Where do I get the dump? Is it necessary to enable kdump in Yast before this action? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Try to trigger a crash dump manually at first to check whether it's working or not. After booting normally, run the following on a terminal as root: echo c > /proc/sysrq-trigger This will trigger the crash dump, and if everything is fine, it should reboot and you get the crash dump. If this doesn't work, something is still missing (or broken :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196465] New: [Build 20220223] openQA test fails in LTP waitid10
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196465 Bug ID: 1196465 Summary: [Build 20220223] openQA test fails in LTP waitid10 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2207703/modules/wait id10/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD24G fails in [waitid10](https://openqa.opensuse.org/tests/2207703/modules/waitid10/steps/… Error log: waitid10.c:34: TPASS: waitid(P_ALL, 0, infop, WEXITED) passed waitid10.c:35: TPASS: infop->si_pid == pidchild (13793) waitid10.c:36: TFAIL: infop->si_status (0) != SIGFPE (8) waitid10.c:37: TPASS: infop->si_signo == SIGCHLD (17) waitid10.c:40: TFAIL: infop->si_code (1) != CLD_DUMPED (3) Failed. Test took approximately 0.0340682910027681 seconds Some test output could not be parsed: 8 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20220221](https://openqa.opensuse.org/tests/2203118) ## Expected result Last good: [20220219](https://openqa.opensuse.org/tests/2199472) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c5 --- Comment #5 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- I tried so set up kdump with yast. I just enabled kdump, no other changings there. After that a reboot was required, then I edited grub. I have seen, that a crashkernel was added, than I added additional no_console_suspend and boot with F10. Suspended the system, power LEDs are flashing. Up to this time everything was as usual. The system did not start by pressing the power button, but by pressing a key. The power LED is permanently on, but in contrast to my testings before the crashkernel, the mouse cursor did not appear. Like before I had to power off the system in a hard way, because the system did not react to any of my actions like pressing the power button shortly nor changing to a terminal with <Alt>+<F1...F8>. The directory for the crash dump (/var/crash) stayed empty, but I got panic-records both in journal and in /var/log/messages. I can see there the point when the system got suspended and resumed some minutes later with a black screen. Is it necessary to adjust kdump, and what information exactly do you need? -- You are receiving this mail because: You are the assignee for the bug.

1 0