September 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c39 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(teo8976(a)gmail.com | |) --- Comment #39 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to teo teo from comment #38) > > The fact that web browser doesn't open > > That's never happened to me. The browser (which is already open and I've > been using for a while) stops responding (meaning I'm unable to switch > between tabs, and/or close tabs, and/or scroll, and/or etc.), but when I > close it and relaunch it it opens immediately, and usually works for a > while. And the same with other applications. Well, that's what I meant -- the unstable behavior of the web browser (or whatever). > > When the problem happens, and when you unplug the USB Ethernet device (instead of power-off / reset), does the problem persist? > > Yes. And what if you logout and re-login? The problem persists? If it's a kernel problem, it should persist. Also it should persist on the another user, too. In anyway, we need a way to verify the buggy behavior with a more simpler application than web browser or those heavy & complex beast. If you can find some issue with a simple command-line application (just does some network access or anything), it can be used for analyzing better what's going on. Once after we find out a simpler test case, we can take a deeper look at the system level via performance monitoring or tracing. And another thing is to try solving the IRQ 9 problem. If you have no BIOS update available, at least try irqpoll boot option to see whether the error message is gone or not. -- 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 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c38 --- Comment #38 from teo teo <php4fan(a)gmail.com> --- > The fact that web browser doesn't open That's never happened to me. The browser (which is already open and I've been using for a while) stops responding (meaning I'm unable to switch between tabs, and/or close tabs, and/or scroll, and/or etc.), but when I close it and relaunch it it opens immediately, and usually works for a while. And the same with other applications. > When the problem happens, and when you unplug the USB Ethernet device (instead of power-off / reset), does the problem persist? Yes. -- 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 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c37 --- Comment #37 from Takashi Iwai <tiwai(a)suse.com> --- If the system is screwed up by the enablement of an Ethernet device, the possible cause is either too many (unhandled / handled) wild interrupts or memory corruption or such bug. Usually the latter should be visible in the kernel log as a kernel crash, while the former isn't always seen -- especially if the irq table is already suspicious (the dead irq 9 was reported). If the interrupts go crazy, everything can happen, no matter which I/O. The fact that web browser doesn't open implies that something is blocked, and it could be a network. I have no grasp how many bugs you already submitted and all smell really like the same cause. When the problem happens, and when you unplug the USB Ethernet device (instead of power-off / reset), does the problem persist? -- 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 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c36 teo teo <php4fan(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(teo8976(a)gmail.com | |) | --- Comment #36 from teo teo <php4fan(a)gmail.com> --- Note that the symptoms that I'm currently observing are those described in issue 1201557, not those described in this report. I comment here because that issue has been closed as duplicate of this one (see comment 26). > If the problem happens, can you check about the network reachability by some other command-line tool? I'm not sure what you mean by that. You want me to check whether the network is _reachable_ when the issue happens?? I can already tell you it definitely is. I have never observed network unreachability. But if you want me to run any test during the issue, just tell me the exact commands you want me to run (commands that I can copy and paste) and I'll post the output. Also note that the transition between "working state" and "broken state" is usually gradual. The system starts behaving erratically (usually in the form of random flickering within certain areas of the screen, and applications or part of their UI failing to respond to clicks and keyboard interaction) every once in a while, then more often, until it becomes so frequent that I have to reboot. I am very skeptical that this has anything to do with network at all. It is unclear whether it is triggered by using wired network (via a USB adapter). It certainly happens whether or not I use wired network, but I am under the impression that when I use wired network it occurs more often. If that is really the case, I suspect it might be related to USB rather than with the network itself. And I wonder if it has more to do with the GPU, as it usually starts with flickering. -- 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 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c35 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(teo8976(a)gmail.com | |) --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- Hmm, it still doesn't show any indication of such behavior from the kernel log *at all* (except for the IRQ 9 warning that was already found in the previous log). That said, from the kernel perspective, everything is still normal. I believe we need some more easier test case than heavy apps like Chrome or FF. If the problem happens, can you check about the network reachability by some other command-line tool? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202707] kernel-firmware-{amdgpu,radeon} update breaks VA-API: Incorrect video output on Radeon RX 6900 (Navi 21/CHIP_SIENNA_CICHLID)
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202707 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203087] New: kernel-default failed to enroll UEFI keys on Raspberry PI
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203087 Bug ID: 1203087 Summary: kernel-default failed to enroll UEFI keys on Raspberry PI Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Raspberry PI I get: Failed to enroll new keys Failed to import /etc/uefi/certs/1F673297.crt warning: %post(kernel-default-5.19.2-1.2.aarch64) scriptlet failed, exit status 255 ...........done] kernel-update aborts with an error, thus transactional-update throws the snapshot away. Update of MicroOS on aarch64 is not possible. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1201066] kernel upgrade fails with Failed to enroll new keys
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1201066 https://bugzilla.suse.com/show_bug.cgi?id=1201066#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk(a)suse.com --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1203087 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 1203081] New: the power source does not use a battery
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203081 Bug ID: 1203081 Summary: the power source does not use a battery 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: shukrullojon.dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in the battery status it is always shows charging when the power is not connected -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202707] kernel-firmware-{amdgpu,radeon} update breaks VA-API: Incorrect video output on Radeon RX 6900 (Navi 21/CHIP_SIENNA_CICHLID)
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202707 https://bugzilla.suse.com/show_bug.cgi?id=1202707#c34 --- Comment #34 from Takashi Iwai <tiwai(a)suse.com> --- Sure, let's wait until AMD people submitting the official update. -- You are receiving this mail because: You are the assignee for the bug.

1 0