October 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 16 Oct '20

16 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177707 http://bugzilla.opensuse.org/show_bug.cgi?id=1177707#c14 --- Comment #14 from teo teo <teo8976(a)gmail.com> --- Is it any of these? kernel-firmware-platform (20201005-3.1) kernel-firmware-radeon (20201005-3.1) ucode-amd (20201005-3.1) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177770] Most available resolutions on laptop display don't work (black screen)
by bugzilla_noreply＠suse.com 16 Oct '20

16 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177770 http://bugzilla.opensuse.org/show_bug.cgi?id=1177770#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Let us know which commits to be backported. We have no hardware to test, so it's hard to judge in our side, unfortunately. Other than that, using the kernel in Kernel:stable would be the best option, so far, for a case like this to support a new hardware. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177707 http://bugzilla.opensuse.org/show_bug.cgi?id=1177707#c13 Felix Miata (offline until ???) <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda(a)earthlink.net Whiteboard| |AMD --- Comment #13 from Felix Miata (offline until ???) <mrmazda(a)earthlink.net> --- Apparently not an issue for all AMD APUs/GPUs on UEFI (e.g. gcn 2nd gen): # inxi -SGMIay System: Host: ara88 Kernel: 5.8.14-1-default x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1440x900@60 drm.debug=0x1e log_buf_len=1M 3 Desktop: Trinity R14.0.8 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: TDM Distro: openSUSE Tumbleweed 20201012 Machine: Type: Desktop Mobo: ASRock model: FM2A88X Extreme6+ serial: E80-38024200616 UEFI: American Megatrends v: P4.20 date: 01/13/2016 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon bus ID: 00:01.0 chip ID: 1002:1313 Display: x11 server: X.Org 1.20.9 driver: amdgpu unloaded: fbdev,modesetting,vesa alternate: ati display ID: :0 screens: 1 Screen-1: 0 s-res: 2560x2520 s-dpi: 120 s-size: 541x533mm (21.3x21.0") s-diag: 759mm (29.9") Monitor-1: DisplayPort-0 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2") diag: 686mm (27") Monitor-2: HDMI-A-0 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2") diag: 730mm (28.8") OpenGL: renderer: AMD KAVERI (DRM 3.38.0 5.8.14-1-default LLVM 10.0.1) v: 4.6 Mesa 20.1.8 direct render: Yes Info:...running in: konsole inxi: 3.1.07 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177770] Most available resolutions on laptop display don't work (black screen)
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177770 http://bugzilla.opensuse.org/show_bug.cgi?id=1177770#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Yeah. It's a rather new GPU and the support in newer Kernels (5.8 on TW) is much better than with Leap 15.2 Kernel (5.3). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177707 http://bugzilla.opensuse.org/show_bug.cgi?id=1177707#c12 --- Comment #12 from teo teo <teo8976(a)gmail.com> --- > How do I upgrade it now? (or hasn't it be released yet?) Also, if I download a Tumbleweed ISO now (on a USB stick) and re-install it from scratch, will it have the new supposedly-fixed version? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177707 http://bugzilla.opensuse.org/show_bug.cgi?id=1177707#c11 --- Comment #11 from teo teo <teo8976(a)gmail.com> --- > Please reopen if you encounter the same problem again after upgrading the > kernel-firmware package at the next time How do I upgrade it now? (or hasn't it be released yet?) Once upgraded, how do I check that I have the right version? > regarding the breakage by the firmware updates in general; there is no > proper way to fix this other than the rollback What is the rollback? > In theory, you can save the former initrd manually before the update Is there a step-by-step guide of how to do that, and how to used the whatever-it-is-you-save to restore the working system? > I proposed such a failsafe stuff once ago, but it was declined because... Then you MUST do the following: Whenever an update this risky is about to be installed, you should: - give a gigantic warning that the system may be rendered unbootable (at least I know I wait until next weekend before I install the pending updates), - allow to hold that update but install the other ones (I guess the update manager widget already allows you to do that with any updates, but it kept crashing, see bug 1177556) - together with the abovementioned warning, give a link to the abover-mentioned guide. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1174278] New: kernel-firmware-amdgpu 20200702 breaks video on Raven Ridge
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174278 Bug ID: 1174278 Summary: kernel-firmware-amdgpu 20200702 breaks video on Raven Ridge 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: adam.reichold(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 839828 --> http://bugzilla.opensuse.org/attachment.cgi?id=839828&action=edit GZippped output of YaST's hardware information module Update kernel-firmware-amdgpu from 20200610-1.1 to 20200702-1.1 breaks video on a HP ProBook 455R G6 containing an AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, i.e. AMD Raven Ridge. The problem manifests itself as a blank screen when the boot splash would be displayed and continuously spinning system fan. The machine is unresponsive when reaching this state, i.e. escape and sysrq keys are not working. Downgrading just the kernel-firwmare-amdgpu packages works around the issue. There is one kernel log message only visible with the new firmware: kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-110). -- You are receiving this mail because: You are the assignee for the bug.

1 17

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177707 https://bugzilla.suse.com/show_bug.cgi?id=1177707#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- BTW, regarding the breakage by the firmware updates in general; there is no proper way to fix this other than the rollback. In theory, you can save the former initrd manually before the update, but such a mechanism isn't implemented in the package level. I proposed such a failsafe stuff once ago, but it was declined because of the dead resource usages and danger to occupy the previous /boot partition size. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177707 https://bugzilla.suse.com/show_bug.cgi?id=1177707#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- The very latest kernel-firmware package should work now as-is, since we switched to symlinks instead of hardlinks. Please reopen if you encounter the same problem again after upgrading the kernel-firmware package at the next time. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177707] Zypper dup completely bricked my computer, can't boot
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177707 https://bugzilla.suse.com/show_bug.cgi?id=1177707#c8 teo teo <teo8976(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(teo8976(a)gmail.com | |) | --- Comment #8 from teo teo <teo8976(a)gmail.com> --- Sorry (not my fault actually) but the comment was submitted before I finished writing (I went to edit a typo in the subject of the issue, and that submitted the unfinished comment too). What I meant to ask was: how do I prevent the next updates from installing the broken amdgpu driver or whatever it is again, and ensure the working one is kept? Obviously I don't want to hold all system updates of everything, and remain stuck forever with today's version of every software on my system. -- You are receiving this mail because: You are the assignee for the bug.

1 0