August 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1201995] Intel Tigerlake: Mostly black screen with X.Org without nomodeset
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201995 http://bugzilla.opensuse.org/show_bug.cgi?id=1201995#c26 --- Comment #26 from Joachim Banzhaf <joachim.banzhaf(a)googlemail.com> --- (In reply to Joachim Banzhaf from comment #24) > What is this "panel self refresh" good for? found it. https://www.kernel.org/doc/html/v4.11/gpu/i915.html#panel-self-refresh-psr-… so the question changes to: can it be fixed and are there plans to fix it? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200989] New: system crash on simultaneous power-on of two monitors
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200989 Bug ID: 1200989 Summary: system crash on simultaneous power-on of two monitors Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I had this already with 15.3, now tried again with 15.4 ... I have this PN50 with two monitors attached, it is always on but I power off the monitors in the evening and turn them on when I get to the system in the morning. If I turn on one monitor, wait for a picture and then turn on the second one, all is fine. If I turn on both at the same time the system freezes completely, does not even ping anymore. AMD Ryzen 7 4800U, AMD Renoir GPU, 2 LG 27 UHD monitors. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1201859] TW 20220719: Running windows in a VM randomly crashes the e1000 driver
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201859 http://bugzilla.opensuse.org/show_bug.cgi?id=1201859#c20 Mathias Homann <Mathias.Homann(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Mathias.Homann@op | |ensuse.org) | --- Comment #20 from Mathias Homann <Mathias.Homann(a)opensuse.org> --- (In reply to Mathias Homann from comment #19) > (In reply to Dario Faggioli from comment #16) > > > Mathias, I know it could be a bit of a problem, since Tumbleweed moves fast, > > but I think that if you'd be able to figure out which one was the latest > > kernel that worked well, and hence the first one where this starts to fail, > > that might help quite a bit pinpointing what could be causing this... > > I just rolled back to 20220714 which has kernel 5.18.9-1, and tried to > reproduce the circumstances for that crash, and it did not happen. > > So my vague guess is that whatever makes this crash happen is somewhere in > the differences between 5.18.9 and 5.18.11 and later. I just ran another test on 5.18.9 with TSO, GRO and SG explicitely enabled in the networkmanager settings for that interface - no crash with that either. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184817] System becomes unstable and unusable when using wired network
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184817 http://bugzilla.opensuse.org/show_bug.cgi?id=1184817#c21 --- Comment #21 from teo teo <php4fan(a)gmail.com> --- IF it is true that 1184817 is a duplicate of this issue, and that's a big if, it means that this has nothing to do with wired ethernet network after all. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201557] Whole system has become generally unstable, basically unusable lately
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201557 http://bugzilla.opensuse.org/show_bug.cgi?id=1201557#c10 --- Comment #10 from teo teo <php4fan(a)gmail.com> --- > I see nothing to distinguish this from bug 1184817 I see a couple of things that might: 1) 1184817 seemed to systematically go away when using wifi network and reappear when using wired network. This one persists regardless. This one clearly has nothing to do with wired network. I have disconnected the USB-to-ethernet adapter entirely, and I'm still suffering from the issue. 1) the symptoms are different. That one usually started with lack of response to keyboard and mouse actions. There was never any flickering nor instances of different pieces of the screen being inconsistent with each other. This one usually starts with random flickering of parts of the screen, then parts of the screen apparently failing to update, or "blinking" between displaying current and random previous content. When stuff starts to stop responding entirely, I actually wonder whether "behind the screen" applications are actually responding and doing their job but the display is just not updating. I haven't been able to test and either confirm or discard that hypothesis, because it's very hard to tell, and in order to do that you would have to be able to interact "blindly" with applications without any visual feedback. I'm not good at that. Having said that, it's _possible_ that they are the same bug, but it would mean that: - when I repeatedly tested stopping using ethernet and using it again, it was a complete coincidence that 1184817 seemed to go away when not using ethernet, while it was infact completely random - the symptoms changed pretty drammatically and overnight for some reason (or have always been random and by pure chance I have lately been observing different variations of them). All that seems unlikely, although not impossible. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201859] TW 20220719: Running windows in a VM randomly crashes the e1000 driver
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201859 http://bugzilla.opensuse.org/show_bug.cgi?id=1201859#c19 Mathias Homann <Mathias.Homann(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mkubecek(a)suse.com | |) | --- Comment #19 from Mathias Homann <Mathias.Homann(a)opensuse.org> --- (In reply to Dario Faggioli from comment #16) > Mathias, I know it could be a bit of a problem, since Tumbleweed moves fast, > but I think that if you'd be able to figure out which one was the latest > kernel that worked well, and hence the first one where this starts to fail, > that might help quite a bit pinpointing what could be causing this... I just rolled back to 20220714 which has kernel 5.18.9-1, and tried to reproduce the circumstances for that crash, and it did not happen. So my vague guess is that whatever makes this crash happen is somewhere in the differences between 5.18.9 and 5.18.11 and later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201557] Whole system has become generally unstable, basically unusable lately
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201557 http://bugzilla.opensuse.org/show_bug.cgi?id=1201557#c9 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #9 from Felix Miata <mrmazda(a)earthlink.net> --- I see nothing to distinguish this from bug 1184817 *** This bug has been marked as a duplicate of bug 1184817 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184817] System becomes unstable and unusable when using wired network
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184817 http://bugzilla.opensuse.org/show_bug.cgi?id=1184817#c20 --- Comment #20 from Felix Miata <mrmazda(a)earthlink.net> --- *** Bug 1201557 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201859] TW 20220719: Running windows in a VM randomly crashes the e1000 driver
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201859 http://bugzilla.opensuse.org/show_bug.cgi?id=1201859#c18 --- Comment #18 from Mathias Homann <Mathias.Homann(a)opensuse.org> --- A little in-between update: TW 20220731, kernel 5.18.12-1, tso, gro, tso and sg on: e1000e still crashing the same way. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201557] Whole system has become generally unstable, basically unusable lately
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201557 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0