December 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c13 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|amdgpu/nouveau: Monitor NO |amdgpu: Monitor NO signal |signal if it hasn't been on |if it hasn't been on since |since system boot |system boot --- Comment #13 from Stefan Dirsch <sndirsch(a)suse.com> --- Summary change is confusing. There is no nvidia GPU in this system any longer. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu/nouveau: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 Kourosh P. <kourosh(a)pourdanandeh.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|amdgpu: Monitor NO signal |amdgpu/nouveau: Monitor NO |if it hasn't been on since |signal if it hasn't been on |system boot |since system boot -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c12 --- Comment #12 from Kourosh P. <kourosh(a)pourdanandeh.com> --- I would like to add the following for reference: My original NEW system had an Nvidia GeForce 3070 GPU with the nouveau drivers, when I started experiencing this issue. Then I installed the Nvidia .run file thinking it might help but it didn't. When I contacted my PC store where I bought the system, Canada Computers, they were kind enough to swap the GPU for the current one, i.e. AMD Radeon RX 6800 (I was lucky that I purchased the extended warranty at the time of purchase). To summarize, I don't think it is ONLY amdgpu driver issue in my humble opinion. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

1 0

[Bug 1193091] Keyboard no longer working at console
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193091 https://bugzilla.suse.com/show_bug.cgi?id=1193091#c2 --- Comment #2 from Fred Blaise <fred.blaise(a)gmail.com> --- Hi, A usb keyboard indeed, a WASD to be exact, with the hardware switch in "mac" position. This is a tower style workstation. I am mentioning because I am now trying with another USB keyboard for the purpose of debugging with the same kernels as before and I can type... Thanks for the info for your repo, this can be definitely useful. I'll do some more tests and come back to you. That's all weird. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193286] Kernel panic after waking up laptop from sleep
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193286 https://bugzilla.suse.com/show_bug.cgi?id=1193286#c3 --- Comment #3 from Krystof Jelinek <krystof186(a)gmail.com> --- Sorry, I forgot to answer your question - the bug happens reliably after every "wake up call", but as described in my previous comment, I can't really put it to sleep now. Interestingly, right now the crash does not happen when I put the computer to sleep after the reboot / poweron, which is the only time I can put it to sleep right now (previous comment). It worked like this before I disabled swap as well, so I suppose that this is a session / desktop environment related problem? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193286] Kernel panic after waking up laptop from sleep
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193286 https://bugzilla.suse.com/show_bug.cgi?id=1193286#c2 --- Comment #2 from Krystof Jelinek <krystof186(a)gmail.com> --- Hi, this bug has occurred even on Leap 15.2, though not so often. As of right now, I have disabled swapfile in hope that it would help, since I read some articles saying that the kernel does not trust unencrypted swapfiles. The hibernation option is now gone, which does not bother me, however, I can now put my system to sleep only before anyone logs in - in other words, I can only put it to sleep right after a reboot / poweron. After anyone logs in, it just refuses to go to sleep - Plasma turns off normally, then the screen goes dark, and a blinking underscore in the top left corner of the terminal (vty7 I think?) stays there for +- 20 seconds. After that, the sddm login screen shows up and the KDE session does not get restored... it's the same with xfce, but it's session is restored. I am quite confused as to what is happening, and unluckily, I can't access any vty during the process described above. I think that I might be able to look into logs after logging in though, however I don't know where they are located. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193142] usb mouse and usb keyboard not recognized by sddm
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193142 https://bugzilla.suse.com/show_bug.cgi?id=1193142#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(jdd(a)dodin.org) | --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- This bug is basically identical as bug 1192569, but caused by the backport of the same commit. Now the fix is destined to SLE15-SP3 git branch, so that it'll be included in the next update kernel (possibly in January). If you still face the very same bug with the test kernel, please reopen. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193379] New: Kernel-5.3-18-59.34.1 crashes USB- and Bluetooth environment with IvyBox
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193379 Bug ID: 1193379 Summary: Kernel-5.3-18-59.34.1 crashes USB- and Bluetooth environment with IvyBox Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: maand(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started my Lenovo Thinkpad t450s with the Kernel-5.3-18-59.34.1 from the Suse Linux Enterprise 15 update repository. I could connect an USB stick to the Thinkpad and use Bluetooth without any issues. But once I connect an IvyBox to the Thinkpad the USB and the Bluetooth environment crashes. I was not able to connect any USB device to my notebook and no Bluetooth adapter will be found. I tried the same with a second kernel from this repository (5.3-18-59-27) and everything went fine. The IvyBox got connected. The same for the USB stick. The Bluetooth environment stayed available. I got a confirmation of another user, that his openSuSE 15.3 box behaved the same with the two different kernel releases. It looks like if there went something wrong within the creation of minor version 34 of the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1193142] usb mouse and usb keyboard not recognized by sddm
by bugzilla_noreply＠suse.com 04 Dec '21

04 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193142 https://bugzilla.suse.com/show_bug.cgi?id=1193142#c10 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maand(a)gmx.de --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1193379 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0