March 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1184232] New: [Build 117.13] echo c > /proc/sysrq-trigger does not trigger reboot
by bugzilla_noreply＠suse.com 31 Mar '21

31 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184232 Bug ID: 1184232 Summary: [Build 117.13] echo c > /proc/sysrq-trigger does not trigger reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://openqa.opensuse.org/tests/1686014/modules/kdum p_and_crash/steps/43 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation kdump test seems to be invoking reboot however we're stuck at the the console. openQA test in scenario opensuse-15.3-DVD-aarch64-extra_tests_in_textmode@aarch64 fails in [kdump_and_crash](https://openqa.opensuse.org/tests/1686014/modules/kdump_an… ## Test suite description Maintainer: okurz(a)suse.de Mainly console extratest. ## Reproducible Fails since (at least) Build [32.4](https://openqa.opensuse.org/tests/1500092) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183525] [Build 102.1] frozen linuxrc at "kexec parameters" on aarch64
by bugzilla_noreply＠suse.com 31 Mar '21

31 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183525 http://bugzilla.opensuse.org/show_bug.cgi?id=1183525#c5 --- Comment #5 from Lubos Kocman <lubos.kocman(a)suse.com> --- Ideally this should be fixed before the RC deadline (24th April) or the bug should be set as soft fail. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183525] [Build 102.1] frozen linuxrc at "kexec parameters" on aarch64
by bugzilla_noreply＠suse.com 31 Mar '21

31 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183525 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 31 Mar '21

31 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c27 --- Comment #27 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extratest https://openqa.suse.de/tests/5672127 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1183825] When in graphical environment on RPI3, system goes down at when screen goes into powersave
by bugzilla_noreply＠suse.com 31 Mar '21

31 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183825 http://bugzilla.opensuse.org/show_bug.cgi?id=1183825#c3 --- Comment #3 from Ang <dillon.ang.h(a)gmail.com> --- After some tests, the last kernel where this works properly is kernel-default 5.9.14-1.1.gc648a46 from obs://build.opensuse.org/home:tiwai. This issue appears to affect both 5.10 and 5.11 kernels I have tested. I am running Tumbleweed snapshot 20210328. One thing of note is that this does not affect systems that boot up to the command line (no graphical environment), however in that situation there is no monitor power management or blanking enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184150] New: kernel-default-extra-5.3.18-51.2.x86_64 RPM install reports "Operation not permitted" errors
by bugzilla_noreply＠suse.com 30 Mar '21

30 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184150 Bug ID: 1184150 Summary: kernel-default-extra-5.3.18-51.2.x86_64 RPM install reports "Operation not permitted" errors Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mail(a)georg-pfuetzenreuter.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upon updating Leap 15.3 Alpha a new install of kernel-default-extra was offered. Installing it produces the following RPM output: (383/466) Installing: kernel-default-extra-5.3.18-51.2.x86_64 ...............................................................................[done] Additional rpm output: ln: failed to create symbolic link '/boot/vmlinuz': Operation not permitted ln: failed to create symbolic link '/boot/initrd': Operation not permitted -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1184002] Black screen on reboot
by bugzilla_noreply＠suse.com 30 Mar '21

30 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1184002 https://bugzilla.suse.com/show_bug.cgi?id=1184002#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Do you see that it happens at the booting, or at it exiting? The log doesn't show that, and without the log, it's impossible to debug, unfortunately. If it's only about the video driver, you can try to boot with nomodeset option. This will disable the native graphics support, hence you might have no GUI after boot, but at least you can test rebooting. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184002] Black screen on reboot
by bugzilla_noreply＠suse.com 30 Mar '21

30 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1184002 https://bugzilla.suse.com/show_bug.cgi?id=1184002#c9 --- Comment #9 from Dmitry Ivanov <Dmnik1(a)mail.ru> --- (In reply to Takashi Iwai from comment #8) > �� , �� "/ sbin / reboot -f" > (�� root), �� ? > > �� "/ sbin / poweroff -f" �� . The problem remains, the screen is black only during the reboot process. During the normal shutdown process, it turns off well -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183872] Regression: System hang when connecting HMDI with i915
by bugzilla_noreply＠suse.com 30 Mar '21

30 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183872 https://bugzilla.suse.com/show_bug.cgi?id=1183872#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Imnotgivingmy nametoamachine from comment #11) > (In reply to Takashi Iwai from comment #10) > > It's being rebuilt now. I didn't notice that the automatic update stopped > > working... > > Thank you very much Takashi! I tested with (drm-tip) > kernel-vanilla-5.12.rc4-2.1.ga3c6ee1 but sadly the bug was still present. > > I then went ahead and tested with kernel-vanilla-5.12.rc5-1.1.g5fe2d5c > because I notice it was available too, you know just to make sure the bug > was indeed still present and all... But the bug doesn't happen with > 5.12.rc5-vanilla... > > Just what the fuck? Was the bug really fixed in exactly the week I reported > the bug but without finding an useful log or call trace? And why the bug > didn't happened on ubuntu? To be honest despite the bug looking like it's > fixed on 5.12.rc5 it's now more annoying not knowing why or how it was fixed > haha > > I'm legit going to read all the commits between 5.12.rc4 and 5.12.rc5 > > That aside what should the status of this bug be? Is it "Resolved" as soon > as there is a patch coming up in a future stable version or it's Resolved > until that patch finally reaches a stable kernel in opensuse? You need to really make sure that it's fixed in 5.12-rc5 code itself. For example, 5.12-rc5 kernel you've tested also contains the kernel configuration change to make CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM=n. This might be the cause, too. And, if that's the case, you could work around in other kernels by passing snd_hda_codec_hdmi.enable_silent_stream=0 boot option, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183990] I think I found the cause of a kernel lock when attempting hibernation
by bugzilla_noreply＠suse.com 30 Mar '21

30 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183990 https://bugzilla.suse.com/show_bug.cgi?id=1183990#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- As already mentioned, the basic checks for debugging the PM issue is described in Documentation/power/basic-pm-debugging.rst or the web version of the same content https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html Could you perform those testing? -- You are receiving this mail because: You are the assignee for the bug.

1 0