March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c8 --- Comment #8 from Larry Finger <Larry.Finger(a)gmail.com> --- Those changes do not look as if anything critical was changed. Is it possible to see the script that openQA was testing? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c7 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger(a)suse.com Flags|needinfo? | --- Comment #7 from Dominique Leuenberger <dleuenberger(a)suse.com> --- Most recent qemu changes in Tumbleweed were: changes files: -------------- --- qemu.changes +++ qemu.changes @@ -1,0 +2,14 @@ +Wed Mar 22 09:29:52 UTC 2023 - Dario Faggioli <dfaggioli(a)suse.com> + +- Further fixes for bsc#1209546 +* Patches added: + test-vmstate-fix-bad-GTree-usage-use-aft.patch + +------------------------------------------------------------------- +Tue Mar 21 22:02:50 UTC 2023 - Dario Faggioli <dfaggioli(a)suse.com> + +- Fix bsc#1209546 +* Patches added: + qemu-osdep-Switch-position-of-extern-and.patch + +------------------------------------------------------------------- -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c6 Larry Finger <Larry.Finger(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. |needinfo? |org) | --- Comment #6 from Larry Finger <Larry.Finger(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > Which kernel is in question? I see no CONFIG_PROVE_LOCKING changes in our > kernels at all. According to the logging from openQA, the kernel in question is 6.2.8-1-default #1 openSUSE Tumbleweed 3fa4abf6558707e35b8fd19fc1aa28b27d42fa When I run 6.2.8-1-default from the TW repos, VirtualBox works correctly with no errors. I have determined that the problems with CONFIG_PROVE_LOCKING are present in VirtualBox 6.1.42, and predate our recent changes in the locking that were needed to improve long-term stability on hosts with many processors and many guests where the graphics was broken, but the underlying guest OS could still be accessed via SSH. I see that the test in question was started with QEMU. Has it or KVM been changed resently? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209805] Kernel regression: Possible integer underflow in input pipeline of ThinkPad trackpoint.
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209805 http://bugzilla.opensuse.org/show_bug.cgi?id=1209805#c18 Honza Nijak� <honzikcernoh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(honzikcernoh@gmai | |l.com) | --- Comment #18 from Honza Nijak� <honzikcernoh(a)gmail.com> --- Sorry for the delay, was AFK, but the kernel you provided fixed the issue, thank you very much! -- 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 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michael Hirmke from comment #19) > (In reply to Takashi Iwai from comment #18) > > (In reply to Michael Hirmke from comment #17) > > > All USB keyboards and mice are affected. > > > > Do I understand correctly that, when you login via sddm, all USB keyboards > > and mouses don't work, no matter how many keyboards / mouses are connected? > > And, if you reconnect one of them, do they all start working? Or it's only > > the reconnected one? > > No, there is alway only one mouse and one keyboard connected, but I tried 3 > different keyboards and 2 different mice - and all of them show the same > behaviour. So, if you connect two USB keyboards, both are gone? Also, it happens no matter which port is used? I guess both yes, but such a thing is worth to test. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- Just run "hwinfo > hwinfo.txt" as root or such would be enough. Ditto for dmesg. This is the very starting point to see what hardware components are included. The debug of suspend/resume is often really tough, unfortunately, as it can't be done remotely and it can't leave useful debug info in many cases (because the device itself is suspended when something happens, hence you can't record it). If we are lucky, it's a crash and leaves some kernel Oops, etc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c19 --- Comment #19 from Fritz Hudnut <non.space.1(a)gmail.com> --- (In reply to Takashi Iwai from comment #18) > Well, the request was the hwinfo program output and the dmesg program output > from openSUSE installations. Sure. I'm just booted in Sid today, so I was checking the command out there, which didn't seem "applicable" or installed. So I'm going to run #hwinfo or something like #cat hwinfo >hwinfo.log.txt ???? Or, something more "granular" in the hwinfo output?? I don't mess around "under the hood" so I'm looking for specific commands to run to provide the info you are looking for? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c5 --- Comment #5 from Larry Finger <Larry.Finger(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > Which kernel is in question? I see no CONFIG_PROVE_LOCKING changes in our > kernels at all. I did not see the problem until I turned on that configuration variable, thus I thought that was the problem. I will take another look. -- 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 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c19 --- Comment #19 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Takashi Iwai from comment #18) > (In reply to Michael Hirmke from comment #17) > > All USB keyboards and mice are affected. > > Do I understand correctly that, when you login via sddm, all USB keyboards > and mouses don't work, no matter how many keyboards / mouses are connected? > And, if you reconnect one of them, do they all start working? Or it's only > the reconnected one? No, there is alway only one mouse and one keyboard connected, but I tried 3 different keyboards and 2 different mice - and all of them show the same behaviour. And as described in https://bugzilla.suse.com/show_bug.cgi?id=1200983#c9 it has prpbably nothing to do with sddm, because the linux console is also affected - not for the mouse, but for the keyboard. > > > And yes, Iit is possible to access the machine via ssh. > > What exactly do you want me to check then? > > At the moment you have no input control after SDDM login, login via ssh. > Then get the dmesg output at first. You can get the hwinfo output at this > moment, too. It happens in a linux console, too. > > Run evtest as root and check whether the corresponding input device appears > there, and test whether the input reacts. > > If the input still doesn't work on the screen, reconnect. And confirm that > it's working, then get the dmesg output and hwinfo output. Ok. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Well, the request was the hwinfo program output and the dmesg program output from openSUSE installations. -- You are receiving this mail because: You are the assignee for the bug.

1 0